Reduce Fuel Costs by Finding the Litres That Did No Work
Almost every litre you waste is bought legitimately, poured into the right tank and burned by the right engine. It just does not move anything. KO Fleetz separates fuel that produced work from fuel that produced heat, noise and a queue at a loading bay.
Fleet and logistics operators run KO Fleetz in production
Fuel is not one cost. It is four problems wearing the same invoice.
Pump price is the number everyone watches and the one you control least. Underneath it sit four things you do control, and they behave nothing alike. An engine running at a standstill converts diesel directly into nothing. A vehicle returning empty burns close to what it burned loaded and earns zero for the trip. A driver carrying speed into every roundabout pays for that momentum twice, once in fuel and once in brake pads. And a vehicle whose consumption has crept up over eight months has a mechanical fault that the fuel data noticed before the workshop did. KO Fleetz splits the invoice back into those four, because the fix for one does nothing for the other three.
These have completely different fixes, which is why treating fuel as a single budget line reliably fails. Idle hours at a bay are a scheduling problem and belong to the depot planner. Empty running is a network design problem and belongs to whoever accepts the loads. A heavy right foot is a coaching problem. Consumption drift is a maintenance problem. Send all four to the fuel card policy, which is the usual response because the card is the only thing management can see, and you address none of them. Meanwhile the operational waste stays invisible in the most common metric of all: a vehicle idling ninety minutes a day covers no distance, so it never appears in litres per hundred kilometres at all. It just quietly makes every other figure on that vehicle look slightly worse, and nobody can say why.
Work out which of the four is yours before spending anything. The Fuel Cost Calculator gives you a baseline, the Idling Cost Calculator prices the hours your engines run standing still, and the Fuel Cost per KM Calculator shows the spread between your best and worst vehicles on comparable work. If that spread is wide, the money is in the tail, not the average.
Why the fuel report gets ignored
The efficiency league table ranks drivers by litres per hundred kilometres, and the same man has been at the bottom for three years. He runs the hill route to the quarry, fully loaded, in traffic. He knows why he is there. Everyone in the room knows why he is there. The report gets tabled, discussed and quietly ignored, which is worse than not producing it at all: it teaches a depot that fuel data is unfair, and the next report that is fair gets ignored too.
Manual fuel management also arrives too late to be operational. The card statement lands weeks after the trips that generated it. Distance comes from an odometer photograph taken whenever the driver remembered. Somebody divides litres by kilometres, produces a figure that is roughly right for the fleet and useless for any vehicle in it, and files it. Nothing in that loop could have changed a driver's behaviour on the day, told a planner that a bay was generating idle hours that morning, or caught an injector going soft in week three of a slow decline. KO Fleetz closes that loop by reading distance and consumption off the feed as the trips run, so a soft injector surfaces in week three rather than in a statement two months later.
- Litres per hundred kilometres punishes route difficulty and rewards easy work, so the ranking measures the roster more than the driver.
- Idling is invisible to any distance-based metric, because the waste happens precisely when the denominator stops moving.
- A monthly average cannot separate a mechanical fault from a driver change, a seasonal load increase or a route change. All four look identical: the truck got thirsty.
- Manufacturer consumption figures make a useless baseline. They were measured on a test cycle at steady speed, and quoting them to a driver hauling twenty-six tonnes through a city loses the room permanently.
- Empty miles never show up as a fuel problem. They show up as a full tank and a completed trip, which is exactly what a fuel report is designed to approve of.
- By the time the statement arrives, the trips are done and the drivers have rotated. There is nothing left to coach, only something to argue about.
How KO Fleetz resolves this
The KO Fleetz modules that fix it
Reduce Fuel Costs is not one feature — it is a few KO Fleetz modules working off the same records. These are the ones that carry it.
The workflow
Separate the four problems, then hand each to its owner
Step 1: Split idle from motion
KO Fleetz counts fuel burned with the engine running and the vehicle stationary on its own clock, in hours and litres, attributed to the site, bay or shift where it happened rather than folded into a per-kilometre rate.
Step 2: Group work before comparing it
Trips sort into peer groups by lane, payload band, vehicle class and terrain. The question stops being who is worst in the fleet and becomes why one of the eleven drivers who ran this corridor at this weight uses noticeably more.
Step 3: Watch each vehicle against itself
Consumption is tracked against each asset's own history. A slow climb over months, with the same driver on the same route, points at dragging brakes, tyre pressure or an ageing injector. That is a workshop question, not a coaching one.
Step 4: Attack the litres that carried nothing
Empty legs, avoidable detours and out-of-route mileage are measured against the plan, so the biggest single lever in most networks — running loaded more often — becomes a number a planner can work with.
Step 5: Coach on evidence, in the same week
Harsh acceleration and over-speeding events link to the fuel burned on the same segment of the same trip, so the conversation is about a specific hill on Tuesday rather than a monthly score.
What you use
The capabilities that do the work
Drawn from across the platform — this problem is not solved by one module.
Idle burn on its own clock
KO Fleetz reports stationary engine hours and their litres separately by site and shift, exposing the loading bay that generates an hour a day across every vehicle that visits it.
Like-for-like driver comparison
Ranks only drivers who ran a comparable corridor at comparable weight, and shows the peer group alongside the ranking so anyone can check the comparison is fair.
Consumption drift detection
KO Fleetz flags the vehicle climbing steadily against its own baseline, the pattern a monthly fleet average is mathematically guaranteed to hide.
Payload-aware efficiency
Litres per tonne-kilometre where weight data exists, so a fully loaded run is not scored against a half-empty one and called inefficient.
Empty and out-of-route mileage
Distance run without a load, and distance run beyond the planned path, are measured as fuel the network design paid for rather than the driver.
Behaviour to burn correlation
Links harsh acceleration, over-speeding and heavy braking to the fuel consumed on that exact segment, turning a safety score into a fuel argument.
Route and stop sequencing
Plans that respect real road speeds, turn restrictions and delivery windows cut the distance you burn fuel over before a driver touches the key.
Terrain and gradient context
Elevation gained across a trip travels with the consumption figure, so a mountain leg and a motorway leg are never placed in the same column.
In the product
What this looks like in KO Fleetz
What changes
The difference it makes
- Idle, empty running, heavy pedal and mechanical drift
- Split four ways
- Stationary litres counted where the metric hid them
- Idle on its clock
- Drivers ranked only against comparable lanes and loads
- Like for like
- The talk names Tuesday's hill, not a monthly score
- Coached in-week
How you will know it worked
Measure these
We publish no savings figure for your fleet, because we have not measured your fleet. These are the metrics that will move if this works.
| Metric | How to measure it |
|---|---|
| Idle hours per vehicle per day | KO Fleetz reads engine-on stationary time from the telematics feed and groups it by site and shift. Measure it before changing anything. Most fleets are surprised by where it concentrates, and it is usually a place rather than a person. |
| Consumption spread within a peer group | The gap between best and worst litres per hundred kilometres among drivers on the same lane at similar weight. This is the coachable number. Fleet average is not, because it moves whenever the roster moves. |
| Loaded distance as a share of total distance | Kilometres run with a load divided by all kilometres run, tracked by lane and by depot. A structural empty-running problem is covered in more depth on reduce empty miles. |
| Vehicles drifting against their own baseline | Count of assets whose rolling consumption has risen against their own history with route and load held steady. Check the fuel sensor calibration before booking the bay, since drift and calibration error look identical on a chart. |
| Litres per tonne-kilometre | Fuel divided by payload multiplied by distance, where weight data exists. The fairest metric available for a fleet whose loads vary run to run, and the only one that credits a driver for carrying more. |
| Out-of-route distance against plan | Actual path length compared with the planned path for the same stop sequence. Persistent gaps usually mean the plan is wrong about road reality, not that the driver is wandering. |
Put a number on it before you talk to anyone
The fuel cost calculator is free, shows its formula, and asks nothing of you. Work out your own figure, then bring it to a demo.
Customer evidence
Fleets using KO Fleetz to do this
Customer story pending. A short, attributed quote from a fleet that used KO Fleetz for reduce fuel costs belongs here — the result, in their words.
Frequently asked questions
The boundary is simple and worth getting right, because the two problems need different people. This page covers litres that genuinely entered the engine and genuinely burned. They just did no useful work. Nobody stole anything; the fuel was wasted by idling, empty running, a heavy right foot or a mechanical fault. Prevent fuel theft covers litres that left the tank without burning at all, or that you paid for and never received. If your consumption is high but your tank curve reconciles against your purchases, you have a burn problem, and a camera at the depot gate will not fix it.
No, and any vendor telling you otherwise is selling you a number they made up. KO Fleetz identifies where fuel is being burned without producing work, and names who can change it. Idle hours at a bay get fixed by scheduling. A vehicle drifting against its own baseline gets fixed in the workshop. A driver heavier on the pedal than his peers on the same lane gets fixed by coaching, and only if the coaching actually happens. We will not quote you a saving percentage, because the honest answer depends entirely on which of those you have, how much of it, and whether anyone follows through.
Card data plus telematics distance is enough to start. It will rank vehicles, expose a genuine outlier, and support idle analysis and behaviour correlation, since those come from the telematics feed rather than the tank. What card data cannot do is tell you when within a period the fuel went, or confirm that the litres you were billed for entered the tank. If your problem is idling and empty running, sensors are not the bottleneck. If your numbers do not reconcile at all, they probably are.
Usually by agreeing with them, because in most fleets they are right. A raw fleet-wide ranking measures the route allocation, not the driver. The fix is to never compare across duty cycles: rank a driver only against others who ran a comparable corridor at comparable weight, show the peer group alongside the ranking, and report against the vehicle's own history where no peer group exists. A driver who can see why the comparison is fair will argue about the cause rather than the method, and that argument is the useful one.
Yes, and blanket idle targets are how fleets learn this the hard way. A refrigerated unit idling is holding the load at temperature. A vehicle idling in freezing conditions may be maintaining cab heat for a driver on a legally required rest, and switching that off is a welfare problem before it is a fuel one. Some equipment needs the engine running to power a hydraulic function that is the actual job. Idle analysis should be read by site and duty cycle, and productive idling should be excluded by policy rather than argued about vehicle by vehicle.
Then your cost went up and your efficiency did not change, and the platform will say so, which is more useful than it sounds. Separating volume from price is the first thing the analysis does. Litres burned per unit of work is the operational metric and it is unaffected by what you paid. Cost is that volume multiplied by a price you mostly cannot control. Fleets that conflate the two end up running a cost programme in a falling market, congratulating themselves, and discovering nothing when prices rise again.
See where your litres stop doing work
Pick one lane you run every week, and KO Fleetz will show you the spread between drivers on it, the idle hours behind it, and which of the two is worth your time.