The ZEV Mandate Just Got Real, What Fleet Operators Need to Track in 2026

One in three new cars registered in the UK this year must be zero emission. One in four vans. Those are not projections — they are the 2026 ZEV mandate targets, and they are already shaping what vehicles your fleet has access to.

The mandate applies to manufacturers, not directly to fleet operators. But the downstream effects hit your procurement, your total cost of ownership calculations, and your compliance reporting whether you are ready for them or not.

Here is what is actually changing — and what you need to be tracking.

The numbers that matter

The ZEV mandate requires 33% of a manufacturer's new car registrations and 24% of van registrations to be zero emission in 2026. Manufacturers who fall short face a non-compliance payment of £12,000 per car and £15,000 per van. They can also trade credits, borrow against future targets, or pool allowances with other manufacturers to stay compliant.

What this means in practice: manufacturers are prioritising EV production and allocation. ICE model availability is tightening. If your fleet renewal cycle assumes the same petrol or diesel options will be there next quarter, that assumption needs testing.

The procurement squeeze

Fleet buyers renewing leases in 2026 are already seeing fewer ICE choices. Manufacturers are steering allocation towards zero-emission models to hit their targets. Lead times on popular diesel vans are stretching. Some models are being quietly discontinued.

This is not a future problem. It is a this-quarter problem for anyone managing a renewal pipeline.

What fleet operators should be tracking now

The mandate does not require you to report anything directly. But if you are not measuring the following, you are making decisions blind.

Your current fleet mix — what percentage of your vehicles are BEV, PHEV, and ICE? How does that compare to six months ago? What does your renewal schedule look like over the next 12 months?

Real-world energy costs — not the WLTP figures, but what your drivers are actually spending. Home charging at 7p per kWh looks very different from rapid charging at 79p. If you are reimbursing drivers for electricity, are you doing it based on real consumption or estimates?

Total cost of ownership by powertrain — an EV might be cheaper on fuel and road tax, but what about depreciation, insurance, and charging infrastructure? The calculation only works if the inputs are real, not assumed.

Battery health across your EV fleet — degradation is not linear and it varies by chemistry, usage pattern, and charging behaviour. A vehicle with 78% state of health has a very different residual value to one at 92%. If you are not tracking this, your defleet planning is guesswork.

Driver charging behaviour — are your PHEV drivers actually charging, or are they running on petrol? The OPCI™ (Orbis Plug-in Compliance Index) exists precisely because this is one of the most common and costly blind spots in mixed fleets.

The compliance reporting angle

Even though the ZEV mandate targets manufacturers, fleet operators face their own reporting obligations. SECR (Streamlined Energy and Carbon Reporting) requires qualifying companies to report Scope 1 and 2 emissions annually. ESOS (Energy Savings Opportunity Scheme) audits are tightening. And for any fleet tendering public sector contracts, carbon credentials are increasingly part of the scoring.

If your emissions data is still coming from a spreadsheet that someone updates quarterly, you are already behind.

What this means for your fleet strategy

The ZEV mandate is not something that happens to manufacturers while fleet operators watch from the sidelines. It reshapes the vehicles available to you, the economics of running them, and the data you need to manage them properly.

The fleets that navigate this well will be the ones that track real consumption against WLTP claims, monitor battery health as a financial metric, understand their actual charging costs, and report emissions from live data rather than estimates.

That is exactly what we built Orbis to do.

Next
Next

Why we built Orbis