In short
- Fix things in order. The network first, then the machines, then the logins, then the reporting.
- Prove it at one location before you repeat it at the others. Changing everything everywhere at once is how these projects stall.
- Hold the standard afterwards with a written change process, a short quarterly check of each site, and buying done centrally.
Running technology across several sites is one of the most common complaints we hear from growing Canadian businesses. The dental group with five clinics and five different setups. The franchise with twelve locations and twelve accounting systems, each chosen by whoever opened it. The firm with offices in Toronto, Calgary and Ottawa where working together means emailing files back and forth.
The waste is obvious. The bigger cost is quieter: when every location works differently, nobody at the top can see what is happening across the business. Something breaks at location four and it takes twice as long to fix, because it is set up differently from location two where you solved the same problem last year.
Why it happens
You grew one location at a time. Each was set up by whoever was available, with their own preferences.
Nobody set a standard. Without one, people decide locally. Those decisions harden into habits, then into dependencies, then into "we cannot change that".
Suppliers sold site by site. A payroll company, a point-of-sale company and a scheduling tool each sold to one manager, and nobody was looking across the whole business.
People left. Whoever chose the original setup is gone, and nobody remembers why.
What the current state costs you
You will need this to get the budget approved.
More money on technology. Maintaining five different setups costs more than maintaining one: separate suppliers, separate training, separate expertise. Most multi-location businesses pay noticeably more than they would on a single standard.
More money on people. Staff cannot cover another site when the systems are different. Training material has to be rewritten for each location. Somebody spends every week stitching five reports into one.
Slower support. A problem a technician solves in 20 minutes at a standard site can take 90 minutes at an unusual one.
More exposure. Every different location is a different risk. One standard lets you push a security fix or a policy change everywhere at once.
The four layers
Fix them from the bottom up.
Layer 1: the network
Every location should have the same brand of firewall set up the same way, separate wifi for staff, guests and equipment, a written plan for how the machines are numbered, wifi points managed from one place, and a private connection back to head office.
The test: when you open location six, the network should be a one-day template, rather than a week-long project.
Layer 2: the machines
Every device at every site enrolled in one management system.
- Windows machines managed from one screen through Microsoft Intune, which you are probably already paying for inside Microsoft 365 Business Premium
- Macs through Jamf if you have a lot of them, or the same Microsoft tool in a mixed office
- A naming rule that says where a machine is and what it does, so YYZ-RCPT-001 is the first reception computer in Toronto
- Updates pushed centrally on a schedule
- The same set of applications on every machine
This layer is what stops location three quietly running an operating system that stopped getting security fixes.
Layer 3: logins and applications
Logins come first. One account per person, held in one central place through Microsoft or Google, working at every location. Every account should live centrally rather than only on one computer, and one email domain covers the whole business.
The test: a staff member covering another site for a week signs in and works. Somebody leaves, one account is disabled, and their access ends everywhere at once.
Then the applications. This is the political part and the valuable part. List every application in use across every location and sort it into three piles:
- Same everywhere. Email, file storage, accounting, point of sale.
- Same by preference. One supplier strongly preferred, local alternatives written down.
- Local choice. Pick from an approved list, no further constraint.
The first pile is usually shorter than people expect, around five to eight applications. Getting those consistent delivers most of the benefit.
Layer 4: data and reporting
Once the first three layers match, the numbers can finally be pulled together.
One place for files. SharePoint or Google Drive with a folder structure that matches how you actually operate: a folder per location, shared spaces for anything crossing them.
One dashboard. When every location runs the same systems, you can see revenue, staff productivity, ticket volume and customer satisfaction side by side without anybody assembling it by hand.
One place to talk. Teams or Slack, one workspace, channels by location and by function.
Do it one location at a time
The biggest mistake here is changing everything at once. That creates maximum disruption, usually stalls halfway, and leaves you half-standardised, which is worse than where you started.
- Write the standard down. Four to six weeks. Exactly what a standard location looks like, agreed by leadership.
- Build it at one site. Four to eight weeks. Choose head office or whichever site is closest to the standard already. Find the problems here. Write down what you learned.
- Repeat, site by site. Three to six months for most businesses. Each one goes faster than the last. Budget four to eight weeks per location.
- Run two systems where you have to. Payroll and accounting rarely move cleanly mid-year. Run both and switch at year end or quarter end.
Handling "we have always done it this way"
Some of the resistance is legitimate and some of it is habit. Sort them.
Investigate every objection before dismissing it. Sometimes a location genuinely does something different for a good reason. Write it down and decide on purpose whether the standard accommodates it.
Bring location managers into the design. People support what they helped build, and it costs you very little to ask.
Say what they get. Faster support, fewer wasted mornings, better tools. Make it concrete during the rollout.
Be clear about what is not up for debate. Security, logins and backups are decisions, not discussions. Say so early.
Keeping it that way
A standard decays without governance. Three habits hold it:
A written change process. Any new application or configuration change goes through a request. Without one, you drift back to fragmentation within a year and a half.
A short quarterly check of each location against the standard, done remotely using the management tools you now have.
One annual review of the standard itself. Some of it will be obsolete; some new tools will deserve a place.
And buy centrally, even when you deploy locally. That is what stops somebody ordering a home router because it was on sale.
How we run this for multi-site businesses is on the multi-location page, and the day-to-day support behind it is on the managed IT page. The repeated steps that a standard makes possible, such as opening a new site or setting up a new hire the same way every time, sit on the automation page. What one monthly price covers across several sites is worked out in what IT support costs in Canada.
Have someone map your current state
Leave your name and number on the contact page and a real person calls you back the same business day, usually within an hour. The free infrastructure audit covers every location and comes back as a written plan in priority order, at no cost.
itopsi manages IT and digital operations for multi-location Canadian businesses from a Toronto base.
