Near-Miss Report Form and Log

What is a near miss in a vehicle fleet?

A near miss is a situation that almost ended in a collision, injury or damage, and did not, thanks to late braking, someone paying attention or plain luck. A truck reverses while a worker walks behind it and stops a meter away. A pallet slides inside the box on a bend and does not fall.

A near miss leaves no visible damage, so the fleet office only hears about it if the driver reports it. A near-miss report form makes that report easy: one page, filled in a few minutes, with no need to name who was at fault.

Why does near-miss reporting matter?

Near misses and real accidents often share the same causes: a tight schedule, a yard with no pedestrian walkway, a missing item on the daily check. The difference is that a near miss shows the cause without anyone paying for it. Fix the cause and the same situation is less likely to come back with a worse outcome. To estimate what a real accident could have cost, use the Road Accident Cost Calculator.

Near misses also happen more often than accidents, so they give you more data, earlier, on where and what the hazards are. The idea of a "safety pyramid" is often quoted: serious accidents sit on a wider base of minor incidents and near misses. The ratios usually attached to that pyramid vary between studies and are still debated, so use the idea and do not base decisions on the numbers.

Reporting only works if drivers trust that a report will not be used against them. That is why the form says plainly that it is not used for discipline, allows anonymous reports, and asks for what happened rather than who was to blame.

How do you set up near-miss reporting, step by step?

1. Announce the no-blame rule in writing before you hand out the form, and say where to hand it in: the supervisor, a box at the depot, or a photo sent to the safety officer.
2. Keep the form in every vehicle and ask drivers to fill it in the same working day, while the details are fresh.
3. Log every report in the Excel log when it arrives, even before review starts. The review window counts from the report date.
4. Review the report with the 5 whys until you reach a cause you can fix, then set the corrective action, its owner and its due date.
5. Close the report and tell the reporter the outcome, and go through the monthly summary at the safety meeting to see which categories and locations repeat.

Which near-miss categories does the form use?

The driver ticks one or more categories. The same categories are in the drop-down on the log, so the summary counts reports by them:

How do you find the root cause with the 5 whys?

Ask "why?" about the event, then about the answer, and so on until you reach a cause a specific action can fix. Five is a rule of thumb; you may get there at the third why. An example from the brake report in the log:

1. Why did the vehicle nearly collide at the gate? The brakes were weak.
2. Why were they weak? The brake pads were worn.
3. Why was the wear not found? The daily check does not cover brakes.
4. Why does it not cover them? The checklist was written for light vehicles and never updated for trucks.

The root cause is an incomplete checklist, not a careless driver. The corrective action is to repair the vehicle and add brakes to the daily checklist, owned by the workshop manager.

How does the Excel log calculate status and the rate per 100,000 km?

The as-of date is today unless you type a fixed date on the Lists sheet, where the review window is 7 days as an example to change to match your procedure. The yearly rate uses only months with km entered, so it does not drop because one month's km is still missing. A row shows a check message when an anonymous report has a name, when an action has no owner or due date, or when a report is closed with no corrective action.

Worked example: September in the example log

Three reports came in during September 2026: fatigue after a night shift, a child stepping out between two cars at a customer site, and a pallet sliding on a bend. The fleet drove 176,500 km that month (an example figure).

• Rate: 3 ÷ 176,500 × 100,000 = 1.70 near misses per 100,000 km.
• Fatigue report: the action "minimum rest between shifts" was due on 1 October and is not closed, so on 15 October its status is Overdue, with 43 days open.
• Pedestrian report: no action written after 28 days, more than the 7-day window, so its status is Review overdue.
• Load report: the action "extra straps and a short briefing" is due on 10 November, so its status is In progress.

Common near-miss reporting mistakes

• Punishing the reporter. A single penalty after a report can be enough to stop reporting.
• Setting a target to cut reports. More reports after launch usually means drivers have started reporting, not that the risk went up.
• Stopping at "driver error". Ask why the driver made the error: a tight schedule, missing training, or a vehicle unsuited to the route.
• No reply to the reporter. A driver who never hears what changed will not report again.
• Actions with no owner or date. An action nobody owns does not get done, which is why the log flags it.
• Mixing near misses with accidents. An event with damage or injury goes on the Vehicle Accident Report Form and in the Fleet Incident and Claims Log.

What the form does not tell you

The form depends on what drivers notice and choose to report, so it does not measure everything that happens on the road. Report counts are not comparable between two branches with different levels of trust. The rate per 100,000 km shows a trend inside your fleet, not a benchmark against other fleets. Actual accidents and injuries are reported under your incident procedure and your authority's requirements, so check its current requirement. This is a working template, not legal advice.