Home / Resources / Driver Scorecard Metrics
Waste & Recycling Ops 3 min read

What Is a Driver Scorecard? The Metrics That Actually Belong on One

A driver scorecard is a recurring report that scores an individual driver across several dimensions at once, not just one. A solid scorecard weighs lifts or stops per hour, on-time rate, safety and incident history, damage or complaint rate, and fuel or idle behavior together, so no single number can be gamed at the others’ expense.

Most scorecard problems start the same way: someone builds it around whatever metric TRUX, Routeware, or Navusoft tracks well, usually lifts per hour or on-time percentage. Both are useful, neither is sufficient alone. A driver who hits every stop fast but backs into mailboxes or skips a walk-around isn’t a top performer; the scorecard hasn’t caught up yet.

What belongs on a driver scorecard

A scorecard that holds up under scrutiny — from drivers, dispatch, and whoever runs payroll off it — usually rests on five metrics, weighted together rather than led by any one of them:

  • Lifts or stops per hour — the productivity baseline, and the metric most scorecards over-index on. See Lifts Per Hour, Explained for how to read it correctly on its own.
  • On-time rate — percentage of stops completed within the route’s scheduled window.
  • Safety and incident rate — accidents, near-misses, and failed or skipped vehicle inspections.
  • Damage or complaint rate — cart damage, property damage, and customer complaints tied back to a specific driver.
  • Fuel and idle behavior — harsh braking, excess idle time, and fuel use per route, where telematics data is available.

The one-metric mistake

Score a driver purely on lifts per hour or on-time rate and you’ll get more lifts per hour and more on-time stops, along with more damage claims, more missed safety checks, and more customer complaints that show up as chargebacks a month later. The fix isn’t dropping productivity metrics. It’s weighting them alongside safety and quality, not instead of them.

Most fleets already have this data; the friction is pulling it together every week by hand from TRUX, Routeware, ADP, and a safety log. That kind of manual reporting is exactly what automation tends to cut by 40-70% once it’s set up once and reused. If you want the profitability math behind route-level decisions rather than driver-level ones, see How to Calculate Route Profitability, and for the fleet-wide view, Route Profitability.

Does this apply beyond waste?

The same distortion shows up anywhere a field workforce is scored on one productivity number — home service techs paid on jobs-per-day, delivery drivers on stops-per-shift, warehouse pickers on units-per-hour. A scorecard built on a single metric always optimizes for that metric, at the expense of everything it doesn’t measure.

FAQ

Common questions

How much weight should lifts per hour get on a driver scorecard?

Weight it, don’t drop it. Lifts or stops per hour should typically count for no more than a third of a driver’s overall score, with safety, damage/incident rate, and complaint rate making up the rest. A driver who scores well on speed but poorly on safety should show up as a mid-pack performer, not a top one.

Where does the data for a driver scorecard come from?

Pull it from what you already run: TRUX, Routeware, or Navusoft for stops, lifts, and on-time data; ADP or payroll records for hours and overtime; telematics for fuel and idle behavior if it’s installed; and dispatch or safety logs for incidents and complaints. The data usually already exists, just scattered across systems.

See it on your data

See a sample route-profitability dashboard

We’ll show you what route-level margin looks like on your kind of data — and where it’s quietly hiding. Built on a sample, modeled on real implementations.