Collisions and Incidents
The situation where location and telematics data is genuinely valuable, and the handling that keeps it usable.
After a collision the data answers questions nobody can answer from memory, and this is the use that most justifies the system to drivers themselves.
What it establishes
Where the vehicle was, and when.
Speed before the event, where the device reports it.
Braking and impact, on units with accelerometers.
Whether the vehicle was stationary, which resolves a substantial share of disputed claims.
Insurers value this, and it protects drivers from false allegations at least as often as it establishes fault.
Preserving it
Place a hold immediately, before routine deletion runs.
Which means a hold mechanism has to exist, scoped to a vehicle and period, surviving the retention schedule.
Export a copy and record who did, when.
Note the accuracy figures, because an insurer's engineer will ask and an unqualified speed figure will be challenged.
Telling the driver
They are entitled to know the data is being used and generally to see it.
Tell them at the time, not after a decision has been made.
Share the export with them, which is both fair and what prevents a dispute about the process rather than the facts.
A driver who learns their data was used against them without being told will be right to object, and the objection will be about the handling.
Reading it carefully
Speed derived from position over short intervals carries substantial error. Where speed matters, use the device's own speed reading if it has one, and state the method.
A single fix is not a trajectory.
Impact detection thresholds vary and produce false positives on potholes and kerbs.
Which means the data supports an investigation rather than concluding one, and presenting it as conclusive is how it gets discredited.
Near misses
Worth capturing deliberately, because they are the cheap version of the lesson.
A driver-reported near miss with the location data attached produces a better picture than either alone.
Only works if reporting is safe — a driver who expects a score penalty will not report.
Which is the argument for keeping incident reporting separate from any behaviour scoring, and saying so.
What to review
Collisions and near misses per distance, trended.
Locations that recur, which is a route or site finding rather than a driver one.
Whether the data was preserved and shared each time, which is a process check.
And whether anything changed as a result, because an investigation that produces no change teaches everyone that reporting is pointless.
Share the export with the driver
At the time, not after a decision.
They are generally entitled to see the data used about them.
Giving it unprompted removes a whole category of dispute — the one about the process rather than the facts.
Include the accuracy figures, so they can assess it as you did.
A driver who learns afterwards that their data was used against them will object to the handling, and will be right.
Check the difficult case
Use this project connection to frame one representative test for this issue. The useful evidence is the record created when a worker challenges an event, a manager reviews it and an administrator exports it.
Independent reference
For an external point of reference, see the Health and Safety Executive. Use official workplace-safety guidance alongside location evidence when defining incident response.