Staff shortages in hospitality: delivering an experience with fewer people
Almost every venue is running tighter than five years ago. You don't notice it in the food, because the kitchen holds up. You notice it in the dining room: less time per table, longer waits to order something, and less room for the chat that makes a visit personal.
The reflex is to work harder. That holds up for a while and then costs you people. The other route is looking at what work can be taken away without the guest missing out on anything.
Where the pressure really lies
If you walk through a night, you'll notice that most interruptions don't come from the order itself but from the waiting around it:
- Guests raising their hand for something small and waiting five minutes until someone walks past.
- Impatience at tables where the food is taking a while, leading to extra questions for the wait staff.
- Chasing reviews afterwards, usually by email and usually without result.
- Kids getting restless, which the wait staff have to work around.
None of those four is actual service. It's all work that arises because something else isn't running smoothly.
What you can take away
Reordering without waiting
A button on the table that lets a guest order an extra drink removes the main source of hand-raising. The order comes in where it belongs, and the wait staff make one trip instead of two.
Waiting time that fills itself
A table with something to do calls out less. Games on the table require no action from your staff whatsoever: no materials, no explanation, nothing to clear away. See how it works.
Reviews at the right moment
Asking while the experience is still fresh delivers more than a follow-up email, and costs no one any time.
What you want to take away isn't the contact with the guest, but the waiting that eats into that contact.
Keeping people is cheaper than finding people
Replacing a staff member costs a job ad, interviews, training time, and a period where the rest of the team picks up the slack. Reckon on six to eight weeks before someone is as fast as the person who left. In those weeks, quality drops in everything that person touched.
That makes the maths different from how it looks. Any measure that lightens the workload pays for itself as soon as it prevents one departure a year.
Why people really leave
Rarely for the pay alone. What keeps coming up in exit interviews:
- Rosters that are published too late to plan anything around.
- Shifts where you're structurally short-staffed, so nothing can be done properly.
- The feeling that guest complaints land on you while you can't change anything about them.
- No moment at all to catch your breath between two rushes.
The first two are about planning. The last two are about how much the work costs you, and that's exactly what this article is about.
Rostering on the moments, not the hours
Most rosters are built around opening hours: one person starts at five, another at six. But the pressure in a dining room doesn't spread evenly across the night.
There are three peaks, and they're all short: the moment the first tables come in and all want to order at once, the moment the first mains go out, and the moment three tables want to pay at the same time. Between those, it's quieter than it feels.
Anyone who builds their staffing around those three peaks instead of spreading it evenly across the night gets more breathing room with the same hours. That does require knowing when those peaks fall at your place, and that differs by venue and by day.
What the staff themselves notice
There's a difference between a heavy shift and an unpleasant shift, and that difference isn't in the number of plates.
- A shift where you go from A to B and finish it off feels light, even if there's a lot of it.
- A shift where you're called away halfway through three times feels heavy, even if there's less of it.
- One guest getting impatient costs more energy than five guests who don't.
Anything that lowers the number of interruptions lowers the perceived workload as a result. That's not a soft win: it's the main reason people leave hospitality.
What you shouldn't automate
There's a line, and it's sharper than the providers of these kinds of systems suggest. These three should stay human work:
- The welcome. A guest who walks in and is greeted by a screen starts at a disadvantage.
- The moment something goes wrong. A well-resolved mistake often earns a higher rating than a flawless visit, but only if there's a person on the other side of it.
- The farewell. That's the last thing someone takes away with them.
Everything in between is largely logistics, and logistics can be made easier.
What it gives your staff
Fewer interruptions means less running around and fewer moments where someone gets called away halfway through something else. That saves you physically, but mostly mentally: it's the constant switching that makes a shift heavy, not the number of plates.
And it gives back something that's the first to go with a tight roster: time for the conversation at the table that guests remember.
What this costs for your number of tables is on the pricing page.
How do you offer good service with too few staff?
By removing the work that arises from waiting - hand-raising for a drink, impatience at the table, chasing reviews - and leaving the contact with the guest exactly as it is.
What shouldn't you automate in hospitality?
The welcome, resolving a mistake, and the farewell. Those are exactly the moments where a guest forms their opinion.
Does tabletop entertainment help with staffing pressure?
Indirectly. A table with something to do calls out for attention less often, and games via a QR code require no action at all from the wait staff.
What's the biggest hidden time-waster in service?
Constantly being interrupted. It's not the number of plates that makes a shift heavy, but how often someone gets called away halfway through something else.
Want to try table games yourself?
Give your guests more experience from day one.
