Insights
Rolling out anything across hundreds of sites, whether new technology, a refit, a piece of equipment or a new way of working, is deceptively hard. A single site is a project any competent team can manage. Two hundred sites, each with its own quirks, running in parallel against a deadline, is a different kind of problem. Get the model right and a large rollout becomes a smooth production line. Get it wrong and it becomes hundreds of small crises. This guide explains how to deliver multi site rollouts well.
By Christopher Fagan
The usual failure is treating every site as a bespoke project. Each one gets designed, negotiated and solved from scratch, so the programme never gets faster and quality swings wildly from site to site. Add local variation, tired crews and thin central control, and the rollout slips further behind with every wave. The problem is almost never any single site. It is the absence of a repeatable model.
The organisations that deliver rollouts well turn the work into a repeatable process. They design the standard site once, build a clear playbook covering exactly what happens and in what order, and then repeat it. The tenth site teaches lessons that make the twentieth smoother, and by the hundredth the process runs like a machine. Standardisation is what turns effort into pace.
Sites are grouped into waves that move through the same steps together, so the programme has rhythm and the central team can plan resources ahead. Wave planning also lets you learn safely. Early waves prove the model on straightforward sites, problems are fixed before they are repeated at scale, and the harder sites come later once the process is mature.
Most rollout delays happen because a site was not ready when the crew arrived. Access was not arranged, a survey was wrong, a dependency was missed. A disciplined readiness check before each site enters delivery removes the wasted visits and the standing time that quietly wreck a schedule and a budget.
Every site is a little different, and pretending otherwise causes as many problems as ignoring standardisation. The skill is deciding what must be identical everywhere, for quality and speed, and what is allowed to flex for local conditions. A good rollout is strict about the core process and sensible about genuine local variation.
With hundreds of sites in flight, leaders cannot manage what they cannot see. A single, honest view of every site’s status, with real progress rather than optimistic reporting, is what lets the central team spot slippage early and act before it spreads. Control at scale is a reporting discipline as much as a delivery one.
PEF delivers large multi site rollouts across sectors, from retail and hospitality to telecoms and EV charging. If you have a rollout to deliver, our delivery excellence team can help you build the model and hold the standard. Talk to us about your programme.
The usual failure is treating every site as a bespoke project, so the programme never gets faster and quality swings from site to site. The problem is almost never any single site, it is the absence of a repeatable model.
Turn the work into a repeatable process, design the standard site once, build a clear playbook and repeat it, and group sites into waves so the programme has rhythm and early waves prove the model before the harder sites.
Be strict about the core process that must be identical everywhere and sensible about genuine local variation, and hold a single honest view of every site status so slippage is caught early.
If any of this is live for you right now, the senior people who wrote it are the people you would work with.