What this is
What is a vehicle incident report?
What is a vehicle incident report?
A record of any event involving a vehicle: collision, contact with infrastructure, load shift or loss, rollover, pedestrian interaction, or a near miss. It covers the vehicle and driver, the circumstances, the immediate response and the potential severity as well as the actual outcome.
Does it cover site vehicles as well as road vehicles?
It should. Powered industrial trucks, yard shunters, tugs and telehandlers produce a significant share of vehicle incidents, and separating them into a different process usually means the site fleet is analysed less rigorously than the road fleet despite operating around more pedestrians.
Scope
When is a vehicle incident report required?
This captures a vehicle event. Investigation, claims and driver management are separate processes.
Use this template when
- Any collision, contact or near miss involving a vehicle, on the road or on site
- Damage discovered without a reported event, which is itself a reporting finding
- Load shift, load loss or securing failure in transit or during manoeuvring
- Pedestrian interaction, however minor, including sudden avoidance
- Incidents involving visiting drivers and contractor vehicles on your premises
Do not use it for
- The insurance claim, which follows and is driven by cost rather than by cause
- Root cause analysis, applied where the potential warrants it
- Driver competence assessment and licence checks, which address the person
- Vehicle defect reporting, which routes to maintenance
- Journey and fatigue assessments, which address exposure before the event
Compliance mapping
Which WorkSafeBC 16 requirements does this satisfy?
Vehicle incidents fall under road traffic law, workplace transport duties and, on site, equipment standards.
| Clause | Requirement | Where it lands |
|---|---|---|
| 29 CFR 1910.178(l)(4) | Refresher training and evaluation after an accident or near miss involving a powered industrial truck | Follow up |
| 29 CFR 1910.178(q) | Trucks in unsafe condition removed from service until restored | Immediate response |
| ISO 39001 cl.6.1 | Road traffic safety risk and performance factors, informed by incident data | Circumstances |
| ISO 45001 cl.10.2 | Incident investigation to determine causes and the need for corrective action | Follow up |
| FMCSA 49 CFR 390.15 | Accident register and retention of required records for commercial vehicle accidents | Event |
| RIDDOR (GB) | Reporting of specified injuries and dangerous occurrences, including certain vehicle events | Severity and potential |
| HSE HSG136 | Workplace transport guidance including investigation of site vehicle incidents | Where |
| ISO 45001 cl.8.1.4 | Contractor coordination, covering visiting drivers and their vehicles | Vehicle and driver |
What it does not cover
- The insurance claim, driven by cost and liability rather than by cause.
- Root cause analysis, applied proportionately to potential severity.
- Driver licence and competence records, addressing the person.
- Vehicle defect reporting, routing to maintenance and to the defect rectification process.
- Journey and fatigue assessments, which address exposure before the event occurs.
How to complete it
How to complete a vehicle incident report, step by step
Capture at the scene, record potential as well as outcome, and read locations before drivers.
Vehicle positions, damage to both parties, road or yard surface, weather, light, sightlines from the driver's actual position, and any marks. Photographs taken before vehicles move are the only version of this that exists, and every investigation afterwards works from them or from memory.
What could have happened. A collision with a wall and a collision at a point where pedestrians cross are the same repair cost and entirely different events. Without a potential field the analysis is driven by damage value, which correlates poorly with how close someone came to being killed.
Which corner, which bay, which junction, which stretch of route. Vehicle incidents cluster geographically, and precise location is what turns individual reports into a finding about a pillar, a blind corner or a poorly angled bay. Vague location descriptions make that analysis impossible.
Damage-only reporting has to be free of penalty or it stops. The system's value depends on minor events being reported promptly by the people involved, and any process that attaches a cost to that will produce a fleet where damage is discovered rather than reported.
What auditors find
Most common vehicle incident report findings
Vehicle findings concentrate on reporting behaviour and on location analysis.
| Finding | Clause | What fixes it |
|---|---|---|
| Damage routinely discovered at inspection rather than reported. | ISO 45001 cl.10.2 | The reporting process is the finding; remove the cost to the reporter. |
| Potential severity not recorded. | ISO 45001 cl.10.2 | Record what could have happened; damage cost is a poor proxy for seriousness. |
| Location recorded too vaguely to aggregate. | ISO 39001 cl.6.1 | Record the specific point; clustering is where the actionable findings are. |
| Site vehicle incidents handled outside the fleet process. | 1910.178 | Apply the same rigour; site vehicles operate among more pedestrians. |
| No refresher evaluation after a truck incident or near miss. | 1910.178(l)(4) | Refresher training and evaluation are required after an accident or near miss. |
| Corrective action limited to driver retraining. | ISO 45001 cl.8.1.2 | Where several drivers hit the same point, the layout is the cause. |
| Damaged vehicle returned to service without assessment. | 1910.178(q) | Remove from service until restored to safe operating condition. |
| Visiting driver and contractor vehicle incidents excluded. | ISO 45001 cl.8.1.4 | Include them; they involve the least familiar drivers in your yard. |
| Photographs not taken before vehicles moved. | ISO 45001 cl.10.2 | Capture at the scene; positions and marks cannot be reconstructed. |
| Near misses and sudden avoidance not reported at all. | ISO 39001 cl.6.1 | These are the leading indicator and carry no damage to prompt a report. |
Case in point
Case in point: eleven drivers and one pillar
A site recorded a steady low level of vehicle damage in its warehouse, reported reasonably well because the culture was reasonable. Each event was investigated, each concluded with a discussion with the driver about awareness, and each was closed.
A review of two years of reports, plotted by location, found that eleven separate incidents involving nine different drivers had occurred at one structural pillar beside a racking run. The pillar sat just inside a turn from a main aisle, and a driver making that turn with a raised load could not see it until the mast was alongside.
Every investigation had correctly identified that the driver had not seen the pillar. None had asked why nine drivers independently had not seen the same pillar.
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.
7 sections
- Reference
- SAF-007
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Actual and potential severity
- Direction
- High is bad
- Singleton
- No
- Basis
- WorkSafeBC 16, OSHA 1910.178
- Links
- Feeds RCA; links Asset, Worker
- Tags
- Incident, Mobile equipment
- Sections
- 7
- Fields
- 48
- Follow up fields
- 12
- Repeating sections
- 0
- Links out
- 8
Event
4 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 of Event*
Date Reported*
Vehicle and driver
8 fieldsVehicle*
Asset ID*
Format AST-0000.
Links to FDN-002 Asset ID
Operator*
Person ID*
Format PER-0000.
Links to FDN-003 Person ID
Licence Or Authorisation Current*
Checked against the authorisation record, not from memory.
- Yes2 pts
- Expired0 pts
- None held0 pts
Authorisation Record ID
Links to TRN-024 Authorisation ID
Pre-Use Inspection Completed*
- Yes2 pts
- No0 pts
Inspection ID
Links to SAF-028 Inspection ID
Where
4 fieldsSite*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Area*
The area within the site.
Exact Location
Drop a pin for anything hard to find.
Circumstances
12 fieldsDescription*
Collision Type*
Speed Estimate
- Walking pace2 pts
- Moderate1 pt
- Fast for the area0 pts
Load Carried
Visibility*
- Clear3 pts
- Partially obstructed1 pt
- Obstructed0 pts
Floor Or Surface Condition*
- Dry and even3 pts
- Minor defects2 pts
- Wet1 pt
- Damaged or uneven0 pts
Pedestrian Involved*
- No2 pts
- Yes0 pts
Pedestrian
Person ID
Format PER-0000.
Links to FDN-003 Person ID
Segregation In Place
Whether pedestrian and vehicle routes were physically separated at this point.
- Physical barrier3 pts
- Marked walkway only1 pt
- None0 pts
Photographs
Damage Description
Severity and potential
6 fieldsSeverity Guidance
Mobile equipment events are a leading cause of workplace fatalities. Rate potential against what a slightly different position would have meant.
Actual Severity*
- No injury4 pts
- First aid3 pts
- Medical treatment2 pts
- Lost time1 pt
- Fatality0 pts
Maximum Potential Loss*
The worst credible outcome had circumstances been slightly different.
- Minor4 pts
- Moderate3 pts
- Serious2 pts
- Fatal or catastrophic0 pts
Investigation Required*
Set by potential outcome, not by what actually happened.
- No3 pts
- Yes0 pts
Investigation Level
RCA ID
Format RCA-2026-00000.
Links to FDN-013 RCA ID
Immediate response
8 fieldsImmediate Action Taken*
What was done to make the area safe before anyone left.
Area Made Safe*
Scene Preserved
Work Stopped
Reportable To Regulator*
- No3 pts
- Yes0 pts
Regulator
Notification Reference
Links to SAF-010 Notification ID
Notification Made
Follow up
6 fieldsAction 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
Supervisor*
Signature*
SAF-007 · record IDs look like CASE-2026-000 · Feeds RCA; links Asset, Worker
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The report is written at the scene by the person involved. What fails is the reporting cost and the location detail nobody aggregated.
Captures the report at the scene with photographs and precise location, records potential alongside outcome, and covers site and road vehicles alike.
Plots incidents by location and surfaces clustering, turning repeated driver conversations into a single design finding.
Applies potential severity classification and routes serious potential events for investigation proportionate to what could have happened.
Removes damaged vehicles from service until restored, and connects infrastructure damage to repair and protection work.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Vehicle Incident Report definitions and key terms
- Potential severity
- What the event could have caused had circumstances differed, recorded alongside the actual outcome.
- Damage-only incident
- An event causing damage but no injury, the leading indicator most sensitive to reporting culture.
- Location clustering
- Concentration of incidents at specific points, which converts individual events into a design finding.
- Sightline
- What the driver could actually see from the operating position, frequently different from what is visible on foot.
- Refresher evaluation
- The retraining and workplace performance evaluation required after a powered industrial truck accident or near miss.
- Load shift
- Movement of a load in transit or during manoeuvring, indicating a securing or distribution failure.
- Accident register
- The record commercial motor carriers must maintain of accidents meeting defined criteria.
- Blind corner
- A turn where the sightline is obstructed, particularly by racking, structure or a raised load.
FAQ
Frequently asked questions about vehicle incident report
Why does damage-only reporting matter so much?+
Because it is the leading indicator and it is the most sensitive to how reporting is treated. Where a damage report costs the driver a conversation, a record or a bonus effect, reporting stops, and damage is discovered at inspection weeks later with no information about how it happened. A fleet where damage is found rather than reported has lost its early warning.
Should potential severity be recorded?+
Yes, separately from damage. A vehicle striking a wall and a vehicle striking a wall at a point where people cross are identical repair costs and entirely different events. Analysis driven by damage value systematically under-ranks the events that came closest to killing someone.
What is the most valuable analysis?+
Plotting incidents by precise location. Vehicle incidents cluster geographically at specific corners, pillars, bays and junctions, and once plotted the pattern is usually immediate. It converts a series of individual driver conversations into one barrier, one mirror or one layout change.
Do site vehicles need the same rigour as road vehicles?+
They generally need more, because they operate among pedestrians continuously. Powered industrial trucks were among OSHA's ten most cited standards in fiscal year 2025, and 1910.178 requires refresher training and evaluation after an accident or near miss, which is a specific obligation many sites do not apply.
What should be captured at the scene?+
Positions before anything moves, damage to both parties, surface and weather, light conditions, and sightlines photographed from the driver's actual seated position rather than from standing. That last one repeatedly shows that an obstruction visible on foot was not visible from the cab, which no later reconstruction will establish.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Incident and Investigation
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Finding
Records a single deficiency picked up during an audit, inspection or check
Effectiveness Verification
Checks whether an action actually worked, some time after it was put in place
Just Culture Determination
Separates a system problem from a genuine choice to take a risk, using a consistent set of questions
Extent of Condition Review
Asks two questions after an investigation: where else does this same condition exist, and where else could this same cause bite us
More in Incidents
Incident Report
Records any unplanned event that caused harm, damage or loss
Near Miss Report
Records something that could have caused harm but did not
First Aid Report
Records a minor injury treated on site with no further medical care needed
Medical Treatment Report
Records an injury needing treatment beyond first aid
Lost Time Report
Records an injury that keeps a worker away from work beyond the day it happened
Property Damage Report
Records damage to equipment, buildings or stock where nobody was hurt
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:
- 29 CFR 1910.178, powered industrial trucks, including refresher training triggers, OSHA
- ISO 39001, road traffic safety management systems
- 49 CFR 390.15, accident register requirements, FMCSA
- HSE HSG136, workplace transport safety (GB)
- ISO 45001:2018 clauses 10.2 and 8.1.4
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.