The most exposed point in any KSA fleet operation is the moment between a driver identifying a defect and the vehicle returning to service after repair. Five things must happen, with documentation that survives both the Ministry of Human Resources' OSH inspector under Royal Decree No. M/51 of 23/8/1426H (2005) — the Labour Law, with the substantive 2024 amendments — and the broader litigation chain that opens after a serious incident: (1) the defect is reported the moment the driver identifies it, (2) the report is received and acknowledged by an identifiable competent person, (3) the vehicle is taken out of service or assessed-as-safe-to-continue with a clear basis, (4) the repair is carried out by an identifiable competent technician with the right parts and the right tools, and (5) the repair is verified by an independent second person before the vehicle returns to service. Each step must produce evidence that carries.

This article is for KSA fleet operators with between ten and fifty vehicles — Jubail Industrial fleets, Ras Tanura supply-chain contractors, Dhahran-area mid-market operators, Riyadh 2nd Industrial heavy-haulage operators, Eastern Aramco / SABIC-tier mechanical contractors, and Eastern Province logistics SMEs. The five-step framework is the same. The Ministry of Human Resources OSH inspection of the workshop file is the same.

Step one: defect reported at the moment of identification

The driver identifies a steering-feel concern, an unusual vibration, a light, a smell, an audible warning. The clock starts at the moment of identification. The defect should be reported through a system that timestamps the report at the moment of submission, captures the driver's identity by the operator's standard method (typically OTP plus device-pairing), captures location through the device's GPS, and allows photographic and audio evidence at the moment of identification.

The places KSA fleets lose the trail at step one:

  • WhatsApp to the workshop manager — no timestamp anchored in an unalterable system, identity by phone-number only, no location, no photographic linking.
  • Verbal report at the depot at end-of-shift — no contemporaneous record, multi-hour gap between identification and report.
  • Paper defect slip handed in next morning — date written by the driver, easily back-dated or front-dated, no identity verification.
  • Telematics alert with no driver-side annotation — the system caught the vibration but the driver's description of the concern, which is what an OSH inspector wants, is missing.

Step two: receipt and acknowledgement by an identifiable competent person

The defect report is received by the workshop manager or the operations manager. Receipt should be timestamped, identity-verified, and produce an acknowledgement back to the driver. The competent person decides whether the vehicle is safe to continue to the depot, must be parked at the current location and recovered, or can finish the day with a clear advisory.

The places KSA fleets lose the trail at step two:

  • "I told the workshop" — workshop has no record, the receiving identity is unclear, the acknowledgement to the driver is verbal at best.
  • "It was Friday" — receipt is delayed to the next working day, the vehicle continues to operate over the weekend, the OSH inspector identifies the gap.
  • "I assessed it on the phone" — the assessment is undocumented, the basis for the safe-to-continue decision is not retrievable.

Step three: out-of-service or assess-as-safe-to-continue with a clear basis

The vehicle is either removed from service or marked safe-to-continue with a documented assessment. The decision is made by an identifiable competent person whose qualifications are on the file. The basis is recorded — what the competent person assessed, what evidence they reviewed, what manufacturer specification or maintenance-schedule information informed the call.

The places KSA fleets lose the trail at step three:

  • Out-of-service decision but the vehicle continues to be deployed — the system says one thing, the operational reality says another.
  • Safe-to-continue decision with no recorded basis — the competent person's call is undocumented; if they later leave the company, the basis is lost.
  • Decision delayed pending diagnosis — the vehicle continues to operate while diagnosis is pending, with no clear deferral basis.

Step four: repair by an identifiable competent technician with right parts and tools

The repair is carried out by a technician whose identity is recorded, whose qualifications are on file, with parts whose origin is recorded (manufacturer-original, OE-equivalent, after-market with specification), with tools appropriate to the task. Photographic evidence captures the pre-repair state, the parts replaced, and the post-repair state.

The places KSA fleets lose the trail at step four:

  • Workshop did not record which technician completed the work — receipt of the repair attached only to the workshop, not to a person.
  • Parts origin not documented — was it OEM, was it OE-equivalent, was it after-market? Three months later neither the operator nor the workshop can answer.
  • No photographic evidence of the work — what was actually done is recorded only in the technician's memory.
  • Receipt produced after the work, with the work itself unrecorded between technician completion and receipt issue.

Step five: verification by an independent second person before return-to-service

The repair is verified by an identifiable second person — typically a workshop foreman or a fleet supervisor — whose identity is recorded, whose verification is timestamped, with photographic and physical-test evidence (test-drive log, brake-pedal feel, hydraulic-pressure check, lighting and indicators, audible warning). The verification produces a sealed entry that returns the vehicle to service.

The places KSA fleets lose the trail at step five:

  • No verification — the repairing technician releases the vehicle back to service, undermining the four-eyes principle.
  • Verbal verification — the foreman said it was OK; nothing is on the file.
  • Test-drive without log — the vehicle was driven, but the route, conditions and outcome are not recorded.
  • Verification by a person whose qualifications for the task are not on file.

The Ministry of Human Resources OSH inspector's read of the workshop file

An OSH inspector arriving for routine inspection — or for incident-driven inspection — reads the workshop file the way a forensic auditor reads a finance file. They sample defect reports across recent months. For each, they trace the five-step chain. They observe whether each step is dated, whether each step has identifiable people on it, whether the photographic evidence corresponds to the dates claimed, whether the defects were closed within reasonable time given their severity, and whether deferred items have a documented basis.

The inspector finds gaps, inconsistencies, and missing evidence. They write findings. Where the findings indicate a systemic OSH deficiency, the file is escalated to administrative penalty under the Labour Law and the Implementing Regulations, or referred to Public Prosecution where the deficiency is severe enough to engage criminal-law provisions in the event of a parallel injury or fatality. GOSI work-injury claims arising from the same incident also draw on the same workshop file as documentary basis.

The litigation backdrop — what survives in court

If a serious incident later happens involving the vehicle, the workshop file becomes the principal evidence in the convergent files we addressed in earlier articles in this series — the Public Prosecution criminal investigation, the General Directorate of Traffic technical examination, the heirs' civil claim, the insurer's coverage decision. The workshop file produced by a sealed-and-chained system is identical when produced for any of those audiences. The workshop file produced by paper, WhatsApp and memory is not — and the gap, when it appears, is fatal to every defence.

Eight steps to fix the chain in your workshop file

  1. Map every defect-to-repair flow currently in operation across your fleet. How many distinct routes does a defect take? Each route is a place a record can fall through.
  2. Identify, for each route, where the timestamping, identity-verification, photographic capture, and chained-record properties exist or are missing.
  3. Audit the past sixty days of defect reports. For each, can you produce, today, the five-step chain with timestamped, identity-verified, photographic evidence?
  4. For each gap, identify whether it is a systems issue (the tool does not capture it), a process issue (the tool would capture it but the team did not use the tool), or a culture issue (the team is bypassing the system).
  5. Address systems issues by adopting a single defect-to-repair tool that captures all five steps with sealed-at-capture, chained, identity-verified records.
  6. Address process issues by training and a workshop-floor sign-off discipline that does not allow a repair to be closed without the verification step.
  7. Address culture issues by clear management messaging that the documentary record is the operator's defence and a bypass costs the directors personally under the Companies Law and the Labour Law.
  8. Re-audit ninety days after the change to confirm the chain is now intact end-to-end.

Sources and further reading

Related Mekavo articles: When the Public Prosecution opens a fatality file, Saher and GDT on Highway 40, Four phrases KSA insurers use, Persons with Disabilities adapted vehicles.

Why this matters to us

Mekavo Fleet was built around the five-stage workflow under the Labour Law and its 2024 amendments. Every defect report is sealed at submission, chained to the vehicle's prior history, EXIF-bound. Every receipt carries the workshop manager's OTP-verified 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 Ministry of Human Resources OSH inspector arrives in Jubail or Dhahran or Dammam or Riyadh, 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 KSA operators.