Driver safety scorecards: measure and coach

Driver behaviour is the part of fleet risk you can change this quarter. The Ministry of Road Transport and Highways recorded 4,80,583 road accidents in 2023, in which 1,72,890 people died and 4,62,825 were injured. Over-speeding alone was associated with 68.4% of those accidents, 68.1% of the deaths and 69.2% of the injuries.

Speed is not a small lever. The World Health Organization puts it plainly: every 1% increase in mean speed produces a 4% increase in fatal crash risk and a 3% increase in serious crash risk. WHO also reports that reducing average travelling speeds by just 5% could cut fatal road crashes by 30%. Restraints matter too: 16,025 of those killed on Indian roads in 2023 were not wearing a seat belt.

A scorecard turns that into something a supervisor can act on: a few behaviours that predict harm, one number a driver understands, and a reason for a specific conversation.

Keep the list short. Four well-defined safety behaviours beat twenty noisy ones.

Measure each one as a rate, never a raw count: per 100 kilometres for the distance-linked events, per engine hour for idling, and as a share of driving time for belt use.

• Over-speeding. Score time spent over the limit and how far over, not how many times the line was crossed. Ten seconds at 5 km/h over is not four minutes at 30 km/h over.
• Harsh braking. Sudden deceleration past a threshold set for the vehicle class, usually a sign of following too closely or reading the road late.
• Harsh acceleration. Rapid pull-away, most common in light commercial vehicles and two-wheelers. It costs fuel and tyres.
• Harsh cornering. Lateral force through a turn. On a laden truck or a tempo that is a rollover risk, not a comfort issue.
• Seat belt use, where your vehicle or tracker reads the signal. Many installations do not, so treat it as a bonus line, not a pillar.
• Idling. Not a crash risk, so keep it out of the safety number. It is the cheapest habit to change, so show it alongside in idle minutes per engine hour.

A score is a claim about a person's work. If the arithmetic is secret, or the weights look arbitrary, drivers argue with the number instead of the behaviour.

Keep safety and efficiency apart. Fuel economy, idling and punctuality are worth tracking, but folding them into the safety number lets a good month on fuel hide a dangerous week on speed.

• Weight by harm, not frequency: over-speeding carries the most weight.
• Use severity bands: a mild brake event and a violent one should not score the same.
• Set a minimum exposure, a distance or a number of trips, before a driver is ranked at all.
• Use a rolling 30-day window, so one bad Monday does not follow someone for a year.
• Publish the formula before anyone is scored. Give every driver the weights, the thresholds and a worked example on one page, in the language they read.

Indian routes punish naive scoring. Unmarked speed breakers, a pothole, cattle, a two-wheeler cutting in, a ghat section at night: each produces harsh events from drivers who did exactly the right thing. MoRTH notes that faults in road design may sit behind what looks like human error.

Run a proper dispute route. A driver who can say "that was the diversion at the bridge" and have the event removed will trust the other ninety-nine.

• Filter by location. If most drivers brake hard within a few metres of the same point, you have found a speed breaker or a blind junction, not a bad driver. Exclude the spot and report the road.
• Compare like with like. City distribution, highway line-haul and site work belong in separate leagues; urban stop-start driving always shows more events per 100 kilometres.
• Calibrate thresholds per vehicle class. A laden 16-tonne truck, an empty tempo and a delivery scooter do not share a threshold. Agree the settings with your hardware supplier and never change them mid-month.
• Treat night and monsoon driving as context rather than fault, and check whether the schedule is forcing the pace.

Speed carries the heaviest weight in the score, so the threshold has to be defensible. In India it is rarely a single number.

There is an employer angle. Since the Motor Vehicles (Amendment) Act, 2019, the speeding offence in section 183 covers not only whoever drives, but anyone who causes a person employed by them, or under their control, to drive over the limit. A schedule that forces the pace is the operator's exposure too.

This is general guidance, not legal advice: confirm the limits that apply to your vehicles with your RTO or state transport department.

• Legal limits differ by vehicle class, road type and state. Under section 112 of the Motor Vehicles Act, 1988, the Centre notifies the maximum, and a State Government or an authority it empowers may fix lower limits on particular roads or areas.
• Speed limiting devices are a legal requirement, not something to assume. Rule 118 of the Central Motor Vehicles Rules, 1989 requires a speed limiting device or function on notified transport vehicles manufactured on or after 1 October 2015. Two-wheelers, three-wheelers, quadricycles, fire tenders, ambulances, police vehicles and vehicles certified to a maximum rated speed of not more than 80 km/h sit outside it. Check each vehicle's own fitment rather than assuming the fleet is covered.
• The presets sit in the rule itself: not more than 80 km/h in general, 60 km/h for dumpers, tankers, school buses, hazardous-goods carriers and any other category the Central Government specifies, and 30 km/h for airport passenger buses. States decide which older vehicles must be retrofitted and may set a lower speed; Odisha's 2016 notification under rule 118(2), for example, covers transport vehicles registered before 1 October 2015.
• Score against the posted limit where you can map it, and set your own fleet ceiling below it.
• Add zone limits for the places a general limit misses: your own yard, a plant, a school street, a market lane.
• Use a small tolerance and a minimum duration before an event counts, so a GPS spike never becomes a disciplinary matter.

A score on its own rarely changes driving. The conversation around it does, and only when it is short, frequent and specific.

Say who sees the score and who does not, before the first one lands. A programme that arrives unexplained is read as surveillance, and it will be gamed.

Driver location and behaviour data is personal data. Check what the Digital Personal Data Protection Act, 2023 asks of you on notice, purpose and retention before you switch capture on, and take your own advice on it.

• Weekly, not annual. Ten focused minutes with a supervisor does more than a yearly review nobody remembers.
• One behaviour at a time. Take the event type contributing most to that driver's score and leave the rest alone.
• Lead with the trip, not the table. Open the replay of one journey and ask the driver to explain it. Most will mention the schedule, the load or the road.
• Agree one concrete change and a date to look again. "More following distance on the ring road after six" is coachable. "Drive safely" is not.
• Coach in private, in the driver's own language, and include drivers supplied by transporters and contractors.
• Escalate in visible steps: conversation, refresher training, a ride-along, then formal action.

Most fleets spend their attention on the bottom of the table, so careful drivers learn that safe driving is invisible.

• Reward the highest scores and the biggest improvement. The second makes the programme feel winnable to everyone else.
• Make recognition frequent and small: a monthly mention, a certificate, first pick of routes.
• Show the fleet-level trend every month, so the whole team can see whether the programme is working.

Do not launch the full scheme on day one; run it in three steps.

Review the thresholds after a quarter. If nearly everyone is failing, they are wrong. If nobody is, they are too loose.

• Days 1 to 30, collect only. Switch on event capture, leave scoring off, and find your real baseline and your hotspots.
• Days 31 to 60, run it in the open. Share the rules, agree them with supervisors, and attach no consequences yet.
• Days 61 to 90, start coaching. Weekly conversations, a monthly recognition, and a named person who owns disputes.