Driver Fatigue Compliance Guide for Australian Operators

1. What Is the HVNL?

The Heavy Vehicle National Law (HVNL) is the primary legislation governing heavy vehicle operations in Australia. It establishes national standards for fatigue management, vehicle maintenance, mass and dimension limits, and speed compliance. The HVNL applies to vehicles over 4.5 tonnes gross vehicle mass (GVM) and is administered by the National Heavy Vehicle Regulator (NHVR).

For transport operators, the HVNL's fatigue management provisions are among the most critical. They set maximum work hours, minimum rest requirements, and record-keeping obligations that apply to drivers, schedulers, and the entire supply chain.

While the HVNL specifically targets heavy vehicles, many transport operators apply similar fatigue management practices to their entire fleet — including light vehicles — as a matter of best practice and duty of care.

2. Chain of Responsibility Explained

Chain of Responsibility (COR) is a key principle under the HVNL. It means that everyone in the transport supply chain — not just the driver — shares responsibility for compliance. If a driver is fatigued, the scheduler who created an unrealistic timetable, the operator who set delivery expectations, and the consignor who pressured for faster delivery can all be held liable.

The parties in the chain include:

• Employers and operators — responsible for systems, schedules, and monitoring that prevent fatigue
• Schedulers and dispatchers — responsible for creating realistic schedules that allow adequate rest
• Drivers — responsible for managing their own fatigue and complying with rest requirements
• Consignors and consignees — responsible for not imposing unreasonable delivery timeframes
• Loading managers — responsible for not contributing to delays that affect driver rest

COR obligations are not optional. Penalties for non-compliance range from infringement notices to criminal prosecution, with fines potentially reaching hundreds of thousands of dollars for individuals and millions for corporations.

The key insight of Chain of Responsibility is that fatigue isn't just a driver problem — it's a system problem. If your scheduling software makes it easy to over-schedule drivers, the organisation is part of the problem.

3. Driver Hours Rules

The HVNL establishes three fatigue management frameworks with increasing levels of flexibility and responsibility:

Standard Hours

The default framework for most operators. Key limits include:

• Maximum 12 hours of work time in any 24-hour period
• Maximum 144 hours of work time in any 14-day period
• Minimum 7 continuous hours of stationary rest in any 24-hour period
• Minimum 24 continuous hours of stationary rest in any 7-day period
• 15-minute rest break required after every 5 hours of work

Basic Fatigue Management (BFM)

An accredited framework that allows slightly extended hours in exchange for enhanced risk management. Requires NHVR accreditation, fatigue risk management systems, and training.

Advanced Fatigue Management (AFM)

The most flexible framework, allowing customised work-rest schedules based on scientific fatigue modelling. Requires the highest level of accreditation and continuous monitoring.

Regardless of which framework applies, the operator's obligation is the same: maintain records that demonstrate compliance. This is where technology becomes essential — manual record-keeping is error-prone and difficult to audit.

4. How Technology Helps

Modern dispatch software transforms fatigue compliance from a manual, reactive process into an automated, proactive one. Here's how:

Automatic Hours Tracking

Instead of relying on driver-completed work diaries, dispatch software calculates working hours automatically from job completion data. Every completed job adds to the driver's running total for the day. This eliminates transcription errors and provides real-time visibility into hours worked.

Proactive Warnings

A three-tier warning system (OK, Warning, Limit Reached) gives dispatchers clear visual indicators before a driver exceeds their limit. The warning threshold is configurable — typically set at 80% of the daily maximum — giving dispatchers time to plan alternative assignments.

Assignment Prevention

When enabled, the system can prevent new job assignments to drivers who have reached their daily limit. This removes the risk of schedulers inadvertently creating non-compliant schedules — a key COR obligation.

Break Detection

Gaps between jobs are automatically detected and recorded as rest breaks. Minimum break duration is configurable (typically 15 minutes) so short gaps between jobs aren't incorrectly counted as rest periods.

Audit-Ready Records

Every fatigue event — job completions, warnings issued, limits reached, and breaks detected — is logged with timestamps. These records can be filtered by date range and exported for compliance reviews, creating the documentation that auditors expect.

5. Compliance Checklist

Use this checklist to assess your organisation's fatigue management practices:

• Hours tracking — Do you have a system that tracks driver working hours in real time? Can you see current hours for any driver at any moment?
• Warning systems — Are dispatchers warned before assigning work to drivers approaching their daily limit?
• Schedule review — Do your scheduling tools check for fatigue conflicts before creating assignments?
• Rest recording — Are rest breaks between jobs automatically detected and recorded?
• Audit trail — Can you produce timestamped fatigue records for any driver over any period for compliance reviews?
• Policy documentation — Do you have a written fatigue management policy that covers your COR obligations?
• Training — Are dispatchers and drivers trained on fatigue management procedures and their COR obligations?
• Escalation procedures — Is there a clear process for when a driver reports fatigue or a warning is triggered?

If you answered "no" to any of these, your organisation may have compliance gaps. Modern dispatch software like Waybill addresses the first five items automatically — giving you the technical foundation for a robust fatigue management system.