What is a good labour cost percentage in hospitality — and how to track it weekly.

This guide covers what a good labour cost percentage looks like across hospitality segments, why the operators who win are tracking it weekly rather than monthly, and how to build automated reporting that makes weekly visibility possible without a finance team.

What counts as a good labour cost percentage in hospitality?

There is no single correct answer — it varies significantly by segment, service model and whether you include or exclude employer on-costs. The benchmarks below are based on total labour cost as a percentage of revenue, including employer National Insurance and pension contributions where applicable.

Quick-service and fast casual: 25–32%. Lower service intensity, higher throughput, tighter margins overall. Labour efficiency is critical. Anything above 34% in this segment is a red flag.

Casual dining and pub restaurants: 28–35%. The most common benchmark range for UK multi-site operators in this segment. A well-run casual dining site sits around 30–32%. Above 36% consistently indicates either a scheduling problem, a revenue problem, or both.

Fine dining and experience-led restaurants: 33–40%. Higher service ratios, longer shifts, more skilled labour. The premium on the menu covers it, but only if covers are consistent. Labour cost percentage is more volatile in this segment because fixed staffing costs do not flex with revenue as cleanly.

Hotels (food and beverage): 30–38%. Highly dependent on occupancy. A hotel F&B operation running below 75% occupancy will almost always see labour cost percentage creep above the top of this range because minimum staffing levels are essentially fixed.

Contract catering and workplace dining: 22–28%. Predictable volumes, fixed contracts, controlled menus. Labour efficiency is easier to achieve and expected to be tighter.

Why your labour cost percentage is probably higher than you think

Most hospitality operators calculate labour cost percentage using payroll data. The problem is that payroll data is typically two to three weeks behind reality. By the time you see last month's labour cost percentage, you are already halfway through the current month with the same patterns repeating.

A second issue is what gets included. Basic wages are easy to track. Overtime, agency cover, holiday pay accrual, employer NI and pension contributions are often either excluded or only captured at month end. A business reporting a 31% labour cost percentage on basic wages alone may be sitting at 36–38% when total employment costs are included.

The third issue is that labour cost percentage is meaningless without context. A site running at 33% on a high-revenue week looks very different from the same site running at 33% on a low-revenue week. The number that matters is not the percentage in isolation — it is the percentage relative to the revenue forecast, tracked in real time.

Why weekly tracking changes the conversation

Monthly P&L review is retrospective management. You are making decisions in week three of the current month based on data from the previous month. The operational response to a labour cost problem — adjusting rotas, reducing agency spend, redistributing hours across sites — needs to happen in the same week the problem emerges, not three weeks later.

Weekly labour cost reporting does three things that monthly reporting cannot.

It gives you time to act. A site running 4% above target in week one of a four-week period can be corrected by weeks two and three. The same problem spotted at month end cannot be corrected retroactively.

It creates accountability at site level. When site managers receive a weekly labour cost report for their site, the conversation about scheduling decisions changes. A number that lands weekly is a management tool. A number that lands monthly is a post-mortem.

It surfaces patterns faster. Seasonality, event-driven spikes, the effect of a new menu launch on kitchen labour — all of these are visible in weekly data. Monthly data smooths them out and makes it harder to understand what is actually driving cost movement.

What a weekly labour cost report needs to show

A useful weekly labour cost report is not a spreadsheet dump. It needs to surface the right numbers for the right audience quickly. For a multi-site operator, that typically means:

• Revenue for the week — actual vs. forecast, by site
• Total labour cost for the week — including employer on-costs, by site
• Labour cost percentage for the week — actual vs. target, by site
• Year-to-date labour cost percentage — to contextualise weekly movement
• Variance flag — any site running more than 2% above target highlighted automatically
• Comparison to the same week last year — particularly useful for seasonal businesses

The report should land in inboxes on Monday morning covering the previous week. By the time the operations team is in their Monday meeting, the numbers are already in the room.

How to automate weekly labour cost reporting

Most multi-site hospitality operators already have the data needed for weekly labour cost reporting. The problem is that it lives in three or four different places — payroll software, EPOS, rota management tools — and assembling it manually takes someone two to three hours every week.

The automated version of this report typically connects four data sources.

Payroll or rota data — actual hours worked and associated costs. If you use BreatheHR, Fourth, RotaCloud or a similar platform, this data is available via API or scheduled export.

Revenue data — usually from your EPOS system (Lightspeed, Tevalis, SYRVE and similar all have export capability). Weekly net revenue by site, pulled automatically.

A labour cost model — a Google Sheet that holds your site-level revenue forecasts, labour cost targets and on-cost rates. This is the one component that needs manual maintenance, but only when targets or rates change.

A reporting output — typically a Google Looker Studio dashboard that updates automatically each week, plus a scheduled email summary generated by Make.com that pushes the key numbers to the relevant people.

The Make.com scenario runs on a Sunday evening. By 7am Monday, the dashboard is updated and the email summary has landed.

What this looks like in practice

In a typical multi-site hospitality operation, the manual version of this process looks like this: someone spends two to three hours every Monday morning pulling data from payroll, EPOS and rota systems, assembling it in Excel and distributing it by midday. The numbers are accurate but the process is fragile — it depends on one person, breaks when they are on leave and produces a report that is already out of date by the time it lands.

The automated version runs on Sunday evening. By 7am Monday, the dashboard is updated and the email summary has landed in the right inboxes. The operations team walks into their Monday meeting with the numbers already in the room.

The difference in management behaviour is significant. When labour cost data lands automatically and consistently, site-level accountability improves, scheduling decisions get made earlier in the week and the conversation in the operations meeting shifts from "where are we?" to "what are we doing about it?".

What you need before building the automation

Before automating weekly labour cost reporting, three things need to be in place.

Clean data sources. The automation is only as good as the data it pulls from. If your rota system and payroll system do not reconcile, the automated report will surface the same discrepancies — just faster. Sort the data quality problem before building the automation.

Agreed targets by site. The report needs something to compare actual costs against. You need a labour cost percentage target for each site, updated at least quarterly. Without targets, the report shows you numbers but not whether those numbers are good or bad.

A clear distribution list. Who receives the report matters. Operations director and general managers at minimum. Finance director if they are involved in site-level performance. Keep the distribution tight — a report that goes to everyone gets read by no one.

If those three things are in place, the automation can be built and operational within two weeks.

The tools that make this work

The stack we use for weekly labour cost reporting in hospitality:

• Make.com — the automation layer connecting data sources and triggering the report
• Google Sheets — holds the labour cost model, targets and on-cost rates
• Google Looker Studio — the live dashboard, updated automatically each week
• BreatheHR or Fourth — payroll and hours data source
• Gmail or Outlook — report distribution

No bespoke software. No expensive BI platform. The total running cost of this stack, once built, is effectively zero.