The monthly meeting starts with a simple question: which branch is doing best? Then the arguing starts. One branch counts every phone call as a lead. Another counts only booked appointments. One general manager logs jobs when they are sold, another when they are finished. Everyone has a spreadsheet, and none of them agree.
This is the most common reporting problem in multi-location service companies. Whether you run HVAC, plumbing, pest control, landscaping, clinics or auto service, each branch grew up doing things its own way. The numbers look like they compare, but they measure different things.
Good multi-location reporting is not a new dashboard. It is an agreement about what each number means, and a CRM set up so every branch records the same things the same way.
Why branch numbers don't line up
Look for these signs:
- Different definitions. "Lead," "booked," "sold" and "closed" mean something different at each location.
- Different sources of truth. Some branches work in the CRM, others in the scheduling or field-service tool, and a few in a whiteboard and a spreadsheet.
- Missing or optional fields. Lead source and location are left blank, so the report fills them with "unknown."
- Shared phone numbers and inboxes. Calls and web requests land in one place and get handed out by hand, so nobody can tell which branch they belonged to.
- Manual roll-ups. Someone at the main office rebuilds the numbers each month by copying from each branch. It takes days, and mistakes creep in.
None of these are people problems. They are setup problems, which means they can be fixed.
Step 1: Agree on definitions first
Before touching any software, write down one plain sentence for each of these words and get every general manager to sign off:
- Lead — what counts, and what doesn't (spam, wrong number, existing customer calling about a bill).
- Booked — an appointment or estimate visit on the calendar with a date and time.
- Sold — the customer said yes in writing or paid a deposit.
- Completed — the work is done.
- Lost — the customer said no or stopped responding, with a reason picked from a short list.
- Repeat or membership customer — how you count service agreements, plans or return visits.
Put these definitions in one shared document. When a new manager joins, this is the first thing they read.
Step 2: Eight fields every branch records the same way
Every lead or job in your CRM should carry the same eight fields, filled in the same way at every location:
- Location — picked from a fixed list, never typed by hand.
- Lead source — a fixed list (website, phone, referral, repeat customer, paid ads and so on).
- Service line — what the customer needs, from a fixed list.
- Date received — set automatically, not entered later.
- First response time — when someone first replied.
- Stage — using the shared definitions from Step 1.
- Owner — one named person at the branch.
- Lost reason — required whenever something is marked lost.
Make the fields required where you can. A report is only as good as its emptiest column.
Step 3: Build one branch scorecard
Pick a small set of location-level KPIs and show them side by side for every branch on one page:
| Measure | What it tells you |
|---|---|
| Leads by source | Where each branch's demand comes from |
| First response time | How quickly each branch picks up new inquiries |
| Booked rate | Share of leads that become appointments or estimates |
| Close rate | Share of estimates that turn into sold work |
| Average job value | Whether branches sell similar-sized work |
| Lost reasons | Why work is slipping away, by branch |
| Repeat or plan customers | How well each branch keeps customers coming back |
Seven measures is plenty. If a number on the scorecard never changes a decision, drop it. For a broader list, see RevOps KPIs.
Step 4: Run a monthly branch review
Thirty to sixty minutes, with every general manager:
- Check the data first. How many records are missing a location, source or lost reason? Fix those before discussing results.
- Compare branches on the same scorecard. No side spreadsheets.
- Ask "why" about the biggest gap. A slow response time at one location is a process question, not a blame question.
- Agree on one change per branch. Write it down, with an owner and a date.
- Share what works. If one branch books more of its leads, find out what it does differently and write it down for the others.
Data cleanup checklist
Run this once before your first scorecard, then quarterly:
- Merge duplicate customers created by different branches.
- Replace typed-in locations and sources with picks from the fixed lists.
- Close out old open leads with a lost reason.
- Make sure each branch's phone numbers and web forms tag the right location automatically.
- Remove users who no longer work at a branch and reassign their open records.
Pipeline data red flags covers more of what to look for.
Where the CRM fits
Your scheduling or field-service tool runs the day: dispatch, technicians, invoices. A CRM for multi-location businesses keeps the customer and lead history across every branch, so the same definitions and fields roll up into one view. The key is deciding which system owns each step and making sure location and source travel with every record from the first call to the paid job.
When a checklist is not enough
Shared definitions and a scorecard will show you where branches differ. They won't fix tools that don't talk to each other, phone systems that can't tag locations, or years of messy records. That is where Desert West Digital's multi-location work starts: tracing real leads from first contact to paid job at each branch and showing where the data breaks. See the multi-location services page for scope.
FAQ
What is multi-location reporting?
Multi-location reporting means tracking leads, sales and jobs for each branch using the same definitions and fields, so you can compare locations fairly and see the whole company in one view.
Why don't our branch reports match?
Usually because branches define "lead," "booked" and "sold" differently, record data in different tools, or leave key fields like location and lead source blank. Fix the definitions and required fields before building new reports.
What KPIs should a branch scorecard include?
Start small: leads by source, first response time, booked rate, close rate, average job value, lost reasons and repeat or plan customers. Drop any measure that never changes a decision.
Do we need a new CRM to fix branch reporting?
Not always. Many companies can fix reporting by agreeing on definitions, making key fields required and cleaning up existing data. A new system only helps if those basics are in place first.
How often should we review branch performance?
Monthly works for most companies, with a quick data check at the start of each review and a fuller data cleanup each quarter.
Ready to see what your branch numbers are really saying?
If every branch reports differently, or the monthly numbers take days to pull together, start with the Revenue Systems Audit — $3,500 fixed. Desert West Digital follows real leads and jobs from first contact to paid invoice across your locations, in the systems you already use, and shows where data gets lost, re-typed or recorded differently. You get written findings, a ranked fix plan and a recorded video walkthrough.
The full $3,500 audit fee is credited toward your retainer if you start within 30 days of delivery. It can be spread across your first three months. Unused credit has no cash value and ends if the retainer is cancelled.
No prep required for the first call. Bring one recent monthly report and one question about your branches that nobody can answer quickly.