DriveCam Events: When to Coach and When to Escalate
Ken Wogan
DriveCam footage is great until you have to decide what to do with it.
The system flags an event: a driver made a lane change without full visibility. You pull the footage. You can see exactly what happened. And then you ask: is this a coaching moment or the start of a discipline conversation?
Get it wrong, and you’re either over-disciplining safety-conscious drivers or missing patterns that need intervention. Get it right, and you improve safety culture.
The Problem with Inconsistent Event Response
Agencies that use DriveCam often struggle with consistency.
One supervisor reviews a close-call event and immediately schedules coaching. Another sees similar footage and writes it up as a formal corrective action. A third reviews it and decides it was just a momentary lapse, so they don’t address it at all.
Same driving event. Three different outcomes.
From the driver’s perspective, this looks arbitrary. The driver who got disciplined for a close call that another driver got coached for won’t accept that as fair. And they’re right—it’s not.
From a legal perspective, it’s a consistency problem that creates liability in exactly the same way discipline inconsistency does.
And from an operational perspective, it’s inefficient. DriveCam data is valuable only if you use it systematically. Random responses mean missed improvement opportunities.
Building a Decision Framework
A defensible DriveCam response process needs three components:
Component 1: Trigger definitions. What types of events do you review? Do you review everything flagged by the system, or do you sample? When do you review in real-time versus later?
Some agencies review every event. Others sample a percentage. There’s no single right answer, but you need consistency. If you sample, use a consistent method (every third event, all events above a severity threshold, etc.).
Component 2: Event categorization. Once you’ve identified an event, categorize it using the same framework as your incident preventability system.
-
Observation: The system flagged something, but it wasn’t actually unsafe. (Example: the camera detected a lane change, but the driver had full visibility and clear intent.)
-
At-Risk Behavior: The driver made a tactical choice that created unnecessary risk. (Example: a lane change without checking the mirror, even though it worked out okay.)
-
Unsafe Behavior: The driver created actual hazard. (Example: talking on the phone while negotiating traffic.)
-
Reckless Behavior: Deliberate violation of safety practices. (Example: knowingly speeding or operating while impaired.)
Different categories get different responses.
Component 3: Response protocols. Define what happens for each category.
Observation: Document and move on. No coaching, no discipline.
At-Risk Behavior: Coaching conversation within 48 hours. Watch the footage together. Ask the driver what they were doing and why. Discuss what they could do differently. Document the conversation.
Note: at-risk behavior coaching is not punishment. It’s education. The tone matters. The goal is helping the driver understand how to reduce risk.
Unsafe Behavior: Formal corrective action. This involves documentation, the driver’s response, and a clear statement that this behavior cannot continue.
Reckless Behavior: Escalation toward discipline. Depending on severity and history, this might mean suspension, mandatory retraining, or termination.
The Coaching Conversation
The difference between a successful coaching response and one that backfires is tone and approach.
A bad coaching conversation sounds like: “You made a stupid lane change without checking your mirror. This could have caused a crash. You need to pay better attention.”
A good coaching conversation sounds like: “I watched the footage from your lane change at mile marker 15. I could see you initiated the change and then checked your mirror. Walk me through what you were thinking at that moment. What made you decide it was safe?”
The good version:
- Shows the specific incident
- Invites the driver’s perspective
- Doesn’t assume you know the driver’s reasoning
- Treats the driver as someone who cares about safety (which most do)
After listening to the driver’s explanation, you have context. Maybe the driver saw a hazard in the original lane that wasn’t visible in the camera footage. Maybe they miscalculated but knew what they should have done differently.
Then you move to education: “Here’s what I’d like you to focus on going forward: always complete your mirror check before you initiate the move. Even if you feel pressured to change lanes, take the extra second to confirm.”
That’s coaching. The driver hears feedback specific to their behavior, understands why it matters, and knows what to do differently.
Compare that to: “Write-up for unsafe lane change. Attend mandatory defensive driving seminar.” That’s discipline, and it creates resentment rather than improvement.
Common Mistakes in Event Response
Mistake 1: Reviewing events too late. If three weeks pass between an event and your review, the coaching conversation is less effective. The driver has moved on. The context is cold. The feedback feels punitive instead of instructive.
Review within 48 hours of flagging. While the incident is fresh.
Mistake 2: Using DriveCam only for discipline. Some agencies review DriveCam footage only when something goes wrong or when there’s a claim. They miss the opportunity to review good driving and reinforce safe practices.
Review good driving too. Tell a driver: “I watched your call yesterday. The way you positioned yourself and the approach you took to that intersection was textbook safe. That’s what I want to see more of.”
This reinforces safe behavior and creates a culture where DriveCam is seen as feedback, not punishment.
Mistake 3: Not addressing patterns. DriveCam is most valuable for identifying patterns. A single close call by a generally safe driver is different than a pattern of close calls by someone.
Track which drivers are flagged repeatedly. That pattern suggests a coaching need or a training gap. But you only see the pattern if you’re actually tracking it.
Mistake 4: Inconsistent categorization. Different supervisors categorize the same event differently. One says it’s at-risk behavior requiring coaching. Another says it’s unsafe behavior requiring discipline.
Your response framework prevents this by making categories explicit and trainable.
Making It Work
To implement a structured DriveCam response process:
First: Define your categories and responses. Don’t leave it to supervisor judgment. Write down what observation, at-risk, unsafe, and reckless look like in your context. Write down what response each gets.
Second: Train supervisors. Walk through real examples. Show how to categorize. Walk through what coaching looks like.
Third: Review events systematically. Set up a process where flagged events are reviewed within 48 hours. Assign responsibility.
Fourth: Document responses. Whether it’s an observation or a coaching conversation, document what you found and what you did.
Fifth: Track patterns. Monitor which drivers are getting flagged and how often. Patterns are data.
What Gets Better
With a structured approach:
Drivers see consistency. That fairness improves morale and safety culture.
You actually use the DriveCam data for improvement instead of just having a system that collects footage.
Your coaching conversations improve safety behaviors because they’re happening in the right tone, at the right time.
Your escalations (when needed) are defensible because they’re part of a documented process.
The Bottom Line
DriveCam footage is powerful. But only if you respond to it systematically. Create a framework that categorizes events consistently and defines what response each category gets. Coach early and often. Escalate when necessary. Track patterns so you can see what’s actually happening with your fleet.
That transforms DriveCam from a collection tool into a safety tool.
Ryan Wogan Wogan Solutions