What is Fleet Intelligence?
Fleet managers have never had more data. And most of it is wrong.
Fuel economy figures from the manufacturer. Mileage from the trip computer. Carbon emissions from an HMRC spreadsheet. Driver behaviour from a black box bolted under the dashboard. Every number tells you something. Almost none of it tells you what your vehicles are actually doing.
Fleet intelligence is the discipline of replacing those estimates with real numbers — and turning those real numbers into decisions a fleet manager can act on before 9am.
What is Fleet Intelligence?
Fleet intelligence is the collection, analysis and interpretation of real-world vehicle data to support operational, financial and compliance decisions across a fleet.
It is distinct from fleet management — which covers the administrative layer of running a fleet (contracts, renewals, driver records, compliance documents) — and from telematics, which traditionally means GPS tracking and black-box event logging.
True fleet intelligence goes deeper than either. It asks not just where a vehicle went, but how efficiently it got there, what it cost, whether the driver behaved safely, whether the battery is degrading, and whether the published efficiency figure bears any relationship to reality.
The answer to that last question, for most UK fleets, is no.
Why Most Fleet Data Is Wrong
The UK fleet sector runs on three sources of vehicle data, and all three have structural problems.
Manufacturer WLTP figures are calculated under controlled laboratory conditions that bear little resemblance to real fleet usage. A plug-in hybrid claiming 287mpg assumes the battery is fully charged at the start of every journey. A diesel claiming 52mpg assumes a standardised drive cycle that no fleet driver ever replicates. These figures are not lies — they are tests. But they are the wrong tests.
Trip computer readings are estimates derived from short-term fuel consumption patterns. They fluctuate with every journey, reset with every driver, and cannot be reconciled with actual fuel purchases at scale. A fleet manager reading trip computer data across 50 vehicles is reading 50 different approximations, not 50 measurements.
Telematics black boxes capture location, speed and harsh event data — but they are a hardware layer sitting on top of the vehicle, not inside it. They do not have access to the vehicle's own fuel consumption calculations, battery state, charging history, or manufacturer diagnostic data. They see what the vehicle does from the outside. Fleet intelligence reads what the vehicle knows from the inside.
What Fleet Intelligence Actually Requires
Real fleet intelligence requires access to the data the vehicle is already generating — not an approximation of it.
Modern connected vehicles generate continuous telemetry through their onboard computers: actual fuel consumption per trip, real battery state of charge, charging session history, odometer readings, predictive maintenance alerts, driver behaviour metrics derived from the vehicle's own accelerometers rather than an external device.
This data flows through manufacturer APIs — the same systems that power the vehicle's own connected services. Accessing it directly, without hardware intermediaries, produces a fundamentally different quality of insight to anything a telematics box can provide.
According to McKinsey & Company, a modern connected vehicle generates up to 25 gigabytes of data per hour. The challenge for fleet managers has never been generating data — it has been accessing it in a form that answers the questions that actually matter.
The Four Questions Fleet Intelligence Should Answer
Not all fleet data is equally useful. The test of a fleet intelligence platform is whether it answers the four questions that drive real fleet decisions.
1. How efficiently is this vehicle actually running?
Not the WLTP figure. Not the trip computer estimate. The actual fuel consumption or energy usage, measured from the vehicle's own systems, compared against what the manufacturer's specification says it should be achieving under real-world conditions.
A vehicle returning significantly less than its benchmark efficiency is telling you something — a maintenance issue, a driving behaviour problem, or in the case of a plug-in hybrid, a charging compliance failure.
2. How safely is this driver operating the vehicle?
Harsh braking, rapid acceleration, aggressive cornering, excessive speed — these are measurable from OEM-native accelerometer and speed data. A driver behaviour score derived from these inputs tells a fleet manager which drivers need coaching, which are insurance risks, and which are doing their jobs well.
3. Is this vehicle compliant with its published specification?
For plug-in hybrids, this is the most urgent question in UK fleet management right now. A PHEV that is not being regularly charged is not producing the fuel economy or carbon emissions it is being reported against. It is consuming significantly more fuel, generating significantly more CO₂, and potentially invalidating the ESG figures in a company's SECR report.
According to the Department for Transport, approximately one third of all road fatalities in Great Britain involve someone driving for work. Fleet compliance — licence checks, MOT status, insurance verification — is the foundation of duty of care, not a bureaucratic exercise.
4. What is going to break, and when?
Predictive maintenance is the fleet intelligence use case with the clearest ROI. A vehicle that flags a battery degradation trend, a service overdue alert, or an anomalous fuel consumption pattern before it becomes a breakdown saves the fleet the cost of roadside recovery, replacement hire, and driver disruption.
Why the ZEV Mandate Makes This Urgent
The UK's Zero Emission Vehicle Mandate requires manufacturers to ensure at least 28% of new car sales are zero emission by 2026, rising to 80% by 2030. Fleet operators account for a disproportionate share of new vehicle registrations — meaning the transition pressure lands on fleet managers before it lands on private buyers.
Choosing which vehicles to replace with EVs, in which order, at what contract term, requires data most fleet operators do not have in one place: actual mileage per driver, real-world range against daily usage patterns, whole-life cost comparison between ICE and EV variants at current energy prices, and BIK modelling at lower, higher and additional rate for each vehicle.
Without fleet intelligence, EV transition decisions are guesswork dressed as strategy.
What Good Fleet Intelligence Looks Like in Practice
A VW Tiguan PHEV on a UK fleet. Published WLTP: 287.2mpg. Actual combined MPG from real telemetry: 46.9. Battery depleted 81% of the time across 799 readings over four months.
The vehicle's petrol engine is working efficiently — scoring 76 out of 100 on a real-world efficiency benchmark. But the plug-in system is contributing almost nothing, because the driver is rarely charging. The result is an ESG report that declares 30g/km CO₂ for a vehicle that is actually emitting an estimated 1.5 times that figure.
That gap — between what is reported and what is real — is what fleet intelligence exists to close.
The same vehicle has been past its service interval by over 8,000 miles. That information is available in the vehicle's own odometer data. It was not in any spreadsheet, any telematics dashboard, or any manufacturer report. It required someone to connect to the vehicle's data and ask the right question.
Fleet Intelligence vs Fleet Management Software
Fleet management software handles the administrative layer — driver records, licence checks, contract management, document storage. It is essential. It is not fleet intelligence.
Fleet intelligence is what happens when you connect the administrative layer to real vehicle data. Licence checks become meaningful when you can see that the driver's vehicle has been past its service interval for three months. Carbon reporting becomes accurate when it draws from actual fuel consumption rather than WLTP estimates. EV transition planning becomes actionable when it is based on real usage data rather than projected mileage.
The BVRLA reports that there are approximately 5 million vehicles registered to fleet operators in the UK. The vast majority are generating data continuously. Most of it is never read.
Frequently Asked Questions
What is the difference between fleet intelligence and telematics? Telematics traditionally refers to GPS tracking and black-box event logging via hardware installed in the vehicle. Fleet intelligence goes further — it accesses data from the vehicle's own manufacturer systems via OEM APIs, producing real fuel consumption, battery state, charging history and diagnostic data that a telematics box cannot see. Hardware telematics shows you what the vehicle does from the outside. Fleet intelligence reads what the vehicle knows from the inside.
What data does fleet intelligence use? Fleet intelligence platforms connect to manufacturer APIs to access odometer data, fuel consumption telemetry, battery state of charge, charging session history, driver behaviour metrics from the vehicle's own accelerometers, and predictive maintenance signals from onboard diagnostics. The best platforms also integrate DVLA licence checking, MOT and tax status, and grey fleet records.
Is fleet intelligence only for large fleets? No. The compliance obligations that fleet intelligence addresses — duty of care, SECR carbon reporting, DVLA licence checking — apply to any organisation with drivers, regardless of fleet size. A two-vehicle SME has the same legal duty of care as a corporate fleet of 500. The difference is that larger fleets have historically had the budget for dedicated fleet managers. Fleet intelligence makes the data accessible to operators of any size.
How does fleet intelligence help with ESG reporting? SECR (Streamlined Energy and Carbon Reporting) requires UK companies above certain thresholds to report actual emissions, not manufacturer estimates. Fleet intelligence platforms that pull real fuel consumption and electricity usage from vehicle APIs produce SECR-compliant Scope 1, 2 and 3 data that can be audited and defended. Reports built on WLTP figures for vehicles that are not being operated as specified cannot be.
What is OEM-native fleet intelligence? OEM-native fleet intelligence accesses vehicle data directly from manufacturer APIs — the same systems that power the vehicle's own connected services. This is distinct from third-party telematics hardware, which sits on top of the vehicle rather than inside it. OEM-native data is more accurate, requires no hardware installation, and covers the full range of vehicle sensors and diagnostics rather than the subset a black box can observe.
What to Check on Your Fleet
If you run more than five vehicles and have not looked at actual vehicle data — not trip computer readings, not WLTP figures, not telematics summaries — these are the questions worth asking:
Are your PHEV fuel economy figures based on WLTP? If so, your carbon reporting may be materially wrong.
Do you know actual MPG per vehicle? Not from the dashboard. From the vehicle's own consumption data.
Are any vehicles past their service interval? On a fleet of any size, without automated monitoring, the answer is almost certainly yes.
Do you know which drivers represent an insurance risk? Not from incident history — from driving behaviour data before an incident occurs.
Can you produce an auditable SECR carbon report from real data? If your sustainability team is using manufacturer figures, they are reporting estimates, not measurements.
The Bottom Line
Fleet intelligence is not a dashboard feature. It is not a reporting tool. It is the difference between managing a fleet on assumptions and managing it on facts.
The vehicles are already generating the data. The question is whether anyone is reading it.
Orbis IO connects directly to your vehicles via OEM-native manufacturer APIs — no hardware, no installation. We surface OES™ (efficiency), ORS™ (risk), OPCI™ (plug-in compliance) and OBI™ (battery index) scores for every connected vehicle on your fleet.
Want to see this on your fleet?
Book a 15-minute call with someone who's spent their career in fleet — not in software.
We'll show you what Orbis would surface from your vehicles on day one.