Matatu and PSV fleet management is the daily discipline of connecting every vehicle, driver, and route run to a reliable operating record. Tracking is part of it, but the real work also includes vehicle readiness, fuel control, maintenance, incidents, and document-expiry follow-up.
A location dot can show that a bus is on Thika Road. It cannot tell the operations team whether the correct driver was assigned, whether the morning defect was closed, why the run left late, or whether the latest fuel fill makes sense. Those answers come from an operating system built around the route run—not from tracking alone.
This guide is operational guidance, not legal advice. PSV licensing and safety rules can change; confirm current obligations with NTSA or a qualified adviser.
What does a PSV fleet need beyond GPS tracking?
GPS is valuable because it provides objective movement data. But a PSV operator manages a service, not a collection of moving dots. The useful unit of work is a route run with a vehicle, a driver, an expected schedule, a start, a close, and any exceptions that happened between them.
The Kenya Law version of the PSV operating regulations covers route adherence, vehicle defect inspections, inspection records, driver and vehicle documents, and additional location-and-speed record requirements for long-distance passenger services. That is a records problem as much as a tracking problem.
Turn vehicle movement into a route operating record.
Kora provides shared fleet records for assigned vehicles and drivers, supported tracking, fuel review, maintenance and documents. Validate repeated daily runs before rollout; ticketing, fare collection and SACCO accounting are not included.
Build one record for every route run
Route control becomes easier when the team can open one record and see who, what, where, and when. A practical route-run record should contain:
- The vehicle and driver assigned to the route run
- The planned route, departure window, and operating schedule
- Vehicle readiness, open defects, and document-expiry status before release
- An opening odometer when the driver starts and a closing one when the run ends
- Fuel issued, fuel filled, and any variance that needs review
- Departure, delay, incident, and route-close timestamps
- Notes or evidence needed for the next shift and maintenance team
This does not need to slow the driver down. The workspace team can prepare the assignment, while the field user confirms a small number of high-value events: departure, an issue or delay, and route close. If connectivity drops, those field actions should queue and sync when the phone reconnects.
A planned run should not inherit a trip-start odometer from the dispatcher. Capture the opening reading at actual start and the closing reading at completion. Where the vehicle has a live odometer feed, those readings can be recorded without typing; otherwise the driver needs to enter the reading shown by the truck.
Make vehicle and driver readiness visible before release
The cheapest defect is the one found before a vehicle leaves. A digital readiness check gives dispatchers one view of the vehicle, the driver, open maintenance work, and the dates on important records. Before assigning a route run, the team should be able to ask:
- Is the vehicle active, roadworthy, and free from an unresolved critical defect?
- Are inspection, insurance, and other required vehicle documents current?
- Is the assigned driver active and are the relevant driver records current?
- Is the planned route clear, and does the team know the expected departure window?
- Is fuel sufficient for the run, and is the starting reading credible?
- Does the next service interval allow the vehicle to complete the planned work safely?
Software should support this decision without pretending to certify roadworthiness or legal compliance. Inspections and licences still come from the relevant authorities; the system keeps the evidence and expiry dates visible to the people releasing vehicles.
Control fuel by connecting litres to distance and route work
PSV fuel loss rarely appears as one obvious event. It often arrives as small exceptions: a fill without a credible odometer, a second fill too soon, a vehicle whose consumption worsens slowly, or a parked fuel-level drop on a sensor-equipped vehicle.
A useful fuel review asks specific questions instead of relying on the receipt alone:
- How many litres were filled, at what odometer reading, and for which vehicle?
- How far did the vehicle travel since the previous credible fill?
- Is consumption consistent with this vehicle, route, load, traffic, and driving pattern?
- Did two fills happen unusually close together?
- Does a sensor-equipped vehicle show a parked fuel-level drop that needs investigation?
- Was the exception reviewed and documented instead of silently cleared?
An anomaly is a prompt to investigate, not proof of theft. Traffic, idling, route changes, mechanical condition, and data-entry mistakes can all affect consumption. The control comes from keeping the exception visible until someone reviews and explains it.
Connect defects, workshop work, and the next service interval
A route team sees symptoms first: brake feel, tyre condition, lights, wipers, unusual sounds, or a warning on the dashboard. The maintenance team needs those observations to become structured work, not disappear in a call or chat.
A strong workflow links the inspection or defect to the vehicle, creates a maintenance job when action is needed, records the assigned mechanic, parts and labour, and keeps the vehicle unavailable when a critical issue is unresolved. Completed work then becomes part of the vehicle history and informs the next service date or odometer threshold.
Track document expiry without claiming to guarantee compliance
PSV operations depend on current vehicle, driver, insurance, inspection, and operating records. The exact set depends on the service and current rules. Store each document privately, record its expiry date, and alert the responsible person early enough to act.
The goal is operational readiness: no dispatcher should discover an expired record while trying to release a vehicle. But expiry tracking is not regulatory filing, licence issuance, or a legal guarantee. Keep that boundary explicit when evaluating software.
What should management review every week?
Daily control handles today's work. Weekly review identifies repeat patterns that a busy route desk may miss. A PSV fleet review should cover:
- Route runs that started late, closed late, or have missing closeout records
- Vehicles with repeated fuel exceptions or falling efficiency
- Open maintenance jobs and defects carried into another shift
- Insurance, inspection, licence, or other records approaching expiry
- Drivers with repeated incidents, missed checks, or incomplete route records
- Vehicles with weak utilisation or too much unplanned downtime
Every exception should leave the meeting with an owner and next action. A dashboard that shows red numbers without a review workflow creates awareness, but not control.
Frequently asked questions
What is matatu fleet management software?
Matatu fleet management software connects each vehicle and driver to a route run, live or recent location, fuel records, maintenance history, incidents, and document-expiry dates. It gives the operator one operating record instead of separate calls, notebooks, tracking screens, and spreadsheets.
Is GPS tracking enough for a PSV or matatu fleet?
GPS tracking answers where a vehicle is and where it has travelled. A PSV operation also needs to know who was assigned, whether the run started and closed correctly, which defects are open, what fuel was used, and which vehicle or driver documents are nearing expiry.
How can a matatu SACCO control fuel usage?
Start by recording every fill against the correct vehicle, time, litres, cost, and odometer. Compare each fill with distance covered and the vehicle baseline, then review excess fills, mileage mismatches, rapid refills, and sensor-detected drops instead of approving every record automatically.
What records should a PSV operator review every week?
A PSV operator should review late or incomplete route runs, open vehicle defects, fuel exceptions, service readiness, driver incidents, utilisation, and documents approaching expiry. The review should produce named actions with owners and due dates.
Does fleet software make a PSV operator legally compliant in Kenya?
No. Fleet software can organize operational evidence, vehicle and driver records, maintenance history, location data, and expiry reminders, but it does not issue licences, perform inspections, file regulatory returns, or guarantee compliance. Operators should confirm current requirements directly with NTSA or a qualified adviser.
Official sources and further reading
Regulatory requirements change. Use these primary sources as a starting point and confirm current NTSA guidance before making compliance decisions.