Chain of Responsibility for executives: the decisions and evidence that matter

An executive of a business with a Heavy Vehicle National Law (HVNL) safety duty must exercise due diligence to ensure the business complies with that duty. In practice, that means understanding the transport activities and public risks, providing and using suitable resources and processes, receiving and responding to information about hazards and incidents, and checking that those controls work. Signing a policy, appointing a transport manager or buying software is not the end of the executive's job. NHVR's executive-duty guidance describes the duty and the role of management in the Chain of Responsibility (CoR).

This is a guide for directors, partners, executive officers and managers involved in businesses that are parties in a heavy-vehicle transport activity. The amended HVNL commenced on 1 August 2026, according to the NHVR commencement announcement. Read current sources, not a pre-commencement reform preview. The HVNL applies through participating jurisdictions—ACT, NSW, Queensland, South Australia, Tasmania and Victoria—and NHVR says it has not commenced in Western Australia or the Northern Territory. A WA or NT vehicle crossing into an HVNL jurisdiction can still become subject to it. Obtain local advice on the actual route, operations and applicable law.

What the executive duty covers

The current NHVR guidance identifies executives broadly: an executive officer, director, partner, manager or another person who takes part in management can be in scope. A job title is not a safe exclusion test. The business must first have a relevant safety duty; the executive then has their own due-diligence duty concerning that duty. The HVNL §26D gives the statutory frame; confirm the current in-force consolidated text after the August 2026 amendments before publication.

The NHVR CoR pages explain the primary duty and other safety-duty provisions, including prohibited requests or contracts. A business may influence safety without operating the truck: a scheduler can create an impossible deadline, a consignor can misstate a load, or a loading site can ignore vehicle condition or fatigue. The executive must understand how their business's decisions affect the transport activity. The duty is not limited to inspecting driver files.

Due diligence is a process of reasonable, active steps, not an absolute promise that no incident will occur. NHVR describes keeping transport-safety knowledge current, understanding the business's activity and hazards, ensuring suitable resources and risk-control processes are used, and making sure hazard and incident information is received, considered and answered promptly. The executive should be able to show how they know these processes operate in practice. A presentation from a manager is useful, but verification may require sampling records, testing exception handling and following a serious issue through to closure.

Start with the business's real CoR footprint

Map the activities rather than applying a generic fleet checklist. For each contract, lane, depot, loading site and transport partner, ask which decisions the business controls or influences. Identify who sets delivery windows; who specifies mass and load restraint; who loads, packs or dispatches; who maintains vehicles; who schedules drivers; and who receives incident or defect information. The resulting map should show the decision owner and escalation route for each risk.

This is a management prompt, not a declaration that every organisation has every listed statutory role. A manufacturer that never schedules drivers may still influence loading or contracts; a carrier that performs all transport work has a different risk profile. Seek specialist advice where responsibilities overlap.

Six executive due-diligence practices

1. Maintain transport-safety knowledge

Assign someone to brief the executive team on the current HVNL, NHVR notices, local derogations and the business's relevant operations. The August 2026 reform makes an old compliance manual a poor sole source. Record what changed, who assessed it, which controls were updated and what training followed. The executive does not need to operate every truck, but must understand enough to challenge an implausible assurance and ask the right questions.

2. Understand the hazards the business creates

Ask for evidence from the actual lanes, depots, products and contractors. A national policy saying “obey speed limits” does not answer whether a dispatcher routinely promises a journey that cannot be completed within legal time and rest arrangements. Review workload peaks, vehicle condition, load restraints, road access and public exposure. Talk to workers and transport partners about what happens when a delivery is late or a vehicle defect is found. Near misses and rejected jobs can be valuable signals.

3. Resource controls that can be used

Set budgets, staffing and decision authority so transport and loading can be stopped when unsafe. A safety manager without power to override an impossible schedule is not a functioning control. Ensure suitable training, maintenance capacity, safe loading equipment, reliable communication and competent supervision. The right level of resource depends on the business's activities and risks; software may organize records, but it cannot replace operational capacity.

4. Establish risk-control and escalation processes

Define how a dangerous instruction is challenged, how a driver or loader reports a concern without pressure to continue, who decides to hold a vehicle or load, and how a subcontractor's repeated breach is addressed. Bring procurement and commercial teams into the process: contract terms and payment incentives can undermine the transport team's procedures. Link the safety management process to actual work orders and decisions, not only a policy folder.

5. Receive and act on hazard information promptly

The NHVR's executive explanation expressly includes processes to receive, consider and respond in a timely way to hazards, risks and incidents. Define what reaches the executive, within what time, and how urgent issues are held pending action. A dashboard showing green can conceal unresolved severe defects if the inputs are late or filtered. Review exceptions, not just monthly averages.

6. Verify that the system works

Select a sample of real trips, loads, vehicle-defect closures and subcontractor decisions. Compare promised process to records and worker accounts. Ask whether the control prevented the foreseeable failure, whether staff knew when to stop, and whether corrective action remained effective after the first audit. Keep minutes, assigned actions and closure evidence. The NHVR Master Code of Practice 2026 provides industry guidance, including evidence of implementation and effectiveness; it does not replace the law or prove compliance by possession alone.

A practical executive review pack

Bring these items to a quarterly or risk-triggered board/management review, with owner, date and action status. The interval is a governance choice, not a universal HVNL deadline.

The pack should show decisions, not merely documents received. For example, an executive who sees repeated late deliveries, fatigue complaints and vehicle-defect deferrals should ask whether the contract and allocation model require a change. A new training slide alone may not address the source of pressure.

Scenario: a retail delivery window becomes unsafe

A warehouse promises the customer a fixed early-morning delivery despite a loading delay. A dispatcher suggests that the carrier “make up time.” The commercial manager, scheduler and transport manager all influence the outcome. Under a useful CoR process, the job is held or the delivery window renegotiated; the driver is not pressured to speed or compromise rest, and the loading team confirms the actual load and vehicle conditions. The executive later reviews why the original promise was made and whether contract or KPI changes are needed. The evidence is the changed dispatch decision, not a post-incident memo stating that safety comes first.

Common executive mistakes

• Delegating and disengaging. A manager can perform tasks, but the executive must take reasonable due-diligence steps to see that the business's safety duties are met.
• Looking only at the carrier. Loaders, consignors, schedulers, commercial teams and clients can create or influence transport risk.
• Treating a contractor contract as a liability transfer. A written allocation does not erase the safety effect of your own requests or decisions.
• Relying on policy counts. An approved procedure is weak evidence if crews cannot use it under real delivery pressure.
• Ignoring public risk. The transport decision can affect road users as well as employees.
• Using pre-August 2026 legal summaries. The amended HVNL is in force; check current NHVR material and local law rather than an old implementation timetable.
• Claiming a software score proves compliance. A dashboard is useful only if the underlying decisions and records are accurate and the executive responds to them.

How Complys may support the record, subject to product verification

The final manifest names /au/chain-of-responsibility-software as the money page, but a current live route was not independently confirmed during this check. The observed Complys Australia pricing page markets transport/fleet CoR, driver and vehicle records and fatigue; that is marketing, not evidence of which workflows are implemented in the user's plan. The observed AU WHS page describes general assessments and record management, but it is not a substitute for a dedicated CoR route. Do not insert a broken commercial link or promise fatigue calculations, legal verification, accreditation, real-time vehicle telemetry or executive-duty certification without a current demonstration.

After route and implementation QA, a truthful CTA would be: Ask Complys to demonstrate how its current Australian product stores your CoR risk decisions, transport/driver/vehicle records, exceptions and executive review actions. An executive still needs to read, challenge and act on the information.

Source, claim, owner, link, product and writer-side QA register — 5 October 2026

Terminal writer-side disposition: READY. No Complys repository or live page was modified.