A useful compliance calendar does more than warn that a date is approaching. It tells the dispatcher whether a vehicle and driver are ready for the planned work, who is checking an unresolved item, and what evidence confirms completion. A reminder alone cannot answer those questions.
Use this guide as an operating template, not a universal list of legal duties. Saudi transport requirements depend on the activity, vehicle and operator. Check the current Transport General Authority rules and the relevant official service before setting a requirement or deadline for your fleet.
Decide which requirements apply
Start by naming each transport activity you actually perform: for example, goods transport for hire, transport for your own account, passenger work or another licensed activity. Do not apply a rule from one activity to every vehicle merely because they share a depot or software account.
For each activity, record the official source, the document or connection it requires, who holds it, and the event that calls for a new check. Keep a link to the source beside the task. If the rule changes, your team should be able to identify every affected vehicle rather than edit a generic annual reminder.
- Activity and vehicle class: what work is this vehicle authorized to perform?
- Official source: which current rule or service defines the requirement?
- Responsible party: operator, driver, provider or finance team?
- Trigger: joining the fleet, renewal, reassignment, incident or another change?
Build one readiness record per vehicle
Give every vehicle one readiness record. Use a stable vehicle identifier and retain the history when a plate, owner, device or assignment changes. Record the relevant registration, insurance, technical inspection, activity permission and tracking status only where those items apply to that vehicle and activity.
Store the document or official response, its validity or effective date, the person who verified it and the next review date. An internal status such as 'submitted' must remain distinct from 'confirmed'. A failed inspection, pending renewal or device replacement may require an operational decision before the next trip.
- Stable vehicle identifier, current plate and assigned branch or operation.
- Applicable registration, insurance and inspection records with evidence.
- Applicable transport permission or operation card and its verified status.
- Device and tracking mapping where the activity requires it.
- Owner, effective date, next check and unresolved dispatch restriction.
Trigger reviews when the fleet changes
A calendar driven only by expiry dates misses changes that happen mid-year. Vehicle acquisition, ownership transfer, reassignment and device replacement can make a previously correct record inaccurate. Driver onboarding, licence changes and departure can do the same for the person assigned to a trip.
Create a short change task when an event occurs. Name the owner, records to update, external steps to verify and the effective time. Keep the old and new identifiers where they explain earlier journeys. If a provider or authority must confirm a change, record that response rather than closing the task when a request is sent.
- Vehicle added, sold, transferred or moved to another activity.
- Driver joined, left, changed licence status or changed assignment.
- Technical inspection failed or a safety-related repair remains open.
- Tracking device or provider changed, including the vehicle mapping.
- A document nears expiry, a renewal is rejected, or an official record differs.
Run a weekly exceptions review
Hold a brief weekly review of exceptions. Start with vehicles planned for work soon, then check approaching validity dates, rejected requests, failed inspections and unmatched vehicle or driver details. Decide who follows up and whether the item blocks dispatch under your own approved procedure.
The useful output is a small exception list, not another spreadsheet of every document. Show the vehicle or driver, the issue, the source of truth, the owner, the next action and when the team will check again. At shift handover, make unresolved items visible to the incoming dispatcher.
- Which planned vehicles or drivers have an unresolved readiness item?
- Which applications are pending, rejected or missing confirmation?
- Which dates require action soon under the applicable rule?
- Who owns each next step and what evidence will close it?
- What must the next shift know before assigning work?
Separate finance and official confirmations
Keep tax-invoice work in a separate finance stream. If your business is subject to ZATCA e-invoicing requirements, finance should verify the applicable phase, invoice type and process against ZATCA guidance. A vehicle work order, supplier bill and invoice your company issues serve different purposes; a fleet calendar can link them without treating them as the same document.
Likewise, a fleet system can hold records, reminders, assignments and evidence, but an internal green badge is not an official approval. Confirm the result in the relevant authority or authorized service channel. Do not infer that location data arriving in your dashboard proves an external tracking update was accepted.
Know when a task is actually closed
At the end of a review, each active item should have a responsible person, a source, a next action and a clear state: confirmed, waiting for evidence, rejected or blocked. Sample completed items against their source documents to catch a process that appears tidy but closes work too early.
Begin with one activity and a small set of vehicles. Run the calendar through a real vehicle change, driver reassignment and renewal. Fix the missing handoffs before expanding it to the whole fleet. Recheck the linked official sources whenever you revise a rule; this guide cannot determine the requirements for every operator.
This page lives at /guides/fleet-compliance-guide.
