The driver came in at 05:45 and asked the shunter for keys. Normal morning. The shunter passed them over. Forty minutes later the driver was in a barrier on the A14 near Kettering, minor injury, cab totalled, and the initial report from the hospital was that he'd fallen asleep.
The police asked if the operator had a fatigue risk management policy. The TM -- a woman I know well from a compliance training course -- didn't know what one was.
She knew the tachograph rules. She knew the WTD limits. What she didn't have was any formal process for managing driver fatigue as a workplace hazard separate from the hours rules. And those are different things.
Why tachograph compliance isn't the same as fatigue management
EU 561/2006 sets driving time limits -- 9 hours daily, 56 hours weekly, 90 hours across any two weeks. Rest periods -- 11 hours between driving days, 45 hours weekly rest. These are legal minimums. A driver who has taken exactly 9 hours of daily rest, driven exactly 9 hours, and done this for six consecutive days is technically compliant. They might also be exhausted.
Fatigue is not a binary state. You can be within every legal limit and still be impaired by cumulative tiredness, poor sleep quality, shift pattern disruption, health issues, or personal stress. The tachograph records when you drove. It doesn't record whether you were fit to drive.
The Health and Safety at Work Act 1974, Section 2 places a general duty on employers to ensure the health, safety and welfare of employees so far as is reasonably practicable. For drivers, that includes managing the risk of driver fatigue as a workplace hazard. Not just complying with hours legislation -- actively assessing and managing the risk.
What a fatigue risk management approach looks like
There's no single statutory document called a "fatigue risk management policy" that the law requires you to produce. What there is, via the Health and Safety at Work Act and the Management of Health and Safety at Work Regulations 1999, is a duty to assess and control workplace risks -- and fatigue on the road is a risk.
DVSA's driver fatigue guidance (available on gov.uk) outlines the factors operators should consider: shift patterns, time of day of driving, sleep opportunity, individual driver factors, break frequency. HSE guidance on fatigue in transport adds more detail on risk factors and controls.
In practice, a documented approach includes:
- A shift pattern that provides adequate sleep opportunity -- not just compliant rest hours but realistic sleep hours
- A process for drivers to report fatigue without fear of consequence
- A policy on what drivers should do if they feel too tired to continue -- where to stop, who to call
- Regular review of near-misses and incidents for fatigue as a contributing factor
- A mechanism for flagging drivers who appear to be accumulating fatigue across a working week
The TM on the Kettering incident had none of this documented. The operator's defence was that the driver was compliant on hours. The investigating officers were asking about the fatigue management process. That's a different question.
The self-declaration trap
Some operators introduce a fatigue self-declaration -- a simple yes/no form a driver completes at sign-on: "I am fit to drive today." The logic is that this transfers responsibility to the driver.
It doesn't. Not fully.
A driver who signs a self-declaration knowing they're tired has done something wrong. But an operator who relies solely on a self-declaration with no other process has still failed their duty of care if the driver turns out to have been fatigued and there was a warning pattern the operator could have seen. The TM who saw a driver's hours building through the week, noted the early starts, and never said anything -- a self-declaration at sign-on doesn't cover that gap.
Self-declarations are a useful part of a fatigue management system. They're not a substitute for one.
What dispatch does to fatigue
I've covered this from the WTD angle in other posts but it's worth saying plainly from the fatigue side: dispatch creates fatigue conditions. A driver who gets a 05:00 start call at 23:30 the night before has been given less than six hours between call and start. Even if they were resting before the call, the quality of that rest and the window for sleep after it is constrained by the short call time.
Operators running tramping work with early morning starts and late-evening completion need to look at the pattern of calls and starts across a driver's week. A driver running four consecutive days with a 04:30 start after an 11-hour rest minimum -- that's technically compliant and realistically challenging.
The WTD post I wrote on the operator duty of care under dispatch covers the legal side of this more formally if you want it. From the fatigue management angle, the practical question is whether you're using your tachograph data and shift logs to spot patterns before they become incidents.
Driver health and fitness
This is the bit most operators don't touch at all. Sleep apnoea is the most discussed one -- it affects an estimated 4-8% of the adult population to a clinically significant degree, and a driver with undiagnosed or untreated sleep apnoea can appear fully compliant on hours while being significantly cognitively impaired by poor sleep quality. DVLA requirements mean drivers with diagnosed sleep apnoea need to declare it and meet treatment conditions for licence retention.
But the duty of care question for operators extends beyond DVLA-declared conditions. If a driver has been visibly struggling -- falling asleep in the yard, reporting being very tired, other drivers commenting -- and the operator has done nothing, the fact that the driver's DVLA medical is clear doesn't remove the operator's liability when there's an incident.
The test is: what did the operator know, or should reasonably have known, and what did they do about it?
When an incident happens
After a fatigue-related incident -- a collision, a near-miss, a driver waking up on a motorway hard shoulder -- DVSA and the police will ask the operator questions. Not just about the driver's tachograph records for that day. About the pattern over the preceding days. About the operator's fatigue management process. About what dispatch knew about that driver's week.
A fleet with a documented fatigue management policy, evidence of it being applied, and a clear process for incident review is in a different position from one that can only point to tachograph compliance. Both might have had the same incident. One of them has a defence.
If you're a transport manager trying to build a clearer picture of your drivers' hours patterns week on week, ShiftOwt tracks 561 and WTD compliance automatically and flags drivers building toward limit. It's 5.99 per month for drivers, agency pricing on request. Not a fatigue management system -- but the data it gives you is part of one.
What the Kettering operator changed
Six months after the incident, the TM had introduced a documented fatigue policy, a shift pattern review with HR, a self-declaration form that actually asked about sleep quality not just fitness, and a process for drivers to flag themselves as fatigued without losing pay for that shift. None of this was expensive. All of it was normal industry practice in larger fleets. It just hadn't filtered down to an eight-vehicle operation in the East Midlands.
The driver was back at work after three months. The operator kept their licence. But it was a closer thing than anyone was comfortable with, and all of it was preventable.