Fuel Telemetry: Getting Data That Is Worth Acting On

Fleet fuel analytics is usually sold on the strength of the dashboard. The dashboard is straightforward. The difficulty is that fuel data arrives from several sources that disagree, and a chart built on unreconciled data produces confident conclusions that are wrong.

Three sources, three kinds of error

Fuel level sensors are inexpensive and imprecise. Readings swing with vehicle attitude, so a truck on a slope reports differently from the same truck on level ground, and sloshing during motion adds noise. Raw readings show apparent fuel gains that never happened.

Flow meters measure consumption directly and more accurately, cost more, and need calibration that drifts.

Refuelling records — from cards, site systems or manual entry — record what was purchased rather than what entered the tank, and the gap between those is exactly where fuel loss hides.

Systems using one source have an incomplete picture. Systems using several without reconciling them present contradictions to the user, which is worse.

Reconciliation is the product

The useful output is not a consumption figure but a comparison: fuel purchased versus fuel that appeared in the tank, and fuel consumed versus distance and duty cycle. Discrepancies in either are where the money is.

That requires aligning events that arrive from different systems on different clocks — a card transaction timestamped by the payment network, a level change timestamped by the telematics unit, both approximately at the same moment. Getting the tolerance right matters: too tight and legitimate refuellings never match, too loose and unrelated events pair up.

Once the alignment works, the analysis is straightforward and unusually valuable, because unmatched purchases are a well-defined thing to investigate.

Idling is usually the largest addressable loss

Engine idling consumes fuel while producing no movement, and in fleets that wait — deliveries, service vehicles, anything with loading time — it is frequently the biggest single category of avoidable consumption.

The measurement caveat is that not all idling is waste. Power take-off operation, cab heating in cold conditions, and mandated rest periods are all legitimate. A system that reports total idle time and attributes it all to driver behaviour will be rejected by drivers, correctly.

Useful measurement separates productive from unproductive idling, which requires knowing whether auxiliary equipment was running and what the ambient conditions were. That is more integration work and it is the difference between a report people act on and one they dispute.

Comparisons must be like for like

Ranking drivers or vehicles by fuel efficiency is the most requested feature and the easiest to get wrong. Consumption depends on load, terrain, weather, traffic and route far more than on driving style, so a naive league table mostly measures who was assigned the hard routes.

Comparisons need normalising for those factors, or restricting to the same route and similar conditions. Where the data is insufficient to normalise properly, the honest response is to say so rather than publish a ranking that will be — rightly — challenged and then ignored.

Emissions reporting has a different bar

Where fuel data feeds sustainability reporting, the accuracy requirements change. Internal optimisation tolerates approximation; disclosed figures do not, particularly under regimes with assurance requirements.

That means documented methodology, defined emission factors with their source and version, and an audit trail from reported figure back to source records. Fuel purchased is generally a more defensible basis than sensor-derived consumption, because it has a financial record behind it.

Worth deciding early which purpose the system serves, because a design adequate for operational insight may not survive assurance.

What makes drivers accept it

Fuel monitoring is easily perceived as surveillance, and a system drivers resent produces disputes, disengagement and occasionally interference with equipment.

What helps: showing drivers their own data rather than only reporting upward, comparing on genuinely comparable work, distinguishing legitimate idling, and being explicit about what is and is not tracked. Systems introduced as a tool for the driver are adopted; systems introduced as a check on the driver are worked around.

Electrification changes the measurement problem

Mixed fleets add a second energy system with different characteristics. Electricity consumption is measured more precisely than fuel, and it arrives from several places — depot chargers, public networks, and occasionally a driver's home supply, which raises a reimbursement question with no clean technical answer.

Comparing across the two requires deciding what you are comparing. Cost per mile is straightforward and moves with tariffs. Emissions per mile depends on grid carbon intensity, which varies by time of day and region, so a fixed factor understates the benefit of overnight charging in some markets and overstates it in others.

Worth settling the methodology before publishing comparisons, because switching it later makes your own trend data incoherent.

Integration determines whether anyone uses it

Fuel analytics that lives in its own portal gets checked occasionally. The same data delivered into the systems people already use — maintenance scheduling, route planning, driver apps, finance reporting — gets acted on.

The highest-value integrations are usually to maintenance, where a consumption change on one vehicle is an early fault signal, and to finance, where reconciled fuel spend feeds cost per mile directly. Both are more useful than another dashboard, and both need the reconciliation described above to be trustworthy first.

Where to start

Reconcile purchases against tank level before building any analytics on top. Separate productive from unproductive idling. Normalise comparisons or do not publish them. Decide whether the output is operational or reportable, because that sets the accuracy bar.

The dashboard is the last thing to build, and it will be far more useful sitting on data that has been reconciled first.