How to control fleet fuel costs without blaming drivers

The control loop

Reconcile the transaction before calculating efficiency or judging behaviour.
Compare each vehicle with its own route- and duty-aware baseline.
Use several weak signals together instead of treating one threshold as proof.
Close every review with an outcome, owner and corrective action.

1. Reconcile every fuel transaction

Join each card movement or receipt to a known vehicle, date, station, volume, amount and odometer. Preserve the source row and record any correction separately so finance can trace the original transaction.

Unmatched transactions belong in a review queue, not in a fleet average. A missing plate, card reassignment or delayed posting can distort litres per kilometre long before it looks suspicious.

Match card number and vehicle assignment for the transaction date.
Validate currency, unit of volume and sign before aggregation.
Reject duplicate source identifiers and flag exact-value repeats.
Keep the source odometer, corrected odometer and reviewer note distinct.

2. Calculate fuel metrics from comparable periods

Efficiency needs two trustworthy odometers around the fuel consumed. Use a consistent period and unit, then compare similar vehicle classes and duties. A city delivery route, mountain route and highway route should not share one target.

Fuel efficiency

distance travelled ÷ fuel consumed

Display km/L or km/gal consistently. If either odometer is unreliable, label the result incomplete.

Metric	Decision it supports
Fuel cost per kilometre	Budget and route-level cost comparison
Distance per litre or gallon	Mechanical, route and driving trend review
Average unit price	Station, region and contract comparison
Unreconciled spend	Data-quality and card-assignment follow-up

3. Use exception rules as questions

An exception narrows the investigation; it does not establish misconduct. Combine tank capacity, time since the prior fill, price, odometer movement and the vehicle’s recent baseline before escalating.

Volume above usable tank capacity or a configured tolerance
Two fills too close together for the vehicle’s normal duty
Odometer lower than the previous accepted reading
Unit price far from comparable nearby transactions
Efficiency change that persists across more than one complete interval

4. Run a fair weekly review workflow

Start with the highest-value unresolved exceptions and give the reviewer the source transaction, recent fills, assignments and odometer history in one view. Ask for evidence before conclusions: receipt, route change, service event or corrected reading.

Outcome	Next action
Valid transaction	Approve it and keep the original evidence
Data error	Correct the derived value and improve the source process
Vehicle issue	Create maintenance work and monitor the next interval
Policy issue	Document facts and follow the organisation’s review process

5. Reduce cost without breaking the operation

Prioritise changes that can be tested: tyre pressure compliance, route planning, idle-time policy, supplier price, preventive maintenance and driver coaching. Track the before-and-after period with the same measurement rules.

Report savings only after separating price effects from consumption effects. Paying less per litre and using fewer litres are different improvements with different owners.

As featured in