A useful fleet plan starts with the transport activity, the vehicles used for it and the people responsible for them. Requirements can differ by activity. Check the Transport General Authority's current rules for yours before turning a general checklist into a compliance decision.
Map one real journey from request to dispatch, delivery and closeout. Write down who approves the vehicle, assigns the driver, handles an exception and records the cost. That map shows where missing information slows the operation.
Start with the work your fleet does
When a vehicle joins, collect its identity, ownership or lease details, inspection and insurance records, and the documents required for its activity. Record the original expiry date and the person who will renew each item.
Confirm any applicable permits, platform registrations and tracking requirements against the current TGA activity rules. A vehicle appearing on an internal map does not by itself prove that an external authority has accepted its record.
Bring a vehicle into service
Before dispatch, check that the vehicle is ready for the assignment, the driver is eligible for the activity, and the required documents are valid. Make the release decision visible so a later shift can understand it.
Keep a calendar for inspection, registration, insurance, permits and activity-specific documents. Store the source date and its calendar type; verify a converted date against the issuing record before relying on it.
Keep documents and drivers current
When a driver joins, verify the licence, any activity-specific qualifications and the assignment process. When someone leaves, review vehicle assignments, access, cards and any records that must be updated with an external service.
Give each renewal an owner and an escalation path. A reminder is useful only if someone can see what was completed, what remains pending and which source confirms the result.
Connect fuel, maintenance and incidents
Fuel records become more useful when transactions, distance and vehicle context are reviewed together. An unusual pattern is a prompt to investigate; it is not proof of misuse.
Record defects at inspection, assign a work order, and close it with the repair and return-to-service decision. Keep the history with the vehicle so repeat faults and total cost can be reviewed.
Choose what the system should do
For a breakdown or incident, preserve the time, location, assignment, people contacted and actions taken. Agree on a handover process before an exception occurs, including who can remove a vehicle from service.
Review a small set of measures each week: vehicles unavailable, overdue work, document exceptions, fuel outliers and open incidents. Give each number a named action owner rather than adding another dashboard.
A fleet system should connect the records your team already uses and show what needs attention. Ask a provider to demonstrate the exact workflow with your vehicle types, roles, Arabic users and real sample dates.
Keep authority submissions and confirmations distinguishable from your internal records. Software can help prepare and monitor work; the operator must still verify the obligations that apply and the status of each submission.
Start with one depot or vehicle group. Measure the time to add a vehicle, resolve an exception and retrieve a complete record before expanding the process.
For activity requirements, use the TGA's current guidance. For vehicle inspection use the MVPI service information, and for electronic invoicing use ZATCA's current guides. Recheck these sources when your operation or the rules change.
This page lives at /fleet-management-guide.
