Shift Work Fatigue: How to Manage It Before It Manages You
Fatigue is shift work's background radiation: invisible on the roster, present in every incident report. It is also — and this is the manageable part — mostly a design output. Specific roster features produce it predictably, which means specific roster decisions reduce it predictably.
Where fatigue actually comes from
Three sources stack. Sleep debt: night and early-morning duty forces sleep into the body's least productive hours; the average night worker sleeps 1-2 hours less per day than a day worker, and the shortfall compounds across a block. Circadian friction: working when the body clock says sleep degrades alertness regardless of how much sleep was banked. Extended time-on-task: the final hours of long shifts — hour 12 especially — carry elevated error risk even in well-rested people.
The roster features that drive it
If you remember one list, make it this one: quick returns (rest gaps under ~11 hours — see minimum rest), backward rotation (direction matters), long night runs (4+ consecutive nights), long shifts in heavy work, and chronic structural overtime (a four-crew operation run on three crews — see the coverage math). Every one of these is a design choice, not weather.
The controls that work
In the pattern: rotate forward; keep night runs short (2-3) or long enough to adapt; protect 11-hour minimum gaps everywhere; cap consecutive shifts; build real recovery after night blocks. Patterns like the continental and 2-2-3 encode most of this. In the operation: schedule high-risk tasks away from 02:00-06:00 and from final shift hours; keep breaks genuinely off-task; treat the handover as a fatigue checkpoint. In the culture: make 'too tired to do this safely' a report, not a confession — fatigue self-declaration only works where it isn't punished.
The warning signs on your dashboard
Rising sickness absence on specific shifts; incidents and errors clustering late in shifts or runs; overtime creeping past 5% of hours; swap requests fleeing particular blocks; exit interviews citing 'the roster'. Each one points at a specific design fix — which is the encouraging news hiding in this whole topic.
Build this schedule in Tommy
Set the rotation once and Tommy fills the weeks ahead — shift swaps, leave and coverage gaps handled in one place, with your team always seeing the latest version.



