Fuel is one of those costs that looks stable until it is not. In a five vehicle fleet you can often see the problem by eye. In a 30 vehicle fleet you feel it in the monthly spend but cannot say exactly where it went. By 100 vehicles, card data alone tells you almost nothing useful. You know what was bought. You do not know whether it was used properly, whether the vehicle was fit, or whether the driver had any chance of returning a sensible mpg on the work given.
Good fuel control is not about watching a pump total creep up and having the same conversation every month. It is about linking fuel use to the real operation, vehicle, route, load, driver and maintenance history. That is where proper fleet fuel management software earns its keep.
What fleet fuel software is actually for
In a UK haulage operation, fuel software should do more than import transactions from a bunker, fuel card or supplier statement. That is the easy bit.
The real job is to show us where consumption has changed, why it has changed, and what needs doing next. That means tying fuel purchases to vehicles, mileage, movement and workshop history so we can separate normal variation from avoidable loss.
For a smaller operator, the practical uses are straightforward.
First, it should give us a reliable fuel figure by vehicle over time. Not one week in isolation, because odd jobs distort it. We need trend lines over enough mileage to mean something.
Second, it should flag exceptions. A truck that has dropped away from its normal mpg. A unit buying fuel without covering the miles. A vehicle with long idle periods. A driver whose figures are consistently poor compared with similar work.
Third, it should support control. If a card is used twice in different places within an impossible timeframe, we need to know. If diesel is being drawn against the wrong registration, we need that corrected before the month end report turns into fiction.
Fourth, it should help the maintenance side. We run a workshop-backed operation, so we see this all the time. Fuel performance often gets worse before a defect becomes obvious enough to stop a vehicle. Tyre pressures, brake drag, DPF trouble, sensor faults, alignment issues, poor service discipline, all of them can show up in fuel use if the data is clean enough.
That matters for cost, but it also matters for roadworthiness. If a defect is affecting performance, it may well be affecting reliability and compliance too. Fuel control sits closer to the O-licence world than some people think. The person answering to DVSA and, if things go badly, to the Traffic Commissioner, needs to know whether weak controls are hiding wider problems.
Where fuel costs really go wrong in a five to 100 vehicle fleet
In smaller and mid-sized fleets, fuel loss is usually boring. It is not one dramatic theft. It is a pile of ordinary operational faults that nobody joined up.
Idling is the first one. A unit sat waiting to tip, queuing at a site, parked up with PTO work, or just left running through habit can burn a surprising amount over a month. If all we see is litres bought, we miss it. If we compare movement time with engine-on time, the pattern starts to show.
Route choice is another. Drivers do not always take the same roads for the same job. Some diversions are justified. Some are not. Urban work, roadworks and customer timing all affect fuel, but so does poor planning. If the operation keeps sending the wrong vehicle on the wrong route, no amount of driver coaching will fix the number.
Driver behaviour matters, but it is often handled badly. Hard acceleration, speeding, long idle periods, poor anticipation and unnecessary detours all affect consumption. So does using cruise properly, keeping momentum where safe, and not rushing into the next brake application. The mistake is blaming the driver before checking the job. If one driver gets the town work with repeated cold starts and another gets the easy trunking, the league table is worthless.
Poor data causes as much trouble as poor driving. This is common in fleets that have grown past spreadsheets. Registrations are entered wrongly. Odometer readings are missed or estimated. A fuel card is assigned to a vehicle that was sold months ago. Agency drivers use whatever unit is free and nobody updates the allocation. Then management looks at a report and makes a decision on bad information.
Vehicle faults are a major source of creeping cost. Underinflated tyres are the obvious one. Brake drag is another, sometimes subtle enough that the driver adapts to it and says nothing until the unit comes in hot. DPF problems can push regeneration behaviour and fuel use in the wrong direction. Wheel alignment, sticking calipers, injector issues, EGR faults, air leaks that keep systems working harder than they should, all can show up as worsening fuel economy before they trigger a bigger workshop event.
Weak controls finish the job. No regular exception review. No check between mileage and fuel drawn. No process for querying odd transactions. No link between workshop defects and operating data. In that situation, costs do not jump. They creep.
What data the system needs to be useful
The best fuel report in the world is useless if the inputs are wrong or incomplete. For a five to 100 vehicle fleet, we do not need every possible data source on day one. We do need the right ones.
Fuel purchases come first. That includes fuel card transactions, on-site bunker issues, supplier invoices and any manual entries for ad hoc purchases. Each transaction needs a vehicle, date, quantity and location. If the source includes odometer entry, keep it, but do not trust it blindly.
Mileage is the second essential input. This can come from odometer readings, telematics, workshop records or tachograph-linked movement data. In practice, telematics or a reliable mileage feed is far better than relying on a driver typing numbers at the pump. If we only know litres and not distance, we are guessing.
Vehicle allocation matters more than many operators expect. We need to know which unit was actually being used, by whom, and on what work pattern. Shared vehicles are normal, but if the system cannot cope with that reality it will produce arguments, not answers.
Movement data is where the picture improves. Telematics gives us route, idle time, harsh events and engine hours. Tachograph data helps us understand duty, movement and inactivity, though it is not a direct substitute for engine data. Used together, they stop us drawing the wrong conclusion from fuel alone.
Workshop defect information should be in the same conversation. If a driver reports poor pulling power, a hot wheel end, repeated regens or a warning lamp, that needs to sit alongside the fuel trend. The same applies to PMI outcomes, brake findings, tyre replacements and service history. This is one reason we build around workshop process, not just office reports. A fuel issue often starts as a maintenance issue.
For many operators, the most useful setup is not the most complicated one. It is a system that combines fuel transactions, actual mileage, vehicle records and workshop events cleanly, then gives us exceptions we can act on. If your maintenance records are already weak, fix that at the same time. We have written before about fleet maintenance records that stand up to DVSA, because if the underlying vehicle history is a mess, fuel analysis will be as well.
How to spot the difference between waste and a mechanical problem
This is where a lot of operators either overreact or miss the point.
If one vehicle shows a sudden drop in mpg, the first question is not "which driver had it?" The first question is whether the work changed. Was it heavier. More urban. More stop-start. More queueing. Different route. PTO use. Seasonal weather. If the answer is yes, that may explain it.
If the work did not change much, look for behaviour next. Excess idle time, speeding, harsh acceleration, route variance and long stationary periods with engine running all point towards waste. That is an operational conversation.
If the behaviour does not explain it, we start thinking mechanically.
Tyres are the simple example. A gradual fall in fuel performance across a few weeks, especially after tyre work or where checks are poor, can point to pressures or alignment. The truck may still feel normal enough to the driver.
Brake drag is often more obvious in hindsight than at the time. One wheel end running hot, a slight smell, a vehicle that does not roll as freely, or fuel use worsening on a unit that otherwise does the same work. That needs workshop investigation quickly.
DPF trouble can be harder. Frequent regeneration, poor response, warning lamps or a unit spending too much time in operating conditions that do not suit passive regen can all affect fuel use. The report alone will not diagnose it, but it can tell us where to look.
Poor maintenance discipline shows up too. Missed service items, dirty filters, injector issues, air system faults and unresolved defects all have a way of appearing first as "that truck seems thirsty lately". If the vehicle is also due a preventative maintenance inspection, or has had repeated defects closed with no proper trend review, the workshop needs to get involved, not just the transport office.
This is one reason fuel control should not be divorced from the workshop. We see the consequences when fleets treat maintenance, compliance and operating cost as separate subjects. They are not. If a unit repeatedly underperforms, inspect it properly. Check tyres, brakes, fault codes, regen history, service status and driver reports. Then decide whether you have waste, a fault, or both.
What to look for before you buy
Most software demonstrations make fuel control look cleaner than real life. The question is not whether the graphs look good. It is whether the system copes with the way your fleet actually runs.
Start with reporting. Can we see fuel by vehicle over time, not just by card account. Can we compare similar vehicles. Can we spot sudden change and gradual decline. Can we filter out noise and focus on exceptions.
Then look at data accuracy. How does the system handle missing mileage, wrong registrations, duplicate transactions and swapped vehicles. If it assumes every input is correct, it will lie politely.
Ease of use matters because smaller operators do not have a data team. The transport manager, workshop controller or business owner is usually doing this alongside ten other jobs. If the system takes too many clicks to correct a bad transaction or investigate an anomaly, it will not be used properly after month one.
Exception handling is where value sits. We want a short list of things that need attention. Vehicle mpg down against trend. Fuel drawn with no matching movement. Excess idle time. Odometer mismatch. Repeated underperformance after maintenance. A report that tells us everything tells us nothing.
Fit with existing process matters more than feature count. If your operation already relies on workshop inspections, defect reporting and scheduled PMI control, the fuel side should work with that, not sit apart from it. The same goes for O-licence compliance, OCRS concerns and day to day roadworthiness management. Fuel is not a separate empire. It is one more operational signal.
For operators who are tightening up the wider picture, it is worth looking at systems that connect workshop and compliance records as well as cost data. Our operator compliance software for O-licence control exists for the same reason. The person responsible for vehicles, inspections and records usually ends up responsible for fuel drift too.
Finally, ask who the software was built by. We say this plainly because it matters. There is a difference between software designed from workshop and transport office routines, and software designed from a product brief. If the people building it understand PMI planning, defect rectification, MOT preparation and the practical mess of shared vehicles and late paperwork, the system usually shows it. If not, you end up changing your operation to suit the screen.
How to put it in without creating more admin
The mistake is trying to switch everything on at once.
For a smaller fleet, start with the minimum set that gives usable answers. Import fuel transactions. Establish a reliable mileage feed. Confirm vehicle records and current allocations. Decide who owns data correction. Usually that is one person in the office, with workshop input where defects are involved.
Then decide the review rhythm. Daily is unnecessary for most fleets unless there is an active issue. Monthly is too late if costs are drifting. Weekly exception review is a sensible starting point. That means one short review of vehicles with unusual fuel movement, poor trend performance or suspect transactions.
Ownership matters. Fuel data should not belong to nobody. In most haulage firms it sits best with the transport manager or operations lead, with the workshop manager involved where the trend points towards a defect. If the same person holds the O-licence responsibility, all the better, because they already have a reason to care about controls, records and roadworthiness.
Keep the actions simple. If a report shows excess idling, speak to the driver and check the job pattern before making accusations. If a vehicle shows worsening fuel use with no operational explanation, book an inspection. If mileage data is patchy, fix the source, not the report. If bunker and card data are both being used, make sure there is one agreed process for reconciliation.
Do not create a separate admin exercise that lives in a spreadsheet beside the software. That defeats the point. The report should lead straight to an action, driver conversation, route check, workshop inspection, card query, or no action because the cause is understood.
It also helps to tie fuel review into existing meetings and maintenance routines. If you already review defects, PMIs and workshop bookings weekly, add fuel exceptions there. If you are still trying to stop missed inspections, start by getting the maintenance side under control as well. Our piece on PMI planning that stops missed inspections covers that part, because fuel trends are much easier to trust when the basic maintenance timetable is sound.
The end goal is not more reports. It is fewer surprises. A fleet that knows which vehicles are costing too much, which issues are behavioural, which belong in the workshop, and which are just bad data, has a proper grip on fuel. That is what good fuel software is for. Not recording diesel after the money has gone, but stopping small fleet costs creeping up in the first place.
What does fleet fuel management software do?
It brings together fuel purchases, mileage and vehicle use so you can see where fuel spend does not match the work being done. The useful part is exception reporting, not just a list of transactions.
Can it reduce fuel theft?
It can help spot patterns that need checking, such as fuel bought without matching mileage or unusual fill volumes. It does not prevent theft on its own. Someone still has to review and act on the exceptions.
Do small fleets need telematics for fuel control?
Not always. A smaller fleet can get value from fuel card data and accurate mileage first. Telematics adds context, but poor vehicle allocation and weak odometer records will still undermine the result.
Can fuel software help with maintenance?
Yes. A sudden drop in mpg can point to tyre issues, brake drag, injector problems or other faults. It is a prompt to investigate, not a diagnosis by itself.
Is fuel management software part of O-licence compliance?
No. It is not a compliance system in itself. But better fuel visibility can support roadworthiness by helping you spot vehicle issues earlier and manage the fleet more closely.
