Driver Incident Investigation

Driver Incident Investigation

The first four hours decide whether an incident can ever be properly investigated — telematics overwritten, the scene cleared, memories consolidated into a story. This gets the evidence secured first, then separates what happened from who was involved, and makes the preventability call against written criteria rather than instinct, because that decision drives insurance, discipline, and whether anyone learns anything.

What This Skill Produces

• The evidence checklist — what to secure immediately, and what is lost if you wait
• A sequence reconstruction — what happened, in order, from evidence rather than recollection
• The preventability determination — decided against stated criteria, with the reasoning recorded
• Contributing-factor analysis — driver, vehicle, route, scheduling, training, and supervision
• Corrective actions — aimed at whichever of those factors actually contributed
• The notification checklist — insurer, regulator, and internal reporting, with their deadlines

Required Inputs

Ask for these if not provided:

• The incident — date, time, location, vehicle, driver, and what is known so far
• Available evidence — telematics, dashcam, ELD or tachograph, maintenance records, and photographs
• The driver's account — taken early, separately, and without leading
• The context — the schedule that day, hours worked, route, weather, load, and any time pressure
• Your framework — the company's preventability criteria and reporting obligations in your jurisdiction

Framework: Secure Evidence, Reconstruct, Then Judge Preventability

1. Secure the perishable evidence first. Telematics and camera footage overwrite on a cycle. Photographs, the load, and the vehicle's condition change within hours. Preserve before you interview.
2. Take the driver's account early and alone. Before it is discussed with colleagues. Ask what happened, not whether they were at fault — and record it verbatim.
3. Reconstruct from evidence, not narrative. Speed, following distance, braking, and timing come from data. Use the account to explain the data, not to replace it.
4. Decide preventability against written criteria. Could a reasonably prudent driver have avoided it, given what they could perceive? Record the reasoning, not just the verdict — this is the part that gets challenged.
5. Look past the driver. Was the schedule achievable? Was the driver fatigued? Was the fault reported before? Was the training adequate? Most incidents have a systemic contributor and blaming the driver ends the investigation prematurely.
6. Act on the actual contributor. Retraining a driver who was awake for sixteen hours because dispatch built the run that way is a corrective action aimed at the wrong thing.
7. Meet the notification deadlines. Insurer and regulator timelines are short and unforgiving.

Output Format

Incident investigation: [ref] · [date] · [vehicle] · [driver]

Incident: [date, time, location, conditions] · Vehicle: [unit, load] · Driver: [name, licence class, tenure] · Injuries: [yes/no, detail] · Third parties: [detail]

Evidence secured — [item · secured by · when] telematics ☐ · camera footage ☐ · ELD/tachograph ☐ · photographs ☐ · maintenance history ☐ · driver qualification file ☐ · police report ☐ · witness details ☐ Anything lost or unavailable: [what, and why]

Driver account: [taken by, when, verbatim summary]

Sequence reconstruction

Preventability determination: ☐ Preventable ☐ Non-preventable Criteria applied: [the written standard] · Reasoning: [why, referencing the evidence]

Contributing factors

Corrective actions: [action · addresses which factor · owner · due]

Notifications: insurer [when] · regulator [if required, when, under what provision] · internal [who]

Not legal advice. Reporting obligations, evidence-retention duties, and the consequences of a preventability determination differ by jurisdiction and by insurer. Involve your insurer and legal counsel early, particularly where there are injuries, and preserve evidence accordingly.

Quality Checks

• Perishable evidence was secured before interviews
• The driver's account was taken early, alone, and recorded verbatim
• The sequence is built from data, with the account used to explain it
• Preventability cites the written criteria and records the reasoning
• Systemic factors — scheduling, fatigue, maintenance, training — were examined
• Corrective actions address the factors actually found
• Notification deadlines were identified and met

Anti-Patterns

• Interviewing before preserving footage. The evidence overwrites while you talk.
• Asking the driver whose fault it was. Produces a defensive account and contaminates the record.
• A preventability verdict with no recorded reasoning. Indefensible on challenge.
• Stopping at driver error. The schedule, the fault report nobody actioned, and the training gap all disappear.
• Retraining as the default corrective action. It is the cheapest action and rarely the right one.
• Missing insurer notification. Can prejudice cover entirely.
• Investigating to assign blame. Guarantees you learn nothing usable.

Example Trigger Phrases

• "Investigate a collision involving one of our trucks"
• "Was this accident preventable?"
• "What evidence do I need to secure after an incident?"
• "Write a post-accident investigation report"
• "Our driver had an accident — what do I do first?"