Consistency across branches is not uniformity

Multi-site operators tend to swing between two failures. The first is enforcing uniformity everywhere, including where local conditions genuinely differ, which makes each site slightly wrong for its own catchment. The second is allowing each site to drift, which means the brand promises something the guest may or may not receive.

The way out is not more control. It is deciding, explicitly, which category each thing belongs to.

## What should be identical

**Core recipes and specifications.** A signature dish must be the same dish. If a guest can tell which branch made it, the brand is two brands.

**Brand expression.** Identity, tone, menu design language and how the venue presents itself.

**Service standards.** The behaviours that constitute the experience: greeting, pace, how a problem is handled, how the bill is presented.

**Reporting.** Same measures, same definitions, same cadence. Without this, branches cannot be compared and problems cannot be seen.

**Food safety and compliance.** Not negotiable anywhere.

## What may legitimately differ

**Menu length.** A smaller site with a smaller kitchen cannot carry the full list, and forcing it to produces a slower, worse version of every dish.

**Opening hours.** Catchments have different rhythms. A business district and a residential neighbourhood do not share a peak.

**Local additions.** A small number of items that respond to a local preference, provided they do not compromise the core.

**Staffing structure.** A site with different volume needs a different rota shape, not the same one scaled.

**Price**, where the cost base or the competitive set genuinely differs — but this needs a stated rule, not case-by-case decisions.

## The real problem: undecided variation

Most inconsistency is not a choice. It is drift.

A supplier substitution made once during a shortage and never reversed. A prep step abbreviated by a new hire who learned from someone who learned from someone. A garnish dropped because it kept running out. A service standard that decayed because the manager who enforced it left.

None of these were decided. Each of them changes the product. And because they arrived gradually, nobody at the site experiences them as a change.

## How drift is caught

**Written specifications.** Drift is only visible against a standard. Without one, every version is defensible.

**Cross-site visits.** People who work at one site stop seeing it. Someone from another site sees the difference within an hour.

**Consistent reporting.** Comparable numbers across branches expose the outlier faster than any inspection.

**A simple check routine.** Weighing a portion, timing a ticket, tasting a signature item — short, regular checks catch drift while it is still small.

## The decision register

The most useful multi-site document is not the operations manual. It is a short register with three columns: the item, whether it is fixed or flexible, and who decides if it is flexible.

Menu length: flexible, decided by operations. Signature recipes: fixed. Opening hours: flexible, decided by the general manager with approval. Coffee supplier: fixed. Local items: flexible up to three, approved centrally.

This document takes an afternoon to write and prevents most of the arguments that consume multi-site management.

## Practical recommendations

1. Write the fixed-versus-flexible register before opening the next site.
2. Specify the signature items in enough detail that a difference is measurable, not arguable.
3. Rotate people between sites. Familiarity is what hides drift.
4. Use identical definitions in reporting so branches are genuinely comparable.
5. Run short, frequent checks rather than occasional full audits.
6. When a difference is found, ask whether it should be corrected or adopted. Sometimes a branch has found something better.

## In short

Consistency is a set of decisions about what must be the same, not a general aspiration to sameness. Written down, it lets sites adapt where they should and holds them where it matters — which is the only version of consistency that survives more than two branches.