One of the most important practical developments in HVNL compliance is not a single new rule. It is the way the primary duty continues to shape expectations across the business. The law requires each party in the Chain of Responsibility to ensure, so far as is reasonably practicable, the safety of transport activities. That broad duty makes it increasingly difficult to defend compliance systems built in silos.
Many transport businesses still organise safety controls by topic: fatigue sits with one team, maintenance with another, loading with operations, speed with driver management, and subcontractor oversight somewhere else again. That structure may look orderly, but it can leave serious gaps where decisions overlap. In the real world, transport risk rarely arrives one subject at a time. A delayed dispatch can affect fatigue. A changed route can alter speed exposure and vehicle suitability. A loading change can influence maintenance stress and delivery timing. The duty applies to the transport activity as a whole.
This is why reform discussions and regulator messaging continue to reinforce systems thinking. The issue is not simply whether a business has a policy in each area. The issue is whether those controls work together well enough to prevent foreseeable harm. If a scheduler can alter a job without triggering fatigue review, or a loader can change a configuration without checking restraint requirements, or maintenance can defer a repair without operational sign-off, the legal weakness is not just procedural. It goes to whether the business has done what is reasonably practicable.
Operators should use this moment to review how decisions move across teams. Look for places where one function can create risk for another without a mandatory check. Review authority levels, exception workflows and escalation triggers. Confirm that risk information travels quickly between dispatch, workshop, site personnel and management. It is also worth examining whether your incident reviews and internal reporting cut across categories or stay trapped within them. If each team reports only its own metrics, leadership may miss the combined risk picture.
A practical starting point is to map a typical job from booking to delivery and return. Identify every decision point that can affect fatigue, speed, mass, dimension, load restraint, maintenance or vehicle standards. Then ask which team controls it, what evidence is created and what happens when the plan changes. Businesses often find that their greatest exposure lies not in the written rule, but in the handoff between functions.
The direction of travel is clear. Under the HVNL, safety duties are increasingly judged by whether the whole operating model can identify and control interacting risks. Businesses that continue to rely on isolated compliance streams may find that those structures no longer match how the law assesses responsibility.
If you need a system that connects fatigue, maintenance, loading, scheduling and evidence in one place, COR Safety Management Systems provides a CoR safety management platform designed to support whole-of-business compliance under the HVNL.