HGV idle & route inefficiency
~14% of HGV fuel burned at idle or in unnecessary repositioning. Visible per-vehicle once telematics fed the tool.
Flannery Plant Hire — Europe's largest plant hire firm — runs 12 sites, 230 light vehicles and 45 HGVs from a Wembley head office. Three overlapping reporting regimes, three different consultants, three sets of numbers. KEES replaced the lot with one Energy & Carbon Management Tool — feeding ESOS, SECR and the Construction Reporting Protocol from a single source of measured data.
Cost reduction identified across head office, sites and the diesel fleet.
Annual energy reduction available from prioritised actions across all 12 sites.
Equivalent carbon reduction — verified against actual fuel and grid factors, not estimates.
Flannery had three compliance regimes and three numbers — and none of them matched.
ESOS, SECR and the Construction Reporting Protocol all want similar data, but cut differently. Flannery's reports were being assembled by separate consultants from spreadsheets that had drifted apart over the years — fuel cards in one place, electricity bills in another, telematics nowhere near either.
The brief: stop estimating. Get every kWh, every litre, every mile under one roof, once, and let the regimes draw from the same well.
The complication: a fleet that does most of the work. 230 light vehicles, 45 HGVs and a yard full of plant — Scope 1 dominates. Without proper telematics integration, fleet is the place every plant hire ESOS report quietly fudges.
Per-vehicle litres & idle time pulled monthly. No more 'average mpg × bills' — actual emissions, per asset.
Half-hour DNO data on every yard meter, replacing supplier-estimated reads that drifted year-to-year.
The same database now exports SECR boundary, ESOS audit ledger and CRP project rollups — automatically.
~14% of HGV fuel burned at idle or in unnecessary repositioning. Visible per-vehicle once telematics fed the tool.
On-site fuel was being booked to whichever site placed the order, not the one running the machine. Project carbon was off.
A subset of the LCV fleet was over-spec for typical load. Replacement cycle now staged against route data, not category.
Out-of-hours yard load was 45% of operational — security lighting and welfare cabins on 24/7 unnecessarily.
Wembley HQ BMS had drifted out of schedule. Recommissioning gave back 12% of HQ gas — the easiest win on the list.
ESOS audit, SECR ledger and CRP project carbon now run from one ECMT instance. No re-keying, no estimate drift.
We didn't start with the report — we started with the data. Once everyone agrees on the numbers, the reports almost write themselves and the savings stop being theoretical.
Fuel cards, telematics platforms, DNO meters, supplier portals, BMS exports. Twelve sites, three platforms — none of them talking to each other.
Single consolidated database with monthly automated pulls. Per-asset, per-site, per-project — granular enough to support any of the regimes.
Every measured value cross-checked against invoiced fuel and metered electricity. Variance < 1.5% — within audit tolerance.
ESOS audit ledger, SECR boundary, CRP project carbon — three exports, one underlying dataset. No more arguments about whose number is right.
The tool is Flannery's, not ours. We ran a four-week handover with the SHEQ team — they own the monthly cycle now.
Before KEES, we had three teams reporting three different numbers, and I couldn't tell you which was right. Now it's one tool, one team, one number — and we use it to actually run the business, not just survive the audit.
If your fleet, sites and reports are pulling from different spreadsheets, you're not alone. Tell us your set-up — we'll be honest about whether one tool can replace your three.