How to Build a Driver KPI System in 30 Days

Most owners want to "measure their drivers" — and most of them never start because they think it needs to be perfect on day one. It doesn't. Here's a 30-day plan that gets you from zero to a real, working driver KPI system without the headache.

Why Most Driver KPI Systems Fail

They fail for the same reason most operational changes fail in small fleets — they try to track too much, too soon, with no plan for what to do with the data. The result is a wall of numbers nobody looks at, drivers who roll their eyes at the system, and an owner who quietly goes back to managing on gut feel.

This plan is the opposite. Three metrics. Four weeks. One conversation per driver. That's it.

Week 1: Pick Three Metrics. Just Three.

The temptation is to track everything — calls, revenue, cancels, ETA, fuel, damage, customer ratings, accident-free days. Resist it. Pick three numbers that actually describe whether a driver is doing the job. The three we recommend for most small fleets:

• Calls completed per shift. Productivity. Easy to pull from any dispatch software.
• Revenue per call. Is the driver upselling appropriately, working complete tickets, and not bleeding revenue on every job?
• Customer feedback rate. Could be a thumbs up/down, a star rating from the motor club, or just complaints per 100 calls. Pick one and stick with it.

That's the whole list. You can add more later. Don't.

Week 2: Get the Data Flowing

Most of what you need is already in your dispatch software. Towbook, Omadi, Beacon, whatever — they all track call counts and revenue per driver. What you usually have to set up is a way to actually see it weekly without re-pulling reports every time.

• Build (or have built) a one-page report that shows the three numbers for every driver, week over week.
• Decide the cadence: weekly is the sweet spot. Monthly is too slow to course-correct. Daily is too noisy.
• Pick a day and time you'll review it every week without fail. Tuesday morning is a good default.

Week 3: Share the Scores

This is the step people skip. The whole point of measuring drivers is to let them see where they stand. Pin the scores in the dispatch office. Email them. Post them in the group chat. Whatever fits your operation.

What happens when drivers can see their numbers next to each other is one of the most reliable things in towing — the bottom three start fighting to not be on the bottom, the top three start competing with each other, and the middle five quietly get better. You don't have to say a word.

One rule: show numbers, not commentary. No editorializing, no "see Mike crushing it this week" notes. Just the data. The drivers will draw their own conclusions, and those conclusions land harder than anything you'd say.

Week 4: One Conversation Per Driver

At the end of the first month, sit down with each driver for 10 minutes. Not a meeting. Not a review. Just a conversation. Three questions:

1. Looking at your numbers, what stands out to you?
2. What's making it hard to be better on any of them?
3. What's one thing we could change that would help?

You'll learn more about your operation from these five conversations than from any consultant report. And the drivers will know — for the first time — that you're paying attention, not just to whether they show up, but to whether they're doing the job well.

After 30 Days

You'll have a working KPI system. It will be rough. The numbers will have weird quirks the first month. One driver will complain that the scoring isn't fair. Another will quietly start outworking everyone. That's exactly what's supposed to happen.

From here, the system gets better by small adjustments — refining a metric, adding a fourth one if it earns its place, building in a small bonus tied to the top score. But don't make those changes in month one. Let the basic system run, and let the drivers see that you're going to keep doing this every week. That consistency is what turns a "KPI system" into a culture.