2026 Master Code: turning Chain of Responsibility controls into daily workflow

What is the Master Code and why does it matter in 2026?

The Master Code is the industry code of practice registered under the Heavy Vehicle National Law (HVNL) that gives operators, consignors, consignees, packers, loaders, drivers, and schedulers a structured framework for meeting their Chain of Responsibility (CoR) duties. Under section 632A of the HVNL, a registered code of practice may be used in legal proceedings—meaning that following the Master Code can help demonstrate that a party took reasonable steps, while failing to follow it may be cited as evidence that reasonable steps were not taken. With HVNL updates scheduled for 1 August 2026, operators need to understand how the Master Code's controls translate into daily, evidence-generating workflow before the regulatory landscape shifts.

Key takeaways

• The HVNL establishes a shared-responsibility principle (s 26A) meaning every party in the transport chain—from consignor to consignee—owes a primary duty (s 26C) to ensure safety so far as reasonably practicable.
• Breaches of CoR duties are categorised as Category 1 (most serious, exposing a person to risk of death or serious injury) or Category 2 (exposing a person to risk of injury) offences under ss 26F–26G of the HVNL.
• Section 632A of the HVNL allows a registered code of practice (such as the Master Code) to be used as evidence in proceedings, making documented adherence to its controls a practical defence tool.
• Fatigue management duties under Chapter 6 of the HVNL require drivers to carry and maintain work diaries (s 293), and authorised officers can require a driver to stop working if the diary is not produced or is unreliable (s 541).
• CoR compliance software helps operators capture, centralise, and retrieve the evidence that Master Code controls were followed—turning policy into provable, daily workflow.

How does the principle of shared responsibility shape CoR duties?

Section 26A of the HVNL codifies the principle of shared responsibility: each party in the chain of responsibility for a heavy vehicle must take all reasonable steps to ensure the vehicle is used safely and complies with mass, dimension, loading, speed management, and fatigue requirements. This is not a generalised aspiration. It creates concurrent, overlapping duties across multiple parties.

Operationally, this means a consignor who dispatches a load, a packer who assembles it, a loader who places it on the vehicle, a scheduler who plans the run, a driver who operates the vehicle, and a consignee who receives the goods all share responsibility for ensuring compliance. No single party can discharge its duty by pointing to another party's role. Each must demonstrate that it took reasonable steps within its own sphere of influence.

For operators, this translates into practical requirements: verifying load mass and dimensions before dispatch, ensuring schedules allow drivers to meet fatigue requirements, checking that transport documentation is accurate, and confirming that vehicles are roadworthy before each journey. The Chain of Responsibility compliance software path exists precisely to help operators generate and store the records that prove these steps were taken.

What are the primary duties every party in the chain must meet?

Section 26C of the HVNL imposes a primary duty on each party in the chain of responsibility. The duty requires the party to ensure, so far as reasonably practicable, the safety of heavy vehicle transport activities related to the party's role. Section 26B sets out the principles applying to this duty, including that it cannot be transferred to another party and that it applies regardless of whether the party's activities are the sole cause of a breach.

Section 26E prohibits requests and contracts that would cause a breach. A party must not make a request, or enter into a contract, that would induce or require another party to breach the HVNL. This means a consignor cannot contractually require a driver to exceed speed or fatigue limits to meet a delivery deadline, and an operator cannot accept a freight rate that makes compliance with maintenance standards impracticable.

Section 26D extends duties to executives of legal entities: an executive officer of a corporation that is a party in the chain must exercise due diligence to ensure the corporation complies with its duty. This is the CoR equivalent of the due-diligence obligation in work health and safety law—it applies to directors and senior managers personally.

How do Category 1 and Category 2 offences apply to CoR breaches?

The HVNL classifies failures to comply with a primary duty into two offence categories under Part 1A.3:

• Category 1 (s 26F): The most serious offences, where a party's conduct exposes another person to a risk of death or serious injury, and the party was negligent about that risk. These carry the highest penalties.
• Category 2 (s 26G): Where a party's conduct exposes another person to a risk of injury, and the party was negligent about that risk.

Section 632 of the HVNL addresses how courts decide whether a person ought reasonably to have known something—relevant to determining negligence. The test includes what the person knew, what a reasonable person in the same position would have known, and what systems and processes the person had in place to identify and manage risks.

This is where the Master Code becomes operationally critical. A party that can show it followed the Master Code's recommended controls—documented scheduling checks, pre-departure inspections, load verification, fatigue diary reviews—is better positioned to demonstrate it was not negligent. A party with no documented controls faces a steeper evidentiary burden.

What role does the code of practice play in enforcement proceedings?

Section 632A of the HVNL provides that a code of practice may be used in a proceeding for an offence against the Law. The provision allows the code to be cited as evidence of what is known about a hazard or risk, and of the measures that may be implemented to eliminate or mitigate that risk. Crucially, the section also allows a court to consider whether a party failed to follow a code when determining whether the party took reasonable steps.

The Master Code, as a registered industry code of practice, therefore serves a dual function:

1. Positive evidence: Demonstrating that a party implemented the code's recommended controls supports a defence that reasonable steps were taken.
2. Negative inference: Failure to follow the code may be treated as evidence that reasonable steps were not taken.

This makes the Master Code more than guidance—it is a practical evidentiary instrument. Operators who embed its controls into daily workflow and capture evidence of adherence are building a compliance position that is defensible in proceedings.

For deeper guidance on building defensible evidence, see audit-ready compliance evidence: what transport operators should centralise before review.

How do fatigue management duties translate to daily workflow?

Chapter 6 of the HVNL governs driver fatigue management. The chapter sets out work and rest hour requirements, work diary obligations, and the duties of parties in the chain to manage fatigue risks.

Section 293 requires a driver of a fatigue-regulated heavy vehicle to carry a work diary. Sections 294–299 set out the information that must be recorded in the work diary, including odometer readings, work and rest times, and other prescribed details. The driver must record information immediately after starting work (s 297).

Section 540 allows an authorised officer to require a driver to stop working if the officer reasonably believes the driver is impaired by fatigue. Section 541 allows an officer to require a driver to stop working if the work diary is not produced or is considered unreliable.

For operators, these provisions create specific daily workflow requirements:

• Driver diary checks: Operators must have a system to collect and verify driver work diaries, checking for compliance with work and rest hour limits. CoR compliance software such as CoRGuard supports this through driver diary entry and verification workflows—while an Electronic Work Diary module is planned for the future, the current capability covers manual diary checking.
• Scheduling controls: Schedulers must plan runs that allow drivers to meet fatigue requirements without exceeding maximum work hours.
• Recordkeeping: Operators must retain work diary records for the period prescribed by the HVNL and be able to produce them on request.

For more on recent enforcement signals and what they mean for operators, see fatigue and driver diary checks: what recent NHVR enforcement signals mean for operators.

What maintenance and vehicle defect obligations affect operators?

The HVNL places obligations on operators to maintain vehicles in a roadworthy condition. Sections 528–530 of the HVNL deal with vehicle defect notices, including major and minor defect notices, self-clearing defect notices, and clearance requirements.

If a vehicle is issued with a major or minor defect notice, section 529 restricts the use of that vehicle contrary to the notice. Section 529A allows for permission to use a vehicle subject to a defect notice in limited circumstances, and section 529B sets out permitted use without an authorised officer's permission.

For operators, the Master Code's maintenance controls translate into daily workflow through:

• Pre-departure inspection records: Documenting that a vehicle was inspected before each journey and that defects were identified and addressed.
• Scheduled maintenance tracking: Maintaining a register of servicing intervals, inspections, and repairs, linked to vehicle identification.
• Defect notice management: Recording when a defect notice was issued, what action was taken, and when the notice was cleared.
• NHVAS evidence: For operators accredited under the National Heavy Vehicle Accreditation Scheme (NHVAS), maintenance evidence must be maintained and available for audit.

CoR compliance software supports this by centralising maintenance records, inspection checklists, and defect tracking in a single system. For more on the transition from NHVAS to the Heavy Vehicle Accreditation (HVA) framework and why maintenance evidence needs to be easier to prove, see NHVAS to HVA transition: why maintenance evidence needs to be easier to prove.

How do transport documentation and container weight requirements work?

Sections 186–187 of the HVNL create offences for false or misleading transport documentation for goods. Section 187 specifically addresses false or misleading information in a container weight declaration. Section 190 imposes a duty of responsible entities for container weight declarations.

These provisions mean that every party involved in providing transport documentation—including consignors, packers, loaders, and operators—must ensure the information they provide is accurate. A consignor who declares an incorrect mass, or a loader who records false dimension information, commits an offence under the HVNL.

The Master Code's controls for transport documentation translate into daily workflow through:

• Consignment verification: Checking that the declared mass and dimensions of a load match the actual mass and dimensions before dispatch.
• Container weight declarations: Ensuring that container weight declarations are completed accurately and retained.
• Documentation chain: Maintaining records of who provided what information, so that liability can be traced to the responsible party.

How does CoR compliance software turn controls into daily evidence?

The Master Code defines what reasonable steps look like. CoR compliance software is the mechanism that ensures those steps are taken consistently and that evidence of compliance is captured automatically. Here's how CoRGuard maps Master Code controls to daily workflow:

Each of these workflows generates a time-stamped, attributable record that can be produced during an audit, investigation, or legal proceeding. The Features page provides a detailed overview of how these workflows function in practice.

What should operators do next to prepare for the 2026 Master Code environment?

Operators should take the following practical steps:

1. Map current controls against Master Code recommendations: Identify which controls are already in place, which are documented, and which exist only in practice without evidence. Use corrective actions and risk registers to track gaps.

2. Centralise evidence in a single system: Move scattered records—paper diaries, spreadsheets, email chains, paper inspection forms—into a CoR compliance software platform that produces structured, retrievable evidence.

3. Implement daily verification workflows: Ensure that each role in the chain has a defined, daily workflow for compliance checks: driver diary verification, pre-departure inspections, load mass confirmation, and documentation accuracy.

4. Brief executives on due diligence obligations: Directors and senior managers must understand their personal duty under s 26D. Provide them with visibility through dashboards and compliance reporting.

5. Plan for the August 2026 HVNL changes: While current HVNL provisions remain active until the scheduled updates take effect, operators should begin reviewing systems now to ensure they can adapt to new requirements without disruption. See What the 2026 HVNL changes mean for transport compliance systems for detailed analysis.

6. Engage expert advisory support where needed: For operators who need gap analysis, training, or chartered risk assessment, MAEZ provides the expert advisory layer. CoRGuard at chainresponsibility.au is the SaaS implementation path where software-generated evidence is needed.

Frequently asked questions

What is the Master Code under the HVNL?

The Master Code is a registered industry code of practice under the Heavy Vehicle National Law. Section 632A of the HVNL allows a registered code of practice to be used as evidence in legal proceedings. Following the Master Code's controls helps parties demonstrate they took reasonable steps to meet their CoR duties; failing to follow it may be cited as evidence that reasonable steps were not taken.

Who has a Chain of Responsibility duty under the HVNL?

Under section 26A (principle of shared responsibility) and section 26C (primary duty), every party in the chain—including consignors, consignees, packers, loaders, drivers, schedulers, and operators—owes a duty to ensure heavy vehicle transport activities are safe so far as reasonably practicable. Section 26D extends this duty to executives of corporate parties, who must exercise due diligence.

What is the difference between a Category 1 and Category 2 offence under the HVNL?

Category 1 offences (s 26F) involve conduct that exposes a person to a risk of death or serious injury, where the party was negligent. Category 2 offences (s 26G) involve conduct that exposes a person to a risk of injury, where the party was negligent. Category 1 offences carry the highest penalties under the HVNL.

Do drivers have to carry a work diary under the HVNL?

Yes. Section 293 of the HVNL requires a driver of a fatigue-regulated heavy vehicle to carry a work diary. Sections 294–299 specify the information that must be recorded, including odometer readings and work and rest times. An authorised officer can require a driver to stop working if the diary is not produced or is considered unreliable (s 541).

How does CoR compliance software help with Master Code adherence?

CoR compliance software turns Master Code controls into structured, repeatable daily workflows—driver diary checks, pre-departure inspections, load verification, and documentation management—and captures time-stamped evidence of each step. This evidence can be produced during audits, investigations, or legal proceedings to demonstrate that reasonable steps were taken.

Can following the Master Code guarantee compliance?

No. Following the Master Code does not guarantee compliance or provide immunity from liability. The HVNL requires each party to take all reasonable steps, and compliance depends on the specific circumstances of each transport activity. The Master Code provides a framework for demonstrating reasonable steps, but parties must still assess and manage risks in their own operational context. CoR compliance software supports this process but does not remove a party's legal liability.

When do the 2026 HVNL changes take effect?

HVNL updates are scheduled for 1 August 2026. Until that date, the current HVNL provisions remain active and enforceable. Operators should prepare for the changes by reviewing their compliance systems now, but should not assume future provisions are in effect before the commencement date.