Two years ago, fleet emissions reporting was something most UK operators thought of as a large-company problem -- something the listed businesses and the government fleet worried about. That framing is no longer accurate. The regulatory scope is widening, customer contract requirements are increasingly including Scope 3 data, and operators who don't have a clean emissions data trail are starting to lose business to those who do.
Streamlined Energy and Carbon Reporting (SECR) has applied to large UK companies since 2019. If your fleet business is a quoted company, or a large unquoted company (500+ employees, turnover over £500m, or balance sheet over £500m), you're already required to include energy use, carbon emissions, and an intensity ratio in your annual report.
For fleet operators, SECR covers Scope 1 emissions -- direct combustion from your owned and operated vehicles. It also requires disclosure of energy efficiency actions taken during the year. The data requirement for SECR compliance is, at minimum, total fuel consumption by fuel type and total miles driven, from which carbon emissions can be calculated using DEFRA's published conversion factors.
What SECR doesn't do is require you to report accurately. You can comply with SECR using estimated data and you'll still be technically compliant. The problem is that TCFD (Task Force on Climate-related Financial Disclosures) reporting -- now mandatory for listed companies and large private companies -- takes a harder line on data quality. TCFD reporters are expected to describe the processes behind their emissions figures, and "we estimated from fuel card totals" is a disclosure that will attract scrutiny from analysts and ESG rating agencies.
Scope 1 is your own fleet. Scope 3 is everything else -- and for many businesses, the fleet is a Scope 3 item on someone else's books. If you operate contracted logistics services for a major retailer, that retailer's sustainability reporting team will eventually ask you for the emissions associated with their contracts. If you can't provide it, they'll either estimate it (at a higher factor than your actual figure) or find an operator who can provide it.
We're already seeing this in procurement cycles. Logistics contracts increasingly include a data schedule alongside the commercial terms, specifying what emissions data the operator must provide, at what frequency, and in what format. Operators who can meet those requirements -- with actual per-route, per-vehicle figures -- are winning contracts that operators relying on estimates are losing.
| Reporting Framework | Who It Applies To | Fleet Data Required |
|---|---|---|
| SECR | Large UK companies (quoted + qualifying unquoted) | Total fuel use, total miles, Scope 1 CO2e |
| TCFD | Listed companies, large LLPs, large private companies | Emissions data with quality narrative, intensity ratio |
| Contract Scope 3 | Any logistics operator with sustainability-active customers | Per-route or per-contract emissions, actuals preferred |
| Net Zero Commitments | Self-declared, but increasingly stakeholder-scrutinised | Baseline year data, annual progress, methodology |
Most fleet operators calculate their CO2 emissions by applying DEFRA's greenhouse gas conversion factors to their fuel consumption data. This is the accepted methodology and it works -- when the underlying consumption data is accurate. When it isn't, the emissions figure inherits the same errors.
DEFRA updates its conversion factors annually. The fuel consumption data going in is only as good as what your fleet management system actually captures. If you have 15% data gaps -- vehicles without telematics, manual fuel card reconciliation errors, missing charging events for EVs -- your emissions figure is 15% unreliable. That matters more when the figure goes in a statutory report than when it stays in a spreadsheet.
The practical steps to get to a defensible emissions reporting position aren't complicated, but they do require committing to data quality as an operational priority rather than a reporting-time exercise.
"The operators who get ahead of CO2 reporting requirements don't wait for a contract requirement or a regulatory deadline. They build the data trail before they need to defend it." — ExoFleets Team
The direction of travel is clear. Reporting requirements will broaden, data quality expectations will rise, and the cost of not having reliable emissions data will shift from reputational to financial. The operators who've invested in the data infrastructure now will find compliance increasingly routine. Those who haven't will be catching up under deadline pressure.
The good news is that the data you need for robust CO2 reporting is largely the same data you need for good TCO management. It's not a parallel project -- it's a consequence of having a properly integrated fleet data model.
ExoFleets includes built-in CO2 reporting with DEFRA conversion factor integration. Request a demo to see how our emissions reporting module works in practice.
