The maintenance prosecutions that succeed in Irish District and Circuit Courts almost never turn on whether a defect existed and was eventually repaired. They turn on the gap in the middle — the period between when a driver said something was wrong and when someone independently confirmed it was right. That gap is where SHWWA 2005 section 8 (general duties of the employer) and section 12 (duties to non-employees) attach; it is where the Director of Public Prosecutions opens the file when there is a death; and it is where the insurer's gross-negligence engineer looks for the line on which to refuse cover.

This article maps the workflow from the moment a driver identifies a defect to the moment the vehicle returns to road, and identifies the five places where Irish SME fleets routinely lose the audit trail. The geography is Donegal because rural single-yard operators are typical of the SME segment; the workflow problem is national.

Stage one — the driver's pre-use check and the defect identification

The legal anchor is in SI 299/2007 (General Application) Regulations 2007 regulation 28 (Information for Use of Work Equipment) and in the broader employer's duty to ensure work equipment is suitable and maintained. For commercial vehicles operating under the EU 561/2006 framework, the driver's pre-use check is part of the documented compliance regime. Even where 561/2006 does not apply, the duty under SHWWA 2005 sections 8 and 12 to maintain a safe place and safe equipment of work is engaged.

What the report must contain to bear evidential weight:

  • Date and time the driver observed the defect — not the time the data was keyed.
  • Identity of the driver, verified, not picked from a dropdown.
  • Vehicle identification — registration mark and ideally VIN.
  • Location of observation.
  • Description of the defect in plain language — not "steering" but the driver's actual experience.
  • A photograph or short video where visually relevant.
  • The driver's assessment: roadworthy / drivable with limitations / not roadworthy.

The first failure point Irish SME fleets show: the defect is reported by phone or text to the operations manager. No record exists in any system. The phone log, if it exists, has a time but no content. The HSA inspector cannot find the trigger event in the file because the trigger event is in the operations manager's head.

Stage two — receipt, decision, and the visible status of the vehicle

The decision-maker — operations manager, fleet supervisor, mechanical lead — must take an explicit decision once the report arrives. The decision is one of:

  • Take the vehicle off the road pending repair.
  • Allow continued use with explicit limitations.
  • Schedule for the next available workshop slot.
  • Continue to monitor — no immediate action.

Whatever the decision, it must be recorded with identity, time, and a one-line reason. The vehicle's operational status must reflect the decision in a way that the next person who might use the vehicle sees. A note in a notebook on the operations manager's desk does not survive the moment the next driver picks the keys off the board.

Second failure point: receipt without a recorded decision. The operations manager sees the report, intends to act, but no decision is captured before the working day moves on. The HSA inspector finds this gap by asking "where is the receipt acknowledgement of the defect?" If the answer is silence, section 8 SHWWA is engaged.

Stage three — taking the vehicle off the road and the visible sign on the cab

Where the defect engages roadworthiness, the vehicle must be taken off the road in a way that the next driver cannot bypass by accident. A note in the system that does not produce a physical or in-cab signal is a near-failure. The classic Irish SME pattern is a chalkboard at the yard or a verbal "don't take the Caddy" — neither of which survives Friday afternoon when the original operations manager has gone home.

What an inspectable workflow looks like:

  • The vehicle's status in the dispatch system is "off road" and cannot be assigned to a job.
  • A physical sign or in-cab notice appears on the dashboard or the steering wheel.
  • Where the system supports it, an in-cab tablet displays the status when the driver opens the cab.
  • The off-road status can only be cleared by a verified decision after repair, not by anyone who happens to remove the sign.

Third failure point: the off-road decision exists in the system but does not produce a visible signal that the next driver perceives. A weekend driver picks the keys, drives the vehicle, the defect causes a roadside event. The HSA inspection now has both the original defect and a workflow that allowed a non-roadworthy vehicle to be driven.

Stage four — the repair

The repair, internal or contracted out, must be documented with:

  • Mechanic identity, ideally OTP-verified at the moment of action.
  • Date and time of the repair.
  • Vehicle identity.
  • Description of the work, with the diagnostic steps recorded.
  • Parts used — manufacturer, part number, supplier reference.
  • Photographs of the removed and installed components.
  • Test drive or functional test outcome.

For Irish SMEs that contract repairs out, the failure point is in the supply chain. The garage works on the vehicle and produces a paper invoice or a workshop printout when asked. The printout is generated at the time of asking, not at the time of the work. A line that reads "steering box replaced" on a workshop record can be opened on the printout query, not at the time the work happened.

Fourth failure point: the repair record is not contemporaneous with the work. Where the case proceeds to the District Court or the Circuit Court, the workshop's software audit log will be requested, and the difference between when the line was opened and when it was claimed to have happened becomes evidence.

The remedial action: a contract with the workshop that specifies same-day photographic evidence, parts traceability documentation, and a mechanic identity that can be authenticated. Where the workshop is internal, the system must capture all of this at the moment of work, sealed and chained, photographs EXIF-preserved.

Stage five — the verification before return to road

The vehicle does not return to road on the mechanic's say-so. A second person — operations manager, workshop supervisor, fleet manager — checks: is the repair completed as ordered? Does the relevant component function? Has the off-road status been cleared as a recorded act? This is the four-eyes check, and Irish SMEs lose it more than any other stage.

What the verification must record:

  • Identity of the verifier — different from the mechanic.
  • Date and time.
  • Reference to the repair record.
  • Outcome — pass / fail / pass with conditions.
  • OTP signature or equivalent authentication.

Fifth and most common failure point: the repair is done, the vehicle reappears in the yard, the dispatcher assigns a job. No one independent of the mechanic has signed off. In a SHWWA 2005 prosecution, the absence of a four-eyes check is the structural fact that the HSA prosecutor will call out. In a Coroner's inquest, a narrative verdict naming "no independent verification of repairs" is the foreseeable form of finding.

The five workflow gaps and how to close each

  1. Defect report without server-side timestamp. Close it with a digital report system that captures the time of submission unalterably and binds it to the device that captured the entry.
  2. Receipt without recorded decision. Close it by requiring an explicit decision in the system before the report is treated as acknowledged.
  3. Off-road status without visible signal. Close it with an in-cab device or a physical sign mandated by the workflow, plus a system-side block on dispatch.
  4. Repair record not contemporaneous. Close it by contractual obligation on the workshop and by capture-time photographs of parts, EXIF preserved.
  5. Return to service without four-eyes verification. Close it by requiring an OTP-verified second-person sign-off before the off-road status clears.

Each gap is, on its own, a question the HSA inspector or the DPP file will ask. Several of them together approach the gross-negligence threshold under SHWWA 2005 section 12 — which is the threshold the State must clear to prosecute on indictment with the higher penalties and the higher reputational cost.

What the inspectable workflow looks like in practice

The Donegal contractor, on a Wednesday morning when the HSA inspector arrives, can present the workflow as:

The fitter reported heaviness in the steering at 06:42 from the Letterkenny yard. The report carries a server-side timestamp, the fitter's identity is OTP-verified, GPS coordinates are embedded. The operations manager received the report on a push notification within seconds. He opened the report at 06:51, took the vehicle off the road, recorded "to Letterkenny garage for inspection same day". His decision was sealed into the chain at 06:51 with his identity. The vehicle's in-cab tablet displayed an off-road notice; the dispatch system blocked any assignment.

The garage took the vehicle at 09:30. The mechanic recorded the diagnosis — worn steering rack — and his work, photographing the removed rack against its part-tag and the new rack as installed. Each photograph carried EXIF, each was hashed, the mechanic's identity was OTP-verified. The workshop record was sealed at 12:14 when work was complete.

The fleet supervisor — not the mechanic — reviewed the test-drive log and signed the verification at 13:47, also OTP-verified. The off-road status cleared automatically. The vehicle was assigned to the afternoon run at 14:05.

The HSA inspector asks for the chain. He receives a single record, byte-for-byte verifiable. He thanks the operations manager and leaves with notes, not a prosecution file.

Six steps for an Irish fleet operator to assess the workflow today

  1. Sketch on a single sheet of paper how a defect report actually moves through your business today. Mark every point at which information passes through a person, a phone call, or a format that does not preserve the time of capture.
  2. For the past ninety days, list every reported defect. For each, can you produce a sealed, timestamped record of receipt, an off-road decision (or the reasoned alternative), the repair, and the verification?
  3. Read your contracts with external garages. Do they require contemporaneous photographic evidence and identifiable mechanic? If not, renegotiate.
  4. Audit your off-road signalling. Is there an in-cab or physical signal that survives weekend driver changeover? If not, design one.
  5. Review your verification practice. Is the four-eyes check enforced by system, or is it convention? If convention, make it system.
  6. Train drivers and dispatchers in the workflow and document the training. Each of these is itself an HSA evidence item.

Sources and further reading

Related Mekavo articles: When the Coroner calls, Garda + RSA roadside on the M8, Four phrases Irish insurers use, Disability Act 2005 and the HSE Section 39 spotlight.

Why this matters to us

Mekavo Fleet was built around the five-stage workflow. Every defect report is sealed at submission, chained to the vehicle's prior history, EXIF-bound. Every receipt carries the operations manager's identity. Every off-road decision lives on the vehicle and cannot be silently cleared. Every repair carries parts, photographs, and an OTP-verified mechanic. Every verification is its own sealed entry by an independent second person. When the HSA inspector arrives in Letterkenny, you are not assembling a defence — you are handing over the live record. We do not give you software. We give you a chain of custody.