A multi-location rollout is not "the same project, several times". It is a different problem, and treating it like a series of one-off builds is the most reliable way to end up with locations that do not match.
Why rollouts drift
Drift is rarely dramatic. It happens because each site is run by whoever was available, decisions get made locally and never travel, and the standard lives in someone's head rather than in a document. Six locations in, the brand update reads as half-finished, not because any single build was bad, but because no two were the same.
Four things that hold a rollout together
A repeatable scope
The scope document is the product. If every location starts from a fresh interpretation of the brand standard, you are relying on judgement to produce consistency, which is exactly the thing judgement is worst at across many people and many months.
One accountable team
Not one crew, but one team that owns the program. The value of the same people running site nine that ran site two is that the mistakes from site two are already priced into site nine.
Consistent reporting
If every site reports differently, you cannot compare them, and you cannot see a problem forming. The same fields, the same cadence, the same photos from the same angles. It sounds bureaucratic until the week you need to answer "which of these twelve sites is actually at risk?"
A feedback loop
The point of doing something twenty times is that it should get better. That only happens if what went wrong on site three changes the scope for site four. Without a loop, you do not have a rollout program; you have twenty separate projects that happen to share a logo.
What to watch for in the first three sites
The first few locations are where the program is actually designed. Watch for:
- Decisions being made on site that nobody records
- Trades varying location to location without a reason
- A scope document that has not changed since site one, which usually means nobody is reading it
- Reporting that describes activity rather than status
The measure that matters
A rollout is working when the tenth location is more predictable than the first: same standard, fewer surprises, less of your own time spent managing it. If site ten feels exactly like site one, the program never actually started.
