Every coachable event is given a Coaching Status. The status decides which queue the event lands in, whether a coach is involved, and whether the event affects the driver's Safety Score. Statuses are set per behavior in Settings > Coaching Workflow.
Coaching Statuses
| F2F Coaching |
An in-person coaching session with the driver. The event is added to a coaching task in the Due for Coaching queue and routed to the assigned coach. |
| Self Coaching |
The driver reviews the event independently in the Driver App. No coach is required unless the review is not completed in time. |
| Remote Coaching |
The coach reviews the event with the driver remotely. The event appears in the Due for Coaching queue. |
| Collision |
The event is routed to the Collisions queue for priority review. |
| FYI Notify |
Informational only. The event appears in the FYI Notify queue, where it can be previewed but no coaching session is created. |
| Positive Recognition |
No coaching task is created. A recognition record is added to the driver's profile and appears in Library > Recognition History. |
| Dismissed |
No coaching task is created and the event status is set to Dismissed. The event does not affect the driver's Safety Score. |
How Statuses Map to Queues
| Due for Coaching |
F2F Coaching, Self Coaching, Remote Coaching |
| Collisions |
Collision |
| FYI Notify |
FYI Notify |
| Assign Drivers |
Any event with no driver assigned, regardless of status. Once a driver is assigned, the event is routed by its status. |
| No queue |
Positive Recognition and Dismissed |
How the Status is Resolved
When an event is created, the program looks for a matching Coaching Workflow row in this order:
- A group override for one of the driver's tags. If the driver carries more than one tag with an override, the most recently created tag is used.
- The fleet baseline row for that behavior.
- The platform default for that behavior.
The first match is used. This means an account that has never opened the Coaching Workflow still routes and scores events using the platform defaults.
Note
Routing is decided at the moment the event is created and does not change afterwards. If you edit the Coaching Workflow or change a driver's tags, existing tasks keep the queue they were routed to. New events follow the updated configuration.
Coaching Tasks
A coaching task groups one driver together with their open coachable events of the same coaching type. Each driver has at most one open task per coaching type, so new events of that type are added to the existing task rather than creating a second one.
Each task carries:
- The driver and the events attached to the task.
- The coaching type – F2F Coaching, Self Coaching, Remote Coaching, FYI Notify, or Collision.
- An assigned coach, resolved from your Coach Assignment configuration. A task with no matching assignment stays unassigned and can be picked up by any user with access to the module.
- A due date, calculated from the Safety Due Days configured for that coaching type.
A task is closed when a coach completes a coaching session for it, or when its last remaining event is dismissed.
Escalation
Coaching can escalate from self-coaching to a face-to-face session automatically:
- When the same behavior recurs more times than the configured occurrence count within the configured time frame.
- When the driver does not complete self-coaching within the configured deadline.
- If a face-to-face session is then not completed within its deadline, a follow-up notification is sent to the coach.
Escalation rules are set per behavior. Read the article Coaching Workflow Settings.