The document exists. It probably has a logo on the front and a signature page at the back. It says drivers must obey speed limits, avoid phone use, and report defects. It is also, in most cases, completely useless.

The HSA's driving for work inspection campaign has been making its way through Irish businesses, and the pattern it keeps finding is the same one safety professionals have known about for years. Companies have policies. Companies do not have systems. Those are two very different things, and the gap between them is where people get killed.

Road collisions are the single largest cause of work-related fatalities in Ireland. Not falls. Not machinery. Roads. Yet fleet safety sits at the bottom of most organisations' risk registers, somewhere below manual handling and above "other." The inspections are exposing exactly why.

What Inspectors Are Actually Looking For

When an HSA inspector arrives to look at your driving for work arrangements, they are not checking whether your policy document uses the right fonts. They want evidence that the system works. That means records. Schedules. Signatures. Maintenance logs with dates. Licence checks that actually happened, not ones that were meant to happen.

The inspection checklist covers three areas: the vehicle, the driver, and the journey. Most companies can produce something on vehicles because insurance usually forces the issue. Driver management is where things fall apart. Licence validity checks done once at hiring and never again. No fatigue management. No process for reporting near-misses on the road. No record that drivers have actually read, let alone understood, the policy they signed.

Journey risk is almost universally ignored. Pressure to meet delivery windows, inadequate route planning, no process for drivers to flag that a schedule is unsafe. These are the conditions that produce serious incidents, and they are almost never documented until after something goes wrong.

The Policy That Does Nothing

Here is the core problem. A policy is a statement of intent. A system is a set of controls with accountability attached. Most companies wrote a policy, told themselves the box was ticked, and moved on.

The "Drive Safe" poster in the canteen is not a control. The paragraph in the employee handbook about not using phones while driving is not a control. A control is a weekly vehicle defect check logged and reviewed by a named person. A control is a quarterly licence audit with a consequence for non-compliance. A control is a journey planning process that a driver can use to push back on an unrealistic schedule without being made to feel like a nuisance.

The hidden cost of complacency in work driving culture is exactly this: the assumption that because nobody has been seriously hurt yet, the current approach is working. It is not working. It is just waiting.

What the Fines Tell Us

Enforcement action in the driving for work space tends to cluster around a few specific failures. Vehicles with known defects still in service. Drivers with expired licences operating company vehicles. No evidence of any risk assessment for driving activities. No fatigue management for drivers covering long distances.

The financial exposure is real. Companies found in breach face improvement notices, prohibition notices, and prosecution. Fines in serious cases run into six figures. Directors can face personal liability. And that is before the civil claims from injured parties, which routinely dwarf the regulatory fines.

The more instructive pattern is what the enforcement does not find: companies that had proper systems in place and still ended up with a serious incident. Proper systems are not a guarantee against everything. But the incidents that end in prosecution almost always involve companies where basic controls were absent or had collapsed through neglect.

What Actually Works

The companies that perform well under inspection share a few characteristics that have nothing to do with the quality of their policy documents.

Someone owns fleet safety. Not in a vague, everyone-is-responsible way. One named person is accountable for the vehicle check schedule, the licence audit, the driver records. When an inspector asks who is responsible, there is an immediate answer.

Defect reporting is genuinely encouraged. Drivers need to know that flagging a problem with a vehicle will result in the vehicle being taken off the road, not in the driver being told to stop making a fuss. This sounds obvious. It is not common.

Journey risk is treated the same way as any other workplace risk. Tight deadlines, unfamiliar routes, adverse weather, early morning starts after late finishes. These are hazards. They need to be assessed. Drivers need a route to raise concerns without it affecting their standing.

Licence checks happen on a schedule and are documented. Every six months at minimum. Annually at absolute minimum for low-risk fleets. The record shows the date, the result, and who conducted the check.

Incidents and near-misses on the road get reported and reviewed. Not to catch drivers out, but to find out whether the schedule, the route, or the vehicle contributed to what happened.

The Accountability Gap

The inspection campaign has done one useful thing beyond issuing notices. It has made clear that driving for work is treated as a workplace activity under the Safety, Health and Welfare at Work Act 2005. The road is not a place where employer duty of care switches off. It is a workplace. The obligations that apply on your site apply in your company vehicle.

Managers who set unrealistic schedules for drivers, directors who approve fleet budgets that defer maintenance, HR departments that never check licence validity after onboarding. These are not administrative oversights. Under the Act, they are failures in the management of workplace risk.

The inspections will continue. The fines will keep landing on companies that assumed a policy document was sufficient. The question is not whether your company has a driving for work policy. It is whether your drivers are actually safer because of it. If you cannot demonstrate how, neither can you demonstrate compliance.

Fix the system. The poster can stay if you like, but it is not doing any work.