In short
- A rollout is one project repeated, so the flow is the standard and each site is a run of it.
- Gates are what stop a site going live before its staff training is signed off.
- The value compounds: the tenth site starts from everything the first nine learned.
The situation
Opening a branch, refitting a store, or introducing a new system at each location is the same project repeated many times. The difficulty is not the work at one site; each site lead usually handles that well. The difficulty is knowing where all of them stand, and making sure the tenth site benefits from what the first one learned.
Without a shared standard, a rollout becomes a set of parallel improvisations that happen to share a budget line.
The three questions an operations lead actually has
Every status meeting is really an attempt to answer the same three things:
- Which sites are behind, and behind on what specifically?
- Is anybody about to skip a step that we will have to come back for?
- Has the thing that went wrong at site three been fixed for sites four to eighteen?
A spreadsheet answers the first one badly and the other two not at all, because it records progress without recording the standard that progress is measured against.
One flow, shared as the standard
The operations team writes a single rollout flow and shares it as a template. Each site lead starts a project from it, named after their location.
- 1Survey — site measured, constraints and local requirements recorded.
- 2Approvals — landlord, local permits, and budget sign-off in writing.
- 3Installation — the physical work, in the order that has already been proven elsewhere.
- 4Staff training — people trained and signed off, before anything is live.
- 5Go-live — the switch, with a named person responsible on the day.
- 6Review — what we would do differently, folded back into the template.
Six phases is deliberately few. A rollout template that tries to describe every local variation stops being a standard and becomes a document nobody reads.
The gates are the point
Every site follows the same gates, so a site cannot go live before training is signed off. This is the control that spreadsheets cannot give you: not a column saying training is at 80%, but a phase that will not close.
Phase 2
Foundation
8 of 8 steps done
Phase 3
Structure
locked until the gate clears
The gate asks one question
Is everything behind this line actually true?
- Foundation inspected
- Inspection report filed
- Payment released
Where it stands, across every site
The view an operations lead wants is every site side by side: current phase, how far through it, and what each one is waiting on.
Worth being plain about: today this is one project per site. The shared console above is not finished yet.
Folding lessons back in
After each site's review phase, the template changes. A missing step found at site three is added once, and sites four onwards get it automatically. Projects already running keep the phases they started with, so nothing in flight is disrupted by the edit.
This is where a rollout stops being linear work and starts compounding. The first three sites pay for the standard; the remaining fifteen benefit from it.
What this does not solve
There is no shared console yet, no role-based approvals, and no cross-site reporting — those are in development, and until they land an operations lead is still collecting status rather than reading it. What exists today is the part that has to come first: one agreed standard, run the same way at every site, improving after each one.
Put it into practice
Build your first flow, or start from a ready-made one, in a couple of minutes.