Somewhere in a group labour meeting, a perfectly sensible conversation takes a dangerous turn.
One venue is sitting at 27% wages, another at 32%, and a third has a remarkably tidy rota that everybody admires. The Operations Director asks why the others cannot follow the same approach. There should be one standard, surely. Fewer variations to explain and fewer different spreadsheets arriving on Monday.
The instinct is understandable. A growing hospitality group needs reliable information, consistent standards and some confidence that labour is being planned rather than guessed.
Then somebody suggests copying the strongest venue's staffing template.
Now we have a problem.
The venues might share a logo, menu, payroll provider and uniform. One makes its money from office workers at 6pm. Another is busy with families at noon. A third has a room that becomes effectively unusable without a dedicated runner. Their Friday nights don't become identical because the group puts them in the same reporting pack.
Consistency is valuable. Copying the wrong thing can become surprisingly expensive.
Two £20,000 Saturdays can need opposite rotas
Imagine two restaurants in the same group. Both forecast £20,000 in Saturday sales, both have a bar and dining room, and both have the same hourly rate for two comparable employees in this example.
At the first venue, trade builds gradually and most of the pressure falls before 6pm. At the second, the day is quiet until evening bookings, walk-ins and drinks arrive together.
The central rota template gives each venue two experienced employees from noon until 8pm.
That's sixteen scheduled employee-hours at each site. At an illustrative £15 per hour, both cost £240 in basic wages if all those hours are paid, before employer on-costs. Actual payroll cost will depend on break arrangements.
Move those same two shifts at the evening-led venue to 4pm until midnight. The total is still sixteen hours and the same £240. But the business has moved eight employee-hours out of noon to 4pm and into 8pm to midnight, where demand actually sits.
At the daytime-led venue, making that change would be absurd. At the evening-led venue, refusing to consider it could mean buying labour during quiet hours and leaving the most valuable service exposed.
The group wage report sees the same forecast, the same hours and the same basic cost. Guests and colleagues experience two entirely different services.
A shared labour percentage makes a reasonable financial boundary but a poor instruction for individual start and finish times.
The building has a vote, even if head office doesn't
Different venues create different amounts of work from the same number of guests.
A compact bar with glasswash next to dispense does not deploy like a venue where every tray of glasses travels down a staircase. A dining room with one clear section may be easier to manage than the same covers spread across a terrace and two floors. A site that takes hundreds of drinks orders at a single point of sale has different bottlenecks from a table-service operation.
These details rarely survive the journey into a group labour dashboard.
Take two venues with 200 guests in the building. At one, they are mostly seated and ordering steadily. At the other, they arrive before a show, place complicated drinks orders and leave together. Headcount tells you very little about staffing pressure without the timing and service model.
We explored this in Headcount Is Not Coverage. A body on the rota does not automatically translate into a working service position. The distinction becomes even more important when comparing different layouts, role mixes and peaks.
Opening and closing are part of the same calculation. One kitchen needs a lengthy prep period. Another receives more food prepared centrally. One site finishes service at 10pm; another has to clear a late-night crowd and reset a large room. If the schedule ignores those jobs, it looks efficient only because somebody is doing uncounted work.
A group template can give managers a place to start. It cannot know every staircase, bottleneck and service rhythm in the estate.
The best venue's rota might be the worst template
Copying a high-performing site's rota can feel evidence-led. The site delivers its budget, wage percentage is healthy and the team appears settled. Why wouldn't the rest of the group work like that?
Start by asking why it works.
Perhaps that GM has two exceptionally strong supervisors who flex between bar and floor without losing control of service. Perhaps the same employees have worked together for years. Perhaps bookings are predictable or the layout is unusually efficient.
The rota may be excellent for those conditions. It may also rely on strengths another site has not yet built.
Give the same late shift to a team containing four new starters and one experienced bartender, and the work can collapse into the one person everybody needs for guidance. Replace the experienced closer with someone still learning the building and the immaculate closing plan starts drifting into overtime.
Share successful practice, certainly. Copy the thinking. Find out which jobs were protected, where the manager built overlap and what they stopped doing. Then test whether those reasons survive the move into the next venue.
A good group can transfer judgement without pretending to transfer the people, building and demand that made the original rota work.
Standardisation still needs teeth
There is a legitimate objection to all this. If every GM can describe their venue as unique, local freedom can become an excuse. A manager can justify almost any extra shift with a sufficiently dramatic story about Saturday.
The answer cannot be to let ten venues use ten different definitions of wages, ignore budgets whenever they like and publish rotas whenever they find time.
Some things should be common everywhere.
Labour cost calculations should be consistent, so group comparisons mean something. Contracted hours, availability, leave, rest checks and break planning should follow the same employment and welfare standards, accounting for applicable arrangements. Every site should have a publication deadline, a named person responsible for the rota and an agreed way of recording material changes after publication.
A group can also insist that managers show their working. What sales are forecast by service period? Which positions need independent cover? What does the budget allow? Who can lead the close? What risk is being accepted when cover is reduced?
Those are proper controls. They improve accountability without prescribing identical names and hours.
The group defines the rules of the game. The venue supplies the conditions under which it is played.
A fair comparison needs a shared language
It is tempting to settle these arguments by putting wage percentages in a league table.
That can start a conversation, but it cannot finish one. Two venues may have different average spend, product mix, trading hours, management structures, wage rates and service expectations. Stronger sales per labour hour may indicate greater productivity. They may also reflect higher-priced items or salaried management costed elsewhere.
None of that excuses poor labour control. The explanation deserves checking before the result becomes a staffing instruction.
Agree exactly what each figure contains. Are salaried managers included? Are breaks paid? Are holiday costs and employer on-costs treated the same way? Are sales and wage figures prepared on a comparable basis? Do you know which trading hours produced the sales, rather than just the weekly total?
Then go down a level.
If one site has a weaker Saturday result, look at when hours were spent and what work was covered. Was lunch overstaffed? Did the late bar require stronger people? Was the building carrying training shifts? Did a booking cancel after publication?
A sound comparison can end with a decision to cut hours. It can equally end with moving them, training somebody or accepting a higher staffing cost at a fragile peak.
Group data should help an operator ask a better question.
Local exceptions need owners, reasons and an end date
Central rules become more credible when departures from them are visible.
Suppose the standard says a particular type of venue should run two supervisors on Saturday evening, but one GM wants three next month. There may be an excellent reason: a new management team, terrace reopening or run of large events.
Allow the exception, but ask for its operational reason, extra cost and review date.
The third supervisor might be needed for four Saturdays while somebody develops. If they remain forever without reconsideration, a temporary training decision has quietly become a permanent wage commitment.
The reverse deserves scrutiny too. If a GM wants to remove a standard position, they should explain what work disappears, who absorbs it and how the site will know whether it worked.
This is where sensible autonomy beats both extremes. A manager makes local decisions without seeking permission for every shift, while an Ops Director sees exceptions that genuinely change the risk or cost of the week.
Keep this lightweight. A two-line explanation and a review date are more useful than a fourteen-stage approval process nobody follows during service.
Give every venue the same questions, not the same answers
Every venue can start with the same information: trading hours, expected demand by service period, critical roles, employee capability, contracted and available hours, breaks, closing requirements and labour cost. Every venue checks the result against the same group rules before publication.
But the values inside those categories belong to the site.
A cocktail-led bar may need more independent stations at 9pm. A neighbourhood pub may put its strongest person on a Sunday roast. A large food hall may need somebody able to move between areas, while protecting the manager's capacity to coordinate the building. A late-night venue may need a longer close and a different plan for safe finishes.
Those choices require a good description of the operation, not a different corporate philosophy.
This makes handovers easier too. When a GM leaves, an incoming manager should inherit more than last week's rota and an assurance that Saturdays are usually busy. They should understand the venue's busiest periods, recurring jobs, skill dependencies and normal staffing patterns.
Could another capable manager understand the plan, spot the risks and adapt when trade moves? Or does it only work because one person remembers the third bartender always starts early when the football finishes?
The structure should be common enough for an Area Manager to inspect, and honest enough that a new GM can run a shift with it.
Try one Friday across three venues
Before rolling out a group template, run a smaller test.
Choose three venues that behave differently. Take the same Friday and ask each GM to map the two busiest hours, the positions requiring independent coverage and the work that regularly pulls people away. Keep cost definitions identical.
Compare the original plan with what actually happened. Did the rush arrive when expected? Were strong employees in the right places? Was the duty manager free to manage? Did the close run beyond scheduled hours? Which changes were made after publication?
Look for similarities worth standardising. Perhaps all three under-allocate time for glassware. Perhaps every site relies on supervisors to cover two jobs at once. Perhaps one GM has a better way to stagger starts and breaks.
Share the practice, explain the conditions in which it worked and let other venues test it over four rota cycles. Measure whether service, hours and team workload improve, rather than declaring success because everyone's spreadsheet now looks the same.
For a broader look at coverage, people checks, labour and rota handoffs, the free Rota Reality Check gives each site the same questions to examine. Its results are a starting point for discussion, not a substitute for the GM's knowledge of the floor.
One group can have several right answers
A multi-site business should expect common standards. Employees deserve consistent people protections. Finance needs numbers it can trust. Ops needs to recognise a good rota and challenge a weak one, whichever building it comes from.
What the group should resist is turning that consistency into identical shifts.
Two venues can spend exactly the same on wages and cover entirely different amounts of useful work. Two venues can need different staffing costs to deliver the same service standard. A rota that works beautifully in one building can become a weekly rescue operation in another.
The central job is to make the reasons visible, then decide which differences are justified.
Give every venue the same standard of thinking. Let each venue build the rota its Friday actually needs.