In every pub, bar, and restaurant in the UK, there is a rota. It tells you who is supposed to be working, when they are supposed to start, and when they are supposed to finish. And in almost every one of those venues, the rota does not match reality. People clock in early. People clock out late. Shifts appear on the payroll that were not on the rota. And the cumulative cost of these discrepancies, across a year, is far larger than most managers realise.
This is not about dishonesty — at least not primarily. Most clock-in discrepancies are the result of habit, poor systems, and a lack of visibility. A team member arrives ten minutes early and clocks in immediately. Another stays fifteen minutes late because service ran over. A third picks up a shift on their day off that never makes it onto the rota but does make it onto the payroll. Each individual instance is small. Collectively, they are significant.
A worked example
Take a typical UK pub with twenty staff members. Average hourly rate: £10 per hour (a reasonable blended average across bar staff, kitchen, and supervisors, accounting for National Living Wage requirements). Each staff member works an average of five shifts per week.
If each shift runs, on average, thirty minutes longer than the rota specifies — combining early clock-ins and late clock-outs — the additional cost per shift is £5.00. Across twenty staff members working five shifts each per week, that is 100 shifts per week with a £5.00 overrun each. Total weekly overrun: £500. Per year: £26,000.
But £500 per week is the extreme scenario — thirty minutes average overrun per shift is at the high end. Let us use a more conservative figure: fifteen minutes average overrun per shift. That gives us £2.50 per shift, £250 per week, and £13,000 per year. Still a significant sum — and still largely invisible in most venues because nobody is systematically comparing the rota against actual clock-in data.
Even at a more modest scenario — twenty staff, five shifts each, averaging just ten minutes of overrun per shift at £10/hour — you get £1.67 per shift, £167 per week, and £8,684 per year. This is real money leaving the business without anyone making a conscious decision to spend it.
Common patterns
Early clock-in. The most common pattern. A team member is scheduled to start at 11am. They arrive at 10:45am because they want to get a coffee, put their things away, and settle in. They clock in when they arrive rather than when their shift starts. Fifteen minutes, every shift, every day. Over a five-day week, that is seventy-five minutes of paid time that was not on the rota. Over a year, for a single staff member at £10/hour, that is £650.
Late clock-out. Service runs late on a Friday night. The bar closes at midnight, but the last customers do not leave until 12:15am. Clean-down takes until 12:45am. The team member was scheduled to finish at midnight but actually clocks out at 12:50am. The rota said eight hours; the clock-in system recorded eight hours and fifty minutes. This happens every weekend, and often during the week as well.
Shifts on days off. A team member picks up an extra shift to cover for a colleague who called in sick. The manager approves it verbally or via WhatsApp. The team member works the shift and clocks in. But the rota is never updated — because the rota was published days ago and the manager did not think to amend it. The shift appears on the payroll as hours worked, but there is no corresponding entry on the rota. This is not always a problem — the shift was genuinely worked — but without cross-referencing, there is no way to verify it. And occasionally, shifts appear on the payroll that nobody authorised and nobody can explain.
Buddy clocking. In venues that use a PIN-based or card-based clock-in system, one team member can clock in on behalf of another. The absent team member is not in the building, but their clock-in record shows them as present. This is outright fraud, and while it is less common than the other patterns, it does occur — and it is almost impossible to detect without cross-referencing clock-in data against camera footage or other presence verification.
Why managers don't catch it
The fundamental problem is that rotas and clock-in systems are typically separate. The rota lives in one system — a spreadsheet, a scheduling app, or a whiteboard on the office wall. The clock-in data lives in another — the EPOS, a time-and-attendance system, or a biometric terminal. Payroll is processed from the clock-in data, not the rota. And nobody routinely compares the two.
Even in venues that use integrated workforce management systems, the comparison is typically done at the end of the pay period — if it is done at all. The payroll manager or accountant processes the hours, sees a total, and approves it. They do not go through every individual shift comparing scheduled start time against actual clock-in time. There are too many shifts, too many staff members, and not enough time.
The manager on duty during the shift is the person best placed to catch discrepancies in real time — but they are also the person with the least time to do so. They are running the floor, dealing with customers, managing deliveries, and handling whatever emergencies arise. Checking whether every team member clocked in within five minutes of their scheduled start time is not a priority when the kitchen has just had a gas alarm.
How automated cross-referencing works
Minnie pulls data from both the rota system and the clock-in system, aligns them by staff member and date, and compares scheduled times against actual times for every single shift. The comparison is done automatically, daily, with no human input required.
Each discrepancy is flagged individually. The system does not just tell you that total hours exceeded rota hours by forty-three hours this week — it tells you that Sarah clocked in eighteen minutes early on Monday, James clocked out thirty-two minutes late on Wednesday, and a shift for Dave appeared on the clock-in system on Thursday that has no corresponding entry on the rota.
Discrepancies are categorised by type (early clock-in, late clock-out, unscheduled shift, missed clock-in) and by magnitude. A five-minute early clock-in might be flagged as informational. A forty-five-minute late clock-out is flagged as requiring review. An entire shift that appears on the clock-in system but not the rota is flagged as requiring immediate attention.
The data is delivered to the manager via the morning briefing — alongside GP data, booking information, and everything else they need to start the day. No additional system to check. No report to run. The information arrives automatically, every day.
What to do when you find it
Set clear expectations. Staff should know that clock-in times are compared against the rota, and that discrepancies are flagged. This alone changes behaviour. When people know the data is being watched, the casual early clock-in tends to disappear.
Implement a grace period. Most venues allow a five-minute grace period around the scheduled start and end time. This accounts for the practical reality that a shift cannot start at exactly 11:00:00. Anything beyond the grace period is flagged for review.
Review unscheduled shifts promptly. Any shift that appears on the clock-in system without a corresponding rota entry should be reviewed the same day. Was it a legitimate cover shift that was verbally approved? Then update the rota to reflect it. Was it unauthorised? Then investigate immediately.
Use the data for payroll verification. Before payroll is processed, run the cross-reference report. Approve all legitimate discrepancies. Query all unexplained ones. This takes ten minutes and can save hundreds of pounds per pay period.
The rota is a plan. Clock-in data is reality. When you do not compare the two, you are paying for reality without knowing how far it has drifted from the plan. For most venues, that drift is costing thousands of pounds per year — and the fix is not discipline or punishment. It is visibility. Once the data is visible, the problem largely solves itself.