This article walks through configuring your coaching workflow, from the fleet-wide baseline to per-group overrides.
Step 1: Open the Coaching Workflow
- Go to Driver Safety > Settings > Coaching Workflow.
- Confirm the scope selector at the top of the page is set to your fleet, so you are editing the fleet-wide baseline.
Step 2: Set the Coaching Status for Each Behavior
- Find the behavior in the Behavior column.
- Select a value in the Coaching Status dropdown.
A practical starting point:
| F2F Coaching |
Behaviors your coaches should discuss in person – for example collision-related and severe distracted driving behaviors. |
| Self Coaching |
Behaviors the driver can review themselves – for example harsh braking or harsh acceleration. |
| FYI Notify |
Behaviors you want visibility on but do not intend to coach. |
| Positive Recognition |
Behaviors that indicate good driving and should credit the driver. |
| Dismissed |
Behaviors that are not relevant to your operation. |
Step 3: Set the Behavior Scores
- Leave Custom Behavior Score empty on any behavior where you are happy with the platform default.
- Enter a positive number where you want a different weight. Use the scale of 1 point = a 1% reduction per 100 km driven: 1 point is minor, 5 points is significant, and 20 points is severe.
- Enter 0 for any behavior that should appear in the queues but not affect the Safety Score.
Note
Always enter a positive number. The Coaching Status decides whether the score is a deduction or a credit.
Step 4: Tune Event Generation
For each behavior, set how many detections create an event and how often:
- Set the Detection Threshold – 2, 3, 4, or a custom value.
- Set the Detection Window – 2, 3, or 5 minutes, or a custom value.
- Set the Event Snooze Duration – 60, 180, or 360 minutes, or a custom value.
If a behavior is producing more events than your coaches can work through, raise the threshold or lengthen the snooze period, then review the Behavior Report after a week to see the effect.
Step 5: Set the Escalation Rules
- Set Self-Coaching First to Yes for behaviors where the driver should review the event before a coach is involved.
- Set the Occurrence Count and Time Frame – for example 3 occurrences within 60 days.
- Set the Self-Coaching Deadline in days.
Keep the deadline consistent with your Safety Due Days configuration, so drivers are not escalated before their self-coaching window has closed. Read the article Safety Due Days Settings.
Step 6: Save
Click Save. All rows in the current scope are saved together.
Warning
Changing a behavior score changes the Safety Scores shown for past periods as well as current ones. Routing changes apply to new events only.
How to Add a Group Override
Use an override when one part of the fleet needs different handling – for example when a long-haul group is coached differently from a local delivery group.
- Go to Driver Safety > Settings > Coaching Workflow.
- Change the scope selector from your fleet to the group you want to configure.
- Set values only for the behaviors that should differ. Every other behavior falls back to the fleet-wide configuration.
- Click Save.
Note
When a driver carries more than one group with an override for the same behavior, the most recently created group is used. Keeping overrides to a small number of groups makes the outcome easier to predict.