Fatigue breaches are often discussed as if they begin with a driver making a poor decision late in the shift. In reality, the problem usually starts much earlier. A delayed load, a long queue at a customer site, a route change, a late booking confirmation or repeated pressure to recover lost time can steadily erode a compliant work and rest plan.
Under the HVNL, fatigue is a Chain of Responsibility issue, not a driver-only issue. Operators, schedulers, consignors, consignees and others in the chain can all influence whether a journey can be completed lawfully and safely. If a business treats predictable delays as simply part of the job, but does not adjust schedules, relief arrangements or delivery commitments, it may be creating the conditions for a breach.
This is where many businesses get caught by normalisation. A planner knows a particular site usually loses an hour in the afternoon. A dispatcher knows Friday freight tends to leave late. A customer service team knows unloading windows are frequently missed. Because these problems happen often, they stop being treated as hazards and start being treated as routine variation. From a compliance perspective, that is dangerous. Known disruption must be built into the task design.
The practical test is simple: when the day goes wrong, what does your system expect the driver to do? If the answer is vague, or depends on the driver somehow making up time, the control is weak. Strong fatigue management requires defined escalation points. Drivers need authority to stop, notify and revise the plan without hidden commercial penalty. Schedulers need clear rules about resetting delivery expectations. Customers need to understand that site delay can lawfully change the arrival time.
Operators should also look beyond work diary compliance alone. A lawful diary does not automatically mean fatigue risk is well managed. Waiting time in queues, poor sleep opportunities, overnight changes, split tasks and repeated start-time variation can all affect fatigue exposure even before a technical breach occurs. Reviewing only infringement data misses those early indicators.
A better approach is to track operational triggers that commonly precede fatigue issues: late dispatch, extended site dwell time, re-routes, failed delivery windows, unplanned overtime, repeated calls to drivers near rest breaks and customer locations with recurring wait times. When those patterns are visible, the business can redesign before enforcement or an incident forces the issue.
Fatigue compliance improves when operators stop asking how to keep the original plan alive and start asking whether the plan remained safe once conditions changed. That shift matters because under the HVNL, safety is judged by what was reasonably practicable, not by how strong the commercial pressure felt on the day.
If your teams need a sharper, shared understanding of how scheduling, customer demands and site delays create fatigue liability under the HVNL, COR Safety Management Systems’ CoR training programs deliver practical training for drivers, schedulers, supervisors and executives.