OHSA prosecutions in South Africa that succeed 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 reported something and when an independent person confirmed the repair was complete and the vehicle safe to return to service. That gap is where OHSA sections 8(1) and 9 attach (the duty to provide a working environment safe and without risk to the health of employees and to non-employees so far as is reasonably practicable), where the DEL inspector's prosecution file opens, and where the insurer's gross-negligence assessor locates the line for refusing cover.

This article maps the South African commercial-fleet workflow from the moment a driver identifies a defect to the moment the vehicle returns to road, anchored on OHSA 1993, the General Safety Regulations, the Driven Machinery Regulations, and the practical experience of DEL inspectors who have seen the gap repeatedly. The geography is Polokwane and northern Limpopo because remote, single-yard SME operators show the gap most distinctly; the workflow problem is national.

Stage one — the daily inspection and the defect identification

The driver's daily inspection is required by NRTA Reg 318 and reinforced by OHSA section 14, which places duties on the user of plant or machinery to ensure it is in safe working condition before use. For commercial motor vehicles, the daily inspection covers the schedule of safety-critical items: brakes, steering, tyres, lights, mirrors, exhaust, coupling devices for trailer combinations, body damage, fluid leaks, and accessibility equipment where fitted. Defects are categorised by severity and direct the driver's decision on whether to operate.

What the report must contain to bear evidential weight in an OHSA proceeding:

  • 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 plate and ideally engine/chassis number.
  • Location of the observation.
  • Description of the defect in the driver's own words.
  • Photograph or short video where the defect is visually apparent.
  • The driver's assessment: roadworthy / drivable with limitations / not roadworthy.

The first failure point South African SME fleets show: the defect is reported by phone or WhatsApp message to the Site Foreman or Operations Manager. No record exists in any system. The phone log, if it exists, has a time but no content; the WhatsApp message can be deleted. The DEL inspector cannot find the trigger event in the file because the trigger event is in the Foreman's head.

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

The decision-maker — Site Foreman, Workshop Manager, Fleet Supervisor — must take and record an explicit decision once the report arrives. The decision is one of:

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

Whatever the decision, it must be recorded with identity, time, and a one-line reason. The vehicle's operational status must be visible to the next person who might dispatch or operate it. A note on the Foreman's notepad does not survive Friday afternoon when the Foreman has gone home.

Second failure point: receipt without recorded decision. The Foreman sees the report, intends to act, but no decision is captured before the day moves on. The DEL inspector finds this gap by asking "where is the receipt acknowledgement of the defect?" If the answer is silence, OHSA section 8(1) is engaged.

Stage three — out-of-service status and the visible signal on the vehicle

Where the defect engages safety-critical operation, the vehicle must be taken out of service in a way that the next driver cannot bypass by accident. A note in the dispatch system that does not produce a physical or in-cab signal is a near-failure. The classic SA SME pattern is verbal "don't take Truck 14" — which does not survive shift change at a remote site.

What an inspectable workflow looks like:

  • The vehicle's status in the dispatch system is "out of service" and cannot be assigned to a job.
  • A physical sign or in-cab notice appears on the dashboard.
  • Where the system supports it, the in-cab tablet displays the status when the driver opens the cab.
  • The out-of-service status can only be cleared by a verified post-repair inspection record.

Third failure point: the out-of-service decision exists in the system but does not produce a visible signal. A weekend driver picks up the keys, drives, the defect causes a roadside event. The DEL inspector now has both the original defect and a workflow that allowed an unsafe vehicle to be operated.

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 diagnostic steps.
  • Parts used — manufacturer, part number, supplier reference.
  • Photographs of removed and installed components.
  • Test drive or functional test outcome.

For SA SMEs that contract repairs out to independent workshops in Industria areas, the failure point is in the supply chain. The shop works on the vehicle and produces an invoice when asked. The invoice is generated at the time of asking, not at the time of the work. A line "steering rack replaced" can be opened on the invoice query, not at the time the work happened.

Fourth failure point: the repair record is not contemporaneous with the work. In an OHSA prosecution, the workshop's software audit log will be requested where it exists, and where the workshop runs only paper invoices the contemporaneity question opens further. The remedial action: a contract with the workshop specifying same-day photographic evidence, parts traceability documentation, and a mechanic identity that can be authenticated. Where the workshop is internal, the system must capture this at the moment of work, sealed and chained, photographs EXIF-preserved.

Stage five — the verification before return to service

The vehicle does not return to service on the mechanic's say-so. A second person — Site Foreman, Workshop Manager, Fleet Supervisor — verifies: is the repair completed as ordered? Does the relevant component function? Has the out-of-service status been formally cleared? This is the second-pair-of-eyes check, and SA 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 an OHSA section 38 prosecution, the absence of this check is the structural fact the State will call out. In a Magistrate's inquest that follows a fatality, the absence becomes a basis for an adverse finding referred to the NPA.

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 submission time unalterably and binds it to the device.
  2. Receipt without recorded decision. Close it by requiring an explicit decision in the system before the report is treated as acknowledged.
  3. Out-of-service status without visible signal. Close it with an in-cab device or physical sign mandated by workflow, plus a system-side block on dispatch.
  4. Repair record not contemporaneous. Close it by contractual obligation on the workshop and capture-time photographs with EXIF preserved.
  5. Return to service without independent verification. Close it by requiring an OTP-verified second-person sign-off before the out-of-service status clears.

Each gap is, on its own, a question the DEL inspector will ask. Several of them together approach the gross-negligence threshold under OHSA — and the threshold the State must clear to prosecute corporate accused with the higher penalty range under section 38.

The POPIA dimension — fleet telematics data

South African fleet operators are increasingly running telematics systems — GPS trackers, dashcams, driver-behaviour monitors. The Protection of Personal Information Act 4 of 2013 (POPIA) applies to the personal data flowing through these systems. POPIA section 11 requires lawful processing; section 13 requires adequacy and not-excessive processing; section 17 requires retention only for as long as is necessary.

For the workflow file, POPIA matters because driver identifiers, location data, and inspection records are personal information. A maintenance system that processes them must comply. The Information Regulator, established under POPIA, has investigation and enforcement powers including substantial administrative fines. Mekavo Fleet operates as a processor under POPIA and binds processing to specified, legitimate purposes; the operator is responsible party.

What an inspectable workflow looks like in Polokwane

The mining-services contractor, on a Tuesday morning when the DEL inspector arrives at the yard, can present the workflow as:

The driver reported the steering pull at 06:42 from the Polokwane yard. The report carries a server-side timestamp, the driver's identity is OTP-verified, GPS coordinates are embedded. The Site Foreman received a push notification within seconds. He opened the report at 06:51, took the vehicle off the road, recorded "to Industria Road workshop 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 out-of-service notice; the dispatch system blocked any assignment.

The workshop took the vehicle at 09:30. The mechanic recorded the diagnosis — worn steering box and one tie-rod end — and his work, photographing removed components against their part-tags and the new components 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 Workshop Manager — not the mechanic — reviewed the test-drive log and signed the verification at 13:47, also OTP-verified. The out-of-service status cleared automatically. The vehicle was assigned to the afternoon run at 14:05.

The DEL inspector asks for the chain. He receives a single record, byte-for-byte verifiable. He thanks the Site Foreman and leaves with notes, not a section 38 prosecution.

Six steps for a South African 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 out-of-service decision (or the reasoned alternative), the repair, and the verification?
  3. Read your contracts with external workshops. Do they require contemporaneous photographic evidence and identifiable mechanic? If not, renegotiate.
  4. Audit your out-of-service signalling. Is there an in-cab or physical signal that survives shift change? If not, design one.
  5. Review your verification practice. Is the second-pair-of-eyes check enforced by system, or convention? If convention, make it system.
  6. Train drivers and dispatchers in the workflow and document the training. Each is itself an OHSA evidence item.

Sources and further reading

Related Mekavo articles: When the Inquests Act brings your file before a Magistrate, SAPS, RTI and AARTO at Mooi River, Four phrases South African insurers use, Adapted vehicles, PEPUDA and the DSD SLA.

Why this matters to us

Mekavo Fleet was built around the five-stage workflow under OHSA 1993 and the South African road-traffic and accessibility frameworks. Every defect report is sealed at submission, chained to the vehicle's prior history, EXIF-bound. Every receipt carries the Foreman's identity. Every out-of-service 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 DEL inspector arrives in Polokwane, in Pretoria, in Cape Town or in Sandton, 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. Mekavo Fleet for South African operators.