Driver Safety Scorecards Drivers Cannot Dismiss
A safety score is only worth publishing if the driver at the bottom can see exactly why he is there. KO Fleetz builds each score from events you already trust, divides by the exposure that produced them, and opens every deducted point back to the incident, the road and the minute it happened.
A number out of a hundred that nobody can explain
The safety review comes round every quarter. Somebody exports the vendor's driver ranking, prints it, and puts it on the table. Ahmed is on 58. Nobody in the room can say what 58 is made of, what it would take to make it 70, or why the same formula gave him 71 last quarter when his driving did not change. Ask the vendor and you get a support ticket and the phrase 'proprietary algorithm'. The meeting produces a printed list and no decisions.
Then look at who sits at the bottom. It is almost always the person who drove the most. Event counts grow with hours behind the wheel, so the full-time city driver on twelve stops a day accumulates far more braking events than the man who does two motorway runs a week. He is not the riskiest person on the fleet. He is the busiest one, and the scorecard has quietly turned exposure into guilt.
The deeper failure is that nothing happens afterwards. There is no route from the score to Monday morning. Nobody is assigned to sit with anybody, nothing gets re-measured, and the same three names appear at the bottom next quarter. The scorecard becomes a compliance artefact produced for the insurance renewal file, and every driver works out inside a month that it carries no consequences in either direction.
A score you can take apart, argue with and act on
KO Fleetz starts every score from evidence rather than from a formula. Each event feeding it arrives from behaviour monitoring with its location, speed trace and severity intact, so a deduction is never an assertion. Open the two points a driver lost on Tuesday and you land on the roundabout where he lost them, at 14:12, with the speed before and after. That property is what lets the number survive being challenged.
Exposure is the denominator, not an afterthought. Events are expressed per hundred kilometres and per driving hour, and drivers are compared inside cohorts that share a duty cycle: urban multi-drop against urban multi-drop, night trunk against night trunk. A driver who covers four times the distance of his colleague is measured on rate rather than on total, which removes the most common reason drivers reject a scorecard outright.
The weights belong to you. A coach operator carrying standing passengers cares about cornering in a way a tipper fleet does not, so the risk model is configured rather than inherited from a vendor default. What the module deliberately withholds is a verdict. It does not issue warnings automatically, does not drive disciplinary action on its own, and refuses to produce a score at all for a driver whose exposure is too thin to support one. An honest blank beats a plausible invention.
Capabilities
What KO Fleetz driver safety & scorecards gives your team
Exposure-normalised scoring
Risk is expressed per hundred kilometres and per driving hour, so the driver with the fullest roster stops being penalised for turning up.
Weights you configure
Decide what cornering, speeding, harsh braking and idling are worth to your fleet. The risk model is written down and editable, not sealed in a vendor algorithm.
Score breakdown to the incident
KO Fleetz traces every deducted point to the specific event that caused it, carrying its road, timestamp and speed trace for review.
Cohorts by duty cycle
Drivers are ranked only against colleagues doing comparable work, so a night trunk driver and a city multi-drop driver never share a league table.
Coaching cycle tracking
A score below threshold opens an assigned coaching item with an owner and a due date, then re-measures that driver over the following weeks.
Per-driver trend line
Shows whether someone is improving against his own past, which is a fairer test than a rank that moves every time a colleague resigns.
Insufficient-exposure flagging
Drivers with too few hours to score are marked unrated rather than issued a number that two trips could swing by twenty points.
Insurer and audit record
Keeps the scoring rules, the score history and the coaching actions taken per driver, which is what a renewal underwriter asks to see.
How it works
How KO Fleetz does it
Step 1: Trust the events before you score them
Thresholds are calibrated per vehicle class in behaviour monitoring first. Scoring disputed events only converts a measurement argument into a personnel argument.
Step 2: Set your risk model
Sit with the safety lead and agree what each event type is worth. Weights are versioned, so a score that moves can be traced to a rule change rather than guessed at.
Step 3: Build the cohorts
Group drivers by the work they do rather than by depot convenience. Anyone without comparable peers is reported against his own history, not forced into a ranking.
Step 4: Publish with the breakdown open
Release scores where any driver can open his own and inspect every deduction. A score presented without its evidence teaches drivers to distrust the whole programme.
Step 5: Coach, then re-measure
Each low score becomes an assigned conversation with a named owner. The next period's rate for that driver is the only evidence the coaching worked.
Outcomes
What changes
- Rate-based scoring, not raw event counts
- Per 100 km
- Each deduction opens to its own incident
- Traceable
- Risk model owned by you, not a vendor default
- Your weights
- Thin exposure says so instead of guessing
- Unrated
Frequently asked questions
Each detected event carries a severity grade and a weight your fleet sets. KO Fleetz sums those weighted events over a period and divides by exposure, giving a rate per hundred kilometres and per driving hour rather than a total. That rate is placed against the driver's cohort to produce the published figure. Every step is visible on screen, including the weights in force at the time. If you cannot reconstruct a score by hand from the events behind it, we have built it wrong.
Behaviour monitoring detects the event and preserves its evidence: the hard stop, where it happened, how severe it was. This module is the layer above. It decides what that event is worth to your operation, normalises it against how much the driver drove, ranks fairly within a cohort, and drives the coaching that follows. Detection without scoring is a stream of incidents nobody prioritises. Scoring without trusted detection is a league table your drivers reject in the first meeting.
Use the events for that, not the score. A score is an indicator built from weightings your team chose, and it compresses a month of driving into one figure. That is useful for deciding who to sit with. It is weak ground for a formal process, and worse for pay, because tying money to a metric reliably corrupts the metric. Where a specific incident warrants action, the incident and its evidence are what stand up. Involve HR and any works council before scores become consequential.
No, and we will not claim it does. Scoring measures observable behaviours associated with risk. It cannot see fatigue, the car that pulled out, ice on an unsalted road, or a moment of inattention no accelerometer registered. Careful drivers crash and careless ones go years without one. Treat the score as a way of finding conversations worth having, not as a prediction about any individual. Anyone selling per-driver crash prediction from telematics events is overstating what this data supports.
They are marked unrated until they have enough exposure to score. This matters more than it sounds. With only a few hundred kilometres recorded, one awkward junction can move a driver twenty places, and a new starter can be labelled a risk in his first fortnight on the strength of a single bad roundabout. The threshold for rating is configurable per fleet. Until a driver crosses it his events remain visible and coachable, they simply do not produce a ranked number.
Yes, and the programme works badly otherwise. A score a driver discovers in a quarterly meeting arrives as an accusation. A score he can open, inspect and dispute during the month becomes something he manages. The usual objection is that visibility invites gaming, and the honest reply is that gaming this score means braking earlier and cornering more gently. Watch instead for drivers refusing difficult routes to protect a number. That is a management signal, and it usually means the weights need revisiting.
Build a scorecard your drivers will engage with
Bring one month of events from your current system. We will run them through KO Fleetz and show you what the ranking looks like once exposure is taken out of it.