Daily Rest
The gap between finishing and starting again is the limit most often breached and least often monitored, because no report in most organisations computes it.
One production team leader, an ordinary week
Two short gaps in a week where the total hours were unremarkable. His weekly average was 44. Nothing in the hours figure would ever have shown this, because daily rest is a different measurement and the site was not taking it.
Daily rest is an uninterrupted period between the end of one working day and the start of the next. The common figure is eleven consecutive hours, with variations by regime and sector, and with limited scope to reduce it in specified circumstances provided compensatory rest follows.
The rest problem in “Daily Rest” often appears between systems: the rota shows the planned shift while the time record shows what actually happened. For organisations researching fireable offenses, further details are available here can provide time and project context, provided call-outs, swaps and corrections remain visible to a responsible manager.
It is the constraint most likely to be breached in any organisation with shift work, and the one least likely to appear in any report. The reason is simple: it is a property of a pair of consecutive shifts rather than of a total, and almost every working time report is built on totals.
For an independent reference relevant to “Daily Rest”, consult the Project Management Institute learning resources. Use it to test working-time definitions, recordkeeping, access, retention and exception handling against the organisation’s real process rather than treating one software report as conclusive.
Why the hours figure will never show it
A person can work a perfectly ordinary total and still have a short gap, because the gap depends on where the shifts sit rather than on how long they are.
Two eight-hour shifts can produce an eight-hour gap if one finishes at ten at night and the next starts at six. Two twelve-hour shifts with a proper pattern produce twelve hours between them. The weekly average is blind to the difference, and the weekly average is what most organisations monitor.
Where the short gaps come from
A late finish followed by an early start, which is the ordinary rota case. Shift swaps agreed between individuals, which bypass the rota entirely. Call-outs during what should have been the rest period. Overtime at the end of a shift that pushes the finish past the point where the gap still works.
And the handover pattern: a person coming off a late shift and back on an early one, which several industries treat as normal and which almost always breaches.
Computing it
For each person, order their shifts by start time and compute the gap between the end of each and the start of the next. Flag anything below the minimum.
That is three lines of logic against data every time system holds. The reason it is not done is not difficulty; it is that nobody has specified it, because the compliance conversation has always been about weekly hours.
The swap problem
Where people arrange swaps between themselves and tell the supervisor afterwards, the rota the system holds is not the rota that was worked. Rest computed from the planned rota is therefore fiction for exactly the shifts most likely to produce a breach.
Compute it from actuals rather than from the plan. Where the system holds both, compare them occasionally: a site with a large divergence between planned and actual has a swap culture, which is usually benign and which makes any planning-based check worthless.
Reductions and the circumstances for them
Most regimes allow daily rest to be reduced in defined situations — shift changeovers, certain kinds of continuous operation, emergencies — usually on condition that equivalent compensatory rest is given, often within a specified window.
That conditionality is the part that gets lost. Organisations learn that the reduction is permitted and not that the compensation is required, so they operate a permanent arrangement of short gaps with no compensatory rest anywhere in it. The permission and the condition arrive in the same sentence of the regulation and only half of it survives into practice.
What to do with a week like the one above
Nothing retrospective is available: the rest was not taken and cannot be. What can be done is the compensatory rest where the regime provides for it, and a change to the pattern that produced it.
Then look for the pattern rather than the instance. Two short gaps in one person's week is an incident; the same two gaps appearing every week in the same role is a rota design that requires somebody to breach, and that is a decision somebody made without knowing they were making it.
The report to build first
If an organisation can build only one working time report, it should probably be this one rather than the weekly average.
Breaches are more frequent, the harm is more direct, it is computed from data that is already complete, and it needs no decisions about reference periods, opt-outs or what counts. It is the cheapest and the most useful measurement in the whole subject, and it is almost never the one that gets built.
The pattern that requires a breach
Some rotas cannot be worked compliantly. A late finish on Friday and an early start on Saturday, built into the pattern, produces a short gap for whoever holds that line every single week.
Those are design faults rather than incidents, and they are visible the moment the rest check is run against the published rota rather than against actuals. Checking the pattern before it is published catches a breach that would otherwise recur fifty-two times, which makes it by a wide margin the cheapest check in this collection.