Most operations leaders I work with can tell me, within a minute, that their rota meets the Working Time Regulations. Far fewer can tell me how alert their night shift is likely to be at four in the morning on the third night of a run. Those are different questions, and only one of them shows up in the incident log.
Compliance is a floor
Hours limits were designed to stop the worst excesses. They say how long people may work and how much rest they must have. They say very little about when that work falls, how shifts follow one another, or what the work itself asks of people at different points in the day.
A rota can pass every check and still put your most demanding tasks in the hours when people are least able to do them well.
“A compliant rota tells you nothing about how alert people are at 04:00.”
What hours limits miss
Fatigue builds from three things working together: how long someone has been awake, where they are in their body clock, and how much sleep they have been able to get over the last few days. Hours limits only touch the first of these, and only loosely.
That’s why the same eight-hour shift can feel completely different on a Monday early and a Thursday night. On paper they’re identical. In the body, they’re not.
Four better questions
- Where do your highest-risk tasks fall against the 02:00–06:00 window?
- How many nights in a row do people work, and how do they come off them?
- Does the pattern rotate forwards, or backwards?
- Who picks up the extra shifts, and is it always the same people?
Where to start
Pick one site and one four-week pattern. Lay the last year’s incidents and absences over it. You’re not looking for proof; you’re looking for clusters. If they’re there, you’ve found the place to begin.
Try the resource Build a week: the rota fatigue builder Use the tool