In this article
Sometime this week, someone won't call, won't text, and simply won't show up for a shift that's already on the rota. The question isn't whether it happens — it's how often, why, and what it actually costs you to cover that spot the same night.
There's a real difference between an employee who falls ill and one who simply doesn't turn up. Illness has a name, a date, and usually a phone call in advance — this site already covered that under "sick leave costs". A no-show has none of that: at 4pm you don't know whether the person is on their way, unwell, stuck in traffic, or has simply forgotten the rota exists. The kitchen keeps moving, the floor fills up, and you're the one making calls.
That isn't a rare accident. Hospitality is structurally more exposed to no-shows than almost any other sector — physically demanding work, irregular hours, often a second job or a course alongside it, and, for a growing share of the workforce, a contract type that doesn't make a shift a hard obligation in the first place.
This article isn't about staff turnover, and it isn't about building the rota itself — this site already has separate pieces on both. It's about the moment the rota, already published, quietly falls apart.
Seven numbers, in this order: how often it really happens, two very different things that both get called a "no-show", what your own contract type does to it, what covering a missed shift costs on the night itself, the maths most restaurants never run, what prevention costs against what it saves, and the tail nobody prices separately: whether anyone else can actually do that job.
Why "we'll sort it out" keeps the problem in place
Most restaurants have no plan for a no-show, for the same reason as with a dine-and-dash: it's never been thought through explicitly. The first time it happens, everyone improvises — the head chef jumps behind the pass themselves, a colleague gets called in on their night off, or a whole station simply runs at half capacity.
Each time, that improvising feels like an exception. Added up over a year, it isn't: it's a recurring cost that never appears on any budget line, because each individual incident feels too small to bother recording.
The rest of this article builds on what's actually known: how often it happens, the distinction between two things that share one name, what your contract does to it, and the one investment that closes the gap fastest — not more staff, but staff who can cover for each other.
Free guide Everything about your team, in one guide From rota to turnover — the complete guide to the numbers behind your staff. Read the guide7 numbers most restaurants have never looked up
Each of these numbers holds up on its own. Together they explain why a no-show isn't bad luck you simply shrug off — it's a cost that the right two habits mostly keep in check.
1. How often it actually happens
Hard EU-wide figures for staff no-shows are scarce — nobody's official statistics agency tracks it. The clearest numbers come from the US, where it is measured at industry level: the Bureau of Labor Statistics recorded a 3.8% absence rate for food preparation and serving roles in 2024, and the sector saw a 146% jump compared with pre-pandemic levels.
Industry benchmarks put a well-run operation at 3–5%, against a typical 5–8% — more than double a standard office environment. This isn't a problem confined to one country: physically demanding work, irregular hours and a young or transient workforce are the same reality across European hospitality as anywhere else.
Run your own numbers: at 70 scheduled shifts a week and even a cautious 3% incidence rate, that's over two missed shifts a week. That's not an edge case anymore — that's something you need a habit for, not an improvisation.
2. Two very different things that both get called a "no-show"
The first is a new hire who disappears before their first shift. A US survey by Click Boarding of hospitality, retail and events workers found that 52% have ghosted an employer at some point in their career — simply stopped responding, no cancellation, nothing. Of that group, 60% did it after receiving a formal job offer, and 31% did it after accepting the job — in other words, after they were already on your rota.
That costs more than it looks like it should: between 75% and 90% of a hiring investment is lost at precisely that moment — after the offer, before the first shift. This is fundamentally a hiring problem, not a scheduling one, and the fix lives in how fast and how personally you stay in touch after an offer, not in the rota itself.
The second is the employee who's been on the team for months and simply doesn't turn up on an ordinary Tuesday. That's the problem the rest of this article focuses on: not a hiring miss, but a gap that has to be filled that same night.
Click Boarding's survey of hospitality, retail and events workers — each figure on its own base, explained as it goes.
This is the new-hire side of "no-show" — a completely different problem from number 7 below, where an existing employee misses a scheduled shift.
3. What your own contract type does to the odds
This is a house document, not legal advice — employment law differs sharply by country, and this number is exactly why that matters here. Under a standard employment contract, unauthorised absence carries disciplinary weight: a warning, a conversation, in the worst case a dismissal process. That weight creates a real threshold against simply not showing up.
Under a flexi-job — an increasingly large share of Belgian hospitality staffing, and mirrored by zero-hour and casual contracts elsewhere in Europe — that's different. The frame contract isn't itself a binding employment agreement; it's the framework inside which each individual flexi-job shift gets its own separate employment agreement. A shift that was never confirmed or accepted as its own contract structurally carries less of that disciplinary weight than a shift inside a standard job.
That doesn't make a flexi-job worker unreliable — most turn up just fine. It does mean that as flexi-style contracts grow as a share of your staffing, you're structurally leaning more on something other than disciplinary process to get shifts covered: good relationships, timely communication, and — see number 7 — enough people who can cover each other's work.
4. What covering a missed shift actually costs
A shift that falls through doesn't cost the wage that was already budgeted for it — you were paying that either way. It costs what it takes to fill the gap that same night: a colleague working overtime at a premium rate, a temp agency worker on short notice, or the head chef covering a station while their own job doesn't get done.
A commonly cited industry rule of thumb: staff brought in at short notice through overtime or a temp agency typically cost one-and-a-half to two times the standard hourly rate. That's an illustrative figure, not an accounting guarantee — your own overtime premium and agency rate may differ, and the calculator below lets you enter them.
What rarely gets counted: the manager's time spent making calls, and the quality of service itself while everyone picks up an extra station. That usually makes the real figure higher than whatever shows up on the payroll.
5. The maths most restaurants never run
Shifts per week, times an incidence rate, times the extra cost of covering one shift: that's your annual exposure, and most owners have never calculated it because each individual incident feels too small to bother with.
Run it below with your own numbers. The point isn't the exact figure — it's that a small percentage, spread across a full year of shifts, rarely stays as small as any single incident felt.
6. What prevention costs versus what it saves
Two investments shrink the problem, and neither is "hire more staff". The first is a small standby allowance for someone who agrees to be reachable as backup — a fixed, modest amount each month in exchange for having someone to call.
The second, and the cheapest over time: cross-training. This site has already covered that separately — an employee who can cover two or three stations is their own replacement for a colleague who doesn't show, with nobody extra needed on the floor at all.
Put that monthly cost next to the annual exposure from number 5. For most restaurants running a few dozen shifts a week, it isn't a close call — run it in the calculator above with your own numbers.
7. The tail nobody prices separately: who's left to cover it
A no-show on a station three people can cover is annoying but manageable: someone steps in, and the night carries on. A no-show on a station only one person knows how to run is a different problem entirely — that station simply goes dark, or you bring someone in from outside at a much higher cost.
That's exactly what this site's skills-matrix tool calls a "single point of failure" — a task exactly one person can do. The same tool flags every station where that's the case today, before a no-show ever happens.
The practical lesson: the real cost of a no-show doesn't depend on who's missing — it depends on who's left to cover it. That's a question you can answer today, not just on the night it goes wrong.
The same no-show, three different bills — depending on how many people can cover that station.
An illustrative ratio, not a precise measurement: with one backup, a colleague simply steps in; with zero, you pay the full premium for outside cover — or the station just goes quiet.
Run it for your own restaurant
Enter your own numbers. The incidence rate defaults to a cautious estimate within the industry range from number 1 — adjust it to match your own experience.
This isn't accounting, it's a thinking tool: the point isn't the exact figure, it's whether the "exposure" column outweighs the "prevention" column.
Annual exposure versus the cost of preventing it
Enter your own numbers — the rest does the maths.
—
Default incidence rate: 3% of scheduled shifts — a cautious estimate within the 3–8% range industry benchmarks report.
This is a thinking tool using your own numbers, not an accounting guarantee — swap out any assumption for your own experience.
What the tool doesn't do: distinguish between a new hire ghosting and a long-serving employee missing a shift. Look at number 2 above to see which one you're actually measuring — the fix differs.
And what it never replaces: number 7 still holds no matter what the maths says — a station with only one backup costs more on every no-show, whatever the calculator shows.
How to fix this tomorrow, without a whole new system
Three steps, in this order — not because the rest doesn't matter, but because these three change what a no-show actually costs you the fastest.
1. Separate the two problems
- Track new-hire ghosting on its own: how many accepted jobs never reach a first shift?
- Track existing-staff no-shows on their own: how many scheduled shifts actually fall through?
- Two different numbers need two different fixes — see number 2 above.
2. Close the gap where it's most exposed
- Identify which stations only one person can run — see number 7 and the skills-matrix tool above.
- Start cross-training there first, not at random — that's where a no-show costs the most.
- Weigh the cost of cross-training against the annual exposure from number 5, not against today's incident.
3. Run the maths yearly, not per incident
- Use the calculator above with your own shifts and cover-cost figures.
- Compare that amount against what a standby allowance or cross-training costs.
- Re-run it whenever your share of flexi-style contracts or your staffing mix changes meaningfully.
The short answer
A staff no-show isn't bad luck you simply write off — it's a recurring number, with two genuinely different causes that each need their own fix.
The fix is small compared with what it prevents: knowing which of the two problems you actually have, and having enough people who can cover each other on the stations that can't yet.
Start with the most exposed station, not the next incident — that's where a no-show costs the most, and where cross-training changes the outcome fastest.