Heavy Vehicle / NHVR Compliance
A dispatch change needs to reach everyone responsible.
A transport task can change between dispatch and delivery. People need to see which plan is current, what checks were made and who acknowledged a change. The applicable heavy vehicle law depends on where the task operates.
A working example / Transport & Logistics
The dispatch plan has to stay current.
An illustrative design question based on this kind of work. This is not a client project, delivered product or claim that every organisation follows this process.
Dispatch revision
What changed or needs checking
- 01Original plan
Load, vehicle, driver and route at dispatch.
- 02Change
What has changed and who requested it.
- 03Checks
Vehicle, driver, route and required controls reviewed.
- 04Acknowledgement
Driver receives and confirms the current plan.
Can the revised plan be sent to the driver?
Everyone works from the current version, with the change history retained.
Discovery notes
What has to be checked in the real operation.
The example above frames a design question. These conditions need to be checked with the organisation and its advisers before scope or software behaviour is decided.
- 01
The HVNL has not commenced in Western Australia or the Northern Territory, but it can apply when vehicles from those jurisdictions travel into a participating jurisdiction.
- 02
Chain of responsibility duties extend beyond the driver to other parties in the transport task, with the applicable duty depending on their role and influence.
- 03
Fatigue management accreditation (Basic or Advanced Fatigue Management) requires ongoing documentation and demonstrated compliance with accreditation conditions.
- 04
Relevant vehicle, load and permit information should be available to the people checking a task and responding to an inspection.
Keep dispatch changes in one current plan.
Examples to investigate, not off-the-shelf products or a claim that an integration is available.
Chain of responsibility registers
Duty documentation for each supply chain party: operator, scheduler, consignor, consignee, packer, and loader.
Fatigue management records
Work and rest record systems aligned to Standard, Basic, and Advanced Fatigue Management schemes.
Mass & dimension tracking
Permit condition tracking for over-mass and over-dimension loads with expiry and route alerts.
Maintenance scheduling
Preventive maintenance linked to odometer or engine hours, with defect and roadworthiness records.
Published obligations to check
Rules and timeframes for Transport & Logistics work.
| Ref | Obligation | Figure |
|---|---|---|
| 5.1 | Ref 5.1: Jurisdictions where the HVNL has commenced | ACT, NSW, Qld, SA, Tas, Vic |
| 5.2 | Ref 5.2: WA and NT vehicles entering a participating jurisdiction | HVNL can apply after crossing |
Bring us the sticking point.
Tell us how this work runs in your organisation. We can assess whether a software project makes sense, with the real rules and existing tools in view.
Send an enquiryRelated capabilities