Guide · Managing multiple locations
Seven workflows that break at the third location.
Two locations can run on one person who knows how everything fits together. By the third, the same manual work starts failing in predictable places. Here are seven, how to spot each one, and what fixing it looks like.
Every example labelled observed comes from our flagship engagement, a five-center behavioral health network. The rest is the pattern, not a measured result.
Where the work breaks, and what fixes it.
Each one is a normal way to run one or two sites. It stops working as sites are added.
Numbers retyped between systems
You noticeSomeone copies the same figures from one system into another every week.Why it breaks with more sitesEach site adds another set of figures to copy, and the work grows with every opening.What fixing it looks likeConnect the sources and draft the output automatically; a person reviews what disagrees.Observed at the networkAttendance was retyped into the billing census, more than a day a week (as described by the client).
Every site keeps its own spreadsheet
You noticeEach location tracks the same thing in its own format, with its own columns and habits.Why it breaks with more sitesRolling up three formats means translating three times, and any change at one site breaks the roll-up.What fixing it looks likeOne shared template, with each site's differences held as settings rather than separate files.Observed at the networkEach site kept its own attendance log. Three outpatient sites now run on one shared census template; the fourth is moving onto it.
No shared ID across systems
You noticeMatching the same customer, patient or order across systems depends on names or memory.Why it breaks with more sitesMore sites means more people with similar names, and more records nobody can match with confidence.What fixing it looks likeAdd a shared record number at the source, so every system can match on it.Observed at the networkThe attendance logs carried names but no record number. One added column closed that class of error.
The roll-up rebuilt by hand
You noticeLeadership numbers come from someone assembling every site's data into one report.Why it breaks with more sitesThe report waits on the slowest site, and nobody sees all sites side by side on the same day.What fixing it looks likeA scheduled roll-up that shows each site together and how fresh each number is.Observed at the networkNobody had looked at all the centers in one file on the same day.
Exceptions found in a meeting
You noticeDiscrepancies surface when people sit together and compare notes.Why it breaks with more sitesThe meeting grows with every site, and problems are found days after they happen.What fixing it looks likeChecks that flag exceptions as the data arrives; a person reviews only what was flagged.Observed at the networkSeven people met on Monday and Tuesday to find discrepancies out loud (as described by the client).
Logins and access per location
You noticeEach site has its own system account, export and password.Why it breaks with more sitesAccess sprawls, credentials live with individuals, and nobody knows who can see what.What fixing it looks likeA list of every source with its owner, read-only access where possible, and a plan for when someone leaves.Observed at the networkFour separate EMR instances, each needing its own credentials for a read-only connection.
Each location's pages and listings
You noticeEvery site has web pages, a map listing and a phone number to keep current.Why it breaks with more sitesPages and listings drift out of date, and new location pages get published without anything linking to them.What fixing it looks likeOne identity per location, linked from the main site and checked on a schedule.Observed at the network51 location pages that nothing linked to, found in a technical audit. A technical finding, not a measured traffic loss.
Which of these does your business have?
Print it, or go through it with whoever runs operations.
- Someone copies figures between two systems every week
- Each location tracks the same thing in its own format
- Records are matched by name rather than a shared number
- Leadership numbers are assembled by hand from every site
- Discrepancies come up in a standing meeting
- Nobody has a full list of logins and who holds them
- Location pages or listings are out of date or unlinked
If you ticked two or more, look at those before the next location opens.
Each new location should add a setting, not a copy.
The common thread in all seven fixes: shared rules, a shared identifier, and a roll-up that runs on its own, so a new site is configured rather than rebuilt.
Where to start, and in what order, is what an audit decides. The automation audit checklist · Operations audit and automation
What owners ask about multiple locations.
Is the third location really the tipping point?
It is not a law. It is where the arithmetic starts to bite, and where one person usually can no longer hold every site in their head. Some businesses feel it at two locations, others at five.
Do we need new software to manage multiple locations?
Not usually first. Most of these fixes connect the systems you already have, add a shared identifier or a shared template, or change a process. Software comes after the audit, if the evidence supports it.
What should we fix first?
Usually the shared identifier and the shared template, because the roll-up, the checks and the reporting all depend on them. An audit confirms the order for your business.
Does this apply outside healthcare?
Yes. The patterns show up wherever several locations feed one set of numbers. Our published examples come from a five-center behavioral health network; results in other industries are not yet published.
Opening another location soon?
Bring the one workflow you dread copying to the next site to a free 20-minute call. We will tell you what we would look at first.