The Safety Score is a single 0–100 number per driver, and it is the only score used across the Driver Safety Program – on the Dashboard, in every Insights report, and on the driver profile. It is calculated from the per-behavior scores you set in the Coaching Workflow and normalized by the distance the driver travelled, so that drivers covering different mileage can be compared fairly.
How the Score Is Calculated
1. Each event contributes points
Every event has a score, taken from the Custom Behavior Score in the Coaching Workflow, or from the platform default when no custom value is set. How the points are applied depends on the event's Coaching Status:
Any coachable status
(F2F, Self, Remote, FYI Notify, Collision) | The score is added as a deduction. |
| Positive Recognition | The score is applied as a credit and raises the Safety Score. |
| Dismissed | Contributes zero. |
2. Deductions are normalized by distance
The scale is 1 point = a 1% reduction per 100 km driven:
- One 1-point event over 100 km deducts 1 point from the score.
- Two 1-point events over 100 km deduct 2 points.
- One 1-point event over 200 km deducts 0.5 points.
Use this scale when setting your own values: a 1-point behavior is minor, a 5-point behavior is significant, and a 20-point behavior is severe.
3. The result is capped between 0 and 100
The final Safety Score is displayed with two decimal places so that small changes remain visible.
Deductions
Alongside the Safety Score, several pages show Deductions – the raw sum of points before distance is applied. Deductions can be negative when recognition credits outweigh deductions. The Driver Scorecard on the driver profile breaks this down per behavior:
| Coachable Behavior | The behavior name. |
| Frequency (A) | How many times it occurred in the period. |
| Weight (B) | The score resolved for this driver, taking group overrides into account. |
| Points (A × B) | The contribution to Deductions for that behavior. |
Correcting a Score
Coaching an event does not change its effect on the score. The score reflects what was recorded, not what was done about it.
To remove an event that was recorded incorrectly, use the Dismiss action from the task card or the coaching session. A dismissed event contributes zero and stops affecting the driver's score.
To stop a behavior from affecting scores across the whole account, set its Custom Behavior Score to 0 in the Coaching Workflow.
Note
Scores are recalculated on every read. Editing the Coaching Workflow or changing a driver's groups also changes their score for past periods the next time a page is opened.
Trends
Report columns labelled Trend compare the selected period with the previous period of equal length and show a signed change. A higher Safety Score is better, so a falling score is shown as a decline in red. When the previous period has no data, the trend shows a dash.
On columns that count behaviors rather than score, the polarity is reversed, because fewer events is the goal – a falling count is shown in green.
Risk Levels
Safety Scores are grouped into four risk levels, shown as a colored pill on the Dashboard leaderboards and in the Group and Driver reports.
Unresolved Events
If a behavior has neither a Coaching Workflow row nor a platform default, the event contributes zero and is counted as Unresolved on the driver profile. If you see an unresolved count, review the behavior in Settings > Coaching Workflow and set a Coaching Status and a score for it.