Chain of Responsibility in Transport: How Asset Management Software Protects Every Party in the Chain

Chain of Responsibility (CoR) under the Heavy Vehicle National Law (HVNL) requires every party in a transport supply chain, including schedulers, consignors, loaders, and operators, to take all reasonable steps to prevent safety breaches. Since the 2018 HVNL amendments, schedulers, loaders, consignors, and operators can all face prosecution if their decisions contributed to a road safety breach, even if they never touched the vehicle. The question for your business is not whether Chain of Responsibility (CoR) applies to you. It is whether your records can prove you took reasonable steps.

Key Takeaways

• Chain of Responsibility under the HVNL applies to every party in the transport supply chain, including schedulers, consignors, loaders, and operators, not just drivers.
• Operators must demonstrate “reasonable steps” to manage safety risks; verbal assurances and undated spreadsheet entries do not constitute sufficient proof.
• Asset maintenance records, pre-start checklists, and defect reports count as CoR documentation when they are timestamped and linked to a specific asset and operator.
• A defect that is raised but not actioned is a liability gap. CoR evidence requires the full loop: defect captured, work order raised, repair completed, and signed off.
• Digital asset management systems generate CoR-ready records automatically, reducing the administrative burden on fleet supervisors and safety officers.

What Chain of Responsibility Means Under the HVNL

The Heavy Vehicle National Law governs the safe use of heavy vehicles on Australian roads. Chain of Responsibility is the framework within the HVNL that distributes legal obligations across every party whose decisions or actions can influence how safely a vehicle is driven, loaded, or maintained. 

Before 2018, CoR obligations were narrower and operators applied them inconsistently. The amendments that came into effect on 1 October 2018 introduced a primary duty of care for all parties in the chain and gave the National Heavy Vehicle Regulator (NHVR) stronger enforcement tools.

Under the primary duty, each party must take all reasonable steps to ensure their conduct does not cause, or contribute to, a contravention of a safety duty. This is not a passive obligation. It requires active systems, documented processes, and evidence that those systems are working.

The 2018 amendments introduced three significant changes: 

• Every CoR party now holds a primary duty of care, not just a duty to avoid specific prohibited conduct. 
• Executive liability provisions mean that company officers can be held personally liable where they knew, or ought to have known, about non-compliance and failed to act.
• The NHVR gained broader powers to issue improvement notices, conduct audits, and pursue prosecutions without waiting for an incident to occur. 

Who is in the Chain and What Does Each Party Owe?

The HVNL identifies seven categories of CoR party: consignors, consignees, packers, loaders, schedulers, operators, and drivers. Most transport businesses occupy more than one of these roles simultaneously. A freight operator who books their own loads, manages their own drivers, and owns their own fleet acts as consignor, scheduler, and operator at the same time, carrying all three sets of obligations.

Each role carries specific duties tied to what that party controls. Consignors must not demand delivery schedules that pressure drivers to speed or skip rest. Loaders must not create loads that make a vehicle unsafe or non-compliant with mass limits. The shared thread is that each party is responsible for what they can control, and they must be able to show what steps they took to exercise that control.

Operator and Scheduler Responsibilities

Operators carry a duty to ensure the vehicle is roadworthy and maintained, that drivers are fit and licensed, and that scheduling does not incentivise unsafe behaviour. Schedulers must not set timeframes that a driver cannot meet without speeding, skipping rest breaks, or driving a defective vehicle. 

Where an operator also acts as scheduler, both sets of duties apply to the same decisions. The NHVR can investigate scheduling practices when an incident occurs, even if the operator was not present and did not direct the driver directly.

What Records You Must Keep to Demonstrate Due Diligence

The categories of records that constitute CoR evidence fall broadly into asset condition, scheduling conduct, and load compliance. For most operators, the first of these is where the most significant gaps exist. Connecting your CoR obligations to your broader QHSE for transport and logistics practices is the most direct way to build a defensible compliance record across both frameworks.

Asset Maintenance Records as CoR Evidence

Records that count as evidence include engine-hour-triggered service logs with dates and odometer or hour readings, work orders with technician sign-off, defect reports linked to a specific asset registration, and documented outcomes showing the defect was rectified. Records that do not hold up include informal notes without dates, verbal instructions with no written record, and spreadsheet entries that lack timestamps or are not tied to a specific asset identifier.

The quality of the record matters as much as its existence. A maintenance history with consistent scheduling, defect records, and completed work orders demonstrates a working system. A history showing regular servicing alongside unexplained gaps invites questions.

Scheduling and Load Records

Trip schedules must show realistic timeframes that do not require speeding to complete. Where drivers log actual departure and arrival times, retain those records and cross-reference them with the schedule. Consignment notes, load plans, and mass management records are all CoR-relevant documents. Retain them for a minimum of three years, or longer if there is any known or pending enforcement activity.

Related: Ultimate NHVR Audit Preparation Tools for Compliance

Pre-Start Checklists and Defect Reporting as CoR Documentation

A completed pre-start check is one of the most direct pieces of CoR evidence an operator can hold. It shows that, before the vehicle left the yard, a driver assessed its condition and either confirmed it was roadworthy or raised a defect. A timestamped digital record with the driver’s sign-off and the vehicle identifier is significantly stronger evidence than a paper form that may be lost, undated, or unreadable.

Using digital pre-start checklists removes the documentation gap between the driver’s inspection and the maintenance record. 

For example, when a driver raises a defect digitally, the system records it immediately. The defect appears on file, the timestamp shows when the driver raised it, and the platform tracks whether a work order followed. That complete record is what CoR requires. A defect raised on paper and handed to a supervisor who may or may not have actioned it produces none of that certainty.

What Happens When an Asset Fails and There is No Maintenance Trail

When a heavy vehicle is involved in an incident or stops operating during a job, investigators look first at whether the operator knew, or should have known, about the vehicle’s condition. Without a documented maintenance history, the operator cannot demonstrate the reasonable steps defence. Investigators do not treat the absence of records as neutral. It signals that systems were not in place.

The NHVR has the authority to issue improvement notices and infringement notices without waiting for a serious incident. Under the executive liability provisions introduced in 2018, directors and senior managers can face personal liability where they failed to take reasonable steps to ensure their business met its CoR obligations. 

Civil penalties under the HVNL can reach into the hundreds of thousands of dollars for severe breaches. Where a fatality is involved and executive liability applies, the consequences extend beyond financial penalties. A complete, exportable maintenance and defect history does not guarantee immunity from investigation, but it gives your business the evidence to demonstrate that your systems were working.

How Kynection Builds an Auditable Asset and Compliance Record

Kynection’s KIM platform connects the records that CoR requires into a single system: pre-start checklists, defect reporting, work orders, maintenance scheduling, and asset history. Each record links to a specific asset identifier, so when an audit request arrives, the operations team can pull the full history for any vehicle without manually reconstructing it from separate sources.

Automated Work Orders

Defect-to-work-order automation means that when a driver raises a defect during a pre-start check, KIM creates a work order automatically. There is no manual re-entry step where a defect can be missed or delayed. 

Maintenance Management

Engine-hour-triggered servicing ensures that assets reach the workshop before they reach a failure point, with the scheduled service date, completion record, and technician sign-off stored against the asset. 

Timestamped Sign-Offs

Timestamped driver sign-offs on digital pre-start checks provide the daily CoR documentation layer that paper-based systems cannot reliably produce. The platform generates an exportable maintenance history so operators can respond to NHVR requests without compiling records from separate systems.

KIM does not deliver CoR compliance automatically. It generates the records operators need to demonstrate they took reasonable steps, consistently, across every asset in the fleet. For operators reviewing their broader asset and equipment management obligations, connecting maintenance records to scheduling and compliance data is where the operational value becomes clear.

Building a CoR Record Your Business Can Stand Behind

CoR liability does not begin when an incident occurs. It begins when your scheduling, maintenance, and documentation practices fall short of what the HVNL requires. 

Building an auditable record requires systems that generate documentation as a by-product of normal operations, not as a separate administrative task. Pre-start checks completed in the cab, defects routed directly to the workshop, maintenance scheduled by the asset itself: these are the records that demonstrate reasonable steps without adding workload to already stretched operations teams.

If an NHVR audit request landed tomorrow, could your business produce a complete maintenance history, pre-start log, and defect trail for every asset in your fleet? 

KIM connects asset records, pre-start checklists, and work orders into a single auditable system, so your evidence is already there when you need it. See how it works and request a free demo.

Frequently Asked Questions

Does CoR apply to small transport operators with only a few vehicles?

Yes. The HVNL applies to all operators of heavy vehicles above 4.5 tonnes gross vehicle mass, regardless of fleet size. A sole trader operating two prime movers carries the same primary duty of care as a large national fleet operator.

What is the difference between primary duty and executive liability under the HVNL?

Primary duty applies to each CoR party as a business entity and requires taking all reasonable steps to prevent safety breaches. Executive liability applies to individual officers within that business, such as directors and senior managers, who can face personal liability if they failed to exercise due diligence to ensure the business met its primary duty.

How long do I need to keep asset maintenance and pre-start records?

The HVNL does not prescribe a single retention period for all records. As a general guide, NHVR recommends retaining work diary records for three years. For maintenance and pre-start records, a minimum of three years is prudent, with longer retention advisable where there is any known or likely enforcement activity or incident history.

Can a paper-based maintenance log satisfy a CoR audit?

Paper records can satisfy an audit if they are complete, dated, linked to specific assets, and accessible. In practice, paper logs are difficult to produce quickly, prone to gaps, and cannot demonstrate the automated triggers that digital systems provide. An auditor assessing reasonable steps will consider whether the system in place was adequate, not just whether some records exist.

What triggers an NHVR Chain of Responsibility investigation?

A road incident involving a heavy vehicle, a complaint from a driver or another party in the chain, a tip-off to the NHVR, or a proactive audit programme can all initiate an investigation. The NHVR also conducts roadside compliance activities where operators and drivers can be checked without prior notice. A history of infringement notices or prior investigations increases the likelihood of further scrutiny.