Chain of Responsibility role matrix for transport clients

A business may call itself “the customer” in a transport contract and still perform functions that matter under Australia's Heavy Vehicle National Law (HVNL). It might consign goods, receive them, schedule deliveries, load vehicles or manage a busy loading premises. A role matrix should map the functions actually performed, the transport activities they influence and the controls they can apply. Job titles and contract labels are a poor starting point.

This guide is for businesses engaging heavy-vehicle transport in jurisdictions where the HVNL applies. The National Heavy Vehicle Regulator (NHVR) explains that Chain of Responsibility (CoR) status attaches to performing one of the defined functions and that the Primary Duty is the same legal duty for each CoR party; its application depends on the activities and risks a party can influence. See NHVR's parties in the CoR and Primary Duty regulatory advice. Verify jurisdiction and actual operations before treating a role as a legal conclusion.

List transport functions, not departments

The NHVR identifies functions including employer of a driver, prime contractor, operator, scheduler, consignor, consignee, packer, loading manager, loader and unloader. One organisation may perform several. A retailer might be consignee at one site, loader at another and scheduler for a contracted fleet. The matrix should ask who makes the relevant decisions, not which department's name appears on the invoice.

Start with a process map from order to delivery: who sets collection and delivery windows, who packs the freight, who communicates weights or dimensions, who loads or unloads, who controls the premises and who receives the goods. Ask the people doing the work. A contract may say the carrier is responsible for safety, but it cannot erase the influence of a shipper that sets an impossible schedule or provides inaccurate load information.

Record the function, activity and risk separately

For each activity, capture the relevant CoR function, the specific decision made, the public safety risk that could arise, the controls in place and the person responsible for reviewing them. For example, a consignor may control the accuracy of freight information, while a loader controls the physical loading method. The same business can occupy both roles. Avoid assigning different “levels” of the Primary Duty based on the role title; the NHVR says the duty is common, while the practical steps depend on influence, control and what is reasonably practicable.

The matrix is not a legal waiver. It is a way to expose gaps and overlaps so parties can coordinate. A field headed “carrier handles everything” is not a control. A better field asks what information the client gives the carrier, what the client verifies and how concerns are escalated.

Connect each function to an operational control

A scheduler may review whether delivery windows create pressure to exceed work or rest limits. A consignor may provide accurate freight description and weight. A loading manager may manage traffic and waiting time at a busy facility. A consignee may avoid receiving arrangements that encourage unsafe unloading. These are examples of risk-control questions, not a fixed statutory checklist for every client.

The NHVR's Primary Duty advice frames the obligation around ensuring, so far as reasonably practicable, the safety of transport activities and not causing or encouraging breaches. The matrix should therefore show who can change a risky practice. If a client has no practical influence over a particular vehicle maintenance decision, do not pretend it can inspect every component; identify the controls it can reasonably apply in its relationship and own operations.

Verify the map with the other parties

Discuss the matrix with carriers, warehouses, brokers and site teams. Where two businesses influence the same matter, record how they share information and what each will do. The NHVR's shared-responsibility advice can help frame that discussion. Do not assume that a service-level agreement alone proves safe practice. Ask whether people know how to raise an overloaded vehicle, an unsafe loading condition or a schedule that cannot be met safely.

Revise the matrix after a new contract, site, freight type, loading method or incident. A role assignment that was accurate when the company only received goods may no longer be accurate when it starts scheduling drivers or operating its own loading dock.

Example: a customer with a busy distribution centre

A company buys goods and contracts a carrier. At one site it also schedules arrival slots, manages a premises where vehicles are loaded daily, and uses its own workers to unload. A role matrix identifies the consignee, scheduling, loading-management and unloading functions as relevant to examine. The site team reviews queue pressure, traffic routes, information supplied to drivers and unloading controls. The carrier separately reviews its own operation. The organisations agree escalation routes for damaged loads and unrealistic delivery windows.

The matrix does not decide liability for a future event. It makes the existing decisions visible so each party can manage the transport risks it influences.

Keep the matrix tied to evidence

A useful matrix links each risk-control decision to a policy, instruction, contract term, meeting record or operational check. Give it an owner and review date. If a control is only proposed, label it as such. A dashboard can show coverage, but it should not automatically call every role “compliant” because a document has been uploaded.

The mapped Complys Australian heavy-vehicle compliance page is the product page for evaluating records. Verify current capabilities in the implementation. This guide does not claim Complys determines CoR legal status, monitors every transport activity or certifies the Primary Duty has been met.