An incident reporting protocol a fleet can actually run

What the driver does at the scene, what the company files, what evidence is kept and for how long, and who is allowed to talk to whom. Written as a clock, because every item on it has a window that closes.

Updated September 13, 2026 Beginner

Every item in a reporting protocol has a window, and the windows are not the same length. The photographs close in minutes, when the vehicles are moved. The other driver’s cooperation closes in hours. The dashcam closes when the loop comes round. The driver’s memory closes in days and nobody notices it happening. A protocol is therefore a clock rather than a list, and it is written below in that order.

Injuries, hazard, emergency services where they are needed, the vehicle made safe. Whatever the local law requires of a driver at a collision — remaining, reporting to police, exchanging particulars — is the floor, and it is not the company’s to negotiate. What the company adds at this point is one instruction and it is a restraint: nothing about fault, from anyone, including apologies that sound like admissions. A driver saying “I didn’t see you” is not being dishonest, and it will be quoted back.

The first ten minutes: the photographs nobody can retake

Position before movement, if it is safe to stand there. The road as the driver saw it approaching, from the driver’s seat height. Both vehicles whole, then the damage close. The other vehicle’s plate and, if there is a business name on it, that too. Skid marks, debris, the state of the surface, the signals and signs, the weather as the light shows it.

This set exists because the scene is destroyed within minutes of the vehicles being moved and is never reconstructible. A driver who photographs their own damage and nothing else has recorded the least contested fact of the entire file.

The first hour: notification inward, details outward

One number to call, staffed, and the driver knows it without looking. A protocol that routes the call to a line manager who might be driving has a hole in it at the exact moment it is needed.

What the driver collects is the other party’s name, contact, insurer and policy reference, the plate, and whether anyone else was in either vehicle. What the driver gives is the reciprocal minimum, which the law requires anyway. What the driver does not give is a view on liability, a statement to another party’s insurer, or a signature on anything.

Witnesses are a first-hour item because they leave. A name and a telephone number written down at the kerb is worth more than anything else a driver brings back, because it is the one item nobody can obtain afterwards.

The same day: the account, the hold, the notice

The account is written while the day is still the day, by the driver, in the driver’s own words, and it is not improved afterwards. The awkward details stay in. What time, where, which lane, speed, what the driver saw and when, what was said, who else was there, whether anyone mentioned pain.

At the same time the evidence is frozen. Someone named — not “the fleet team” — exports the dashcam clip and the trip data for that vehicle and puts them somewhere the systems that recycle them cannot reach. This is the step most protocols omit and the one that is irrecoverable when omitted, because the footage is gone on a schedule that has nothing to do with the claim.

The company’s own file is opened the same day too, and it is not a copy of the insurer’s. It holds what the insurer has no interest in: which route and which assignment, who authorised the driver to be in that vehicle, the vehicle’s last inspection, the cost the incident is generating in labour and lost work, and whether the driver has been here before. That record is what makes an incident readable later as something other than bad luck, and it is what answers an allegation that the company put an unfit driver or an unfit vehicle on the road. A fleet keeping only the insurer’s paperwork has documented the claim and not the incident.

Then first notice to the insurer or broker, the same day. Whether the insurer owes an acknowledgement or a decision within a stated period is in the rules for your jurisdiction below. Whether late notification itself has consequences depends on the applicable rules and the policy, and this page asserts neither.

The following week: who talks to whom

One named contact for the file, and everyone else declines politely. Third-party insurers and claims agents will approach the driver directly, and a driver who is helpful in that conversation can undo the day’s careful documentation in ten minutes. This is not about concealment; it is that an account given once, in writing, on the day, is better evidence than a version reconstructed conversationally a week later, and both cannot be the account.

Internally, the driver is debriefed rather than interrogated, and the distinction is operational rather than kind: a driver who expects a disciplinary conversation reports less next time, and a fleet’s information supply depends entirely on drivers telling it things it would rather not hear.

The weeks after: the tail

Injury claims arrive late. A file closed internally after a repair is a file with no live owner when a letter arrives months later, and the letter will be answered by whoever happens to open it.

Retention is the unresolved part of this, and it is unresolved because the fleet is pulled two ways at once. One pull is evidential: the records are worth having for as long as anything can still be claimed, and the day they are needed is not a day anyone can predict. The other is that the same records are about identifiable people, including people who never worked for the fleet and were simply on the road at the time. We do not tell you how that is settled where you operate, because it is settled by rules we have not read and it is the one part of this protocol that needs local advice rather than a general answer. What is inside the fleet’s own gift is to decide it deliberately and write the decision down, instead of letting a system’s default recycling schedule decide it by accident.

What this protocol is for

Not compliance. A fleet that runs this sequence is buying one thing: the ability to answer, months later, with contemporaneous documents rather than recollection. Every disputed claim resolves in favour of whichever party has dated evidence of the ordinary facts — where the vehicles were, how fast, what was said, who was there — and those facts are cheap on the day and unobtainable afterwards.

The part that decides whether any of it happens is the part nobody writes down: the driver has to be able to run it while shaken, at the roadside, without reading anything. Which means the protocol has to be short enough to have been learned, rehearsed once at induction, and carried in the vehicle in a form that survives being wet.


Appendix — the driver’s card. Kept in the vehicle, one side of one card. Safety first, emergency services if anyone may be hurt. Say nothing about fault. Photograph the position before moving, then the road ahead from the driver’s seat, then both vehicles, then the damage, then the other plate. Collect name, phone, insurer and policy reference; give yours. Take any witness’s name and number. Call the incident number before leaving the scene. Write your own account the same day, in your own words. Refer any other insurer or agent to the company contact.

Rules in your jurisdiction

Deadlines, fault rules and minimum coverage differ by state and country. Pick yours to see the rules that apply to this topic.

Select a jurisdiction to see its rules.

Frequently asked questions

The other driver's insurer called our driver directly. Should he talk to them?

Not without the company knowing, and as a matter of protocol not at all. A third-party insurer calling a driver is gathering a recorded account from the person least prepared to give one, days after the event, with no note of what was asked. The courteous answer is to refer them to the single contact the company has nominated, and the company's own insurer will normally tell you to do exactly that. It is not obstruction: the account has already been given, in writing, on the day.

How long should we keep dashcam footage and telematics data after an incident?

Longer than the system's default, which is the whole problem. Footage loops and overwrites on a cycle measured in days, and telematics detail is often thinned to summaries after a short window, so the practical step is a preservation hold placed the same day — a named person exports the clip and the trip record for that vehicle and stores them outside the system that recycles them. How long the export may then be retained is a data-protection question rather than an insurance one, and the answer depends on where you operate and on what the footage shows of people who are not your drivers.

Does a driver have to write a statement when nothing seems to have happened?

Yes, and the low-consequence incidents are exactly where it pays. A note taken on the day of a contact with no visible damage is what answers a claim that arrives months later describing an injury. It costs a few minutes on the day; reconstructing the same account from memory after a solicitor's letter is not possible, and its absence is read as though nothing occurred.