Royal Decree No. M/85 of 26/10/1428H (2008) — the Traffic Law — and the Implementing Regulations issued by Council of Ministers Resolution No. 251 of 1437H set the federal road-traffic regime in the Kingdom. It is enforced by the General Directorate of Traffic under the Ministry of Interior, supported by the integrated Saher automated enforcement and tracking system. A combined GDT-and-Saher intervention on Highway 40 is a standard tool of regulatory practice along the Jeddah-Mecca-Madinah corridor, especially during pilgrimage seasons when traffic volume and supply-chain pressure peak together.

This article is for KSA fleet operators with between ten and fifty vehicles — Jeddah-based logistics SMEs, Mecca-area distribution operators, Madinah-area light-fleet contractors, and small commercial fleets supporting the corridor's retail and pilgrimage supply chain. The roadside intervention is where federal Traffic Law meets the operator's daily documentation, and twelve minutes is genuinely the order of magnitude for a competent intervention.

The framework — what the GDT officer is checking

A GDT officer at a roadside intervention has authority under the Traffic Law and the Implementing Regulations to verify vehicle registration, mechanical fitness via the Motor Vehicle Periodic Inspection (MVPI / الفحص الدوري) certificate, driver licensing class, operator licensing where applicable for commercial fleets, axle-weight compliance against the gross vehicle weight on the registration document (الاستمارة), load restraint, and the documentation supporting any goods movement (delivery notes, ZATCA documents for cross-border, hazardous-materials documentation where relevant).

The Saher system gives the officer a starting database before the driver hands over a single document: vehicle plate-history, driver-licensing history, prior traffic violations, prior incident events, current vehicle insurance and inspection status. What the officer verifies at the roadside is the alignment between the database picture and the physical reality presented by the vehicle and the driver.

The standard intervention has a sequence:

  1. Driver to provide National ID or Iqama (residency permit), Saudi driving licence (correct class for the vehicle), vehicle registration card (الاستمارة), and insurance certificate.
  2. Vehicle inspection by the officer — MVPI certificate validity (cross-checked instantly via Saher), technical condition (lighting, tyres, brake-pedal feel, mirrors, cab indicators, audible warning), seat-belt operation, and visible body and chassis state.
  3. Load and goods documentation — delivery notes, weight calculation against the GVW on the registration, restraint and securing.
  4. Operator-side documentation — where the vehicle is on a Transport General Authority commercial operator licence, the licence document and any vehicle-specific authorisation.
  5. Decision — clear release, advisory release with rectification window, or formal escalation to a designated inspection compound.

The MVPI fitness-certificate dimension

KSA vehicles undergo periodic technical inspection at MVPI centres operated under the regulatory oversight of the Transport General Authority. The fitness certificate that issues from a passing inspection is a regulatory document — it is reflected in the central MoI / Saher database and accessible to the officer at the roadside instantly via plate-query. The officer's position at the roadside is therefore informed: she or he already knows whether the certificate is current, when it expires, and whether the registration is in good order.

What the operator controls is whether the physical condition of the vehicle aligns with the certificate. A vehicle whose tyres are below tread, whose lighting fails on the officer's walk-round, with a current certificate, raises the question of post-certificate degradation — and the answer must be the operator's daily-inspection record.

The driver-side documentation

What sits in the driver's cab on a competent fleet:

  • Today's daily vehicle inspection — done before the run, accessible via the operator's app on the driver's device, with the timestamp showing the inspection was completed at the start of the shift.
  • The most recent defect report and its status — open, repaired-and-verified, or assessed-and-deferred (with a clear deferral note).
  • The vehicle's last service entry and parts-replacement log, retrievable on the device.
  • The vehicle's MVPI fitness-certificate, registration and insurance position — typically in the operator's app and in the cab's document holder.
  • The driver's own duty-and-rest position for the past 28 days where the vehicle is subject to commercial driving-time regulation.

The escalation track if the intervention goes badly

Where the officer concludes that the vehicle is not roadworthy, the standard escalation is diversion to an inspection compound for full technical examination. The vehicle is held until rectification and re-inspection. Depending on the technical finding, an administrative penalty issues to the operator under the Traffic Law and the Implementing Regulations. Repeat or serious findings affect the operator's licensing position with TGA and may trigger a wider review of the operator's fleet.

Where the driver is found to be driving without entitlement, with an expired licence, with open serious traffic violations, or with the vehicle in a manifestly unsafe state with the operator's knowledge, the file may be referred to the Public Prosecution under the Traffic Law and corresponding criminal-law provisions. The operator faces administrative action, possible criminal exposure for the relevant officer, and reputation cost in the small KSA commercial fleet community.

The corporate-governance turn — what survives in court

What survives in court — administrative-tribunal review, Court of First Instance criminal proceedings, or insurer disputes that emerge later from the roadside file — is the documentation that was created before the intervention, sealed at the time of capture and chained against the vehicle's prior operational record. A re-typed weekly inspection sheet produced to the prosecutor a month later, lacking timestamp evidence, lacking photographic anchor and lacking identity verification on the inspector who completed it, is worth less than the paper it is printed on. A daily inspection produced from the operator's app, with a server-anchored timestamp, EXIF-bound photographs, OTP-verified driver identity, and a SHA-256 hash chained to the vehicle's prior inspection sequence, is evidence that holds.

Eight steps before the next twelve-minute intervention

  1. Map the fleet to the regulatory tier — vehicles operating Jeddah-internal versus corridor versus cross-border (Bahrain via King Fahd Causeway, UAE via Al-Batha) carry different documentation needs.
  2. Audit MVPI fitness-certificate status across the fleet today against the central Saher database — the officer knows before you do whether yours are current.
  3. For every vehicle in service today, confirm the daily inspection was completed at start-of-shift and the result is retrievable on the driver's device.
  4. Audit the past sixty days of defect reports. For every defect, can you trace receipt, repair, and post-repair verification — each timestamped and bound to a specific identifiable mechanic?
  5. Audit the driver-side licensing position monthly. Driver entitlement is checked at every roadside intervention; a lapse you do not know about is an exposure you cannot manage.
  6. Pull your operator licence and supporting TGA documentation. Is it current? Are the vehicle authorisations on it correctly mapped to the fleet?
  7. Review your insurance-position transparency to drivers. The cab document holder should hold the insurance certificate; the driver should know which insurer covers the vehicle.
  8. Within sixty days replace paper records with a system producing sealed, chained, independently verifiable records. A roadside intervention is an information-density event; the operator who can produce information density wins it.

Sources and further reading

Related Mekavo articles: When the Public Prosecution opens a fatality file, Four phrases KSA insurers use to refuse a fleet claim, Driver defect to verified repair under Labour Law M/51.

Why this matters to us

Mekavo Fleet gives the KSA driver a single screen for the daily inspection, the defect report, the photographic evidence, the licensing-and-insurance position. Every entry carries a server-side timestamp from the moment of submission, is cryptographically chained to the vehicle's previous record, EXIF-and-SHA-256 bound to the device that captured the photograph. At a Highway 40 GDT intervention the driver produces an entry the officer cannot back-date or front-date — and the cross-check against the Saher database lines up. At any later proceeding — Public Prosecution review, Court of First Instance criminal hearing, insurer dispute, Ministry of Human Resources follow-up — the same record produces itself, identical, re-verifiable by anyone. See Mekavo Fleet KSA.