How to Reduce Fuel Consumption in UK Fleets

The fuel card invoice lands before the monthly transport review, and the numbers rarely line up neatly. Finance sees litres and cost. Operations sees tachograph records, mileage, delivery schedules and workshop notes. Drivers know where engines sit running at depots, queues and customer sites, but that knowledge often stays informal.

That gap makes it difficult to answer a basic question with confidence: how to reduce fuel consumption without damaging service reliability or operator-licence discipline. The practical answer isn't a single dashboard or a blanket driver rule. It's a controlled process that connects fuel purchases, actual vehicle activity, route conditions, maintenance, driver coaching and compliance evidence.

Road transport is the dominant oil user in the UK. Government evidence found that more than half of all oil was consumed for road transport in 2018, equal to just over 36 million tonnes, while the UK motor vehicle fleet had grown to 39.4 million vehicles by that year, more than a quarter higher than at the end of 2001. (UK government review of road fuel consumption and the vehicle fleet) For a mixed HGV and LCV operation, small waste points matter because they repeat across a large vehicle parc.

Table of Contents

• Why Fuel Spend Is the Hardest Number to Control in a UK Fleet
  • Build the evidence before changing behaviour
• Measuring an Accurate Baseline with CAN, FMS and Telematics Data
• Cutting Idling and Harsh Driving Without Slowing Deliveries
  • Set rules around the work
• Planning Routes, Loads and Depots Around Fuel Efficiency
  • Match the plan to the vehicle
• Maintenance, Tyres and Vehicle Spec That Quietly Save Fuel
  • Start with tyres and rolling resistance
  • Protect the driveline and aerodynamics
  • Make coaching beat dashboard theatre
• Connecting Dashcams, GPS and Analytics into One Workflow
  • Turn alerts into assigned work
• KPIs, Reporting and the ROI Case for the Board
  • Report three views, not one score

Why Fuel Spend Is the Hardest Number to Control in a UK Fleet

A fuel card report tells you what was bought. It doesn't tell you whether the litres went into the right vehicle, whether the vehicle covered the recorded mileage, or whether the engine spent an avoidable period running while stationary. A tachograph records driving activity and other duties, but it doesn't reconcile the fuel transaction. Mileage sheets may arrive late, and workshop records often sit in a separate system.

The result is a reconciliation gap. Split tanker deliveries, separate HGV and LCV billing cycles, AdBlue cross-charging and regional pump price differences can all distort the apparent cost per mile. Operator-licence evidence adds another layer because the records used for compliance aren't always organised around the same vehicle, route and accounting period used by finance.

Build the evidence before changing behaviour

Start with four controls:

1. Reconcile the fuel source. Match fuel-card transactions to registration, date, litres, fuel type and odometer where available. Investigate missing, duplicated or implausible transactions rather than smoothing them into an average.
2. Define the fleet boundary. Decide whether the baseline includes owned vehicles, leased vehicles, trailers, pool vans, subcontracted work or only vehicles operating under your operator licence.
3. Set a baseline period. Use at least 90 days so the comparison includes different routes, payloads, weather conditions and operating patterns. This is a planning rule for a defensible baseline, not a claim about a published performance result.
4. Name the KPI owner. One person should own the definition, data quality, review frequency and action log. Shared responsibility often becomes nobody's responsibility.

The government's sub-national methodology uses traffic activity, vehicle licensing, MOT mileage, fleet composition and fuel-consumption factors. It also uses traffic census information, fleet-turnover modelling, vehicle-kilometre data and ANPR information to estimate activity by fuel type and Euro standard. (UK methodology for sub-national road-transport fuel statistics) Your fleet doesn't need to replicate the national model, but it should follow the same principle: measure activity, vehicle mix and fuel use together.

Driver tips still have a place, particularly for private or light-commercial driving. A useful plain-English resource is these tips for cutting fuel costs, but HGV operators must add route, load, duty-time and compliance controls. Fuel is therefore a compliance-adjacent cost, not just a procurement line.

Measuring an Accurate Baseline with CAN, FMS and Telematics Data

A fleet baseline is only useful if it connects fuel to the work completed. For each vehicle, record fuel consumed, distance travelled, payload or job type, and the operating conditions that affected the result. Fuel-card litres answer only part of the question. They can also mislead when a driver fuels a replacement vehicle or a transaction is assigned to the wrong registration.

Start with vehicle identity and data ownership. Match fuel-card records, registration numbers, odometer readings and telematics devices before calculating MPG or litres per distance. Keep the raw records behind each figure, because finance, the transport manager and an operator-licence auditor may all challenge the definition or source.

On newer HGVs, CAN data may provide fuel rate, engine status, odometer information and selected diagnostic signals, depending on the vehicle and interface. FMS data gives a more standardised fleet output, although available parameters and data quality still depend on the vehicle, installation and configuration. LCVs vary more widely. An OBD-derived signal or aftermarket sensor may need checking against fuel purchases, known mileage and workshop records.

Use one reconciliation process for the mixed fleet. Telematics mileage should align with fuel-card activity, while missing transactions, duplicate fills, incorrect fuel types and vehicle substitutions should be flagged rather than averaged. API connections keep records current, but automation cannot correct poor identifiers or inconsistent operating definitions.

A useful review asks four questions:

• Which vehicle, route or job consumed the fuel?
• Was the distance measured consistently across HGVs and LCVs?
• What operational factor explains an unusual result, such as payload, refrigeration, PTO use, traffic or depot work?
• Is the exception a genuine performance issue or a data-quality problem?

Normalise comparisons before ranking drivers or vehicles. A loaded HGV on trunk work should not be compared directly with an urban multi-drop van, and a refrigerated vehicle needs its equipment use recorded. The same applies to construction vehicles using PTO equipment. Without those tags, a league table can reward the wrong behaviour or prompt coaching where the vehicle was doing its assigned work.

The baseline should also identify what the figures cannot show. A fuel result may deteriorate because of tyre condition, servicing, route changes, low utilisation or inaccurate mileage. Record maintenance events and operational changes alongside consumption, so later reviews can separate behaviour from vehicle or planning causes.

A guide to HGV fuel efficiency monitoring can help configure the telematics fields, but supplier documentation still needs checking against each vehicle. Do not begin driver coaching until the baseline survives a basic challenge from finance, operations and compliance. Consistent definitions make fuel control support operator-licence discipline rather than compete with it.

Cutting Idling and Harsh Driving Without Slowing Deliveries

A flat five-minute idling rule looks simple, but mixed fleets don't operate in simple conditions. A refrigerated HGV, a construction tipper and an urban multi-drop LCV have different operational requirements. The right threshold depends on whether the engine is powering refrigeration, PTO equipment, safety systems, loading processes or nothing productive at all.

Set the rule around engine-running stationary time, not total stationary time. Transport Scotland's case study used telematics to make that distinction, which prevented manual estimates from confusing a parked vehicle with a parked vehicle burning fuel.

Set rules around the work

At a depot, agree when drivers should switch off during loading and what exceptions apply. For refrigerated work, record the conditions that require the unit to run. For tippers and tail-lift operations, distinguish PTO operation from unnecessary engine running. For urban vans, identify customer queues and delivery windows where a controlled engine-off policy won't compromise safety or service.

Harsh-event scoring needs context too. A braking event on a steep approach, a loaded vehicle descending a gradient or a driver avoiding a hazard shouldn't receive the same interpretation as repeated acceleration and braking on a clear route. Review the event against road type, gradient, load, traffic and video evidence before coaching.

A useful driver conversation sounds operational rather than accusatory:

Practical rule: Ask what task the engine was supporting before deciding that the event was waste.

Report patterns weekly to the transport team, then use monthly one-to-ones for persistent issues. Focus on a vehicle's trend, route and circumstances instead of publishing a league table that encourages drivers to hide difficult work or chase an artificial score.

The benchmark cited by Fleet News, using TRL data, says an HGV can consume up to 21.7 grams of diesel per minute while idling, equivalent to about 3 pence per minute in fuel cost. The same article reports 10 to 15% fuel savings from telematics-backed driver-behaviour monitoring paired with training, with some fleets achieving up to 20%. (Fleet News on idling and behaviour monitoring)

Use the fuel-efficient driving guidance to give drivers a consistent reference, but tailor the coaching to the actual work. A driver shouldn't be asked to sacrifice delivery performance for a score that ignores customer access, load security or legal duty limits.

Planning Routes, Loads and Depots Around Fuel Efficiency

A route can look efficient on a screen and still burn fuel through waiting, backtracking and unsuitable vehicle assignment. A multi-drop round in an urban centre has different constraints from a motorway trunk between depots or a rural consolidation run. Review GPS traces by route class, then connect the findings to operator-licence discipline, driver hours and vehicle suitability rather than relying on one fleet-wide average.

Start with completed journeys. Flag repeated backtracking, unnecessary yard movements, queues outside delivery sites, poor stop sequencing and empty returns. Test each proposed change against customer time windows, driver hours, vehicle dimensions, weight restrictions and dependable access. A shorter route that creates an illegal parking problem or leaves a driver without enough duty time is not an efficient route.

Match the plan to the vehicle

Vehicle assignment changes the result. A rigid HGV may suit one delivery pattern, while an LCV can reach a dense urban cluster without the access restrictions and waiting associated with a larger vehicle.

• Urban multi-drop: sequence stops to limit backtracking and waiting while protecting delivery windows.
• Motorway trunking: use stable schedules and suitable vehicles, then investigate diversions and unplanned stops.
• Rural consolidation: combine compatible drops only when the load and duty plan remain workable.

Load utilisation needs the same scrutiny. A vehicle may be cube-out without being weight-out, or weight-out while carrying unused volume. Review backhauls, delivery density and dropside or tail-lift sequencing. A half-empty van covering a long distance carries a fuel penalty that routing software cannot remove.

Depot decisions affect fuel and compliance together. Time gate-in and loading to reduce queues, separate productive PTO use from yard manoeuvring, and assess whether a micro-hub or cross-dock would cut repeated deadhead travel. Compare actual mileage, waiting, handling time, customer service and operator-licence impact before changing the layout.

Use route-planning software for fleet operations to compare scenarios, while keeping the transport planner responsible for constraints the system may not interpret reliably. The workable route reduces wasted mileage without compromising the delivery promise, vehicle limits or duty plan.

Maintenance, Tyres and Vehicle Spec That Quietly Save Fuel

Driver coaching gets attention because it produces visible conversations. Vehicle condition often produces quieter gains, and it can prevent a good driver from being penalised for a mechanical problem. A vehicle with poor tyres, a dragging brake, a faulted emissions system or incorrect alignment can appear to have a behaviour problem when the cause sits in the workshop.

Start with tyres and rolling resistance

Tyre pressure should be checked against the correct cold-inflation specification, with particular attention to twin rear axles and vehicles that move between different payloads. A pressure check needs an owner, a recorded result and an escalation route. Telling drivers to “check their tyres” without giving them a reliable gauge, timing and defect process produces inconsistent evidence.

For vehicles spending most of their time on motorways, low-rolling-resistance tyres may deserve consideration at replacement. That decision must include wet grip, mileage, axle position, retread policy, operating environment and total cost, not just the label on the tyre. A tyre that performs poorly on a mixed urban and construction route can create safety, wear and downtime problems that outweigh a theoretical fuel benefit.

Wheel alignment and uneven wear deserve the same attention. Compare tyre patterns with fuel trends and defect records. If one vehicle's consumption deteriorates after a suspension or kerb-impact issue, send it for inspection before blaming the driver.

Protect the driveline and aerodynamics

Aerodynamic equipment only works when it's correctly fitted and used. Check roof deflector alignment against trailer height, inspect side skirts, and make sure gaps or damage aren't undermining the intended airflow. Doors and curtains need to close properly. An open back door creates unnecessary aerodynamic drag, so door checks belong in the loading and defect routine rather than in a fuel presentation.

AdBlue and emissions-system faults need prompt handling. A dosing fault, DPF issue, EGR problem or injector imbalance can affect vehicle performance and trigger operational disruption. Telematics diagnostics can help identify the vehicle and timing, but the workshop must confirm the cause and record the repair.

Scheduled maintenance should connect service events to fuel trends. Review:

• Engine systems: EGR, DPF, injectors, filters and oil condition.
• Running gear: wheel alignment, brakes, hubs and suspension.
• Body and equipment: deflectors, skirts, tail-lifts, refrigeration and PTO systems.
• Data quality: odometer, CAN, FMS and fuel-sensor plausibility after repairs or electrical work.

Don't buy more hardware while a known mechanical fault remains unresolved. In a constrained budget, tyre condition and DPF health usually deserve attention before adding another dashboard.

Make coaching beat dashboard theatre

A dashboard can show a poor score. It rarely explains the moment that produced it or gives a driver a credible way to improve. Fleet News' benchmark associates telematics monitoring with training, reporting 10 to 15% fuel savings, with some fleets achieving up to 20%, when the two are used together. (The Fleet News benchmark on telematics and driver training) Treat that as a benchmark for programme design, not a guaranteed outcome.

Coach anticipation, gear selection, steady motorway cruising, rolling approaches where safe and engine-off behaviour during avoidable stops. Don't prescribe a single speed band as a legal or universal rule. A driver must remain within posted limits, road conditions, vehicle capability and the operator's procedures.

Use forward-facing dashcam footage in monthly one-to-ones. Select a small number of scored events, explain the context, agree one behaviour change and review it later. League tables can damage trust, especially when drivers receive the hardest routes. Reward sustained improvement instead, using options such as vouchers, route-baselined MPG recognition or relevant Driver CPC learning time, subject to company policy and employment arrangements.

Operator-licence discipline should sit inside the same workflow. Tachograph downloads, driver-hours review, maintenance records and defect follow-up demonstrate control of the operation. Coaching that reduces unnecessary speeding, harsh events and rushed dispatch can support safety and compliance, but it must never encourage a driver to extend a duty, skip a break or compromise a defect report.

The UK's energy reporting continues to identify transport as a major national energy user, which reinforces the scale of the operational issue, but it doesn't tell an individual fleet which vehicle to change first. (UK Energy in Brief 2025) That decision belongs in the vehicle-level evidence.

Connecting Dashcams, GPS and Analytics into One Workflow

A mixed HGV and LCV fleet rarely gives you one clean data feed. Newer HGVs may offer an appropriate FMS or CAN connection, while LCVs may require OBD-II or another vehicle-specific interface. Older HGVs can need a third-party FMS gateway or a connection behind the tachograph.

The installation brief should therefore include data validation. Confirm the vehicle registration, asset ID, fuel type, odometer source, ignition status and driver association before the first report. Then compare recorded journeys with known depot departures and fuel transactions. A device can be online and still produce a worthless baseline if the wrong odometer or fuel signal is mapped.

Dashcam footage, GPS and vehicle data answer different questions. AI-enabled dashcams should send selected events into a scorecard workflow, rather than leaving managers to watch hours of video. GPS adds journey and location context. CAN or FMS contributes vehicle activity and selected diagnostics. Combined, these sources can show whether harsh braking occurred on a congested urban approach, whether an idle alert was linked to PTO use, or whether a fuel anomaly followed workshop work.

Operator-licence discipline belongs in the same workflow. Tachograph evidence, driver-hours review, maintenance records and defect follow-up should be available alongside operational alerts, with access controlled by role. Fuel saving must not encourage a driver to extend a duty, miss a break or suppress a defect.

Turn alerts into assigned work

Use a rule that ends with an action, not just a notification:

1. Detect engine-on stationary time beyond the vehicle's agreed operational threshold.
2. Attach the vehicle, driver, location, route and time window.
3. Send the alert to the responsible transport manager.
4. Add it to a weekly pattern report.
5. Create a coaching or maintenance action when the pattern continues.

Set GPS sampling around the question being answered. High-frequency location data can help reconstruct a complex route, while lower-frequency reporting may cover basic asset visibility. Balance accuracy, network coverage, battery demand and SIM costs instead of selecting the highest setting by default.

Access controls should cover mapping, route, compliance and driver records. Footage and location data need a defined purpose, retention policy, permissions and clear communication with staff. GDPR handling, driver consultation and the operator-licence process for tachograph and maintenance evidence should be agreed before deployment.

For a broader explanation of structuring analytics work, see this practitioner's guide to analytics. An API-first platform can then pass approved data into payroll, maintenance, transport planning and board reporting, rather than keeping it inside a supplier portal.

Fleetalyse is one UK option combining GPS tracking, remote tachograph downloads, smart dashcams, driver-behaviour monitoring and CAN or FMS integration for commercial fleets. Assess any platform by what happens after an alert: assigned coaching, a maintenance task, documented evidence or a compliance review.

KPIs, Reporting and the ROI Case for the Board

A board pack should make fuel performance actionable. Report litres per 100 kilometres or MPG by vehicle class, idle percentage, harsh-event rate per 10,000 kilometres, route adherence, and CO2 per tonne-kilometre where payload records are reliable. Pair each measure with an owner, a review frequency and the action it is meant to trigger.

Use the first 90 days to establish a reconciled baseline. Set targets against the benchmark cited earlier in this article, rather than promising a fixed result. Where behaviour and idling losses are clearly controllable, an initial reduction within the cited 10 to 15% range may be a reasonable planning assumption, with a separate review for operations that might approach the cited 20% upper benchmark. (Fleet News benchmark) Adjust the target for vehicle replacement, route changes, payload, fuel type and exceptional work.

Report three views, not one score

The transport manager needs a weekly exception view. Show vehicles with rising idle time, repeated harsh events, fuel-card mismatches, route deviations and overdue maintenance. Each exception should have an owner and due date, so the report supports action rather than becoming another dashboard.

The compliance lead needs a control view covering tachograph downloads, driver-hours risks, defect actions and evidence retention. That links fuel-efficiency work to operator-licence discipline. A reduction in fuel use does not justify missed downloads, unmanaged defects or pressure on drivers to compromise legal hours.

The board needs a one-page summary:

• Cost: fuel spend, consumption trend and variance by vehicle class.
• Operations: mileage, utilisation, route adherence and service exceptions.
• People: coaching completed, repeat events and driver engagement.
• Risk: unresolved defects, speeding patterns, missing records and corrective actions.
• Investment: programme cost, realised fuel reduction and forecast payback.

Keep the ROI model transparent. Do not hide assumptions inside a headline saving.

The board will ask whether the saving came from fewer miles, cheaper fuel, route mix or genuine efficiency. It will also ask whether service levels changed, whether drivers were treated fairly, and whether compliance exposure increased. Answer with a vehicle-level audit trail, sensitivity analysis and a 90-day action plan. Separate controllable efficiency gains from changes caused by work mix or fleet composition.

Days one to thirty should clean identifiers, reconcile transactions and establish ownership. Days thirty-one to sixty should coach the worst controllable patterns and fix obvious maintenance or depot issues. Days sixty-one to ninety should compare like-for-like routes, confirm whether the change held, and approve the next intervention from the evidence.

A fleet that can explain its fuel number can manage it. Connecting that number to driver hours, vehicle condition, delivery performance and documented corrective actions supports lower cost without weakening operational control.

Fleetalyse can connect GPS tracking, remote tachograph downloads, dashcams, behaviour monitoring and fuel or mileage data into a practical workflow for mixed UK fleets. Visit Fleetalyse to review the available fleet-management tools and start building a reconciled fuel baseline.