Rest break compliance: proving UK working time rules
How to prove rest break and working time compliance without spreadsheet chaos
Rest break compliance sounds simple until you have to prove it.
A rota says one thing. A timesheet says another. Somebody skipped lunch because the shift blew up. Somebody else clocked out late after closing. By the end of the month, a manager is trying to reconstruct reality from spreadsheets, screenshots and memory. That is not a compliance process. It is archaeology.
The short version
Under UK working time rules, rest break compliance is not only about offering breaks. It is about being able to evidence them clearly. If someone works more than six hours, they are usually entitled to a 20-minute uninterrupted break. Workers are also usually entitled to 11 hours' rest between working days and weekly rest of 24 uninterrupted hours every seven days, or 48 hours every 14 days. Night workers have additional limits.
The hard part is not understanding those rules. The hard part is proving, later, that your operation followed them in practice.
That is where spreadsheet chaos starts.
What rest break compliance actually means
A lot of teams talk about breaks as if they sit on their own. They do not. Rest break compliance usually sits inside a wider working time picture.
For most shift-based businesses, these are the rules that matter most:
Area | What the rule says | What this means in practice |
|---|---|---|
In-shift rest break | If someone works more than 6 hours in a day, they usually have the right to one uninterrupted 20-minute rest break. | The break needs to happen during the shift, not at the very start or end. |
Daily rest | Workers usually have the right to 11 hours' rest between working days. | A late finish followed by an early start can create a problem fast. |
Weekly rest | Workers usually have the right to 24 uninterrupted hours each week, or 48 hours each fortnight. | Repeated short-turn scheduling can breach the rules even if each day looks manageable on its own. |
Night work | Night workers must not usually work more than an average of 8 hours in a 24-hour period. | Teams with overnight work need stronger records, not rougher ones. |
The clearest public guidance is on GOV.UK's rest breaks page, GOV.UK's maximum weekly working hours page, GOV.UK's night working guidance, and Acas guidance on rest breaks.
The important operational point is this: if a worker says they did not get proper rest, or an inspector asks you for records, the fact that a break was planned on a rota is not enough on its own.
Why spreadsheets fail the audit test
Spreadsheets are good at planning. They are much worse at proving.
That is because spreadsheets usually capture the version of the day that managers hoped would happen. Compliance needs the version that actually did.
Imagine a normal week in a shift-based business:
a supervisor delays their break because a delivery arrives late
a team member leaves the floor for ten minutes, gets called back, then tries to take the rest later
somebody works past shift end because closing took longer than expected
another person agrees a same-day swap by message
None of this is unusual. All of it affects the record.
Once that happens, three problems appear.
1. Planned time and worked time drift apart
The rota says the break happened from 1:00 to 1:20. Real life says otherwise. If your system cannot capture the difference, you do not have evidence. You have an assumption.
2. Managers end up relying on memory
Most spreadsheet processes quietly depend on somebody remembering what happened, or chasing the team later. That is slow, fragile and not especially convincing if a dispute lands months later.
3. The audit trail becomes muddy
Retroactive edits are the heart of spreadsheet chaos. A workbook gets updated after the fact. Then copied. Then corrected. Then emailed around. You might still find the right version in the end. But that is not the same thing as having a clean, secure, searchable compliance record.
This is why rest break compliance becomes such an admin sink. The problem is not only the law. It is the gap between the law and the tools.
What good rest break record keeping looks like
The best compliance processes are dull in the right way. They do not rely on heroics. They rely on repeatability.
1. Build the rule into the schedule
Start before the shift begins.
Shift lengths, rest windows and night patterns should be visible while the rota is being built, not after the week has already happened. If someone is scheduled into a pattern that squeezes daily rest, the problem should be visible early.
This is one reason scheduling software matters. It turns working time rules into part of the workflow instead of a policy document managers have to remember under pressure.
2. Capture breaks when they happen
If your record depends on somebody filling in a sheet later, it is already vulnerable.
The strongest evidence comes from real-time capture. Clock in. Clock out. Start break. End break. Simple.
That is the practical role of time and attendance. It gives you a record of what happened on the floor, not only what was supposed to happen on paper.
3. Review exceptions while they are still fresh
Not every missed or delayed break means misconduct or systemic failure. Shift-based work is messy. But the variance needs to be visible.
Managers should be able to review exceptions the same day or the same pay period, while people still remember what happened. If someone did not get their proper break, that should be flagged and dealt with, not buried in a month-end clean-up.
4. Lock a clean audit trail before payroll
By the time payroll is processed, your compliance record should already be coherent.
That means you should be able to show:
what shift was scheduled
what was actually worked
when breaks were taken
where exceptions happened
who reviewed and approved the record
That is the difference between rest break record keeping and rest break guesswork.
How to move from reactive admin to clear evidence
If your current process still runs through Excel, paper notes and messaging threads, you do not need a grand transformation story. You need a better sequence.
A practical model looks like this:
Build rotas with working time rules in mind.
Capture worked hours and breaks digitally.
Flag short-rest or missed-break exceptions quickly.
Approve timesheets against reality, not assumptions.
Export a record payroll can trust.
That flow is not glamorous. Good. Compliance should not be glamorous. It should be boring, fast and defensible.
What better systems actually change
A connected platform does not remove responsibility from managers. It removes unnecessary friction.
Instead of remembering every rule, managers get clearer prompts.
Instead of asking, “Did Sam take their break that day?” they can check.
Instead of rebuilding history from edited sheets, they can pull a record.
Instead of treating compliance as a monthly admin event, they can manage it as part of the shift itself.
That is the bigger operational gain. Better visibility creates more predictable shifts. And predictable shifts tend to create better compliance, cleaner payroll and less management drag.
The standard is not perfection. It is proof.
No shift business runs in a straight line. Lunches get delayed. Deliveries go wrong. People step in for each other. That is real life.
The question is not whether reality ever moves around the plan.
The question is whether your process can show, clearly and credibly, what happened next.
If the answer still lives in three versions of the same spreadsheet, it is probably time to stop calling that a system.
If you want a cleaner way to track breaks, worked hours and exceptions without burying managers in admin, explore how Planday supports connected scheduling and time tracking for shift-based teams.