Month end, and every site counts differently
Each clinic manager sends in a spreadsheet: consultations, cycles started, enquiries, storage patients, revenue. One site counts a new patient at enquiry, another at first consultation. A satellite that does scans only reports scans but not which main clinic the patient belongs to. The operations director spends days reconciling before the board pack is ready, and the numbers still spark arguments.
Why group reporting is so hard
- Sites may use different clinic management systems or different setups of the same one.
- Definitions differ between sites.
- Satellites and main clinics share patients, so counts overlap.
- Finance data sits in separate accounts files.
- Reports are assembled by hand, so they arrive late and cannot be drilled into.
Groups that have grown by acquisition feel this most. Each clinic arrived with its own system, its own habits and its own spreadsheet. Replacing every system at once is rarely sensible, so for years the group has to report across systems that were never designed to agree.
What it costs
Senior staff time goes on reconciliation. Decisions wait for the report. Disagreements about numbers take the place of discussion about what to do. Problems at one site can go unnoticed until they are large.
| Measure | Site spreadsheets | Reporting layer |
|---|---|---|
| New patients | Each site's own definition | One agreed definition |
| Satellite activity | Reported separately | Linked to the patient's main clinic |
| Enquiries | Often missing | From the enquiry system |
| Revenue | Separate accounts | Combined, by site |
There is a quieter cost too. When each site produces its own figures, site managers spend their own time on spreadsheets every month, and the group loses the chance to compare like with like. A satellite that looks quiet may simply be counting differently.
How we build it
- We agree definitions with your operations and finance leads for each measure.
- We connect to each site's systems through reporting databases, APIs or scheduled exports, and to your accounts system.
- Data is loaded into a central store, cleaned and matched, so shared patients are counted once.
- Dashboards in a tool such as Power BI or a custom web page show the same measures for every site, with drill-down.
- Data quality checks flag sites whose data looks incomplete.
- The monthly pack is generated from the same data.
We report operational and financial measures. We do not produce or publish clinical outcome figures.
Where sites record the same thing in different ways, we build mapping tables rather than forcing an immediate change in how each clinic works. A site calling something a 'new patient consultation' and another calling it a 'first appointment' can both be counted under one agreed measure, and the mapping is visible so anyone can check it.
Access follows your structure. Site managers see their own clinic in full and the group in summary, directors see everything, and finance sees revenue and debtors. Patient-level detail is only visible to people who already have access to it in the source systems.
What managers get
The same numbers, defined the same way, for every site, available when needed. The operations director reviews rather than reconciles. Site managers see their own figures alongside the group's.
Because the dashboards update from the source systems, a manager can spot a drop in enquiries or a growing backlog at one site during the month, not after it. Site managers can also compare how their clinic runs against others in the group using measures they have all agreed, which makes those conversations more useful.
Does this sound familiar?
- Month-end reports are built from site spreadsheets.
- Sites define measures differently.
- Satellite activity is hard to attribute.
- The board pack takes days to assemble.
- Numbers are argued over rather than acted on.