Understaffing costs more than the shift you saved

The weekly labour report looks good: Friday dinner ran with one server fewer than usual, and the saving shows clearly in the wage bill. What the report does not show is the table of six who waited twenty minutes for menus and left after starters, the desserts nobody had time to suggest, the two dishes comped for long waits, the regular who did not book again and the server who worked the whole night without a break and handed in her notice the following week. Understaffing costs more than the shift you saved, but the cost appears in places the labour report never looks.

Cutting a shift is one of the quickest ways to reduce labour cost, and sometimes it is right: a quiet night with too many people on is money wasted. But on a busy service, one person short starts a chain of effects that cost far more than the wages saved. The saving is certain and visible; the costs are spread across sales, service and staff, and are easy to miss.

This guide covers what one person short does to speed of service, spend per head, mistakes, the team and staff retention, how to price it out in a worked example and how to tell a sensible cut from a costly one. Every venue and figure in it is an example.

The saving from a cut shift is easy to see. Six hours of a server's time at twelve pounds an hour is seventy-two pounds, plus employer costs. On a busy week, cutting one shift on each of three nights saves over two hundred pounds. It shows up in the labour cost the next morning.

That is why understaffing is tempting. The saving is precise and immediate; the costs are vague and delayed. A manager under pressure to control labour cost sees the first and rarely the second.

One person short on a busy service sets off a chain. Each remaining person has more tables, more tickets or more tasks. Things take longer: greeting tables, taking orders, cooking, running food, clearing, bringing bills. Small delays add up, and the service falls behind.

Once behind, it is hard to catch up. Guests wait longer, tables turn more slowly, the team has no time for the extras that raise spend and mistakes creep in. The effects reach the guests, the takings and the team, all on the same night.

The first casualty is speed of service. With fewer people, tables wait longer to be greeted, to order, to be served and to pay. A wait of a few extra minutes at each step adds up to a much longer evening, and guests notice.

Speed of service is not about rushing guests; it is about removing waits they did not want. Our guide to speed of service without rushing anybody covers where those waits come from. Understaffing adds to almost all of them at once.

In the kitchen, one cook short means each station handles more tickets, and the slowest station sets the pace for every table. Ticket times rise, plates wait at the pass and the timing between courses drifts. On a busy night, a ten-minute rise in ticket times is common.

Long ticket times affect guests directly, as late main courses and long gaps, and indirectly, by slowing table turns and leaving the floor team apologising for delays.

On the floor, one server short means more tables each, and tables waiting at every stage: for menus, for drinks, for orders to be taken, for food to be run, for plates to be cleared, for the bill. Guests who catch a server's eye and are told "I'll be right with you" for the third time begin to feel neglected.

The waits that frustrate guests most are often at the end: waiting to order dessert, waiting for the bill, waiting to pay. They leave the evening's last impression, and they are exactly the waits a stretched team struggles to avoid.

Slower service means slower table turns. A table that would have left at half past eight leaves at nine, so the next booking waits or cannot be seated. Walk-ins are turned away because tables are not ready. On a busy night, the venue serves fewer covers than it could have.

Even a few lost covers on a busy night cost more than the shift saved. At forty pounds a cover, eight fewer covers is over three hundred pounds of sales, most of it margin, because the kitchen and room were already paid for.

A stretched team has no time for the things that raise spend per head: suggesting a drink, describing the specials, offering a second bottle, recommending a dessert, mentioning coffee. Guests who are not asked often do not order. Some skip dessert simply because nobody came to the table in time.

A small fall in spend per head across a full room adds up. Three pounds less per guest across 120 covers is 360 pounds, on top of the covers lost to slow turns.

Rushed teams make more mistakes: wrong orders, missed modifiers, dishes sent to the wrong table, allergens not passed on. Each mistake means a remake, which uses ingredients and time and slows the kitchen further, and some mean a gesture to put things right.

Allergy mistakes are the most serious. A team stretched too thin is more likely to miss an allergy note, and the consequences can be far worse than any cost on a spreadsheet.

Long waits and mistakes lead to gestures: a round of drinks for a table kept waiting, a dish taken off the bill, desserts on the house. They are the right response, but they have a cost, and on an understaffed night there are more of them.

Look at comps and remakes on short-staffed nights compared with fully staffed ones. The difference is part of the cost of the saved shift, and it is often larger than expected.

Guests who have a slow, disorganised evening tell people. Some complain on the night, some write reviews and many simply do not come back. A review that mentions "understaffed and chaotic" is seen by many potential guests, long after the shift that caused it.

The cost of a lost regular, or of the guests who read the review and chose somewhere else, never appears on a labour report. It is real nonetheless, and over a year it can outweigh many saved shifts.

Understaffing often leads to overtime: the people on shift stay late to clear up, come in early to catch up on prep, or are asked to cover the next shift too. Overtime is often paid at a higher rate, and it can quickly cancel out the saving from the cut shift.

Watch overtime alongside the rota. If cutting a shift leads to longer hours for everyone else, the saving may be smaller than it looked, or gone entirely.

The heaviest cost often falls on the team. A shift spent short-staffed is exhausting: more tables, no breaks, apologising to guests, covering for the missing person. One such night is manageable. Week after week, it wears people down.

Tired, stretched teams are less patient with guests and with each other, more likely to make mistakes and more likely to call in sick. The atmosphere of the whole venue suffers.

Repeated understaffing is one of the most common reasons good staff leave. People who feel they are always covering for missing colleagues, never get a proper break and are blamed for slow service they could not prevent start looking for a job elsewhere.

Staff retention is cheaper than recruitment. Our guide to staff retention: the four reasons people leave covers why people go, and workload is near the top of the list.

When someone leaves, the venue pays to replace them: time spent recruiting, interviewing and training, shifts covered at overtime rates while the post is empty, and lower productivity while the new person learns. The broader measure of how often staff leave is known as employee turnover, and in hospitality it is often high.

A single resignation can easily cost a venue more than many weeks of saved shifts. If understaffing pushes even one good person to leave, the saving has been wiped out several times over. Our guide to hiring restaurant staff who stay past August covers recruiting when it happens.

To see the real cost, add up the effects of the short-staffed service: covers lost to slow turns, multiplied by gross profit per cover; the fall in spend per head, multiplied by covers; extra comps and remakes; extra overtime; and a share of the cost of any resignation or lost regular that the strain helped cause.

The numbers will be estimates, but even rough ones are revealing. Set them against the wages saved by the cut shift. On a busy night, the costs usually come to several times the saving.

Labour cost percentage, labour cost divided by sales, can make understaffing look good. On a short-staffed night, labour cost is lower and, if sales hold up, the percentage falls. The report shows an efficient night, even if guests waited, spend fell and the team was exhausted.

Read labour cost percentage alongside measures of service, such as ticket times, comps and spend per head. A low percentage with slow service is not efficiency; it is a cost moved somewhere the percentage does not see. Our guide to labour cost percentage, by service not by month covers how to read it.

Understaffing tends to cluster in predictable places: the busiest services of the week, such as Friday and Saturday dinner and Sunday lunch; the weeks after holidays, when people are away; the start of a busy season, before extra staff are in place; and nights when someone calls in sick and is not replaced.

Knowing where it happens helps prevent it. The busiest services deserve the most care in the rota, and the weeks around holidays deserve cover planned in advance.

Several measures show understaffing before it becomes a habit. Covers per labour hour above its usual range, with rising ticket times, suggests the kitchen is stretched. More comps and remakes than usual on certain nights suggests the floor is. Spend per head falling on busy nights while it holds on quiet ones is another sign.

Our guide to covers per labour hour: the kitchen's real metric covers how to read output against hours. Looked at weekly, these measures show which services are short before the team tells you.

Cutting a shift is not always a mistake. On a quiet service with more people than the trade needs, a cut saves money with no effect on guests. The skill is telling the two apart: a quiet Tuesday with too many people on is overstaffed; a busy Friday with one person short is understaffed.

Use the forecast and past results to decide. If a service's covers per labour hour is well below its range and ticket times are fast, there is room to cut. If it is near the top of its range, cutting will cost more than it saves.

Work out the minimum team each service needs to run well: the number of cooks, servers, runners and hosts below which service suffers. It depends on the covers, the menu, the room and the style of service, and it differs between a quiet lunch and a busy dinner.

Treat the minimum as a floor that the rota does not go below on busy services. Cuts can then be made above it, on quiet services or quiet hours, where they save money without harming guests.

On the busiest services, build in a little buffer: one person more than the bare minimum. It covers the unexpected, such as a large walk-in party, a sick call or a rush that comes earlier than forecast, without the whole service falling behind.

The buffer costs a few hours of wages. Without it, one surprise on a Friday night can cost a great deal more in lost covers, comps and goodwill.

When someone calls in sick, the cheapest response is often to find cover quickly rather than run short. Keep a list of people willing to pick up extra shifts at short notice, and the roles each can cover, so the gap can be filled within an hour.

Spread the extra shifts fairly, rather than always asking the same reliable person, so cover does not become another source of strain. Our guide to a staff rota that survives first contact covers handling gaps.

The team knows when a service is understaffed long before any report does. Ask them after busy nights: did we have enough people? Where did it fall behind? Their answers often point straight to the shift that needs another person.

Listening also matters for retention. A team that sees managers acting on their feedback about staffing is far more willing to cope with the occasional short night, because they trust it is the exception rather than the plan.

A stretched team is more likely to cut corners on safety: rushing around hot oil and sharp knives, skipping cleaning between tasks, missing the temperature checks that keep food safe. The risks are real, and the consequences can be far more serious than slow service.

Make sure the minimum team for each service is enough to work safely, not just quickly. A service that can only run by cutting safety corners is understaffed, whatever the numbers say.

New starters suffer most on understaffed services. Thrown onto a busy shift with no one free to help them, they make mistakes, feel overwhelmed and often leave within weeks. Each early departure means the cost of recruiting and training again.

Protect new starters' first shifts: put them on alongside experienced colleagues, on services with enough people for someone to help. A new starter who is supported is far more likely to stay.

An invented bistro cuts one server from Friday dinner, saving six hours at twelve pounds an hour: seventy-two pounds, about ninety with employer costs. That night, slower turns mean about eight fewer covers, at roughly twenty-six pounds of gross profit each: about 210 pounds. Spend per head falls by about three pounds across 120 covers, as fewer desserts and second drinks are suggested: 360 pounds of sales, around 240 of gross profit.

Two tables receive gestures for long waits, costing about sixty pounds, and the remaining servers stay forty minutes late. That is around 510 pounds of gross profit lost against ninety saved, before counting the regular who did not rebook and the server who, after several such Fridays, resigned. The bistro restores the Friday server and cuts an hour from its quietest weekday lunch instead.

servearound does not record hours worked or staffing levels: there are no timesheets or rotas, though rotas are coming, so who was on each service comes from your own rota. What it shows is the effect on service. Kitchen analytics show ticket times, median and P90, by day and hour and by station, the on-time rate against one fixed fifteen-minute mark and the remake rate, and order analytics show the comp and void rates and the comped checks with their value.

Payment analytics show revenue by hour and who collected it, the dashboard shows spend per cover against the previous period and table analytics show the median seating time, revenue per seated hour and the gap between seatings, so a short-staffed Friday can be compared with a fully staffed one. See Analytics.

On quiet services, often. On busy services, the costs usually outweigh the saving.

Speed of service, ticket times, covers, spend per head, mistakes, comps, overtime and the team.

Because it falls on a short-staffed night even when guests waited and spend dropped.

Add lost gross profit from fewer covers and lower spend, extra comps, overtime and a share of turnover costs, and compare with the wages saved.

Watch covers per labour hour, ticket times, comps and spend per head on busy services.

The fewest people a service needs to run well. Do not go below it on busy services.

Yes, one person above the minimum covers surprises.

Fill the gap from a cover list rather than running short.

Understaffing costs more than the shift you saved. The saving is visible on the labour report; the costs are spread across slower speed of service, longer ticket times, fewer covers, lower spend per head, more mistakes and comps, extra overtime and a tired team more likely to leave. One resignation can cost more than many weeks of saved shifts.

Price it out: lost gross profit from covers and spend, extra comps and overtime and a share of turnover costs, against the wages saved. Read labour cost percentage alongside service measures, set a minimum team for each service, add a buffer on the busiest ones, cover sick calls and make cuts on quiet services and quiet hours, where they genuinely save money.