If you run more than one branch, crew base or franchise territory, the question you ask every Monday is simple: which location needs my attention this week? A multi-location dashboard should answer that in two minutes. Most don’t, because the numbers underneath aren’t set up to be compared.
This guide covers what to track per location, how to structure your data so the comparison is fair, and a weekly routine that uses it.
First decide what a “location” is
Before any dashboard, agree on one definition and stick to it:
- Branch office — its own staff, trucks and phone number.
- Service territory — one team, split by area (north county, south county).
- Franchise unit — separately owned, reporting to you.
Then make two rules non-negotiable:
- Every job belongs to exactly one location. A job with no location silently disappears from every rollup, and the totals stop matching your books.
- A technician who works two locations is counted once. Split their hours by where the work was done. If you add up headcount per location, shared techs get double-counted and utilization looks better than it is.
The numbers worth comparing
| Metric | How to calculate | What it tells you |
|---|---|---|
| Revenue | Invoiced revenue from completed jobs in the period | Size, not health |
| Jobs completed | Count of jobs marked complete | Volume |
| Average ticket | Revenue ÷ jobs completed | Pricing and upsell discipline |
| Estimate close rate | Estimates accepted ÷ estimates sent | Sales quality |
| Callback rate | Return visits for the same problem ÷ jobs completed | Workmanship |
| Response time | Request received → technician on site | Customer experience, capacity |
| Utilization | Billable hours ÷ paid hours | Scheduling efficiency |
| Receivables over 30 days | Unpaid invoice total older than 30 days | Cash risk |
| Customer rating | Average post-job rating | Reputation |
Two rules for comparing locations fairly:
- Normalize. Compare revenue per technician or per truck, not raw revenue. A 12-tech branch will always “win” against a 4-tech branch.
- Compare the same period and the same mix. A branch doing mostly installs will have a higher average ticket than one doing service calls. Compare installs with installs.
Measured numbers vs estimates
Be suspicious of any dashboard tile you can’t trace back to records. “Projected revenue” or “today’s jobs” calculated as a percentage of the month so far looks like data but isn’t. Every number on a multi-location view should answer: which jobs or invoices is this adding up? If you can’t click through to the records, treat it as a guess.
A 15-minute weekly review
- Sort locations by callback rate and receivables over 30 days. Problems show up there before they show up in revenue.
- Check response time. A branch that’s slow to arrive is usually understaffed or badly scheduled, and it will lose reviews next month.
- Look at average ticket and close rate together. High close rate with a low ticket often means a branch is underpricing.
- Pick one location and one number to fix this week. Write it down, check it next Monday.
Where Exoserva stands today
I’d rather be straight about this. In Exoserva, branches are set up as Organizations, and properties link to them. Service territories are a separate, company-wide list — they aren’t tied to an organization. The Organizations page and the cross-location dashboard at /enterprise are both on the Enterprise plan today, they’re open to owners and administrators, and neither has a menu link yet, so you get there by typing the address. It is still early: not every metric in the table above is in the product, and several tiles in that view are placeholders rather than measured numbers — the health score, and the technician count and response time, which repeat one company-wide figure for every location. The revenue goal and projection are this month’s revenue plus a fixed percentage, not a target you set. I’ll update this post as the product catches up. Until then, the structure and the weekly routine above work with any system that lets you export jobs and invoices per location.
How many locations do you run, and what’s the first number you look at on Monday? Share it below.