Blog ·

How to Reduce Restaurant Labour Costs Without Hurting Service

Cut restaurant labour costs without cutting service: measure the right numbers, match rotas to demand, cross-train, keep staff longer and trim admin time.

Restaurant manager reviewing rota and sales figures

The fastest way to reduce restaurant labour costs is to stop paying for hours that don’t serve a guest. That means rotas built around real demand, fewer staff leaving and being replaced, and less front-of-house time spent on repetitive admin such as phone calls, emails and booking messages. Cutting the headcount on a busy shift is the one move that usually backfires.

This guide walks through how to measure labour cost properly, where the avoidable spend hides, and what to change first. We run an AI host for restaurants, so we say where we fit in, but most of this works with any set-up.

Nomi
Spend Less Time on Guest Admin
Nomi helps restaurants handle repeat guest questions and reservation requests, so staff can focus on service while keeping control of decisions.
Explore Nomi

TL;DR

  • Count the full cost of labour (wages, overtime, employer on-costs, holiday pay) before you compare your percentage with anyone else’s.
  • Match staff hours to demand shift by shift. Sales per labour hour shows you which shifts are overstaffed and which are stretched.
  • Every leaver costs you recruiting, training and lost productivity, so retention is a labour-cost lever, not just an HR one.
  • Admin that interrupts service (calls, emails, DMs, booking changes) is paid time too. Write down your rules, then hand the repeatable part to a system or a rota slot.
  • Track service guardrails (complaints, ticket times, overtime) so a saving never turns into lost guests.

Table of Contents

Start with the real number

Most owners look at the rota total and call it labour cost. It is lower than the true figure. Labour cost covers wages and salaries, overtime, payroll taxes, benefits, workers’ compensation and payroll processing, and in the UK that means employer National Insurance, pension contributions and holiday pay as well. Another guide makes the same point: a roster total alone usually understates real labour cost once on-costs and leave accrual are added.

The formula is simple:

Labour cost % = total labour cost ÷ total sales × 100

A worked example from Lightspeed’s guide: $8,900 of labour on $27,500 of sales gives 32%. Run it weekly, not just monthly, so you can see the shape of the problem. A month that looks fine can hide two bad Tuesdays and one over-staffed Sunday.

What is a good percentage?

It depends on your format, and the published ranges are wide. In a 2025 survey reported by Chain Store Age, about 40% of restaurants kept labour between 20% and 25% of revenue and another 26% between 26% and 30%. US National Restaurant Association figures put median labour cost at 36.5% of sales for full-service and 31.7% for limited-service restaurants. The EU’s RESTwithEU guidebook says labour usually makes up 30–40% of operating expenses in restaurants.

Treat these as a rough frame. Your own trend over the last 12 weeks tells you more than any national median, and the comparison is only fair if you include the same costs in the numerator.

Find where the hours go

A percentage tells you something is wrong. It doesn’t tell you which shift. Two simple checks do.

Sales per labour hour

Sales per labour hour (SPLH) is total sales divided by total labour hours. A drop on certain shifts can point to overstaffing, while a spike can mean the team is stretched thin and service is suffering. Work it out for each daypart, not for the week.

A simple example with made-up numbers: Tuesday lunch takes £600 with 40 labour hours (£15 per hour). Friday dinner takes £4,200 with 120 hours (£35 per hour). The gap tells you where to trim and where to protect.

Guardrails that stop you cutting too far

One operations guide suggests watching ticket time, guest complaints, order accuracy, table turn time, overtime and how often a manager has to step in. If these slip after you trim hours, the saving is false. Pick three, write down today’s numbers, and review them every fortnight.

Build the rota around demand

The rota is where most avoidable cost sits. Four habits help:

  1. Schedule from sales history. Use the same weekday and daypart from the last six to eight weeks, then adjust for bookings, local events and weather.
  2. Stagger starts and finishes. Prep and the first wave don’t need the full team at 5pm sharp. Close down in stages as covers drop.
  3. Set a budget per shift in hours, and check it daily rather than at month end.
  4. Stop copying last week’s rota. Demand moves, so the rota should too.

Be realistic about the target. One fast-casual guide suggests that a 7–12% SPLH improvement over six months is achievable without cutting service, while 15% or more usually needs menu or scheduling redesign. That is a US fast-casual benchmark, so a table-service restaurant should aim lower and measure its own baseline first.

Pool your tables, not just your people

Labour efficiency isn’t only about staff. A Cornell University simulation found that pooling reservations, assigning tables in real time rather than locking them at booking, can cut table turn times by 15 minutes more than 15% of the time. The same study’s survey of 425 restaurants found over 80% lock bookings to specific tables when the booking is made. Faster, smoother turns mean the same team serves more covers in the same hours.

Cross-train so you can run lean

A team that can only do one job needs cover for every gap. A cross-trained team can be thin on a quiet Tuesday and stretched on Saturday by moving people to where the activity is. One industry guide estimates that covering a callout internally rather than through overtime saves $30–$80 in premium pay each time. Treat that as an illustration, not a promise.

A KAIZEN case study of a quick-service network found that variability was driven less by volume than by unclear roles and too much multitasking. Defining primary and secondary responsibilities for each station reduced duplicated effort and improved handoffs. You can do a small version of this in an afternoon:

  • List every station and shift.
  • Name one primary person and one backup for each.
  • Note who is trained on what, and where the gaps are.
  • Train the biggest gap first.

Keep people longer

Hiring is labour cost too, and it hides in several budgets. Estimates for replacing one hourly restaurant worker vary a lot, depending on what is counted. One US source puts it at over $2,300 in hard separation, hiring and training costs, another at $5,864 including the productivity gap. Toast reports average industry turnover of nearly 80%, with low pay, poor management, lack of recognition and limited career growth among the causes.

The UK picture is similar. Gusto Italian reported FY25 staff turnover of 55%, which it described as 4 points better than the industry average, with a much lower figure for new hires in their first 90 days.

The cheap fixes are mostly management ones:

  • Pair every new starter with an experienced buddy for the first week. One source reports this cuts early exits by 35%, though that figure comes from Indian restaurants.
  • Give a clear first-week plan and a named person to ask.
  • Offer predictable rotas, published early.
  • Show people how they can move up.

The quiet connection to admin: staff who spend a busy service answering the phone with one hand and carrying plates with the other burn out faster. Taking that pressure away helps with retention as well as with hours.

Cut the admin that interrupts service

This is the part of labour cost that rarely appears on a rota. A booking call at 7:30pm pulls a host or a server away from a table. An email about a birthday group sits in an inbox until someone has time. A DM asking about allergens goes unanswered until Monday. All of it is paid time, and some of it loses you the booking.

The EU guidebook notes that online booking tools and digital channels reduce errors and remove the need for manual phone-in reservations. The principle holds whichever tool you use. Here is a practical order of work.

1. Write your rules down

A system, or a new member of staff, can only apply rules that exist. Write the largest group you take without a deposit, how long you hold a table, when the kitchen closes, how you handle allergies, and what you do about children and dogs. Our guide to restaurant booking rules to write down gives you a template, and it is useful whatever software you end up using.

2. Count the enquiries

For one week, tally every call, email and DM by type: availability, opening hours, menu questions, groups, changes, complaints. Most restaurants find that a large share are the same five questions. Those are the ones to standardise first.

3. Stop missing calls

A missed call at peak time is a missed booking. We cover this in how to stop losing tables to missed restaurant calls and seven ways restaurants lose bookings between 5pm and 10pm. If staff do answer, a consistent script helps, and you can start from how to take a restaurant reservation over the phone.

4. Reduce no-shows with confirmations

No-shows are wasted labour: you staffed for covers that never arrived. An Italian study of 300 restaurants reported by Ristorazione Moderna found a mean no-show rate of 12.8%. A €20 per-person deposit or pre-authorisation brought it to 5.4%, and automatic SMS, WhatsApp or email reminders cut it by a further 32%. Those are Italian results, so your own numbers will differ, but the mechanics carry over. See our guide to reducing no-shows with simple booking confirmations.

No-show rates after deposits and reminders

5. Pick one place for bookings

If reservations live in a diary, an inbox and a booking app at once, someone is paid to reconcile them. Our overview of restaurant reservation management and the comparison of reservation apps for small venues can help you choose. If guests book through Instagram, read booking tables from Instagram DMs. For busy walk-in services, there is also restaurant waitlist management.

A simple 30-day plan

Week Do this Measure
1 Calculate full labour cost % and SPLH by daypart Baseline for each
2 Tally every enquiry by channel and type; write your booking rules Enquiries per day, missed calls
3 Rebuild the rota for your two weakest dayparts; name backups for every station Hours per shift vs budget
4 Review guardrails; decide what to change permanently Complaints, ticket time, overtime

Change one or two things at a time. If you change everything at once, you won’t know what worked.

Where Nomi fits

We built Nomi because we kept seeing the same thing in restaurants: the owner is at the pass, the host is carrying plates, and guest messages pile up across the phone, email and social media. Nobody is doing a bad job. The rules just live in one head.

Our view is that guest communication should follow the restaurant’s own rules, not a generic script. That is why each business gives Nomi its own knowledge and guidance, and why the team stays in control of how it responds and which actions it can take.

We also think an AI host should know its limits. Nomi is designed to bring requests that need a human decision, such as allergies, complaints and large bookings, to your team rather than guess. That way the routine questions get answered, and your people spend their time on the guests in front of them.

Nomi Team

What Nomi does today

Nomi is an AI host for restaurants. It answers calls, emails and social media messages in multiple languages, using your own information and booking rules. It supports reservations through connected booking systems, can recognise returning guests within a venue, and flags requests that need a person: allergies, complaints and large bookings. It works around the clock, so a late-night enquiry doesn’t wait until morning.

It is designed to reduce the repetitive communication that eats into front-of-house time. We make no promise of a particular saving, because the effect depends on how many enquiries you get and how you staff today. Use the enquiry tally from week 2 above to judge it for your own venue.

What Nomi does today

Some things are on our roadmap rather than live: tracking requests and promises, coordinating group and event enquiries, personalised offers and follow-ups. We’ll say so when they ship.

Plans are published on the pricing page: Starter at €49 per month, Standard at €149 per month and Pro at €299 per month, with extra credits from €45 one-off per 500 credits. If you want to see how it handles email first, look at AI email replies for restaurants, or join the early access list.

Nomi

FAQ

What counts as labour cost in a restaurant?

It covers wages and salaries, overtime, payroll taxes, benefits, workers’ compensation and payroll processing, plus bonuses and paid time off, according to Toast’s guide. In the UK, think employer National Insurance, pension contributions and holiday pay. Include all of them before comparing yourself with any benchmark.

Is cutting staff hours the best way to lower labour costs?

Usually not on its own. Cutting a busy shift can hurt service and sales, which pushes your percentage up. Start with quiet dayparts, overtime, turnover and admin time, and watch complaints and ticket times as you go.

How do I reduce admin workload for front-of-house staff?

Write your booking and policy rules, count what comes in by channel, and standardise the repeat questions. Then hand the routine part to a single booking system, a set rota slot for messages, or an AI host such as Nomi. Keep a person in charge of anything involving allergies, complaints or large groups.

How long before I see a change in labour cost percentage?

Rota changes show up within a few weeks. Retention and training effects take longer. One guide suggests a 7–12% SPLH improvement over six months is realistic in fast casual, so track weekly and judge over a quarter.

Sources

Written with BabyLoveGrowth to grow AI visibility