A sick line cook doesn't cost you his wage — that was budgeted whether he showed up or not. He costs whatever it takes to fill his spot tonight, and that's a different number entirely.
Ask an owner when their kitchen last stood at full strength, and the answer comes hesitantly. Staff absence feels like something that just happens to you — a call at 9am, a shift rearranged at the last minute, a colleague quietly picking up an extra station. What rarely happens is anyone actually working out what that one absence cost.
That's not because it can't be calculated. It's because the feeling — "we sorted it, the shift went ahead" — creates the impression that nothing broke. But a shift that "goes ahead" one pair of hands short isn't a free fix: it carries a premium on the covering hours, it earns less revenue than a full shift would, and it hides a pattern that only becomes visible once you actually measure it.
This article walks through seven numbers that together decide what unplanned absence costs a hospitality business: the premium you pay to get a shift covered in a hurry, the revenue an understaffed shift never earns back, your own absence rate as the starting point, the Bradford Factor that explains why ten separate days off disrupt a roster far more than one long stretch, the roster float you need to absorb that without emergency cover every time, what it costs when only one person can run a station, and what it costs to have no plan at all.
It is not advice on sick-pay law — that varies from country to country and from collective agreement to collective agreement, and that's what your own accountant or payroll adviser is for. What it is, is arithmetic any venue can do for itself: what an unplanned absence costs tonight, how much float that calls for, and where that pattern shows up in your own roster.
Why this goes further than one phone call
The instinct is to treat staff absence as a people issue — something for a private conversation. Operationally it's mostly an ARITHMETIC issue: every unplanned absence sets off a chain of decisions, from "who do I call now" to "which dish comes off tonight's menu", and every link in that chain has a price tag.
The problem is that most of those price tags stay invisible because nothing books them separately. The extra overtime disappears into the general payroll line. The slower service disappears into a revenue figure that already swings from day to day. The only moment it becomes visible is when you put the two side by side — what this shift should have cost, against what it actually cost.
And the pattern is predictable enough to plan for, even though any single absence isn't. A venue that knows how many days a year it loses per staff member to sickness can build a buffer for that — instead of being surprised by the same phone call every time.
Staff guide The complete staff guide for your restaurant From rostering to retention: everything that keeps your team running, in one place. Read the guideThe 7 numbers
Seven numbers, in the order they actually hit a shift — from the morning phone call to next year's roster.
1. The replacement premium
When someone calls in sick, you don't pay their wage twice — that was already budgeted, whether it's paid by the business or by a sick-pay scheme (and exactly how that works varies hugely by country and collective agreement — check that with your own accountant). What you DO pay extra for is the premium to get that shift covered at short notice: overtime for whoever steps in, or the higher hourly rate of a temp.
For one missed shift of 8 hours, at a premium of 50% on top of the normal hourly rate, that's €62 extra — just to get that one shift covered. Multiply that by how often it has already happened this year, and it stops being a rounding error on the payroll.
2. The output you don't get back
An understaffed shift "gets through" because the team makes it work — but making it work isn't the same as running unchanged. One station down means slower tickets, dishes quietly pulled off the board once it gets busy, and a chef simplifying a course rather than letting the kitchen seize up.
Below is what that looks like in practice — one Saturday night, from the 9am call to the last guests turned away. The numbers are an illustration, not a measured statistic: every kitchen has its own bottleneck, but the pattern — slower, then less, then closed — repeats wherever a station runs short.
From the 9am phone call to the last guests turned away — an illustration of what one understaffed shift brings with it.
The call
The line cook running the grill calls in sick — two hours before the shift starts.
Doors open
The chef moves the strongest cold-section cook onto the grill. Cold starters now run on one pair of hands instead of two.
Tickets slow down
Average ticket times climb by roughly 9 minutes as the grill falls behind.
The menu gets simplified
The chef quietly stops firing the two dishes that need the grill's full attention — dessert and side upsell drops by roughly 15%.
Guests get turned away
The host starts turning down walk-ins rather than risk a 45-minute ticket — 6 covers that don't happen tonight.
This is an illustration of the pattern, not a measured average — every kitchen has its own bottleneck, but "slower, then less, then closed" repeats wherever a station runs short.
3. Your own absence rate
Days off per staff member per year is the number everything else here rests on — and it's a number you have to add up yourself, not one we're going to hand you. Hospitality typically runs a higher absence rate than the economy as a whole, but "higher than average" isn't a number you can build a buffer around. Only your own roster from the past year gives you that.
Simply add up the whole team's sick days over the last twelve months and divide by the number of full-time equivalents (FTE). That one number — days per FTE per year — is all the calculator further down needs to run the numbers for your own venue instead of an average one.
4. The Bradford Factor
Ten days off isn't always ten days off. One staff member out for ten consecutive days — flu, surgery — is one roster to rearrange, once. Another staff member who misses ten separate single days is ten 6am phone calls, ten shifts you still have to fill.
The Bradford Factor, developed at Bradford University School of Management, captures exactly that difference: B = S² × D, where S is the number of SEPARATE spells of absence and D is the total number of days. Ten single days gives 10² × 10 = 1000. One ten-day spell gives 1² × 10 = 10 — a hundred times lower, for the exact same number of days off. It's not a legal threshold, just a rule of thumb for spotting which pattern actually disrupts a roster.
The same ten days of absence — but a hundred-times-higher Bradford Factor, depending on how they fall.
Both staff members missed exactly ten days. From a scheduling standpoint they aren't comparable: ten separate days are ten 6am phone calls, one long spell is one roster to rearrange, once.
5. The float you actually need
Once you know how many days a year the whole team misses on average, you can work out how much roster slack you need for that structurally — not as an emergency fix each time someone's out, but as a standing part of the plan.
Take the team's total absence days and divide by the number of working days one full-time staff member covers in a year on average (roughly 225, after weekends, public holidays and their own leave). For a team of 14 people each averaging 9 absence days, that's 0.56 FTE — about 21 hours a week spread across the roster. Not an extra hire, but a buffer you plan for on purpose instead of improvising.
6. The single-point-of-failure cost
Some absences don't cost a premium — they cost the shift itself. If only one person can run the sauce station, or knows the booking system, or is the only one who actually understands the allergen chart, that shift doesn't shrink when they're out — it stops at that point.
That's exactly what the skills & cover matrix makes visible: which stations in your venue run on exactly one pair of hands. Every one of those is an absence you can never fix with a premium, because there's nobody to hire in at any rate.
7. The cost of not having a plan
The most expensive kind of absence is the one that never becomes one: someone sick coming in anyway because there's nobody to cover for them. Short-term that costs nothing visible — the shift is covered — but it lengthens recovery, and in a kitchen it's also a real food-safety risk.
EU Regulation (EC) No 852/2004 is explicit about this: anyone posing a contamination risk may not work in areas where food is handled until that risk has passed. Exactly what your team is owed and entitled to during sickness — what percentage of pay, from which day, paid by whom — varies hugely by country and collective agreement; that belongs in your own contracts and with your own payroll provider, not in this article. What does hold everywhere is that a venue with no plan leaves that choice to the sick staff member themselves — and that choice rarely favours the kitchen.
Run the numbers for your own team
The numbers above are an example — your team, your hourly rate and your own absence rate aren't. Enter your own figures below and see straight away what a year of emergency cover costs and how much float you need to absorb it structurally.
Below that sits a separate Bradford Factor calculator: enter one staff member's number of separate spells and total days off, and see instantly whether that pattern deserves a conversation or is simply part of life.
The staff absence cost calculator
Enter your own team — the numbers start filled in with an example, but every one is editable.
—
Every amount is the EXTRA cost on top of the wage that was already budgeted — never the covering staff member's full wage. What an absent staff member is paid themselves varies by country and collective agreement and isn't part of this figure.
Bradford Factor for one staff member
Enter the number of separate spells and the total number of days.
This is a scheduling rule of thumb from Bradford University School of Management — not a legal threshold, and not a tool for judging any one person. It says something about the ROSTER, not about the reason for the absence.
The "float" figure above is an average, not a guarantee — it spreads a year of absence evenly across the roster, while a real year comes in waves (a flu season, a stomach bug going round). That's exactly why the Bradford Factor sits alongside it: it catches the clustering a yearly average never shows.
Keep the annual replacement-premium figure somewhere you can find it easily. It's the number that decides between "we'll sort it out" and a structural buffer you deliberately build into the roster.
Your absence action plan
Three steps, from this week to next year's roster.
This week
- Add up the whole team's sick days over the last twelve months and divide by FTE — that's your own absence rate.
- For every absence this month, note how it was covered: overtime, a temp, or a colleague picking up an extra station.
- Open the skills & cover matrix and mark every station that runs on exactly one pair of hands.
This month
- Work out the Bradford Factor for anyone with more than two absences this year, and plan a conversation with anyone above 400.
- Run the roster-float calculator above with your own numbers instead of the example.
- Decide who on your team is called first when someone's out — and a second name for when the first can't either.
This year
- Build the float the calculator points to structurally into your roster, instead of improvising it every time.
- Compare the annual replacement-premium figure with what a standing on-call staff member would cost — past a certain buffer, that's often cheaper.
- Repeat this calculation every year: an absence rate you noted down five years ago says nothing about your team today.
In conclusion
Staff absence feels like a problem of the day itself — someone calls in, someone else sorts it. But the costs that come with it aren't a daily surprise: they're an annual, addable figure the moment you put them side by side.
The good news: it's arithmetic, not guesswork. Once you know your own absence rate, the rest is a matter of the right formulas — a premium per shift, a Bradford Factor per staff member, a float per team.
This article doesn't replace an HR policy or legal advice on sick-pay law. What it does do is hand you the questions to ask your own roster: what did my last unplanned absence actually cost me, and who is the only person who can run that station?