What this is
What is a road near miss?
What is a road near miss?
An event on the road that had the potential to cause injury or damage but did not, separated from a collision only by timing, margin or another party's reaction. It includes hard braking and swerving, conflicts with pedestrians or cyclists, load movement and unexpected vehicle behaviour.
How does a near miss differ from a defect or a breakdown?
A defect is a condition found on the vehicle; a breakdown is a loss of function. A near miss is a dynamic event involving the vehicle, the driver, the road and often a third party. The same faulty brake can produce all three records, and each one answers a different question.
What does potential severity mean here?
It is the outcome the event could reasonably have produced had the margin been smaller, not the outcome it did produce — which by definition was nothing. Scoring on potential is what allows a no-damage event to be prioritised above a minor kerb strike.
Scope
When is a near miss road report required?
This record covers the close call that produced no collision, no injury and no damage. The moment any of those exist, the event belongs in a different template — and the reporting duties change with it.
Use this template when
- A driver braked hard, swerved or took evasive action to avoid contact
- A conflict occurred with a pedestrian, cyclist or other vulnerable road user without contact
- The load shifted or behaved unexpectedly without damage to it or to the vehicle
- A hazard was encountered at a customer site, yard or junction that could have caused an incident
- Telematics flagged a harsh event and the driver can describe what actually happened
Do not use it for
- Road Collision Report, which covers events where contact occurred; once there is damage or injury the reporting and insurance duties are different
- Roadside Breakdown Record, which records a loss of function and its recovery rather than an avoided event
- Cargo Damage Report, which is for damage discovered in transit or at delivery; a load shift with no damage stays here
- Vehicle Defect Report, which records a condition found on the vehicle and should be raised alongside this record, not instead of it
- Speeding Event Record, which is a telematics conduct record; folding conduct management into near-miss reporting is the fastest way to stop reports arriving
Compliance mapping
Which ISO 39001 requirements does this satisfy?
ISO 39001 is a management system standard for road traffic safety, so its requirements attach to the system this record feeds rather than to the individual event. The mapping below shows which part of the system each section serves.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 39001:2012, Clause 6 | The organisation must identify the road traffic safety performance factors it can influence, including speed, fatigue, route and road conditions. | Contributing factors |
| ISO 39001:2012, Clause 8 | Operational planning and control must extend to the road use the organisation directs, including third-party sites it delivers into. | Location and pattern |
| ISO 39001:2012, Clause 9.1 | Road traffic safety performance must be monitored and measured, with leading indicators as well as outcome data. | What happened |
| ISO 39001:2012, Clause 10 | Events must be examined, action taken to prevent recurrence and the effectiveness of that action reviewed. | Follow up |
| Health and Safety at Work etc. Act 1974, s.2 | Employers owe a general duty to ensure the health and safety of employees, which extends to work-related driving. | Follow up |
| Health and Safety at Work etc. Act 1974, s.3 | The duty extends to persons not employed who may be affected — pedestrians, cyclists and other road users. | What happened |
| Heavy Vehicle National Law, s.26C | Each party in the chain of responsibility must so far as reasonably practicable ensure the safety of its transport activities, including schedules that induce speed or fatigue. | Contributing factors |
What it does not cover
- A telematics harsh-braking alert, which records that the vehicle decelerated but not what the driver saw, avoided or expected — the event without the explanation.
- A verbal mention at a driver briefing, which leaves no location, no time and nothing that can be counted against the same junction next month.
- A report with no potential severity, which cannot be ranked and so is triaged by how vividly it was written rather than by what it could have caused.
- A near miss logged as a collision with no damage, which contaminates your collision rate and hides the leading indicator inside the lagging one.
- A closed report with no learning shared, which spends the driver's goodwill for reporting and returns nothing, guaranteeing fewer reports next quarter.
Global
Near Miss Road Report requirements by country
Road events sit awkwardly between road traffic law and workplace safety law, and the boundary moves by country. These three determine whether your near-miss data is voluntary, expected or effectively obligatory.
ISO 39001:2012, Road traffic safety management systems
A certifiable management system standard built explicitly around leading performance factors rather than crash counts.
The Contributing factors section is written to the standard's performance-factor list. If you are certified or being audited by a customer to this standard, near-miss data is the evidence that the factors are actually being monitored.
Health and Safety at Work etc. Act 1974 and RIDDOR 2013
Work-related driving is squarely inside the general duties, but most road traffic accidents are excluded from statutory RIDDOR reporting.
The gap is the point. Because road events rarely generate a statutory report, your internal near-miss record is often the only contemporaneous evidence that a risk was known and acted on.
Heavy Vehicle National Law, Chain of Responsibility
Duties reach beyond the driver to schedulers, consignors and customers whose demands shape how the journey is driven.
Time Pressure A Factor and Customer Site Involved are chain-of-responsibility fields. A pattern of time-pressure near misses is evidence about the schedule and the customer, not about the driver.
How to complete it
How to complete a near miss road report, step by step
The form is designed to be finished in under two minutes. Four judgements decide whether those two minutes produce something defensible.
Potential Severity should be set against a plausible worse version of the same event — same junction, same speed, one second less margin — not against the worst imaginable outcome and not against what actually happened. Systematic under-rating buries the events worth investigating; systematic over-rating makes every report a fatality and destroys the ranking.
Third Party Behaviour, Road Or Infrastructure Factor, Weather Or Light Factor and Our Vehicle Factor can all be Contributed at once, and usually more than one is. Resist the pull to name a single primary cause so the record can be closed. Marking a third party as primary cause does not remove the question of what the driver could still have had available.
Recurring Location is a judgement the driver often cannot make alone — they may only know their own trips. Set it at supervisor review against Exact Location and the existing reports, and treat a Yes as an obligation to look at routing, timing or the site rather than at the individual event.
Where Customer Site Involved is Yes or an infrastructure hazard is identified, Raised With Customer Or Authority forces a decision about escalation. Recording a known hazard at a customer's yard for eighteen months without raising it is a worse position than never having noticed it — the record proves the knowledge.
What auditors find
Most common near miss road report findings
These findings recur wherever road near-miss reporting has been running long enough to be audited.
| Finding | Clause | What fixes it |
|---|---|---|
| Reporting volume fell steadily and was reported upward as improved safety performance | ISO 39001:2012, Clause 9.1 | Track report rate as a participation measure, not a safety outcome. Investigate a falling rate, and check No Adverse Consequence For Reporting is genuinely being confirmed. |
| Repeated hard-braking events at one roundabout, each closed individually | ISO 39001:2012, Clause 8 | Report on Exact Location as a cluster before closing individual records; a Recurring Location Yes should open a routing or infrastructure action, not a driver coaching note. |
| Time pressure named in a dozen reports with no change to the schedule | Heavy Vehicle National Law, s.26C | Route Time Pressure A Factor results to whoever owns the schedule, and review them alongside hours-of-service data rather than inside the incident file. |
| A known hazard in a customer's yard never raised with the customer | Health and Safety at Work etc. Act 1974, s.3 | Make Raised With Customer Or Authority mandatory whenever Customer Site Involved is Yes, with the escalation date recorded. |
| Near misses logged but never fed back to drivers, so the same conflict recurred | ISO 39001:2012, Clause 10 | Use Shared As Learning and Discussed At Driver Briefing as closure conditions; a report that returned nothing to the crew is not closed. |
| Telematics events and driver reports held in separate systems with no reconciliation | ISO 39001:2012, Clause 9.1 | Capture Telematics Event Recorded on every report and reconcile weekly; unreported telematics events indicate where reporting confidence is weakest. |
Case in point
Case in point: the junction that everybody knew about
A chilled distribution operator introduced near-miss reporting and got seven reports in the first quarter, four of them at the same left turn out of a customer's yard — poor sightlines, a cycle lane, and a delivery slot that put trucks there at school-run time. Each report was closed with a coaching note to the driver concerned, because that was the fastest way to close it.
In the fourth month a cyclist was struck. The investigation found the four earlier reports, all with Exact Location within thirty metres of each other, all with Recurring Location left at No because each driver only knew their own trip. The routing change made afterwards took an afternoon. The evidence for it had existed for three months and was never read as a set.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- FLT-017
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Potential severity
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 39001
- Links
- Feeds RCA, coaching
- Tags
- Fleet, Incident, Leading
- Sections
- 5
- Fields
- 48
- Follow up fields
- 4
- Repeating sections
- 0
- Links out
- 4
Header
20 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Completed By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Exact Location
Drop a pin. Roadside events rarely have a useful address.
Vehicle*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Unit Number
The number painted on the door, which is what drivers actually use.
Driver*
Person ID*
Links to FDN-003 Person ID
Licence Class
The Ones That Cost Nothing
A near miss on the road is the same event as a collision with better timing. Drivers who report them are the ones you want, so make it quick and never punitive.
Trip Or Route Reference
Origin
Destination
Odometer Reading
Load Carried
Chilled, frozen, ambient, mixed temperature, dangerous goods or empty.
Customer Or Site
What happened
6 fieldsEvent Type*
Near collision, swerve or hard brake, pedestrian or cyclist conflict, load shift, or vehicle behaviour.
Time Of Event*
Description*
How Close*
- Some margin2 pts
- Close1 pt
- Very close0 pts
Potential Severity*
- First aid4 pts
- Medical treatment3 pts
- Lost time2 pts
- Serious injury1 pt
- Fatality0 pts
Telematics Event Recorded
- Yes3 pts
- No1 pt
Contributing factors
6 fieldsThird Party Behaviour*
- Not a factor3 pts
- Contributed1 pt
- Primary cause0 pts
Road Or Infrastructure Factor*
- Not a factor3 pts
- Contributed1 pt
- Primary cause0 pts
Weather Or Light Factor*
- Not a factor3 pts
- Contributed1 pt
- Primary cause0 pts
Our Vehicle Factor*
- Not a factor3 pts
- Contributed0 pts
- Primary cause0 pts
Fatigue A Factor*
- No3 pts
- Possibly1 pt
- Yes0 pts
Time Pressure A Factor*
Schedules that only work if nothing goes wrong show up here first.
- No3 pts
- Possibly1 pt
- Yes0 pts
Location and pattern
5 fieldsRecurring Location*
Several reports at the same junction or yard is actionable intelligence.
- No3 pts
- Yes0 pts
Customer Site Involved*
Customer Site Hazard
Raised With Customer Or Authority
- Yes3 pts
- No0 pts
Route Change Recommended*
- No3 pts
- Yes1 pt
Follow up
11 fieldsShared As Learning*
- Yes3 pts
- No0 pts
Discussed At Driver Briefing*
- Yes3 pts
- No0 pts
No Adverse Consequence For Reporting*
- Confirmed3 pts
- Not confirmed0 pts
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Driver*
Signature*
Transport Supervisor*
Second Signature*
FLT-017 · record IDs look like CASE-2026-000 · Feeds RCA, coaching
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Near-miss reporting fails on the follow-through: reading reports as a set, routing a schedule finding to whoever owns the schedule, and closing the loop back to the crew who reported.
Holds the report against vehicle, driver and route, clusters events by location and factor, and keeps the telematics reconciliation alongside the driver's own account.
Runs the potential-severity triage, escalates the high-potential events to investigation, and keeps near-miss rate reported as a participation measure rather than a safety score.
Takes the time-pressure and customer-site findings into scheduling and network decisions, where a recurring near miss becomes a routing or slot change.
Surfaces repeat locations before the fifth report, chases the learning-shared loop back to the crew, and holds every write for your approval before it touches a record.
This template lives in KnowFleet — fleet and transport. Drivers, vehicles, hours, cargo securement and operator licence compliance.
Meet KnowFleet→Glossary
Near Miss Road Report definitions and key terms
- Near miss
- An unplanned event that had the potential to cause injury or damage but did not, distinguished from a collision only by margin, timing or another party's reaction.
- Potential severity
- The outcome an event could reasonably have produced under slightly worse conditions, used to rank events whose actual outcome was nothing.
- Leading indicator
- A measure that moves before harm occurs — near-miss rate, telematics events, factor patterns — as opposed to lagging measures such as collision and injury counts.
- Chain of responsibility
- The principle that duties for safe transport extend beyond the driver to schedulers, consignors, customers and operators whose decisions shape the journey.
- Vulnerable road user
- A pedestrian, cyclist, motorcyclist or similar road user with no protective structure, for whom the potential severity of any conflict is disproportionately high.
FAQ
Frequently asked questions about near miss road report
Do we have to report road near misses to a regulator?+
In most jurisdictions, no. Road traffic events are largely excluded from statutory workplace incident reporting, and near misses produce no outcome to report. That is precisely why the internal record matters: it is usually the only contemporaneous evidence that a road risk was identified before it caused harm.
Should a near miss with no damage still be investigated?+
Ones with high potential severity, yes. Investigation effort should follow Potential Severity and How Close, not the presence of damage. An event rated at serious-injury potential deserves more attention than most low-cost collisions in the same period.
How do we stop reporting being used against drivers?+
Keep the report out of the performance process by design, confirm it in the record itself, and demonstrate it. Discussed At Driver Briefing and Shared As Learning are the visible return on reporting. If drivers see their reports produce route or site changes rather than coaching notes, volume rises.
Should telematics events auto-generate reports?+
No. Telematics tells you the vehicle decelerated hard; it cannot tell you what the driver avoided or why. Use it to prompt a report and to reconcile afterwards through Telematics Event Recorded, but keep the driver's account as the record.
What if the third party was entirely at fault?+
Record it as primary cause, and keep going. The useful questions survive fault: was the following distance recoverable, was the driver fatigued, was the light poor, is it the same junction as last month. Fault decides liability, not learning.
How does this record feed a root cause analysis?+
Individually it usually should not. Its value is in aggregate — clusters by location, by factor, by time of day. Escalate a single report to full analysis only where Potential Severity and How Close both sit at the severe end, and let the pattern reports drive the rest.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Fleet and Driver Compliance
Transport Provider Assessment
Assesses a haulier for licensing, driver management, vehicle standards, temperature capability and load security
Driver Vehicle Inspection Report
The pre-trip and post-trip inspection a driver completes on a commercial vehicle
Annual Vehicle Inspection
The yearly statutory inspection of a commercial vehicle
Trailer Inspection
Checks trailer coupling, brakes, lights, tyres, doors and structure
Reefer Unit Check
Checks refrigeration unit operation, fuel, temperature setpoint and alarm history
Vehicle Defect Report
Reports a defect found on a vehicle at any time, not just during a scheduled inspection
More in Road Incidents
Road Collision Report
Records a collision involving a company vehicle on public roads
Roadside Breakdown Record
Records a breakdown on the road, including cause, location and recovery
Cargo Damage Report
Records damage to cargo discovered in transit or at delivery
Post Incident Driver Assessment
Assesses a driver's fitness and competency following a serious incident
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 39001:2012 — Road traffic safety management systems, Clauses 6, 8, 9.1 and 10
- Health and Safety at Work etc. Act 1974 — sections 2 and 3
- RIDDOR 2013 — Reporting of Injuries, Diseases and Dangerous Occurrences Regulations
- Heavy Vehicle National Law — section 26C, primary duty
- HSE INDG382 — Driving at work: managing work-related road safety
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.