Compare with context
A simple ranking can identify high and low results but not whether the comparison is fair. Group sites by relevant conditions such as format, maturity, trading pattern, local demand, labour availability and property constraints.
Context turns a league table into a useful management conversation and reduces the risk of pushing the wrong action onto a different operating model.
For example, a hotel dining outlet, a high-street cafe and a destination restaurant may all need margin control, but their demand signals and operating levers are not the same.
Define the non-negotiables
Be explicit about the standards that should remain consistent, including guest experience, reporting definitions, approval boundaries and key operating controls.
Leave room for local teams to respond to their market within those boundaries. Ownership improves when consistency is not confused with central micromanagement.
The centre should define the operating language: what counts as waste, what counts as a stockout, how contribution is measured and when an exception needs review.
Find positive variation
Exception management should not focus only on problems. A site that protects margin, improves availability or reduces labour pressure may have a practice worth understanding.
Capture the operating conditions behind the result before trying to scale it. What worked in one location should become a testable playbook, not an unsupported instruction.
Positive variation is one of the most valuable assets in a group. It shows what is possible under real conditions, with real teams and real guest behaviour.
Support the site that needs it
Central teams add value when they can identify where support will have the greatest impact. That requires timely, comparable signals and a clear route from insight to local action.
This is especially important when capacity and labour pressure are uneven. UKHospitality has reported major pressure around employment, vacancies and operating capacity, which means support should be targeted where it will change the next week, not only where last month looked weak.
The goal is a group that learns across locations while each manager remains responsible for running the operation in front of them.
Make consistency a learning system
Consistency should mean the group can see variation, explain it and decide what to do. It should not mean every site is forced into the same operating response.
A practical group rhythm reviews outliers, identifies causes, captures strong practice and agrees support. The same rhythm can be used for margin, waste, demand, labour, guest experience and availability.
That is how a multi-site business becomes easier to manage without flattening the local judgement that makes each location work.