The Complete Guide to Fleet Management for Kenyan Transport Companies

Running transport requires reliable vehicle, driver, dispatch and financial records. Payment methods, connectivity and document requirements vary by operation. This guide sets out a practical record-keeping framework, not an exhaustive legal checklist.

The sections below cover common fleet-management activities. Specialised cargo, cross-border work and passenger services can require additional controls.

Whether you are running your first fleet or scaling an operation that has outgrown spreadsheets and WhatsApp, the principles here apply across fleet sizes and vehicle types — trucks, matatus, tankers, pickups, and everything in between.

1. Vehicle management

Every fleet management process starts with knowing your vehicles. Not just how many you have — but the condition, status, compliance, and cost profile of each one.

A well-managed vehicle record includes the registration number, category, make and model, year, fuel type, tank capacity, baseline fuel efficiency, and current odometer. These are not just administrative details — they are the inputs that make fuel anomaly detection, maintenance scheduling, and utilisation analysis possible.

Vehicle status matters for dispatch. A vehicle that is in maintenance is not available for a trip. A vehicle that is in transit cannot be assigned to another job. Knowing the real-time status of every vehicle — active, in transit, in maintenance, retired — prevents the common mistake of dispatching a vehicle that is not actually available.

Trailers and prime movers need to be tracked as linked pairs. The trailer assignment changes trip capacity and determines which compliance documents apply to that specific movement.

2. Dispatch and trip management

Dispatch is the centre of daily fleet operations. It is where vehicles get assigned to jobs, drivers receive their instructions, and the movement of cargo is translated into business records.

Good dispatch depends on five things being clear at all times:

• Vehicle availability — knowing which vehicles are active, in transit, in maintenance, or available
• Driver assignment — matching the right driver and vehicle to the right job
• Trip records — capturing every assignment with client, route, cargo, and timing
• Status visibility — knowing where active trips are and whether they are on schedule
• Client communication — giving clients reliable ETAs and delivery confirmations

In a manual dispatch system — calls, WhatsApp, a notebook — these five things are held in the head of one or two people. That works until the fleet grows, the coordinator is unavailable, or something goes wrong and there is no record to fall back on.

Digital dispatch creates a record for every trip: who is assigned, what vehicle, which client, which route, what cargo, and what the agreed rate is. That record connects to invoicing, to fuel logs, and to driver settlement — so each trip becomes a complete operational and financial unit rather than an isolated event.

Keep the vehicle's last known odometer visible to dispatch without letting a planned trip claim mileage before it starts. In Kora, the trip's opening reading is captured when the driver starts work and its closing reading when the driver completes it. A live tracker can supply the reading; otherwise the driver enters the truck's reading. The completed trip keeps that pair even as the vehicle continues to move.

Those readings are the distance basis for reviewing vehicle economics. See the fleet cost-per-kilometre calculation for an example that separates fuel and workshop spend from driver pay.

For drivers, dispatch should be mobile-native. Instructions should arrive on a phone, not through a chain of WhatsApp messages. Trip status — departure confirmed, en route, at destination, completed — should be captured by the driver on the same device, not called in.

3. Fuel management and anomaly detection

Fuel can be a substantial operating cost, but its share varies with route, payload, vehicle, utilisation and prices. Calculate your own fuel share rather than applying an unsupported percentage to every Kenyan fleet.

Record litres, time, vehicle and odometer at each fill. Fuel added is not necessarily fuel consumed: use consistent opening and closing tank levels, or a reconciled measured-level window, before calculating consumption.

Good fuel control practice covers:

• Record every fuel fill with litres filled, cost per litre, and odometer at fill
• Cross-check consumption against distance covered since the last fill
• Flag anomalies: excess fills, mileage mismatches, rapid refills
• Review flagged logs before approving — do not let anomalies clear automatically
• Track fuel spend per vehicle and per trip to identify problem patterns

Examples worth reviewing include purchases above the recorded tank capacity, implausible odometer changes and repeated refills with little movement. Check partial fills, data errors and legitimate changes in workload before treating an anomaly as loss.

Fuel anomaly detection is not about assuming every driver is dishonest. It is about creating a system where honest drivers are protected from false accusations and exceptions are visible enough to be investigated. The culture that emerges from systematic review — where drivers know that records are read — reduces waste regardless of intent.

4. Driver management

Drivers are the most operationally critical people in a transport company. How they are managed — assignment, communication, accountability, payment — has a direct effect on trip performance, client satisfaction, and cost.

A driver record should capture more than just name and phone number. Licence category, licence expiry, ID number, settlement reference contacts, assigned vehicle, and trip history are all part of managing a driver properly. When a licence is about to expire, the operations team needs to know before the driver is dispatched on a job that would put the company in violation.

Driver communication in the field should happen through a mobile app — not calls and messages that leave no trace. A driver starting a trip should confirm departure through the app. Completing a trip should require delivery confirmation. Reporting a problem — breakdown, delay, cargo issue — should generate a logged incident, not a WhatsApp thread that gets buried.

Check offline support for the exact field workflow. Kora queues supported trip actions and incident reports; fuel accounting belongs in the workspace and consignment handovers currently require connectivity. Verify sync and keep a fallback for unsupported actions.

5. Driver settlements and M-Pesa references

Agree driver rates, allowance eligibility, how trip cash is given and accounted for, and payment timing before work starts. Keep the calculation and payment evidence together so both the driver and finance team can reconcile the amount.

A trip settlement typically covers:

• Trip pay from the agreed rate — per kilometre, a fixed trip fee, or both
• Less any advance the driver drew on this trip’s pay before it was done
• Mileage allowance for long-haul routes
• Accommodation or per diem for multi-day routes
• M-Pesa transaction confirmation as proof of payment

Keep the two kinds of advance apart. Money handed to a driver for border fees, tolls and road charges is a cost of the trip, recorded against that trip — never taken back from the driver's pay. Money a driver draws for their own use before the trip is done is their pay, drawn early, and comes off the settlement. Mixing the two is how a driver ends up paying for the company's road costs out of their own earnings.

When this calculation is done manually for each driver across multiple trips per week, errors are common and disputes are inevitable. A platform that prepares the settlement calculation — drawing the rate from the driver's rate card and the distance from the trip record — reduces both the error rate and the time it takes to reconcile driver settlements.

Every M-Pesa transaction confirmation can be recorded as part of the trip record. This matters for accounting, for audit, and for resolving disputes when a driver claims they were not paid correctly.

6. Vehicle maintenance

A vehicle breakdown on the Nairobi–Mombasa highway costs far more than the repair bill. Lost revenue, recovery costs, driver downtime, client damage, and the knock-on disruption to the rest of the schedule all add up. The best way to manage maintenance cost is to prevent breakdowns — which requires knowing when maintenance is due before the vehicle fails.

A complete maintenance record for each service should include:

• Service date and odometer at service
• Type of service performed — scheduled, corrective, tyres, brakes, engine
• Parts used with part numbers, quantities, and unit costs
• Labour costs and mechanic assigned
• Next service interval (odometer or date)

With odometer readings captured at every fuel fill and every maintenance event, a fleet management system can calculate the current distance from the last service for every vehicle and send alerts when any vehicle approaches its next interval. This shifts maintenance from reactive — fixing things after they break — to planned, which is both cheaper and safer.

Cost tracking across maintenance events also helps identify vehicles that are becoming a liability. If a single truck has consumed KES 300,000 in parts and labour over three months, that is information the owner needs to see — not buried in individual invoices from different workshops.

7. NTSA compliance and document management

NTSA compliance is a non-negotiable operating requirement for every commercial vehicle on Kenyan roads. Vehicles without current documentation face impoundment, fines, and the reputational damage that comes from a client watching their cargo sit on the roadside.

The documents a Kenyan commercial fleet must manage include:

• Inspection certificate — confirm the applicable inspection cycle and current NTSA instructions for each vehicle class
• Motor insurance — check the policy period, permitted use, scope and exclusions with the insurer
• Speed-limiter records — confirm the vehicle-class and unladen-weight requirement; do not use a rounded three-tonne rule
• PSV or commercial licence — depends on vehicle category
• Cargo declarations, permits and customs references appropriate to the specific cross-border movement
• Driver licences with correct category endorsements
• Cargo-specific permits or equipment certificates where required; verify the exact requirement rather than assuming every specialised vehicle uses the same certificate

A shared folder or paper register can work with clear ownership and consistent review. As record volume grows, check whether the team can still find current documents and arrange renewals in time.

A digital register can highlight recorded expiries and support renewal reminders. Confirm which documents affect dispatch readiness and how missing records are handled. Reminders depend on correct records and configured notifications; they do not guarantee compliance.

8. Client billing and invoicing

Every completed trip should generate a clear billing record: the client, the route, the cargo, the agreed rate, the delivery date, and commercial terms. Without a direct link between dispatch records and invoicing, billing depends on whoever received the trip information remembering to create an invoice — a process that creates gaps, delays, and disputes.

An invoice should trace back to the agreed commercial terms and delivery evidence. Review the billed account, amount, tax treatment and exceptions before issuing it. Part-load work needs separate commercial reconciliation for each customer.

Agree payment terms with each customer and review overdue balances before accepting further credit work. Do not assume one credit period applies across the transport industry.

Overdue invoice tracking, credit limit management, and payment recording are all part of the financial ledger that a well-run transport company maintains. When these connect to the operational record — every trip, every vehicle, every driver — the business has a complete financial picture rather than fragments held across multiple spreadsheets.

Putting it all together

The difference between managing a fleet well and managing it poorly is not usually a single missing system or a single bad process. It is the compounding effect of disconnected information — fuel data that does not connect to trips, maintenance records that do not connect to vehicles, invoices that do not connect to dispatch, driver payments that do not connect to trip settlements.

When these are connected — when every trip is a complete record that links the vehicle, the driver, the client, the route, the fuel, and the payment — the business becomes easier to manage, easier to audit, and easier to grow.

A connected fleet system can support that operating record. In Kora, confirm the supported dispatch, fuel, document and finance workflows against your own scenario, including separate consignment billing and offline limitations.

Connected records make it easier to evaluate fuel, maintenance, service and payment performance. Whether they improve those outcomes depends on data quality and the team’s follow-up; measure results rather than assuming them.

Frequently asked questions