What is a driver scorecard?
A driver scorecard turns each driver's monthly driving events into one number that can be compared across the fleet. It shows who drives safely, who needs watching and who needs coaching, and whether each driver is getting better or worse from month to month.
This monthly driver scorecard template in Excel converts five event types to rates per 100 km, scores each from 0 to 100, combines them with weights you set, and ranks the drivers. A coaching log records every conversation and checks the next month's score.
Events in the driver scorecard and default weights
| Event type | Measured as | Default weight | Scores 0 at |
|---|---|---|---|
| Speeding events | events per 100 km | 30% | 2.0 per 100 km |
| Harsh braking | events per 100 km | 20% | 2.0 per 100 km |
| Harsh acceleration | events per 100 km | 15% | 2.0 per 100 km |
| Idling | minutes per 100 km | 15% | 60 min per 100 km |
| Seatbelt violations | events per 100 km | 20% | 1.0 per 100 km |
All weights and zero-score rates are editable defaults on Settings. Tune them to your fleet once, then keep them stable so the trend stays meaningful.
How to use the driver scorecard template
- Agree the rules on Settings: weights, zero-score rates, band limits, minimum km and trend threshold.
- Enter the month on Monthly data: one row per driver with km driven and the five event counts.
- Read the scorecard for the month set on Settings: rank, score, band, change and weakest area.
- Coach every driver in the Coach band and anyone trending Worse, and record it on the Coaching log.
- Follow up the next month: the log shows the new score and whether the driver improved.
How is the driver score calculated?
The rank counts how many drivers with enough km scored higher in the same month, so 1 is the best. The weakest area is the event type with the lowest event score, which is where coaching should start.
Worked example: one driver, one month
In September, K. Hassan drove 4,200 km with 14 speeding events, 22 harsh braking events, 10 harsh accelerations, 1,000 idling minutes and 1 seatbelt violation. Per 100 km that is 0.33, 0.52, 0.24, 23.8 minutes and 0.02, which give event scores of 83.3, 73.8, 88.1, 60.3 and 97.6.
A score of 81.5 is in the Good band. In August he scored 76.9, so the change is +4.6 and the trend is ▲ Better. His weakest area is idling, at 60.3.
O. Saleh scored 46.1 in August, the Coach band, with speeding as his weakest area. After a ride-along on the Coaching log, he scored 66.0 in September, so the log shows the result as Improved.
Using the driver scorecard for coaching
Start each conversation from the weakest area and the events behind it, not from the rank. Agree one or two specific changes, set a follow-up date, and record them on the Coaching log. Recognize drivers who stay in the Good band or improve sharply, too: the scorecard works better as a coaching tool than as a league table.
Common driver scorecard mistakes
- Ranking on raw event counts. Drivers who drive more always look worse. Normalize per 100 km.
- Scoring drivers with very little distance. A few hundred km make rates swing. Use the minimum km setting.
- Changing event thresholds mid-year. If the telematics definition of harsh braking changes, the trend breaks.
- Changing the weights every month. Agree them once, or drivers will not trust the score.
- Comparing very different routes. City delivery produces more braking than highway work. Compare within teams.
- Coaching with no follow-up. Without a follow-up date and next month's score, nobody knows if it worked.
Limits of a spreadsheet driver scorecard
The scorecard is only as good as the event counts typed in each month, and those depend on how your telematics or video system defines each event. It cannot see context, such as a harsh brake that avoided a collision, so review the events behind a low score before you act on it.