Multi-site fit-out programmes are usually framed as design problems. We see them more often as specification-discipline problems.
We deliver regional rollouts for property and facilities clients. The cost difference between a good outcome and a poor one is rarely about which kit was chosen. Which display. Which switch. Which meeting-room system. It is about whether the specification for each system was identical across all sites. Or whether each site quietly added a variation.
The cost of variance is paid every month after handover. Each variation needs its own support documentation. Its own spare parts. Its own training. Its own integrator relationship. Five small variations across four sites generate twenty small ongoing decisions. None of those decisions is large enough to escalate. Together they are the reason multi-site standardisation programmes drift.
Where variance actually creeps in
We see three reliable sources of variance.
The first is local building constraint. A site with a shorter ceiling height. Different cable risers. The team specifies a different mounting or routing approach to fit.
The second is local procurement. A site where one part of the original kit was discontinued between phases. A substitute was approved without changing the standard.
The third is local relationships. A regional integrator suggests a known-good alternative for a single system. The standard is silently amended.
None of these is a poor decision in isolation. Each is a sensible local response. Together they generate the variance that erodes the value of the standard.
The procurement discipline that holds standards in place
Multi-site procurement discipline rests on three practices.
The first is a single product schedule. It names the exact part numbers approved for the standard. It includes a documented substitution process when a part is discontinued.
The second is a single labelled cabling, mounting, and commissioning standard. It is applied identically across all sites. The documentation is produced to the same template.
The third is a single integrator accountable for all sites. Or a small named set of integrators working from the same standard with the same review process.
The test is whether the documentation produced at site four reads the same as the documentation produced at site one. If it does, the standard has held. If it does not, the standard has drifted. Someone will pay for that later.
Where this shows up commercially
The commercial case for standardisation is usually presented at fit-out. It is realised over the following five years.
A standardised estate can be supported by a single engineering team. With a known set of spare parts. A single content management system. A known set of integration points.
A non-standardised estate needs more of all of those things, every year, in perpetuity. The variance compounds.
The pattern we observe is that businesses do not lose the standard at the fit-out stage. They lose it in the first eighteen months after. Local pressures push small variations through. No single decision-maker would approve those variations if the cumulative pattern were visible.
A worked example
We delivered a four-city workplace standardisation programme for a FTSE 100 publishing group. The cities were Newcastle, Plymouth, Bristol, and Cardiff.
Six standard components were specified for each site. Smart meeting rooms with one-touch join. Distributed signage with centralised content control. Structured cabling with AV over IP backbone. Collaboration and breakout zones with a consistent equipment loadout. Media-ready environments at the sites that required them. Reception signage with a single arrival experience.
The discipline that made it work was straightforward. A single product schedule. A single commissioning standard. Both applied identically at all four sites.
The full delivery model is set out in the Regional multi-site rollout case study. Property and facilities teams scoping similar programmes can see the standard in full.
What this means for your rollout
If you are scoping a multi-site programme now, our view is direct. The most useful early discipline is the procurement standard, not the design. Decide once. Document once. Audit each site against the same checklist.
The cost of doing this is small. The cost of not doing it is the recurring drift that erodes the value of the standardisation programme over the following five years.
We deliver that procurement-standard discipline through our Managed Infrastructure and Workplace Automation services. We set it out at the design stage through a Critical Systems Review. For sector context, see how we support Multi-Site operators.