Labour Shortages: How to Keep Staffing Costs Under Control

Labour shortages are costing you £100k a year—here’s how to stop it bleeding further

The problem isn’t just fewer bodies. It’s the domino effect: fewer staff means longer shifts, more overtime, higher turnover, and a kitchen or front of house that’s always one person short. The numbers don’t lie—if you’re paying £15 an hour for a full-time equivalent (FTE) and losing 10% of your team every quarter, that’s £100k a year in wasted wages before you even account for training new hires or the drop in service that chases away regulars.

The fix isn’t hiring more. It’s hiring smarter—and automating the tasks that eat up time without adding value. The goal isn’t to replace staff; it’s to free them from the grind of admin, repetitive orders, and manual checks so they can focus on what keeps customers coming back: speed, consistency, and a bit of human touch.

Start with the time-sinks. A server spending 15 minutes an hour writing up orders, reconciling tabs, or chasing down missing items isn’t serving tables—they’re stuck in a paperwork loop. That’s £300 a week in lost revenue per server, or £15,600 a year. Multiply that by your team, and you’ve found your first leak.

The second leak is in the kitchen. If your cooks are spending 20% of their time waiting for orders, checking stock levels, or arguing over what’s been sent back, that’s not just lost productivity—it’s lost margin. A busy kitchen runs at 90% efficiency; yours might be at 70%. That’s the difference between a £50k and a £150k annual food-cost bill on a £1m turnover.

Automation isn’t about robots taking jobs. It’s about giving your team the tools to do their jobs better. A till that auto-suggests modifiers (“Would they like garlic bread with that?”) cuts down on “I’ll have the same” orders that hide upsell opportunities. A kitchen display that flags missing items before they hit the pass stops the “Where’s my order?” chaos. And a system that tracks labour costs by shift, branch, and even individual table lets you see exactly where you’re overspending—not just in wages, but in wasted time.

The trade-off? You’re not just saving money; you’re improving service. A server who isn’t drowning in paperwork serves faster. A cook who isn’t guessing what’s coming next makes fewer mistakes. And a manager who can see real-time labour costs in a dashboard isn’t playing guesswork roulette with payroll.

But here’s the catch: not all automation pays off. If you automate the wrong thing—like replacing a loyal barback with a self-ordering kiosk—you’ll lose the institutional knowledge that keeps your team running smoothly. The rule is simple: automate the repetitive, not the judgemental.

What actually costs more: understaffing or overstaffing?

Most operators assume understaffing is the bigger risk. It’s not. Overstaffing is the silent killer of margins—and it’s easier to do than you think.

Here’s how it happens: you hire for peak hours, but your off-peak shifts are still running at 80% capacity. That’s fine until you realise your average order value drops by 20% after 8pm, and suddenly you’re paying for labour you’re not using. Or you schedule a team based on last month’s sales, only to find this month’s footfall is down 15%. Now you’re overstaffed and underperforming.

The numbers don’t lie. Say you’re paying £12 an hour for a 4-person team during a 3-hour lunch shift. That’s £144 an hour in labour—before tips, before overtime. If your average table turnover is 45 minutes and you’re serving 12 tables in that time, you’re at £12 per table in labour alone. If your food cost is 30% and your profit margin is 10%, you’ve just eaten half your potential profit on that shift.

Overstaffing also kills morale. A team sitting around waiting for orders gets restless, makes mistakes, and starts looking for other jobs. Turnover isn’t just about hiring costs—it’s about the hidden cost of training replacements while your service suffers.

The fix? Schedule by actual demand, not guesswork. Use your POS data to see which hours are truly busy—and which aren’t. If your sales drop by 30% on a Tuesday evening, why are you still scheduling four servers? If your kitchen can handle 20 covers an hour but you’re only hitting 15, you’re overstaffed.

Here’s the worked example:

Current setup: 4 servers, £12/hour, 3-hour lunch shift = £144/hour labour cost.
Actual demand: 12 tables in 3 hours = 4 tables/hour. At £12/hour labour per table, you’re paying £48/hour for what you should be paying £48/hour for. That’s £96/hour wasted.
Optimised setup: 2 servers for the first hour (when tables arrive faster), 1 server for the second hour (when turnover slows), and 1 server for the last hour (when covers thin out). Labour cost drops to £72/hour—half of what you’re currently paying—for the same output.

The catch? You can’t do this with a spreadsheet. You need a system that tracks labour costs per table, per hour, and per branch. If you’re running multiple locations, one size doesn’t fit all—your high-street café might need more staff at weekends, while your cloud kitchen can run leaner with rider-only shifts.

The hidden cost of shift swaps and last-minute calls

Shift swaps aren’t just an inconvenience. They’re a margin killer—and they’re getting worse. That’s not just the cost of paying someone extra to cover; it’s the cost of disrupting your entire schedule.

Here’s how it adds up:

The direct cost: You pay £15/hour for a cover, but the swap means you’re now paying £22.50/hour (£15 for the original staff member plus £7.50 for the premium rate you have to offer to get someone in at short notice). That’s a 50% increase on labour for that shift.
The ripple effect: The person covering the shift is often less experienced, which means more mistakes—wrong orders, slower service, or even food waste if they’re not used to your kitchen’s workflow. At £30 per table in lost revenue from errors, that’s £300 a month if swaps happen twice a week.
The morale cost: Your regular team sees the favouritism, resents the chaos, and starts looking for stability elsewhere. High turnover isn’t just about hiring; it’s about the culture of unpredictability you’re creating.

The fix isn’t to ban swaps. It’s to control them. Start by setting a policy: no swaps within 48 hours of the shift, and no more than two swaps per month per staff member. Then, use your scheduling software to flag potential conflicts before they happen. If you see three people trying to swap out of the same shift, you’ve got a problem—and it’s usually a sign that your original schedule was wrong.

Here’s the worked example for a medium-sized café:

Current swap cost: 2 swaps per week at £7.50 premium = £150/week in extra labour.
Error cost: 1 extra mistake per swapped shift (wrong order, slow service) = £30 lost per table × 2 tables = £60/week.
Total hidden cost: £210/week, or £10,920 a year.

If you cut swaps by 50% by enforcing a 48-hour rule, you’ve just saved £5,460 a year—without firing anyone or reducing hours.

The other lever? Incentivise reliability. Offer a £20 bonus for every month a staff member doesn’t swap shifts. It’s not charity; it’s an investment in stability. A team that knows they’ll get paid for showing up will show up.

How to spot (and fix) your biggest labour waste

You know you’re wasting labour when:

Your servers spend more time writing orders than serving tables.
Your cooks are arguing over missing items instead of cooking.
Your managers are playing detective, trying to reconcile the day’s sales with what actually left the kitchen.
Your till system forces staff to re-enter orders because the connection dropped.

The first step is tracking where time is being lost. If your POS doesn’t give you a “time per order” report, you’re flying blind. Here’s what to look for:

Task	Time Lost (per hour)	Cost (at £12/hour)	Annual Cost (40-hour week)
Manual order entry	15 mins	£3/hour	£5,200
Chasing missing items	10 mins	£2/hour	£3,460
Reconciling tabs	20 mins	£4/hour	£6,920
Shift handover delays	15 mins	£3/hour	£5,200

That’s £20,780 a year in wasted labour—before you even account for the customers who leave because service is slow.

The fixes are specific:

For manual order entry: Use a tablet-based ordering system that syncs with your kitchen display. If a server can take an order in 30 seconds instead of 2 minutes, that’s 15 minutes back per hour—enough to serve an extra table.
For missing items: Implement a kitchen display that flags “sent back” orders in real time and auto-reassigns them to the right cook. No more “I didn’t get that” arguments.
For tab reconciliation: Switch to a system that auto-calculates splits and tips. If your servers aren’t spending 10 minutes per table reconciling payments, they’re serving more tables.
For handover delays: Use a digital shift log where the outgoing team can tick off tasks (e.g., “stock checked,” “equipment cleaned”) before leaving. No more “I thought you did that” moments.

The key? Measure before you act. If you don’t know where the time is going, you can’t fix it. And if you’re not tracking labour costs per table, you’re leaving money on the table—literally.

The labour cost you’re not tracking: training and turnover

Hiring costs are easy to see. Training costs? Not so much. And turnover? That’s the real hidden drain.

Here’s the maths:

Hiring cost: £500 per new hire (advertising, interviews, onboarding).
Training cost: 40 hours at £12/hour = £480 to get someone up to speed.
Lost productivity: A new hire works at 60% efficiency for their first 3 months. That’s £1,800 in lost revenue if they’re serving tables.
Total cost per hire: £2,780.

Now multiply that by your turnover rate. If you lose 20% of your team every year, that’s £27,800 a year in wasted labour—just to keep the doors open.

The worst part? High turnover isn’t just about money. It’s about consistency. A team that’s always changing means your food quality fluctuates, your service slows down, and your regulars start going elsewhere. And once they’re gone, they’re not coming back.

The fix starts with retention. Here’s what actually works:

Pay fairly—but not just in wages. A £1/hour premium over market rates won’t stop turnover. What does? Flexible hours, free meals, and a clear path to progression. If your best servers see a dead end, they’ll leave.
Reduce the grind. If your staff are working 50-hour weeks with no breaks, they’ll burn out. Schedule in buffer time—even 15 minutes between shifts to reset. A tired team makes mistakes, and mistakes cost money.
Give them ownership. Let servers suggest menu tweaks, or let cooks lead a “waste audit” to cut food costs. People stay where they feel valued.
Track the right metrics. Don’t just measure turnover. Measure why people leave. Exit interviews aren’t just HR box-ticking—they’re your early-warning system.

Here’s the worked example for a 20-seat restaurant:

Current turnover: 25% per year = 2.5 hires/year at £2,780 each = £6,950/year.
After fixes: Turnover drops to 10% = 1 hire/year at £2,780 = £2,780/year.
Savings: £4,170/year in direct costs, plus the intangible cost of keeping regulars happy.

The other lever? Cross-train your team. If your servers can also bus tables and your cooks can handle the fryer, you’ve got flexibility. No more “I can’t cover because I’m only trained on the grill” excuses.

What breaks when you cut labour costs?

The biggest risk isn’t that service will suffer—it’s that you’ll cut the wrong things. Here’s what happens when you go too far:

Service slows down. Customers wait 10 minutes for their food, then leave and never come back. The cost? £50 per lost regular, multiplied by how many you chase away.
Quality drops. Understaffed kitchens rush orders, leading to more complaints and refunds. At £20 per refund, that’s £2,080 a year if it happens 4 times a month.
Staff burn out. A team working flat-out with no breaks makes mistakes, calls in sick, and quits. The cost? See the turnover section above.
You lose control. Without enough eyes on the floor, you can’t spot waste—food spoilage, over-pouring drinks, or staff stealing. That’s £3,000 a year in hidden losses for a medium-sized café.

The solution? Cut smart. Focus on:

Automating the repetitive. Use a self-ordering system for simple items (burgers, pizzas) to free up servers for high-touch tables.
Optimising shifts. Schedule by actual demand, not guesswork. If your lunch rush is 11am–1pm, don’t schedule extra staff at 10am.
Training for efficiency. Teach your team to work smarter, not harder. A server who knows how to upsell without being pushy makes more per hour.
Measuring the right things. Track labour cost per table, not just total wages. If you’re spending £15 in labour for a £25 table, you’re overstaffed.

The red line? Never cut labour below 70% of your peak capacity. Below that, and you’re not just saving money—you’re losing customers.

Frequently asked questions

How do I know if I’m overstaffed or understaffed?

Check your labour cost per table. If you’re spending more than 30% of your revenue on labour during peak hours, you’re overstaffed. If your average wait time is over 10 minutes during peak, you’re understaffed. Use your POS data to compare sales per hour with labour costs per hour—if labour costs are rising faster than sales, you’ve got a problem.

Can I really save money by cutting shift swaps?

Yes—but only if you enforce rules. Start with a 48-hour notice period for swaps, and cap the number of swaps per staff member. The cost isn’t just the extra wages; it’s the errors and lost revenue from rushed service. Track your swap rate for a month, then calculate the hidden cost of each one.

What’s the fastest way to reduce training costs?

Cross-train your team so one person can cover multiple roles. For example, train your servers to bus tables and your cooks to handle the till during quiet periods. This cuts turnover (because staff are more flexible) and reduces the time it takes to bring someone up to speed.

How do I stop staff from calling in sick last-minute?

Offer incentives for reliability, like a £20 bonus for every month without a sick day. Also, make sure your schedule isn’t the problem—if shifts are too long or too early, people will call in sick to avoid them. Use your scheduling software to flag unfair shifts before they’re assigned.

What’s the biggest mistake operators make when cutting labour costs?

Assuming that fewer staff means instant savings. The real cost is in service quality and morale. Always measure the impact on wait times, order accuracy, and customer complaints before you make permanent cuts. If your regulars start going elsewhere, you’ve cut too deep.

Start by pulling your labour reports for the last three months. Look for the shifts where labour costs exceed 35% of revenue—that’s where you’re bleeding money. Then, pick one area to fix: either automate the order-taking, optimise your shifts, or reduce turnover. Small changes add up, but only if you measure them.

If you’re using spreadsheets to track this, stop. You need a system that gives you real-time labour costs per table, per shift, and per branch. Berryin’s labour analytics let you see exactly where you’re overspending—and where you can save without sacrificing service.