Multi-location reporting without the monthly export

If the monthly report starts with “can you send me your spreadsheet”, the problem is not the spreadsheet. It is that every location keeps its own version of the truth.

The BittaFlow team

3 min read

On this page
  1. Why the exports never match
  2. Standardise four things first
  3. The numbers that belong on one screen
  4. What a live view changes
  5. What to keep local
  6. Permissions, briefly
  7. The migration, in order
  8. One workspace, many locations

Every multi-location business has the same monthly ritual. Someone asks for the numbers. Five managers send five spreadsheets in five slightly different shapes. Someone spends a day merging them, and the answer arrives three weeks after the month it describes.

By the time it lands, nobody can act on it.

The fix is not a better spreadsheet. It is agreeing on a small number of definitions and keeping the data in one place.

Why the exports never match

Three reasons, and none of them are laziness.

Different definitions. One location counts an enquiry when the phone rings. Another counts it when a quote is sent. Both are honest, both are wrong to compare.

Different tools. One site uses the booking system, another keeps a paper diary, a third uses a spreadsheet the manager built. There is no shared structure to merge.

Different timing. One manager exports on the last day, another on the fifth of the month after a clean-up. The totals disagree before anyone has done anything wrong.

Standardise four things first

Before any dashboard, agree on these in writing:

  1. What is a lead. The moment a person expresses interest, in any channel. Not when it is qualified, not when it is quoted.
  2. What is answered. A human replied, or a system booked something. An auto-reply alone does not count.
  3. What is booked. A date and time on the calendar, with a name attached.
  4. What is completed. The work happened, or the visit happened. This is the only number that turns into money.

Four definitions, one page, signed off by whoever runs the locations. It is the least exciting document in the business and the one that makes every later report trustworthy.

The numbers that belong on one screen

Once the definitions exist, a useful weekly view is small:

Number Why it matters
Leads per location Demand, and whether marketing is reaching the right place
Answered rate Where the phone is failing, not where the traffic is
Booked rate Whether the front desk converts or just listens
Completed rate Whether the schedule survives the week
Response time The leading indicator for all of the above

Five numbers per location, refreshed daily, beats forty numbers refreshed monthly. If a manager has to explain a drop, they can open the record and see what happened, rather than guessing from a total.

What a live view changes

It moves the conversation from reporting to fixing. A location with a falling answered rate is visible on Tuesday, not on the twentieth of the following month.

It removes the merge job. Nobody spends a day copying columns. That day goes back into the business.

It makes comparison fair. Same definitions, same source, same window. Comparing two locations finally means something.

It survives staff changes. When a manager leaves, the numbers do not leave with them.

What to keep local

Standardising does not mean centralising everything. Each location still needs its own calendar, its own team, its own local notes. The reporting layer should read from those, not replace them.

The rule of thumb: shared definitions, local detail. The centre owns the meaning of the numbers; the location owns the day-to-day record.

Permissions, briefly

A regional manager should see their region. An owner should see everything. A receptionist should see the customers they are dealing with, not the group’s revenue.

This is not a security formality. Reports get ignored when they are full of numbers people are not allowed to act on.

The migration, in order

  1. Write the four definitions. One page.
  2. Pick the source of truth per number. One system per number, not one per team.
  3. Clean the current month only. Do not attempt three years of history.
  4. Run the weekly view for four weeks alongside the old ritual.
  5. Retire the exports once the numbers agree twice in a row.

One workspace, many locations

BittaFlow keeps every location in one workspace with per-location views: leads, answered rate, bookings, response time and completions. Read them at group level, drill into a single conversation when a number looks wrong. Multi-location is a setting, not a second installation.

If you are still merging spreadsheets, the four definitions above cost nothing to write this week. They will improve the reporting whether or not you change tools.

Useful? Send it to someone who runs the phones.