One of the clearest directions in heavy vehicle regulation is the shift away from treating written procedures as compliance in themselves. Under the HVNL, the legal test has always been about what was done to ensure safety so far as is reasonably practicable. But as reform discussions continue, the practical message for industry is becoming sharper: having a process is not the same as controlling the risk.
That distinction matters because many businesses have invested heavily in policies over recent years. They have fatigue procedures, maintenance checklists, load restraint instructions, subcontractor terms and escalation rules. Yet when those systems are stress-tested, the weaknesses are often the same. Staff do not follow the process consistently, exceptions are handled informally, records are scattered, and management receives summary reporting that does not reveal whether the control is effective on the ground.
In other words, the compliance gap is often not absence of paperwork. It is absence of operational proof. Can the business show that route assessments are current and used? Can it demonstrate that loading instructions reached the relevant party before the task commenced? Can it verify that maintenance defects were triaged and closed within a controlled timeframe? Can it point to evidence that speed, fatigue or mass exceptions triggered intervention rather than being absorbed into normal work?
This is where reform will matter most in practice. Operators who still rely on verbal workarounds, local habits or “experienced people knowing what to do” will find that approach increasingly hard to defend. A documented process without verification tends to fail at the exact point an investigator asks what happened on a specific day, for a specific task, under specific constraints.
The HVNL’s offence framework already supports scrutiny of failures that expose people to risk, even where no catastrophe occurred. Categories of breaches and maximum penalties are designed to reflect seriousness, including very substantial consequences for reckless or highly unsafe conduct. That is why a false sense of comfort from policy documentation is dangerous. The question is not whether a procedure exists. The question is whether the business can prove it operated as a control.
Operators should review three things now. First, where are the recurring exceptions? Second, how is control effectiveness tested rather than assumed? Third, what evidence would you produce if asked to show how a specific decision was made and supervised? A short list of verified, well-used controls is far stronger than a large set of documents that no one can reliably execute.
If your business wants to move from policy-heavy compliance to operationally verified control, COR Safety Management Systems offers a practical CoR safety management platform that helps centralise evidence, track exceptions and show how duties are being managed in real work.