Not every behavior the camera identifies becomes a coaching task. The Driver Safety Program separates what the device reports from what your coaches are asked to review, so that a driver who braked hard three times in one minute does not generate three separate coaching items.
Detections and Events
| Detection |
A single instance of driving behavior identified by the device using AI* or vehicle telemetry. Detections are stored in the cloud but are not coaching work on their own. |
| Event |
Created when detections of the same behavior cross the configured threshold within the configured time window. An event is what appears in the queues, the reports, and the driver's Safety Score. |
Video is requested and stored only when a detection becomes an event.** This helps reduce unnecessary uploads over the cellular connection and helps keep the recording timeline focused on behavior your team reviews.
The Three Event Generation Settings
Each behavior has its own values for the three settings below, configured in Settings > Coaching Workflow:
| Detection Threshold |
How many detections of the behavior are needed to create one event. |
| Detection Window |
The rolling period in which those detections must occur (in minutes). |
| Event Snooze Duration |
How long the program waits after creating an event before the same behavior can create another one for the same driver (in minutes). |
Example
A behavior is configured with a Detection Threshold of 3, a Detection Window of 2 minutes, and an Event Snooze Duration of 180 minutes.
- The driver produces two detections in 2 minutes – no event is created.
- The driver produces three detections in 2 minutes – one event is created and its video is requested.
- Further detections of the same behavior in the next 180 minutes do not create another event.
- After 180 minutes, the next set of detections that crosses the threshold creates a new event.
Default Values by Behavior
Every account starts with the platform defaults below. Any value you change in the Coaching Workflow applies to your account only.
| Behavior |
Category |
Coachable |
Detection Threshold |
Detection Window (min) |
Snooze (min) |
| Harsh Braking |
Harsh Driving |
Yes |
1 |
2 |
15 |
| Harsh Acceleration |
Harsh Driving |
Yes |
1 |
2 |
15 |
| Harsh Turning |
Harsh Driving |
Yes |
1 |
2 |
15 |
| Red Light |
Harsh Driving |
Yes |
1 |
1 |
30 |
| Tailgating |
Harsh Driving |
Yes |
1 |
1 |
60 |
| Pedestrian |
Harsh Driving |
No – notification only |
– |
– |
– |
| Rolling Stop |
Harsh Driving |
Yes |
3 |
2 |
60 |
| Absolute Speed |
Speeding |
Yes |
1 |
1 |
60 |
| Speed Limit |
Speeding |
Yes |
1 |
1 |
60 |
| Distracted Driver |
Distracted Driving |
Yes |
3 |
2 |
180 |
| Phone Usage |
Distracted Driving |
Yes |
3 |
2 |
180 |
| Seatbelt |
Distracted Driving |
Yes |
3 |
2 |
180 |
| Smoking |
Distracted Driving |
Yes |
3 |
2 |
180 |
| Drinking or Eating |
Distracted Driving |
Yes |
3 |
2 |
180 |
| Fatigue |
Distracted Driving |
Yes |
2 |
30 |
120 |
| Collision |
Collision |
Yes |
1 |
– |
– |
Note
Collision creates an event from a single detection and has no window or snooze period. Pedestrian is sent as a notification only and never creates an event.
What Happens After an Event Is Created
- The event is assigned a Coaching Status based on the Coaching Workflow. Read the article Understanding Coaching Statuses and Queues.
- If the status is coachable, the event is added to the driver's open coaching task, or a new task is created.
- If the event has no driver assigned, it goes to the Assign Drivers queue instead.
- The event contributes to the driver's Safety Score. Read the article Understanding the Driver Safety Score.