FleetOptix

Sign in
← All posts
Operations24 February 2026 · 5 min read

The KPIs a transport manager should actually track

It's tempting to track activity — miles covered, deliveries completed — but those don't say much about whether a fleet is actually compliant. The more useful KPIs tend to be leading indicators of a risk before it becomes a roadside stop or an audit finding.

What's actually worth watching

  • Driver CPC and licence checks due in the next 30 days across every depot
  • Recent tachograph infringements, and whether they're trending down or recurring with the same drivers
  • Vehicles with outstanding defects from daily checks, and how long they've been outstanding
  • OCRS risk trend over time, not just the current score in isolation

The thread connecting these: they need to be visible without a transport manager having to actively dig for them, and they need to work across every depot the fleet operates from, not just the one the manager happens to be sitting in that day.

Leading indicators versus lagging indicators

It's worth being explicit about the distinction. A lagging indicator tells you something already happened — a prohibition notice issued, a public inquiry called, a driver disqualified. Useful to know, but by the time it exists the risk has already materialised. A leading indicator tells you something is trending toward a problem before it becomes one — a defect that's stayed open three days longer than usual, a driver whose infringement count has ticked up over the last month, an operating centre approaching the vehicle capacity it was approved for. Most transport managers already have the lagging indicators covered, because those are the things that force attention on their own. The leading ones are the ones that need a deliberate system to surface, because nothing forces them into view otherwise.

Driver-level versus fleet-level KPIs

It's useful to separate KPIs that describe an individual driver's risk from those that describe the fleet as a whole. Driver-level indicators — endorsement trend, infringement frequency, upcoming CPC and licence renewal — flag which specific people need attention. Fleet-level indicators — OCRS trend, aggregate outstanding defects, depot-by-depot compliance comparisons — flag whether the operation as a whole is drifting in the wrong direction, sometimes in ways that aren't obvious from any single driver's record. A fleet can have every individual driver looking fine on paper while the aggregate trend across the whole roster is quietly worsening month over month; that's only visible if someone's actually looking at the fleet-level number, not just the individual ones.

How often these should actually be reviewed

A KPI that's only reviewed monthly is, in effect, a lagging indicator with extra steps — by the time a monthly review catches a trend, a month's worth of risk has already accumulated. The more useful cadence is closer to weekly for anything genuinely operational (outstanding defects, upcoming renewals in the next 30 days), with a monthly or quarterly step back for the slower-moving trend indicators like OCRS. What matters more than the exact frequency is that the review actually happens on a fixed schedule rather than only when something prompts it — a KPI dashboard nobody looks at until after an incident isn't really functioning as a leading indicator at all.

Benchmarking against the fleet's own history, not an external average

Without a reliable external benchmark to compare against, the most useful reference point for most of these KPIs is the fleet's own historical trend rather than some assumed industry norm — is this month's outstanding-defect count better or worse than the same point last quarter, is the infringement rate per driver trending in the right direction compared to six months ago. That internal comparison is more actionable than chasing an external figure that may not be genuinely comparable across different fleet sizes, vehicle types and operating patterns anyway.

Reporting KPIs upward, to ownership or the board

The KPIs a transport manager needs day to day aren't quite the same as what's useful to report upward to business owners or a board — the operational detail (which specific vehicle has which defect) matters less at that level than the trend (is the fleet's outstanding-defect count rising or falling; is OCRS moving in the right direction; are CPC and licence renewals consistently handled ahead of deadline or is there a recurring pattern of near-misses). Translating operational KPIs into a small number of trend-level summaries for non-specialist stakeholders is worth doing deliberately, both because it keeps compliance visible above transport-manager level, and because it forces the transport manager to actually articulate the trend rather than only ever looking at the current snapshot.

Avoiding KPIs that quietly encourage the wrong behaviour

A poorly chosen KPI can actively distort behaviour rather than just fail to help — a target based purely on "defects closed this week," for instance, can inadvertently reward closing defects quickly over closing them properly, if there's pressure to hit the number. The KPIs worth tracking are ones that reward the underlying behaviour actually wanted (defects genuinely resolved and verified, licence checks done thoroughly, not just completed on schedule) rather than a proxy that's easy to game under pressure. Reviewing not just what a KPI measures, but what behaviour it incentivises if someone's under pressure to hit it, is worth doing before rolling any new metric out fleet-wide.

  • A depot's outstanding defect count creeps up gradually over several weeks with no one noticing until a vehicle fails at annual test
  • One driver's infringement pattern worsens steadily over two months, invisible unless someone compares this month to last
  • Fleet-wide OCRS trend is quietly worsening even though no individual driver or vehicle looks obviously problematic on its own
  • A KPI dashboard exists but is only opened after something has already gone wrong, rather than reviewed on a fixed schedule

Key takeaways

  • Track leading indicators — upcoming CPC/licence checks, infringement trends, outstanding defects, OCRS trend — not just activity volume.
  • Leading indicators need a deliberate system to surface them; lagging indicators tend to force attention on their own.
  • Separate driver-level KPIs (individual risk) from fleet-level KPIs (aggregate trend) — a fleet can drift while every individual driver looks fine.
  • Review operational KPIs on something close to a weekly cadence, not just monthly or after an incident prompts it.
  • A risk that isn't visible is still a risk, whether or not anyone's noticed it yet.
  • KPIs need to work across every depot in the fleet, not just wherever the manager is currently based.

The FleetOptix team

Written by people who work daily with fleet operators on drivers' hours, tachograph records and the paperwork that holds up under a DVSA inspection.