Driver scoring: 22% fewer accidents
May 27, 2026 · Suso Merino · CEO
A fleet of 60 delivery vans can rack up between 8 and 14 reported accidents a year, not counting the minor parking bumps that never get reported. The average cost of each accident (deductible, days off the road, replacing the service, premium increase) is around €1,800-3,500. Cutting that figure by 22% means €4,000 to €11,000 a year in a mid-sized fleet alone. And you get there with a well-implemented driver scoring program.
Scoring isn’t about spying on drivers. It’s about measuring patterns that correlate with accidents and fuel consumption, giving objective feedback and rewarding improvement. Done badly, it breeds resentment and turnover. Done well, it lowers accidents, premiums and fuel all at once.
What exactly a driver scoring program measures
Scoring aggregates several signals that the tracker captures from the vehicle’s OBD port and its internal accelerometer. The five metrics that really matter are:
- Harsh acceleration: speed changes greater than 2.5 m/s². It indicates nervous driving and pushes fuel consumption up by 15% to 25%.
- Harsh braking: decelerations above 3 m/s². It’s the indicator most correlated with accidents: a fleet with a high rate of harsh braking files 30% to 50% more claims.
- Speeding: driving time above each road’s speed limit. Exceeding it momentarily isn’t what matters; what counts is the percentage of the trip spent over the limit.
- G-force in curves: lateral acceleration when cornering. It correlates with rollovers in tall vehicles (large vans, trucks) and with premature tire wear.
- Prolonged idling: minutes with the engine running and no movement. It doesn’t cause accidents, but it penalizes fuel consumption, the engine and the comfort of the next driver.
Some platforms add seatbelt use (if the CAN bus exposes it), following distance (requires ADAS) and hours behind the wheel (relevant in professional haulage).
How the score is weighted
A useful score is a number from 0 to 100, normally calculated per trip and aggregated per driver over weekly and monthly windows. The usual weighting in real fleets:
| Metric | Typical weight | Comment |
|---|---|---|
| Harsh braking | 30-35% | The most predictive signal of an accident |
| Harsh acceleration | 20-25% | Impact on fuel consumption and wear |
| Speeding | 20-25% | Weighted by margin and road type |
| G-force in curves | 10-15% | More weight if the fleet has tall vehicles |
| Idling | 5-10% | An economic factor, not a safety one |
The usual trap is weighting everything equally. Harsh braking on a highway at 110 km/h isn’t the same as on a neighborhood roundabout, and a good system puts it in context with speed and road type.
What results are realistic after 6 months
Consolidated industry data and the fleets we’ve seen working with scoring + training point to these ranges six months after rollout:
- Reduction in reported accidents: 18% to 25%.
- Reduction in harsh braking: 35% to 50% (the signal drops much faster than actual accidents).
- Reduction in fuel consumption: 5% to 9%.
- Reduction in brake and tire wear: 15% to 20%.
At 12 months, fleets that keep up the discipline (weekly review, individual feedback) consolidate accident reductions of 25% to 35%. Beyond that it gets harder to go lower because external factors come into play: weather, infrastructure, third parties.
There’s an important side effect on insurance. Insurers in Spain (Mapfre, Allianz, Generali, Zurich) have spent the last three years rolling out policies with discounts for documented scoring. A monthly certificate from the telematics provider showing the fleet’s aggregate driving behavior usually unlocks a policy discount of 8% to 15%. In fleets of more than 30 vehicles, this practically covers the annual cost of the telematics software.
How to implement it without driver pushback
The technical part is the easy one. The hardware (FMM003 or FMC003 on OBD, reading the vehicle bus) already captures the signals without touching anything in the vehicle. The part that decides whether the program succeeds or fails is how it’s presented to the workforce.
A transparent internal announcement
Before activating anything, hold a meeting with the drivers. Explain what’s measured, what isn’t (location during breaks isn’t used for penalties, communications aren’t monitored) and why it’s being done. Hand out a written fair-use policy for the data, signed by management and by workers’ representatives if there are any. The GDPR requires this step, but beyond legal compliance it’s what keeps day one from getting off to a bad start.
Gamification with no penalties for the first 3 months
During the adjustment period, nobody is penalized. A weekly ranking is published, anonymized by driver code. Each driver sees their individual position and the average. The fleet manager talks privately with those who have low scores, but without threats: “here’s your data, let’s see how to improve it.”
A bonus for the top three each month
A modest bonus (€50-150) for the monthly top 3 in the scoring has more effect than any penalty. If the winners are also announced internally, the reputational effect reinforces it. Some fleets use a collective bonus if the average exceeds a certain threshold, which creates positive peer pressure.
Targeted training for the lowest scorers
In most cases, drivers with persistently low scores aren’t bad professionals. They tend to have ingrained habits (a lot of late braking, a lot of aggressive acceleration when changing lanes) that improve with a half-day eco-driving session. That training is the investment with the best ROI in the program.
Five mistakes that kill a scoring program
- Penalizing without context: harsh braking in rain or a traffic jam isn’t the same as on a dry road. Systems that don’t add context create a sense of unfairness and resistance.
- Comparing drivers on different routes: a driver doing dense urban routes can’t compete with one doing intercity routes. Comparisons should be made by route type or normalized by kilometers.
- Focusing on punishment instead of improvement: if the first use of scoring is to fire the worst driver, everyone else hides what they can and sabotages the program. Scoring works as an improvement tool, not as a pile of charges.
- Not reviewing thresholds: the manufacturer’s factory thresholds are generic. A fleet of urban vans has different acceleration profiles from an intercity fleet. Thresholds are calibrated after 30-60 days.
- Forgetting the fleet manager: the manager needs training to interpret data, talk with drivers and avoid turning the dashboard into a punitive tool. Without that, the system withers.
What hardware supports it
Any fleet with vehicles under 12 years old can start with an FMM003 (LTE Cat M1) or FMC003 (LTE Cat 1) plugged into the OBD port. Installation takes 2 to 5 minutes per vehicle. The scoring data it collects is the same as with hardwired models, with the advantage that it can be moved between vehicles without an installer. More detail on the hardware in Teltonika hardware for fleets and in differences between the FMM003, FMC003 and Eye accessories.
If the fleet combines combustion and electric vehicles, scoring works the same on both. What changes is that idling becomes meaningless in EVs, and regenerative braking gains weight: it acts as a light brake before the mechanical brake and automatically improves the score.
How scoring fits into an AI-powered system
On its own, scoring is statistics. When it’s connected to the predictive maintenance model, useful correlations emerge: drivers with very high harsh braking scores wear out brake pads two or three times faster than average, and that’s anticipated in the workshop schedule. The same goes for clutches in manual transmissions and tires in fleets that drive lots of curvy roads. There are more case examples with real metrics in AI applied to fleets: real use cases with ROI and in predictive maintenance in fleets.
Conclusion
A well-designed driver scoring program reduces accidents by 18% to 25% within six months, lowers insurance premiums by 8% to 15% and cuts fuel by 5-9%. For a fleet of 60 vehicles, the return is between €20,000 and €50,000 a year, well above the cost of telematics.
The technical part is trivial: OBD hardware installed in minutes. The part that decides success is the human rollout: transparency, no penalties in the first quarter, bonuses for the best drivers and training for those who most need to improve. If you’d like to set up a pilot with a subset of your fleet or understand how scoring is calculated for your vehicle types, get in touch and we’ll plan it together.