Rest Between Shifts
Why the gap between shifts is the constraint that actually binds, where rotas break it without noticing, and what to check in a pattern before it is published.
Every gap between shifts in one published fortnight, for one team
Produced by two swaps approved separately.
Fixed in the pattern and comfortable.
The same overtime on a day shift would have cost nothing.
The rota plans a gap the shift does not deliver.
No action needed.
Two of the five gaps were shorter than the pattern claims, and neither was produced by a decision anybody would recognise as a decision about rest. One came from two separate swap approvals and one from a routine overrun. This is one employer's own fortnight, not a statement of what any rule requires.
The gap between one shift ending and the next beginning is the clearest example of a constraint that genuinely binds. It is required rather than preferred, it applies to the individual rather than the team, and it cannot be satisfied on average.
The rule discussed in “Rest Between Shifts” is easier to test when the published schedule can be compared with a consistent record of actual hours. A team reviewing using remote workforce management software in workforce forecasts for remote workforce management software can add current attendance and project context while keeping contractual rules and manager decisions explicit.
What the required gap is, which workers and sectors it applies to, and what may be varied by agreement differ by jurisdiction and are a question for somebody qualified in the place concerned. What follows is about where rotas breach it without anybody intending to.
As a separate benchmark for “Rest Between Shifts”, see CQC staffing guidance. Keep the source rule, operational interpretation and scheduling decision distinct.
Why it binds differently from other rules
Most rota constraints are about coverage: how many people, with what skills, at what time. This one is about a person's own sequence, and a rota that satisfies every coverage rule can still breach it for one individual in one week.
That is why it survives coverage-based checking. The pattern looks correct from above and is wrong from the perspective of a single row.
The four places it breaks
- A late shift followed by an early the next day, which is the classic and the one most people know about.
- A swap approved on its own merits, without reference to what the person is already working either side of it.
- Overtime added to the end of a shift, which shortens the gap at the far end rather than the near one.
- A shift that overruns routinely, where the rota shows a gap that the actual finishing time does not provide.
The last two are the ones systems miss, because the rota holds planned times and the breach happens in actual ones.
The swap problem
Swaps are approved individually and breaches are produced collectively. Two swaps that are each perfectly reasonable can combine to leave somebody with eight hours between shifts, and the person approving the second one is usually looking at a different screen.
The fix is a check at the point of approval rather than a rule in a handbook: before any swap is confirmed, look at what both people are working on either side.
Overtime at the wrong end
A person asked to stay two hours late has had their rest shortened at the start of it, not at the end. Overtime offered at the end of a late shift therefore costs more than the same overtime offered at the end of a day shift, and the cost falls on the next day's start time.
That is worth knowing when deciding who to ask. The cheapest person to ask is frequently not the one whose turn it is.
Where overruns hide it
If a shift regularly finishes thirty minutes after its planned end, the rota is planning a gap that does not exist. Nobody is breaching anything on paper and the person is getting less rest than the pattern claims.
Comparing planned finish times against actual ones for a month is a twenty-minute exercise, and in many operations it moves two or three shifts into a different category.
Checking a pattern before it is published
Run the check per person rather than per shift: for every individual, sort their shifts by start time and look at every consecutive pair. The arithmetic is trivial and it is the only reliable way to see it.
Most scheduling systems do this automatically and it is still worth knowing how to do by hand, because the automatic check is configured with a number that somebody typed in once.
The number in the configuration
That number is the constraint as the system understands it, and it is worth going to look at. Systems are commonly configured with a default rather than with the requirement that applies to the people on the rota.
A single wrong digit in a configuration screen is indistinguishable from compliance, which is a good reason to check it against the document rather than against what the system reports.
On-call, standby and the gap
Arrangements where somebody is available rather than working complicate the picture considerably, and the complication is jurisdictional rather than operational.
The operational point is narrower and safe to state: a rota that treats on-call hours as rest and then calls the person out twice is planning a gap it does not deliver, whatever the local position on how those hours are counted.
What to record
For each pattern, the shortest gap it produces for any individual in a full cycle, and the date that was checked. One number, one date.
It takes a minute to produce and it is the first thing anybody asks for when a pattern is questioned, which is usually at the least convenient moment and long after the person who built it has moved on.
Why this one is worth getting right
Because it is unambiguous. Most rota arguments are about fairness, preference and judgement, where reasonable people disagree. This one either holds or does not, the arithmetic is visible, and a breach is hard to defend after the fact.
An organisation that can show its shortest gap by pattern, dated, has removed one entire category of dispute for the cost of a monthly check.