The NHVR auditor asks for three months of fatigue records and maintenance history for a particular truck. The work diaries are in the telematics platform. The maintenance log is in a spreadsheet the workshop keeps. The driver's start and finish times are in payroll. And the dispatch records that prove the schedule was reasonable sit inside the TMS, behind a login nobody in compliance uses. Each system has its piece of the story. No system has the whole story, and pulling it together for a single truck over three months takes someone a day of exports, cross-referencing and hoping the dates line up.
That is the practical problem with chain of responsibility (CoR) compliance for most transport and logistics businesses. The law is clear on what you need. The difficulty is that the evidence lives in five or six places, and nobody built a bridge between them.
What chain of responsibility actually requires
Under the Heavy Vehicle National Law (HVNL), every party in the transport chain has a primary duty to ensure, so far as is reasonably practicable, the safety of their transport activities. That applies whether you are a carrier, a consignor who sends the freight, a loading manager, a scheduler or an employer. The NHVR identifies ten party types, and a single business can wear several hats at once: a wholesaler that dispatches on its own trucks is both consignor and operator (nhvr.gov.au, Chain of Responsibility).
What matters here is the evidence. If an auditor or investigator turns up, they want to see that you identified the risks, put controls in place and kept records that prove it. The main record areas are:
- Fatigue management: work diaries or Electronic Work Diaries (EWD) showing each driver's work and rest hours, and evidence that someone reviews them regularly.
- Mass and dimension: documentation proving loads comply with mass limits, including Container Weight Declarations for freight containers.
- Vehicle maintenance: scheduled servicing, pre-trip inspections, defect reports and evidence that defects were followed up.
- Load restraint: records showing loads were restrained according to the loading performance standards, and that the people doing it were trained.
- Speed and scheduling: evidence that schedules, contracts and incentives don't pressure drivers to speed or breach fatigue rules.
The NHVR's approach is risk-based, much like workplace health and safety law. There is no single prescribed form. But if you cannot show the records when asked, the regulator draws its own conclusions (nhvr.gov.au, Complying with your Primary Duty obligations).
Where the records actually live in a typical transport business
Here is where it gets messy. In most businesses we see, each record type sits in a different system and is maintained by a different person.
Dispatch and scheduling lives in the Transport Management System (TMS) or job system. It holds customer orders, run allocations, planned routes and load details. The dispatcher owns it.
Fatigue and work diaries sit in the telematics or EWD platform (Teletrac Navman, MTData, Trimble, or one of the newer EWD apps). The compliance officer or safety manager checks them, sometimes weekly, sometimes when something goes wrong.
Maintenance is tracked in a fleet maintenance system, a workshop spreadsheet, or sometimes just a filing cabinet of service receipts. The fleet manager or mechanic owns it.
Driver hours and pay land in the payroll system (or a timesheet tool feeding payroll). The office or HR manager owns this.
Mass records and Container Weight Declarations are filed at the depot, often as paper or scanned PDFs.
Load restraint training might be a spreadsheet of certificates, or in an HR/training system.
Each of these systems does its own job well enough. The problem is that none of them knows about the others. The dispatch record says a driver was allocated a run on Tuesday, but it does not know whether that driver's fatigue hours allowed it. The maintenance system knows the truck was serviced on the 15th, but the compliance officer checking a specific run on the 12th has to open a separate system and match dates by hand.
Why it is hard to produce on request
When an auditor or investigator asks for evidence, they ask about a specific event: a truck, a driver, a date, a route. They want to see the dispatch record, the driver's fatigue hours before and after, the vehicle's maintenance state at the time, the load details, the mass documentation and any relevant training records. All joined together, for that one event.
In most transport businesses, that join happens manually. Someone exports from the TMS, opens the telematics portal, pulls up the maintenance log, checks payroll for the driver's hours, and assembles it in a folder. If the auditor asks for a pattern across three months or a fleet of twenty trucks, it takes days. And every manual step is a chance to miss something.
The other difficulty is timing. Telematics data might be available for 90 days before it rolls off. Paper dockets get filed in a box, and finding a specific one from four months ago depends on how the box was sorted. Driver records might be in a system the driver's employer controls, not the prime contractor.
What connecting it looks like
The goal is not one massive system that replaces everything. The dispatcher still uses the TMS. The mechanic still uses the workshop system. The goal is a layer that ties them together so you can pull up a truck, a driver or a date and see the linked records in one place.
In practice, that means:
- A driver or vehicle lookup that brings together the dispatch record, fatigue hours, maintenance status and load details for a given date or period, drawing from each source system.
- Automated alerts when something doesn't add up: a driver scheduled for a run whose fatigue hours are approaching a limit, or a truck dispatched without a current service record.
- A report pack that can be produced quickly when an auditor asks, joining records across systems and presenting them in a readable format with dates and references.
The starting point is usually getting the data out of each system. Most TMS platforms have an API or at least an export. Telematics providers generally offer data feeds. Maintenance systems range from APIs to spreadsheets (and sometimes the spreadsheet is the fastest path). Payroll is often the hardest, because the timesheet data enters payroll summarised and the original shift detail is elsewhere.
We often find that the first step is not a big integration project. It is a spreadsheet or simple database that pulls a weekly extract from each system and stores it in one place, with the truck rego and driver name as the common key. Once that exists, the compliance officer can search by truck or driver and see everything in one view. The next step, if the volume justifies it, is a live connection that keeps the data current.
What we would not do
We would not tell you which telematics provider or EWD app to use. We would not offer legal advice on what level of record-keeping satisfies the NHVR for your particular operation, because that depends on your risk profile, your routes, your fleet and your accreditation status. That is a conversation for your compliance adviser or a transport lawyer.
What we do is connect the systems you already have, so the evidence is findable, linked and ready when someone asks for it. If a spreadsheet works for a small fleet, we will say so. If you need something more, we scope it and quote it.
Consignors and loaders: this applies to you too
CoR duties are not only for carriers. If your business sends freight, you are a consignor. If you load trucks at your warehouse or factory, you are a loader or loading manager. The NHVR holds you responsible for the safety of those transport activities. That means you need records too: what was dispatched, its weight, how it was loaded and restrained, and whether the schedule was reasonable.
For wholesale and distribution businesses and manufacturers that ship by road, the evidence for your CoR duties sits alongside your dispatch, warehouse and production systems. Connecting that evidence to a transport record is the same kind of cross-system problem.
Frequently asked questions
What records do I need to keep for chain of responsibility?
The HVNL does not prescribe a single form or system. You need evidence that you identified the risks in your transport activities and put controls in place. In practice, that means records of fatigue management (work diaries or EWD data), vehicle maintenance, mass compliance, load restraint and scheduling. The records should be retrievable for a specific vehicle, driver or event when asked (nhvr.gov.au).
How long do I have to keep CoR records?
Record-keeping periods vary by record type and state or territory regulations. Work diaries must generally be kept for at least three years. Maintenance records should be retained for the life of the vehicle plus a reasonable period. Check the specific requirements for your accreditation and jurisdiction with the NHVR or your compliance adviser.
What happens if I can't produce the records?
If the NHVR investigates and you cannot demonstrate that you took reasonably practicable steps to ensure safety, you face enforcement action. Penalties are indexed annually, and infringement amounts are set at ten per cent of the maximum court-imposed penalty. Investigations typically start with business management, not individual drivers, because management has greater control over practices and resources.
Does chain of responsibility apply to my business if I don't own trucks?
Yes. If you send goods by heavy vehicle (as a consignor), load them, pack them, schedule transport or manage a loading site, you have CoR duties. A wholesaler dispatching freight, a manufacturer loading pallets, or a quarry scheduling truck arrivals all fall within the chain.
Can one system replace all of this?
For most transport businesses, no single off-the-shelf system covers dispatch, fatigue, maintenance, mass, payroll and training. The practical approach is to connect the systems you already use so the data can be found in one place when it is needed. Our work with transport and logistics businesses focuses on exactly this kind of cross-system join.
Next steps
If your CoR evidence sits across systems and you are not confident you could produce it quickly for an auditor, book a free initial chat and we will talk through what connecting it involves. You might also find these useful: