What a Chain of Responsibility fine actually looks like — and how to avoid one
"Chain of Responsibility" gets thrown around a lot without anyone explaining what actually happens when it goes wrong. Not the theory — the actual sequence of events. Here's a realistic picture of how a CoR breach plays out, built from how these matters typically proceed under the Heavy Vehicle National Law, followed by what the penalties actually are and what would have prevented it.
Illustrative example — not a real case
A solo operator is intercepted for a routine check. The brakes fail inspection — a defect that, on review, had been building for weeks. There's no pre-start record for that day, or the three before it. The officer asks a simple question: how do you know your vehicle was safe to be on the road this morning? There's no answer beyond "it seemed fine." That gap — not the defect itself — is what turns a mechanical fault into a Chain of Responsibility matter.
Why the missing record matters more than the defect
A defect alone is usually a vehicle standards issue — serious, but generally dealt with as its own thing. What escalates it into CoR territory is evidence (or the absence of evidence) about whether the operator took reasonable steps to prevent it. A brake fault that develops gradually, with no record of any inspection catching it, tells a very different story to a fault that appears despite a documented history of regular, passing checks. The second scenario shows reasonably practicable steps were in place. The first suggests they weren't — and that's the gap the Primary Duty under HVNL section 26C is built to catch.
What the penalties actually are
Breaches fall into three categories, and they apply to both the business and the individual running it. Figures are indicative and indexed annually — always check current NHVR guidance for exact amounts.
- Category 1 — reckless conduct, disregard for safety or the law. The most serious tier: individual penalties can include imprisonment, and corporate fines can run into the millions.
- Category 2 — conduct exposing someone to risk of death or serious injury. Substantial fines, scaled below Category 1.
- Category 3 — failing to comply with the safety duty without those risk elements present. Lower tier, but still significant for a one-truck operation.
On top of whatever penalty applies to the business, executives carry personal due diligence obligations separately, under HVNL section 26D. If you're a solo operator, that executive is you — there's no corporate shield to stand behind.
What would have prevented it
Going back to the scenario above: the mechanical fault might well have happened either way — parts fail. What changes the outcome entirely is a contemporaneous record showing the vehicle was checked regularly and any developing issue caught early. That's not a sophisticated system. It's a same-day, timestamped pre-start record that exists whether or not anyone ever asks to see it.
- Do the pre-start every day, not just when you remember. The habit matters more than the format.
- Record it the same day, not from memory later. A reconstructed record carries far less weight than one made at the time.
- Keep it somewhere you can actually produce it. A record that exists but can't be found when an officer asks is close to no record at all.
- Don't wait for a defect to start. The record that protects you is the one built before anything goes wrong, not after.
None of this requires new equipment or a course. It requires a habit that survives a 5am start in the cold, which is exactly the problem CoRShield is built around — a text takes ten seconds, and it's timestamped and stored the moment you send it.
Free Pre-Start Checklist
Keep a printable, NHVR-aligned pre-start checklist in the cab — the exact record that would have changed the scenario above.
Get the free checklist →