Managing by phone call
You have four sites, or twelve. Each one has a manager who is good at their job and does things slightly their own way. One uses a spreadsheet, one uses a paper diary, one uses the till system for everything.
Every Monday head office emails each site for its numbers. Some reply the same day. Some reply with a photo of a whiteboard. Someone spends the morning pulling it together, and by the time it is ready it is already out of date.
When something goes wrong at one site, you find out late, and when a site finds a better way of doing something, the others never hear about it.
Why every branch drifts
Sites drift because each one solved its problems locally, with whatever was to hand, before there was a central way of doing it. Nobody was wrong. But the result is that head office has no common language to compare sites in.
Adding a group-wide reporting spreadsheet usually makes it worse, because it adds a job for each site manager on top of their own system. It gets filled in late, differently, or not at all.
The fix is not forcing every site to be identical. Some differences are real: opening hours, local suppliers, staffing rules. The fix is agreeing which parts of the operation must be the same, and making the rest configuration rather than improvisation.
What the drift costs you
| Problem | Effect |
|---|---|
| No live view of each site | Problems found days or weeks late |
| Data collected by email | Staff time at every site and at head office |
| Different processes per site | Inconsistent customer experience |
| Local workarounds | Good ideas stay local, bad habits spread quietly |
| New sites set up from scratch | Each opening reinvents the same processes |
How we connect the sites
- Visit or call each site and map how they actually do the core jobs: bookings, stock, staffing, takings, maintenance.
- Separate genuine local differences from habit, and agree with you which processes will be common.
- Give each site the same tools for the common processes: a web app or existing system configured once, with site-level settings for the real differences.
- Pull data from the systems each site already uses, such as the till, booking tool or Xero tracking categories, through their APIs rather than asking managers to report it.
- Build one head office view with every site side by side, updated automatically, with alerts when a site falls outside normal ranges.
- Set up permissions so site managers see their own site and head office sees all of them.
Where a site uses something different and it works well, we connect to it rather than replace it. The goal is one picture, not one piece of software for its own sake.
Rollout happens one site at a time. We usually start with the site whose manager is keenest, fix whatever the first real use shows up, and only then move on. A system that works in one busy location is far easier to sell to the next manager than one that only exists in a presentation.
Running the group from one screen
Head office stops chasing numbers because the numbers arrive by themselves. Site managers stop filling in a separate report. You can compare sites fairly, spot one that is struggling early, and copy what the best one does.
Opening a new location becomes a matter of adding a site to the system and setting its local options, rather than building its processes from nothing.
Site managers usually gain the most. They get a clear view of their own numbers without building it themselves, and when head office rings, it is to talk about what the figures mean rather than to ask for them.
Signs your sites need joining up
- Head office collects figures from each site by email or phone.
- Each location keeps records in a different format or tool.
- You find out about problems at a site after they have grown.
- Setting up a new location means starting its admin from scratch.
- Site managers spend time on reporting instead of running the site.