Why a Single-Clinic Dashboard Stops Working Once You Add a Second Site
A single-clinic dashboard is a solved problem: one calendar, one till, one team, one number for each metric. Add a second site and the same dashboard becomes misleading rather than simply incomplete. Is a 15% drop in appointment volume this month a group-wide problem, or is it fully explained by the branch that opened eight weeks ago and has not built up a client base yet? A raw total cannot tell you that on its own.
The groups that struggle most with reporting are usually the ones that grew organically rather than by design — a second location got bolted onto the first clinic's spreadsheet, then a third onto that, and by the time there are four or five sites nobody fully trusts the combined numbers, because everyone knows at least one branch is logging things slightly differently to the rest.
The Metrics That Actually Belong on a Group-Level Dashboard
Per-clinic financial and clinical figures matter, but a group dashboard needs to answer a different question than a single-clinic one: not "how did we do", but "which site needs my attention this week, and why". That means every metric has to exist at two levels — per site, and rolled up — with the ability to move between them in one click.
- Revenue per site, shown against that same site's prior month and prior year — never just this month's figure sitting on its own
- Appointment utilisation per site and per vet, so a quiet week at one branch does not disappear inside a busy group-wide average
- No-show and late-cancellation rate per site — this varies far more by location than most owners expect, driven by things like local transport links and client demographics
- Average transaction value per site, to catch a branch seeing plenty of patients but converting that into less revenue per visit than the rest of the group
- Recall and retention rate per site — a struggling branch usually shows up here months before it shows up in the revenue line
- Staff cost as a percentage of revenue per site, to compare operational efficiency rather than just raw size
Normalise Before You Compare
Comparing raw revenue between a two-vet branch and a six-vet branch tells you almost nothing useful — of course the bigger site brings in more money. The comparison that matters is revenue per vet, per chair, or per FTE, because that is what actually reveals whether a site is performing well relative to its size, not just its scale.
New sites need the same treatment in reverse. A branch in its first three to six months is still building a client base and will drag down group averages if it is blended in with established sites on day one. Most groups handle this by excluding new sites from the "group average" view for a defined ramp-up period, while still tracking them individually so nobody loses visibility.
One thing worth building in from the start: RCVS record-keeping obligations apply per site, not just to the group as a whole, so it is worth tracking record completion and retention as its own metric per clinic rather than assuming that because head office is compliant, every branch automatically is too.
Common Mistakes Groups Make Building Their First Dashboard
Most of the pain in group reporting comes from a small set of avoidable habits, repeated every month.
- Comparing branches by raw revenue instead of per-vet or per-chair output
- Reviewing the dashboard monthly instead of weekly, so problems are three or four weeks old before anyone reacts to them
- Averaging a brand-new site's ramp-up months into the group total, dragging down a number that was never a fair comparison to begin with
- Assembling the dashboard by hand from five separate exports every month — by the time it is finished, the data is already stale
- No named owner for the dashboard — everyone on the leadership team receives the report, but nobody is actually responsible for acting on what it shows
What a Well-Built Group Dashboard Looks Like Day to Day
In practice, the groups that get the most value out of their reporting are not the ones with the most metrics — they are the ones with the clearest drill-down path. A group summary view shows the headline numbers across every site at a glance. Clicking into a site shows that clinic's detail. Clicking into a provider shows their individual performance. Three levels, one consistent structure, no separate spreadsheet for each layer.
The other habit worth adopting is reviewing this weekly rather than monthly, even if only for fifteen minutes. A no-show rate creeping up at one branch, or a provider's utilisation quietly slipping, is a five-minute fix if you catch it in week one and a much bigger conversation if it surfaces for the first time in a month-end report.
How VettoCRM Supports Multi-Site Group Reporting
VettoCRM was built with multi-site groups in mind from the start, not adapted afterwards from a single-clinic product. Every KPI — revenue, utilisation, no-shows, retention, staff productivity — is available per site and rolled up across the whole group, with one click to move between the two views.
Because scheduling, records, inventory and invoicing all sit in the same system per clinic, the numbers on the dashboard are generated automatically from real activity rather than compiled by hand at month end. For a group that has outgrown spreadsheets held together by one person's memory of "how each site does things", that difference alone is usually worth the switch.