How do Kenyan fleets detect fuel theft and leakage?

By logging every refill with driver, vehicle, and odometer context, tracking fuel per kilometre, comparing each vehicle against its own consumption baseline, and reconciling records weekly so anomalies surface while they can still be explained.

What should be captured at every fuel refill?

Date, litres, cost, driver, vehicle, and odometer reading. Photo evidence of the receipt and odometer removes disputes later.

Why are per-vehicle fuel baselines better than fleet averages?

Because vehicles differ by age, load, and route, a fleet average hides the outliers. A per-vehicle baseline flags refills that deviate from that vehicle’s own normal, which is how siphoning and unauthorized detours actually show up.

Blog

Fuel Management Best Practices for Kenyan Fleets

March 6, 2026 · 7 min read · LogixFleet Team

Why fuel leakage goes unnoticed

Leakage usually comes from small, repeated gaps: unverified refills, missing trip context, weak reconciliation, and delayed reporting. Without clean data, losses are hard to prove.

That is the uncomfortable part for most Kenyan fleet operators. Fuel is usually the largest variable cost in the operation, yet the controls around it are often the weakest: a stack of station receipts, a fuel card statement nobody reconciles until month-end, and a spreadsheet that depends on one person keying everything in correctly.

Nobody loses a full tank at once. Losses arrive a few litres at a time: a rounded-up figure here, an undocumented refill there, a route detour that burns more than it should. Each event is too small to chase on its own. Over a quarter, across a fleet, the total is real money.

Practice 1: Log every refill with full context

Every refill should capture date, litres, cost, driver, vehicle, and odometer reading. Miss any one of those and the record loses most of its value. Without the odometer you cannot compute consumption. Without the driver you cannot assign accountability. Without the vehicle you cannot compare units.

Make capture easy at the pump. A photo of the receipt and the odometer takes seconds and removes the argument later. The rule is simple: if the refill is not logged with full context, it does not get reimbursed.

Practice 2: Track fuel per kilometre by vehicle and route

Raw fuel spend tells you almost nothing because it rises and falls with activity. Fuel per kilometre is the number that exposes problems. The same vehicle on the same route should burn roughly the same fuel week after week. When it does not, something changed: the route, the load, the vehicle's condition, or the honesty of the records.

Practice 3: Use per-vehicle baselines, not fleet averages

A fleet-wide average hides the outliers you are trying to find. An older truck on rough upcountry roads will never match a newer van doing Nairobi deliveries, and comparing both to one average flags the wrong vehicles.

The stronger control is a baseline per vehicle. This is where software earns its keep: Siphyy's AI builds a consumption baseline for each vehicle after about five fills, then flags refills that deviate from that vehicle's own normal. That is the pattern behind siphoning, unauthorized detours, and excessive idling. See how the workflow fits together on the fuel management software page.

Practice 4: Reconcile weekly, not monthly

Month-end reconciliation finds losses after four weeks of repetition. Weekly reconciliation finds them after one. Match refill logs against card statements or cash floats every week, and treat unmatched entries as exceptions to be closed, not noise to be tolerated.

Weekly cadence also protects data quality. A driver can explain last Tuesday's refill. Nobody can reconstruct the 14th of last month.

Practice 5: Review high-variance vehicles with operations and finance together

Run a short weekly review of the highest-variance vehicles with both operations and finance in the room. Operations knows the legitimate explanations: a changed route, a heavy load, a mechanical issue. Finance knows the cost. Together they can close each exception with a reason or an action instead of letting the list grow stale.

Recurring variance on one vehicle is often a maintenance signal rather than a driver problem. Fuel economy degrades with underinflated tires, clogged filters, and overdue service, which is why the fuel review should connect to the preventive maintenance checklist rather than run in isolation.

Reporting cadence

Use a weekly review to catch outliers early, and a monthly review for trend analysis and budgeting. Separate operational alerts from finance summaries so teams can act quickly.

What to measure

Fuel cost per kilometre
Consumption variance by vehicle against its own baseline
Refill anomalies by driver and route
Month-over-month fuel spend

Driver-level patterns belong in the same conversation as coaching, not just enforcement. Connecting fuel behaviour to driver scorecards keeps the review constructive and gives careful drivers visible credit for the fuel they save.

Where Siphyy fits

Siphyy gives Kenyan fleets the workflow behind these practices: structured refill logging, per-vehicle baselines with AI anomaly detection, and fuel reporting that operations and finance read the same way. The Kenya-specific view is on the fuel management software Kenya page, and the broader cost picture is covered in how to reduce fleet costs with better data.

Final takeaway

Strong fuel control is less about complex policy and more about consistent data capture, fast exception handling, and weekly discipline.

Log every refill, compare every vehicle to its own baseline, reconcile weekly, and review exceptions with operations and finance together. Leakage does not survive that routine.