The fleet KPIs that actually matter
Telematics platforms can chart almost anything, which is exactly the problem. These are the ten metrics worth a weekly meeting — and the vanity numbers worth ignoring.
The average telematics dashboard can render dozens of metrics, and the average fleet manager looks at three of them, irregularly. The fix is not more dashboards — it is a deliberately short list of KPIs, each with an owner, a target, and a review cadence. The fleets that improve year over year typically run on eight to ten numbers spread across four areas: utilization, cost, safety, and compliance. Everything else is drill-down detail you consult when one of the ten moves.
Utilization comes first because it questions the size of the fleet itself. Track utilization rate (days a vehicle is used divided by days available) and flag any asset idle more than seven consecutive days. Most fleets that measure this for the first time find 10–15% of their vehicles are barely working — capital parked against a wall. The companion metric is empty or non-revenue miles as a share of total miles; rising empty miles usually mean territory or scheduling drift, and they compound directly into fuel and maintenance spend.
On cost, the metric that survives every argument is cost per mile, computed monthly, total and split into fuel, maintenance, and fixed buckets. Per-mile costing normalizes across busy and slow months and exposes which vehicle classes are quietly expensive to keep. Pair it with fuel economy tracked per vehicle against its own trailing average — a vehicle 8% below its own baseline has a mechanical or behavioral problem worth a work order — and idle percentage, which is the most directly coachable cost number a fleet has.
Safety metrics need to be rate-based, or growth will masquerade as risk. Harsh events (braking, acceleration, cornering) per 1,000 miles is the standard; absolute counts punish whoever drove the most. Add speeding percentage — the share of driving time meaningfully above the limit — and preventable collisions per million miles for the board-level view. The leading indicators (harsh events, speeding) move weeks before the lagging one (collisions); fleets that coach on the leading numbers consistently see the lagging number follow within two to three quarters.
Compliance and maintenance round out the ten: PM on-time percentage (target above 90%), HOS violations per driver per month, and DVIR completion rate. These are the boring metrics that prevent the expensive surprises — failed audits, out-of-service orders, roadside breakdowns. They are also the easiest to game with sloppy definitions, so define them precisely: a PM completed two weeks late is not "done," it is late, and the metric should say so.
Be ruthless about excluding vanity metrics. Total miles driven says nothing without revenue context. Number of alerts generated measures configuration, not performance. Average speed is meaningless across mixed routes. A good test: if the number moved 20% next month, would anyone do anything differently? If not, take it off the page. Every KPI you keep should have a named owner and a threshold that triggers action — a metric nobody is accountable for is decoration.
Finally, set the cadence. Operations reviews the weekly numbers — idle, harsh events, PM due, unassigned HOS time — in a 15-minute standing meeting. Management reviews the monthly trends — cost per mile, utilization, collision rate — with quarter-over-quarter comparisons. The discipline of a short list reviewed on a fixed schedule beats a beautiful dashboard reviewed whenever someone remembers. Pick your ten, write down the targets, and let two quarters of consistent review do what no dashboard redesign ever will.
More guides
Put this playbook to work
See how fleets use TrackPro to turn guides like this one into measurable results — in a 30-minute walkthrough tailored to your operation.