Running a transport company in Kenya is operationally complex. Vehicles move across difficult roads and varying connectivity. Drivers expect to be paid quickly and correctly through M-Pesa. NTSA compliance requires tracking multiple documents with different expiry cycles. Clients expect updates and accurate invoices. Fuel is a major cost with real theft risk. Maintenance, if delayed, turns into expensive breakdowns at the worst possible time.
This guide covers all of it — every major area of fleet management, what good practice looks like, and how a connected system makes each area easier to run.
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.
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.
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:
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.
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.
One dispatch dashboard for your whole fleet.
Kora Fleet gives dispatchers a clear view of every vehicle, driver, and active trip — with assignments, status updates, and trip records in one place.
Fuel is the single largest variable cost in any transport operation. For a Kenyan fleet running diesel trucks on long-haul routes, fuel typically represents 35 to 45 percent of total operating costs. That makes fuel management not just an accounting exercise — it is a core operational discipline.
The foundational rule of fuel management is simple: every fill must be recorded with the odometer reading at the time of fill. From this one discipline, a system can calculate consumption per fill, compare it against the vehicle's baseline efficiency, and flag anything that does not match.
Good fuel control practice covers:
The most common fuel anomalies in Kenyan fleets are excess fills — where litres filled significantly exceed expected consumption for the distance covered — and mileage mismatches, where the odometer reading does not align with the volume purchased. Both patterns are difficult to sustain when every fill is reviewed against the trip record.
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.
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, M-Pesa phone and name for payouts, 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.
For drivers on long routes with limited connectivity, the app must work offline. Actions taken while offline should queue automatically and sync when connectivity returns — not be lost.
Driver payment is one of the most friction-prone processes in Kenyan fleet operations. Most companies pay drivers after each trip or at the end of the month. Most of those payments go through M-Pesa. And most companies manage this through a combination of mental arithmetic, WhatsApp messages, and manual M-Pesa transfers that are reconciled — if at all — from bank statements.
A trip settlement typically covers:
When this calculation is done manually for each driver across multiple trips per week, errors are common and disputes are inevitable. A platform that automates the settlement calculation — drawing the trip rate from the dispatch record, the advance from the advance request, and the mileage from the odometer — and then initiates the M-Pesa B2C transfer directly reduces both the error rate and the time it takes to settle drivers.
Every M-Pesa transaction confirmation becomes part of the trip record. This matters for accounting, for audit, and for resolving disputes when a driver claims they were not paid correctly.
Pay drivers directly through M-Pesa.
Kora Fleet calculates trip settlements automatically and initiates M-Pesa B2C payouts from the platform — with every transaction linked to the trip record.
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:
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.
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:
Managing these across a fleet of ten or more vehicles through a shared folder or a physical file cabinet means compliance lapses are a question of when, not if. Expiry dates cluster around renewal periods. The person responsible for renewals is often the same person running daily operations. Reminders get missed.
Fleet software that stores every document with its expiry date and sends alerts 30 days in advance — and again at 7 days — turns compliance from a crisis-management activity into a routine process. It also gives drivers and dispatchers a way to confirm that the vehicle being assigned is compliant before departure.
Every completed trip should generate a clear billing record: the client, the route, the cargo, the agreed rate, the delivery date, and any applicable VAT. 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.
Good fleet invoicing connects the trip record to the invoice automatically. The client, route, and rate pull from the dispatch record. The delivery confirmation provides the proof of delivery basis. The invoice is generated from actual data, not from memory or manual entry.
Kenyan transport companies typically invoice with 16 percent VAT and payment terms of 30 to 60 days. Clients on credit terms need to be tracked for outstanding balances — a client with an overdue invoice should not be dispatched another trip without the finance team being aware.
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.
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.
That connection is what fleet management software does. For Kenyan transport companies, the platform needs to do it with M-Pesa at the centre, NTSA compliance built in, offline field support, and fuel anomaly detection as a first-class feature — not an afterthought.
The companies that get this right spend less on fuel, have fewer breakdowns, retain better clients, pay drivers faster, and build the kind of operational record that makes growing the fleet a choice — not a gamble.
The complete platform for Kenyan fleets
Kora Fleet connects dispatch, fuel, drivers, maintenance, compliance, invoicing, and M-Pesa payouts in one platform built for Kenyan and East African transport companies.
