Investigating a heavy-vehicle fatigue exception in Australia

A driver reports being too tired to continue, a work diary shows a potential breach, or a delivery delay creates pressure to drive beyond a safe limit. Each event needs an immediate safety response. A useful investigation then asks how the transport system contributed, not only whether one driver made a mistake. The record should link the event, decisions, causes and corrective action.

This guide concerns operational investigation of a fatigue exception in heavy-vehicle transport where the Heavy Vehicle National Law (HVNL) applies. It is not a work-diary completion guide or a substitute for legal advice about an alleged breach. The National Heavy Vehicle Regulator's current fatigue and fitness-to-drive duties guidance describes post-1 August 2026 provisions. Check the applicable jurisdiction, vehicle and fatigue scheme before applying a specific rule.

Make the immediate trip safe

If a driver is impaired by fatigue or otherwise unfit, do not ask them to continue merely to meet a delivery window. Arrange a safe stopping place, rest, replacement driver or rescheduled delivery as appropriate. Communicate the changed plan to people who need to know without sharing unnecessary health details. If an incident has occurred, follow emergency and regulator notification requirements separately.

The NHVR says compliance with work and rest hours does not necessarily mean a driver is fit to drive. That is why an exception process must accept a driver report even when the roster has no obvious breach. Equally, a diary anomaly may indicate a record error, scheduling failure or actual unsafe work; investigate before drawing conclusions.

Preserve the event as it happened

Capture the driver's report, time and location, planned and actual work, rest opportunity, loading delays, route conditions, dispatcher instructions, vehicle availability and any relevant messages. Retain the original work diary or electronic record according to the applicable rules. If a record is corrected, preserve the original value and reason rather than silently replacing it.

Avoid treating a vague “fatigue exception” tag as sufficient. Was the issue a driver feeling unfit, a planned schedule that could not be performed safely, a diary entry discrepancy, or an actual breach? The category affects the response and evidence needed. Protect sensitive personal and medical information; an investigator may need more detail than a customer receiving a revised ETA.

Investigate contributing decisions

Ask who set the delivery window, whether the travel and loading plan allowed realistic rest, whether there were queues or repeated delays, and what pressure was put on the driver. Review whether prior concerns were reported and acted on. The NHVR's regulatory advice on fatigue and fitness encourages consideration of factors beyond formal work-rest compliance. A CoR party's influence over its transport activity matters.

Interview the driver in a way that supports accurate reporting. If every admission is treated as a disciplinary matter before system causes are examined, future drivers may stay silent. Also speak with schedulers, loaders and dispatchers where relevant. Separate a fact established by evidence from an assumption. A late arrival does not by itself prove the driver exceeded hours; a clean diary does not by itself prove there was no fatigue risk.

Assign controls that address the cause

Actions may include revising delivery windows, changing handover arrangements, improving loading forecasts, providing a relief driver, training dispatchers to recognise unsafe pressure or correcting a record process. Match the action to the finding. “Remind drivers of the rules” is weak if the underlying cause was an impossible schedule set by the client.

For each action, record the owner, target date, interim control and evidence of completion. Then check whether the change works in practice. A revised policy is not enough if dispatch still rewards the same unsafe behaviour. If another party in the Chain of Responsibility controls part of the risk, discuss and coordinate the response; do not write “carrier issue” and stop there.

Example: a recurring loading delay

An operator schedules an overnight delivery after a loading window that repeatedly overruns. A driver reports being too fatigued to start the final leg. Dispatch finds a safe place to stop and arranges a replacement. The investigation reviews work diary entries, actual loading times, communication between warehouse and dispatch, and customer delivery pressure. It finds the route plan assumed loading would finish two hours earlier than recent evidence supported. The parties revise the booking window and review later trips to see whether the pattern improves.

The driver report is not treated as a failure to be hidden. It is evidence that a control worked by prompting a safe stop, and evidence that the planning system needed review.

Keep this distinct from routine fatigue monitoring

An investigation record is event-specific. Routine roster checks, driver education and diary review are separate ongoing controls. Link them when the event shows a programme weakness. Do not claim a software dashboard can infer impairment from hours alone or decide whether a driver is medically fit.

The NHVR's safety-management guidance supports learning from hazards and incidents. The mapped Complys Australian heavy-vehicle compliance page is the commercial context for evaluating records. Verify actual implementation; this guide does not claim Complys detects fatigue, interprets work diaries automatically or determines breach liability.

Separate systemic causes from individual choices

A fatigue exception may involve scheduling, delay, loading practice, route changes or driver decisions. Collect the chronology before attributing it to one person. Compare planned and actual work, breaks, demands and messages. Ask whether the driver had a realistic way to report fatigue and stop. A corrective action directed only at “remind drivers” can miss the dispatch or customer pressure that made the exception likely.

Review whether the response actually changed future trips. If an amended schedule still relies on the same tight turnaround, the action is not effective merely because a briefing was signed. Keep a clear record of who approved changes to the roster and how a later trip was checked. Where several parties influence a journey, document the handover rather than assuming the driver alone controlled all contributing factors.