Staff & Time Tracking

Time Clock Leaks: 4 Ways Restaurants Lose Untracked Hours

Six minutes clocked in early. Eight minutes clocked out late. A break that keeps running. Each one looks harmless on its own — together they're the hours that never make it onto the payroll.

In this article
  1. Why this isn't an overtime problem — it's a recording problem
  2. The 4 leaks, each with its own maths
  3. Calculate the leak in your own team
  4. Your action plan for the next team meeting
  5. Conclusion: four small leaks, one yearly figure

Your rota says a shift runs from 6pm to 11pm. What actually happens almost never lines up exactly.

The waiter arrives at 5:52pm so they don't have to queue at the clock. The chef doesn't clock out until 11:24pm, once the last pot is washed. Someone takes a fifteen-minute break but rarely presses the separate break button, so that time keeps running as worked time. And on a busy Friday, someone simply forgets to clock out — the system keeps counting until someone corrects it by hand the next morning, if anyone does.

None of these four things is theft, and none makes headlines the way structural overtime does. But together they're four leaks in your time records that rarely get noticed on their own — and that, added up over a year and a team, do produce a number. This article gives you that number: four leaks, each with its own maths, and one calculator that adds them up for your own crew.

Why this isn't an overtime problem — it's a recording problem

Overtime is about hours ABOVE the rota — a busy week, a festival, a closing shift that runs long. That maths lives in our guide to overtime pay in hospitality. This article is about something smaller and far more common: the gap between what's SCHEDULED and what actually gets CLOCKED, on a completely ordinary shift with no peak at all.

That gap doesn't exist because anyone is breaking a rule. It exists because nobody ever wrote a rule for what happens before the scheduled start, after the scheduled end, or during a break that never gets clicked separately. Without an agreed rule — round to the nearest 15 minutes, always clock breaks separately, always clock out before leaving the building — everyone fills that gap their own way, and rarely in the business's favour.

The four leaks below build on the same example: one staff member, an hourly wage of €14, five shifts a week, 48 weeks worked a year. Each leak looks small on its own. Together — 30 minutes a shift — they add up to €1,680 per staff member a year, as the chart further down shows.

One thing here sits outside the maths and is simply law: since the Court of Justice of the EU's ruling in CCOO v Deutsche Bank (C-55/18, 14 May 2019), every EU member state must require employers to set up a system that measures each worker's daily working time objectively, reliably and accessibly — not a rota showing planned times, but a record of what actually happened. Exactly how each country implements that duty — digital or on paper, what an inspection penalises — differs by member state. This article doesn't explain any one country's law; it shows where the hours actually leak once you have a recording system in place, and what that leak costs.

The shift nobody clocks exactly

Scheduled shift: 6pm–11pm. What happens before and after it rarely gets recorded as it really was.

6pm–11pm · scheduled shift
5:52pm Arrival — clocked in 6 min before start
11:08pm Departure — clocked out 8 min after end

6 minutes early clock-in + 8 minutes late clock-out = 14 minutes outside the scheduled time, on a single shift. Add the break that keeps running and the occasional forgotten clock-out and you're at 30 minutes a shift — see the chart further down for what that becomes over a year.

The 4 leaks, each with its own maths

1. Early clock-in: 6 minutes nobody counts as work

The most harmless of the four, and the most common. A staff member would rather arrive early than late, clocks in the moment they walk through the door — often out of habit, sometimes to avoid queuing at the clock right before the shift starts — and that time gets counted as worked time without anyone thinking twice, even though the actual shift hasn't started yet.

At 6 minutes a shift, an hourly wage of €14, five shifts a week and 48 weeks worked a year, that's 6 ÷ 60 × €14 = €1.40 a shift, €7.00 a week and €336.00 per staff member a year — for time during which, according to the rota, nobody was actually working yet. This is the leak a single agreed rule fixes: clock in at the scheduled start time, whatever happens before it.

2. Late clock-out: 8 minutes that may or may not count as closing up

The mirror image of the first leak, and usually a little more expensive because it's less visible: the end of a shift has no hard edge the way the start does. Clearing the last table, counting the till, emptying the dishwasher — it all feels like "just wrapping up", and nobody checks the clock before those last tasks start.

At 8 minutes a shift, that's 8 ÷ 60 × €14 = €1.87 a shift, €9.33 a week and €448.00 per staff member a year. The difference from the first leak isn't a coincidence: closing up after a shift almost always takes longer than setting up before it, which is exactly why the end of a shift is where most unpaid minutes live.

3. The break that keeps running

The biggest of the four leaks, and the least visible. A staff member takes a fifteen-minute break, but there's no separate break button in the system — or there is, but nobody presses it consistently, because it's "only a quarter of an hour". The result: the clock keeps running as if work was happening, while in reality twelve of those fifteen minutes carried no work at all.

At 12 minutes a shift, that's 12 ÷ 60 × €14 = €2.80 a shift, €14.00 a week and €672.00 per staff member a year — more than the first two leaks combined. It's also the only one of the four a rota alone can't fix: it needs a system where clocking a break is as automatic as clocking in and out, and a rule everyone actually follows.

4. Forgotten clock-outs: the ghost hours nobody corrects

The least frequent leak, but the most expensive per occurrence. On a busy night, someone simply forgets to clock out when they leave. The system keeps counting — sometimes until midnight, sometimes until the next clock-in — and unless someone corrects it by hand the next day, the payroll suddenly shows a fourteen- or fifteen-hour shift for work that never happened.

If that happens on average once every ten shifts and adds 40 extra ghost minutes that go uncorrected, spread out that's 4 minutes a shift — 4 ÷ 60 × €14 = €0.93 a shift, €4.67 a week and €224.00 per staff member a year. Small on average, but it's also the only leak that can dump a full extra shift's pay onto the payroll in one go if nobody notices — which is exactly why it's worth checking the time sheet every week, not just at pay-run time.

From 30 minutes to €1,680

The same 30-minute-a-shift leak, added up over time — for one staff member, at an hourly wage of €14

 
1 shift
 
1 week (5 shifts)
 
4 weeks (20 shifts)
 
1 year (48 weeks)

This is one staff member. A team of eight on the clock multiplies this figure by eight — use the calculator below for your own crew.

Calculate the leak in your own team

Enter how many staff are on the clock, how many minutes leak on an average shift (add up the four leaks above — 30 minutes is a realistic average if you have no agreed rules yet), the average hourly wage, shifts per week per staff member, and weeks worked a year. The calculator turns that into what it's costing your whole team.

What does the leak cost your team?

Four leaks together, multiplied across your whole crew

Early clock-in + late clock-out + break creep + ghost hours combined — 30 minutes is a realistic starting point
Excludes leave weeks and closure periods

Extra paid minutes per week

1.200 min

Added up across your whole team

Extra cost per year

€13.440

That equals

120

extra 8-hour shifts, at the same hourly wage

With the default figures — 8 staff, a 30-minute leak per shift, €14 an hour, 5 shifts a week and 48 weeks worked a year — that comes to €13,440 a year, or 120 extra 8-hour shifts you could have paid for with that amount. That's not theft and it's not worth getting angry about: it's a process with no agreed rules, which is exactly why the action plan below starts with an agreement, not a difficult conversation with your team.

Your action plan for the next team meeting

You don't have to fix this all at once. This is the order that works:

Step 1 — Calculate (this week):

  • Fill in the calculator above with your own team, wage and a realistic estimate of the leak
  • Check your last two weeks' time sheet: how many minutes on average sit before the scheduled start and after the scheduled end?
  • Check whether your system has a separate break button, and whether it's actually used

Step 2 — Agree the rules (within two weeks):

  • One rule per leak: clock in at the scheduled start time, always clock breaks separately, check weekly for forgotten clock-outs
  • Put the opening and closing round on paper with our free opening & closing checklist, so it's clear which tasks belong before and after the scheduled shift — and therefore should be clocked time
  • Decide who checks the time sheet weekly, not just at pay-run time

Step 3 — Repeat (every quarter):

  • Recalculate the leak after a few months — a rule that sticks shrinks the number by itself
  • Compare it against your rota with our free staff rota generator: a rota that matches the real opening and closing routine leaves less room for a leak
  • Read our guide to overtime too, if the leak mostly piles up during peak weeks rather than on an ordinary shift

Conclusion: four small leaks, one yearly figure

None of the four leaks in this article feels like a problem on its own. Six minutes clocked in early isn't fraud, a break that keeps running isn't laziness, and one forgotten clock-out in ten shifts is human. The number only appears once you add the four up over a shift, a week and a year — and then thirty unremarkable minutes a shift turn into €1,680 per staff member a year, for time nobody consciously recorded.

At HappyChef, that starts with visibility: a reservation system with 0% commission that puts your staff planning next to your revenue, so a scheduled shift and a clocked shift move closer together. Read our guide to overtime or try it free for 30 days.

Frequently asked questions

Is this the same as overtime?

No. Overtime is about hours ABOVE the scheduled rota — a busy week, a festival. The four leaks in this article happen on a completely ordinary shift with no peak at all: the gap between what was scheduled and what was actually clocked. See our guide to overtime pay in hospitality for that other topic.

Am I required to record actual hours worked?

Since the Court of Justice of the EU's ruling in CCOO v Deutsche Bank (C-55/18, 14 May 2019), every EU member state must require employers to set up an objective, reliable and accessible system that records each worker's daily working time. A rota showing scheduled times isn't enough — it shows what was planned, not what actually happened. Exactly how that duty is implemented differs by member state; check with your payroll advisor or a lawyer who knows your own country's rules.

Can I round clocked time to the nearest 15 minutes?

That depends heavily on the country, the collective agreement, and the direction the rounding goes. Some systems round symmetrically (up as well as down), others always round in the employer's favour — and the latter is exactly the kind of rounding many jurisdictions penalise at inspection. Check the exact rules for your country before setting a rounding policy.

Does a break that keeps running count as paid time?

If there's no separate break record and the clock keeps running, that time is usually simply booked as worked time — even though no work was happening. Whether a break must legally be paid differs by country and agreement; what this article is about is something else: that the time often isn't even recorded correctly in the first place, which does conflict with the recording duty above.

Is this my team's fault?

Rarely. The four leaks in this article almost always happen because there's no clear rule — no rule for exactly when to clock in, no consistently-used break button, no weekly check for forgotten clock-outs. Treat it as a process question, not a trust question: most teams follow a clear rule without argument once one actually exists.