Compliance guide

WHS primary duty and HVNL Chain of Responsibility alignment: what transport operators must know

The HVNL primary duty under section 26C and the WHS primary duty both require parties to ensure safety so far as is reasonably practicable. This article explains how the two regimes align, who holds duties, and what evidence operators need.

WHS primary dutyHVNL primary dutyChain of Responsibility alignmentHVNL section 26CHVNL section 26D executive duty
Workers in hi-vis vests reviewing compliance documents at a desk inside an Australian heavy vehicle transport office, with prime movers and trailers visible through the window in the depot yard beyond.
GPT-generated CoRGuard article image
Published 4 September 2026/WHS and HVNL primary duty alignment

What is the WHS primary duty and HVNL Chain of Responsibility alignment?

The HVNL primary duty (section 26C) and the WHS primary duty are structurally aligned: both require duty holders to eliminate or minimise risks to safety so far as is reasonably practicable. The HVNL applies this duty to every party in the heavy vehicle transport supply chain — consignors, packers, loaders, receivers, schedulers, operators, and drivers — while WHS law applies it to persons conducting a business or undertaking (PCBUs). Transport operators must satisfy both regimes simultaneously, which means building compliance systems that produce evidence for both WHS regulators and the National Heavy Vehicle Regulator (NHVR).

Key takeaways

  • HVNL section 26C imposes a primary duty on each CoR party to ensure the safety of transport activities, so far as is reasonably practicable. This duty is modelled on the WHS primary duty concept.
  • Executive officers have a separate personal duty under HVNL section 26D to exercise due diligence to ensure the entity complies with its primary duty — mirroring the WHS officer duty under WHS legislation.
  • HVNL section 26E prohibits requests, contracts, or arrangements that would encourage or require a driver or another party to breach the law, including speed, fatigue, mass, dimension, or loading requirements.
  • Fatigue, vehicle maintenance, speed, and loading are the core operational areas where primary duty compliance is tested during NHVR investigations and audits.
  • Evidence is the deciding factor: regulators assess whether a duty holder took reasonably practicable steps by examining documented systems, records, and corrective actions — not intentions.

What is the HVNL primary duty under section 26C?

Under the Heavy Vehicle National Law, section 26C establishes the primary duty for every party in the Chain of Responsibility. Each party must ensure, so far as is reasonably practicable, the safety of transport activities related to a heavy vehicle. This duty extends to all aspects of the transport activity that the party influences or controls, including scheduling, loading, vehicle maintenance, driver fatigue management, and speed management.

The HVNL sets out the principle of shared responsibility in section 26A, which makes clear that responsibility for heavy vehicle safety is shared among all parties in the transport supply chain. Section 26B sets out the principles applying to duties, reinforcing that the duty is not transferable — a party cannot contract out of it. Even if you outsource an activity, you retain a duty to the extent you influence or control that activity.

Operationally, this means that an operator cannot simply rely on a driver to manage fatigue, a loader to manage mass, or a scheduler to manage time. The operator must take active steps to ensure those parties perform their roles safely, and must be able to demonstrate those steps with evidence.

The NHVR has published regulatory guidance confirming that under HVNL section 26C, each party has a primary duty to ensure the safety of transport activities, so far as is reasonably practicable.

How does the WHS primary duty align with HVNL CoR duties?

The WHS primary duty, found in model WHS legislation (and enacted in each participating jurisdiction), requires a PCBU to ensure, so far as is reasonably practicable, the health and safety of workers and others who may be affected by the work. This duty covers the same risk-management territory as the HVNL primary duty: identifying hazards, assessing risks, implementing controls, and reviewing their effectiveness.

The alignment between the two regimes is deliberate. The HVNL CoR provisions were reformed in 2018 to bring CoR duties closer to WHS-style duties, replacing the older "reasonable steps" defence with a primary duty framework. Both regimes now use the "so far as is reasonably practicable" test, which requires duty holders to consider what could be done, what is reasonable in the circumstances, and whether the cost and effort of a control is proportionate to the risk.

For transport operators, the practical implication is that a single, well-structured safety management system can address both WHS and HVNL duties simultaneously. However, the two regimes have different regulators, different enforcement powers, and different penalty categories. An operator may face action from both SafeWork (or the state WHS regulator) and the NHVR for the same incident or systemic failure. For a deeper comparison of how CoR obligations extend across the supply chain, see Chain of Responsibility Compliance Software.

As MAEZ has noted, HVNL duty-of-care obligations and penalties are modelled on WHS law, meaning many systems can be aligned — but CoR duties extend across the entire transport supply chain, not just the workplace.

Who holds the primary duty in the transport supply chain?

The HVNL identifies multiple parties who each hold a primary duty:

  • Consignors — parties who commission or engage the transport of goods by heavy vehicle.
  • Packers — parties who pack or assemble goods for transport.
  • Loaders — parties who load goods onto or into a heavy vehicle.
  • Receivers/consignees — parties who receive goods transported by heavy vehicle.
  • Schedulers — parties who schedule the transport of goods by heavy vehicle, including setting time frames that affect driver fatigue or speed.
  • Operators — parties who operate a heavy vehicle, including the registered operator and anyone who manages or controls the vehicle's use.
  • Drivers — the person driving the heavy vehicle.
  • Executives — officers of a corporation or unincorporated association, who hold a separate personal duty under section 26D.

Each party's duty is limited to the extent of their influence and control over the transport activity. A consignor who does not control loading is not responsible for a loading breach they had no capacity to influence — but they are responsible for ensuring they do not provide false or misleading information about the goods, mass, or dimensions that could create a risk.

What does "reasonably practicable" mean for transport operators?

The "so far as is reasonably practicable" test requires duty holders to do what a reasonable person in the same position would do to eliminate or minimise risk. Under the HVNL and WHS regimes, this involves considering:

  • The likelihood of a hazard or risk occurring.
  • The degree of harm that might result.
  • What the duty holder knows (or ought reasonably to know) about the hazard and ways to eliminate or reduce it.
  • The availability and suitability of controls.
  • The cost of implementing controls, assessed against the risk.

For transport operators, this means you cannot simply set a fatigue policy and assume compliance. You must actively check driver work diaries, verify that schedules are realistic, confirm vehicles are maintained, and ensure loading meets mass and dimension requirements. You must also respond to incidents, near misses, and breach notifications with documented corrective actions.

For practical guidance on what the NHVR expects operators to prove in relation to fatigue, see NHVR fatigue checks and operator evidence obligations under the HVNL.

What are the executive officer duties under HVNL section 26D?

HVNL section 26D imposes a personal duty on executives of entities that have a primary duty under the HVNL. An executive (director, partner, or person who participates in the management of the entity) must exercise due diligence to ensure the entity complies with its primary duty.

This duty mirrors the officer duty under WHS legislation, where officers of a PCBU must exercise due diligence to ensure the PCBU meets its health and safety obligations. Due diligence under both regimes requires the executive to:

  • Acquire and keep up to date with knowledge about work health and safety matters.
  • Gain an understanding of the nature of the operations and the hazards and risks involved.
  • Ensure the entity has and uses appropriate resources and processes to eliminate or minimise risks.
  • Ensure the entity has and uses appropriate processes for receiving and considering information about incidents, hazards, and risks, and for responding in a timely way.
  • Ensure the entity implements processes for complying with any duty or obligation.

Operationally, this means an executive cannot delegate compliance to a safety manager and then disengage. They must be able to demonstrate that they have actively overseen the compliance system — reviewing reports, asking questions, approving resources, and following up on corrective actions. For operators preparing for the upcoming HVNL reforms, this duty is likely to become more prominent as the new Heavy Vehicle National Law takes effect from 1 August 2026. See HVNL 2026 reform and transport compliance software for transition guidance.

What are prohibited requests and contracts under HVNL section 26E?

HVNL section 26E prohibits a person from making a request, entering into a contract, or making an arrangement that would encourage or cause a driver or another party to breach the HVNL. This includes breaches related to:

  • Speed limits.
  • Fatigue management (work and rest hours).
  • Vehicle mass, dimension, or loading requirements.
  • Vehicle standards.

The prohibition applies regardless of whether the breach actually occurs — the act of making the request or contract is itself an offence. This means a consignor who sets an unrealistic delivery time that would require a driver to exceed speed limits or breach fatigue rules has committed an offence under section 26E, even if the driver does not actually speed or drive fatigued.

Operationally, transport operators must review their contracts, scheduling practices, and communication with drivers and customers to ensure no term, condition, or informal arrangement creates pressure to breach the law. For guidance on embedding CoR controls into daily workflow, see 2026 Master Code: turning Chain of Responsibility controls into daily workflow.

How do fatigue management obligations connect to the primary duty?

Fatigue management is one of the most significant areas where primary duty compliance is assessed. Under HVNL Chapter 6 (Vehicle operations — driver fatigue), the law sets out:

  • Standard hours for solo and two-up drivers (Division 2 of Part 6.2).
  • BFM (Basic Fatigue Management) hours for accredited operators.
  • AFM (Advanced Fatigue Management) options for operators with more sophisticated fatigue management systems.
  • Work diary requirements (Division 5 of Part 6.2) — drivers of fatigue-regulated heavy vehicles must carry and complete a work diary.
  • Operator duty under section 264 — employers, prime contractors, operators, and schedulers must take all reasonable steps to ensure a driver does not breach work and rest requirements.

The primary duty under section 26C overlays these specific provisions. Even if an operator is not accredited under BFM or AFM, they still hold a primary duty to manage fatigue risks. This means the operator must have systems to check work diary entries, verify rest periods, ensure schedules allow for legal compliance, and respond to fatigue-related incidents or breaches.

CoRGuard supports fatigue compliance activity through driver diary checks, which allow operators to record and review work diary entries, flag potential breaches, and document corrective actions. The Electronic Work Diary module is not yet live, but the current driver diary check functionality provides a structured workflow for capturing, reviewing, and evidencing fatigue compliance.

How do vehicle maintenance and vehicle standards connect to the primary duty?

Vehicle maintenance is another core area where primary duty compliance is tested. The HVNL imposes vehicle standards requirements, and operators must ensure their vehicles are maintained in a roadworthy condition. A failure to maintain vehicles — whether brakes, tyres, lights, couplings, or structural integrity — is a breach of the primary duty if the operator could have taken reasonably practicable steps to prevent it.

For operators accredited under the NHVAS (National Heavy Vehicle Accreditation Scheme), the maintenance module requires documented maintenance schedules, inspection records, and defect reporting. Even without NHVAS accreditation, the primary duty requires operators to have a systematic approach to maintenance.

CoRGuard supports maintenance evidence through structured workflows for recording inspections, defects, repairs, and corrective actions. This evidence is critical during NHVR audits, roadside inspections, and post-incident investigations. For detailed guidance on maintenance evidence, see Vehicle maintenance evidence for NHVAS audit readiness and corrective actions.

What evidence do operators need to demonstrate primary duty compliance?

The HVNL and WHS regimes both shift the burden of proof in practice — if a breach occurs, the duty holder must be able to demonstrate what steps they took. Without evidence, the regulator and courts will infer that no steps were taken.

The evidence an operator needs includes:

  • Policies and procedures — documented systems for fatigue, maintenance, speed, loading, and mass management.
  • Records of action — work diary checks, maintenance inspections, defect reports, pre-departure checks, load weight records, and scheduling records.
  • Training records — evidence that drivers, schedulers, loaders, and managers have been trained on their CoR obligations.
  • Contract reviews — evidence that contracts and arrangements have been assessed for prohibited terms under section 26E.
  • Incident and breach records — documentation of incidents, near misses, and breaches, along with the corrective actions taken.
  • Executive oversight records — minutes, reports, or dashboards showing that executives have actively overseen compliance.
  • Risk registers — a living document identifying hazards, risks, controls, and residual risk ratings.

For a comprehensive view of what to centralise before an audit or investigation, see Audit-ready evidence: what transport operators should centralise before review. To understand how corrective actions and risk registers form the backbone of ongoing compliance, see Corrective actions and risk registers: the quiet backbone of audit-ready compliance.

How CoRGuard workflows support primary duty compliance

CoRGuard at chainresponsibility.au is the SaaS implementation path where software evidence is needed. The platform provides structured workflows that map to the primary duty obligations under the HVNL and WHS:

Fatigue and driver diary checks

CoRGuard's driver diary check workflow allows operators to record work diary entries, compare them against applicable work and rest hour limits, flag potential breaches, and document the operator's response. Each check creates a timestamped record that can be produced during an NHVR investigation or audit. This directly supports the operator's duty under HVNL section 264 to take all reasonable steps to ensure driver compliance.

Maintenance evidence

The platform's maintenance workflows support recording of inspections, defects, and corrective actions, creating an evidence trail that demonstrates the operator's primary duty to maintain vehicles in a safe condition. This is particularly important for operators transitioning from NHVAS to the new Heavy Vehicle Accreditation (HVA) framework. See NHVAS Compliance Software for more detail.

Risk register and corrective actions

CoRGuard includes a risk register and corrective action module that allows operators to identify hazards, assign controls, track implementation, and review effectiveness. This directly supports the due diligence duty of executives under HVNL section 26D and the WHS officer duty, because it provides a visible, auditable record of executive oversight.

Centralised evidence

All workflows within CoRGuard feed into a centralised evidence repository. This means that when the NHVR, a WHS regulator, or an auditor requests evidence of compliance activity, the operator can produce it quickly and consistently. Explore the full range of capabilities at Features.

Practical next steps for transport operators

To align your WHS and HVNL primary duty compliance:

  1. Map your CoR parties — identify every party in your supply chain who holds a primary duty and confirm they understand their obligations.
  2. Audit your contracts — review all contracts, scheduling practices, and informal arrangements for prohibited terms under HVNL section 26E.
  3. Implement structured fatigue checks — use CoRGuard's driver diary check workflow to systematically record and review work diary entries.
  4. Document your maintenance system — ensure inspections, defects, and repairs are recorded in a consistent, auditable format.
  5. Maintain a living risk register — identify hazards, assign controls, track corrective actions, and review effectiveness on a recurring schedule.
  6. Record executive oversight — ensure executives can demonstrate due diligence through documented review of compliance reports and active engagement with the safety system.
  7. Prepare for the 2026 HVNL transition — the new HVNL takes effect from 1 August 2026. Start aligning your systems now to avoid a last-minute scramble.

For operators who need expert advisory support — including chartered risk assessments, gap analysis, and training — MAEZ provides the advisory and training layer. CoRGuard provides the software implementation layer where documented evidence is required. To learn more about the platform, visit About CoRGuard.

Frequently asked questions

What is the HVNL primary duty and how does it differ from the old reasonable steps test?

The HVNL primary duty under section 26C requires each CoR party to ensure the safety of transport activities so far as is reasonably practicable. This replaced the earlier "reasonable steps" defence, which required a party to show they had taken reasonable steps to prevent a breach. The primary duty is broader — it is a proactive, ongoing obligation to identify and manage risks, not a reactive defence after a breach has occurred.

Do WHS and HVNL primary duties overlap, and can one system satisfy both?

Yes, the duties overlap significantly because the HVNL CoR provisions were modelled on WHS law. Both use the "so far as is reasonably practicable" test and both require hazard identification, risk assessment, control implementation, and review. A well-structured safety management system can address both regimes, but operators must ensure their systems produce evidence that satisfies both the NHVR and the relevant state WHS regulator.

Who is an executive for the purposes of HVNL section 26D?

Under HVNL section 26D, an executive is a person who participates in the management of an entity that has a primary duty. This includes directors, partners, and other senior managers who are in a position to influence the entity's compliance. The executive duty requires due diligence — meaning the executive must actively oversee the compliance system, not merely rely on delegation.

What is a prohibited request under HVNL section 26E?

A prohibited request is any request, contract, or arrangement that encourages or causes a driver or another party to breach the HVNL — including speed limits, fatigue requirements, mass or dimension limits, or vehicle standards. The offence is committed when the request or contract is made, regardless of whether the resulting breach actually occurs.

What evidence does the NHVR look for when investigating a primary duty breach?

The NHVR looks for documented systems and records that show the duty holder took reasonably practicable steps. This includes policies, training records, work diary checks, maintenance records, scheduling records, contract reviews, incident reports, corrective actions, and evidence of executive oversight. The absence of documented evidence is treated as evidence that no steps were taken.

Can CoRGuard guarantee compliance with the HVNL primary duty?

No. CoRGuard does not guarantee compliance or remove liability. The HVNL primary duty is a legal obligation that depends on the specific circumstances of each operator's activities. CoRGuard provides structured workflows that support compliance activity and generate evidence — but the duty holder remains responsible for ensuring that those workflows are used correctly and that the resulting evidence reflects genuine, reasonably practicable steps.

What should operators do to prepare for the HVNL changes in 2026?

Operators should begin aligning their compliance systems with the upcoming HVNL reforms now, ahead of the 1 August 2026 commencement date. This includes reviewing safety management systems, ensuring evidence workflows are in place for fatigue and maintenance, and confirming that executives can demonstrate due diligence. Early preparation reduces the risk of non-compliance during the transition period.

Frequently asked questions

Practical answers

What is the HVNL primary duty and how does it differ from the old reasonable steps test?
The HVNL primary duty under section 26C requires each CoR party to ensure the safety of transport activities so far as is reasonably practicable. This replaced the earlier 'reasonable steps' defence, which required a party to show they had taken reasonable steps to prevent a breach. The primary duty is broader — it is a proactive, ongoing obligation to identify and manage risks, not a reactive defence after a breach has occurred.
Do WHS and HVNL primary duties overlap, and can one system satisfy both?
Yes, the duties overlap significantly because the HVNL CoR provisions were modelled on WHS law. Both use the 'so far as is reasonably practicable' test and both require hazard identification, risk assessment, control implementation, and review. A well-structured safety management system can address both regimes, but operators must ensure their systems produce evidence that satisfies both the NHVR and the relevant state WHS regulator.
Who is an executive for the purposes of HVNL section 26D?
Under HVNL section 26D, an executive is a person who participates in the management of an entity that has a primary duty. This includes directors, partners, and other senior managers who are in a position to influence the entity's compliance. The executive duty requires due diligence — meaning the executive must actively oversee the compliance system, not merely rely on delegation.
What is a prohibited request under HVNL section 26E?
A prohibited request is any request, contract, or arrangement that encourages or causes a driver or another party to breach the HVNL — including speed limits, fatigue requirements, mass or dimension limits, or vehicle standards. The offence is committed when the request or contract is made, regardless of whether the resulting breach actually occurs.
What evidence does the NHVR look for when investigating a primary duty breach?
The NHVR looks for documented systems and records that show the duty holder took reasonably practicable steps. This includes policies, training records, work diary checks, maintenance records, scheduling records, contract reviews, incident reports, corrective actions, and evidence of executive oversight. The absence of documented evidence is treated as evidence that no steps were taken.
Can CoRGuard guarantee compliance with the HVNL primary duty?
No. CoRGuard does not guarantee compliance or remove liability. The HVNL primary duty is a legal obligation that depends on the specific circumstances of each operator's activities. CoRGuard provides structured workflows that support compliance activity and generate evidence — but the duty holder remains responsible for ensuring that those workflows are used correctly and that the resulting evidence reflects genuine, reasonably practicable steps.
What should operators do to prepare for the HVNL changes in 2026?
Operators should begin aligning their compliance systems with the upcoming HVNL reforms now, ahead of the 1 August 2026 commencement date. This includes reviewing safety management systems, ensuring evidence workflows are in place for fatigue and maintenance, and confirming that executives can demonstrate due diligence. Early preparation reduces the risk of non-compliance during the transition period.

See how CoRGuard handles your compliance workflow

Book a short demo and we will map CoRGuard to your fleet, depots, drivers, contractors, NHVAS obligations, and Chain of Responsibility risk points.