Knowella

Vehicle Incident Report Template

Vehicle incidents are reported by the person most exposed to consequences from reporting them, frequently alone, at the roadside or in a yard, under time pressure. The design problem is that the information most useful for prevention is the information the driver has least incentive to volunteer.

KnowSafeRecordSAF-007Pinned in navigationFull guide
Captured at
The scene, by the driver
Design problem
Reporting has a cost

Summary

In short

  • Damage-only events are the leading indicator and the ones least likely to be reported, because reporting costs the driver something and produces nothing visible.
  • Record potential severity alongside actual. A mirror clipped at a pedestrian crossing point and a mirror clipped in an empty yard are the same damage and different events.
  • Capture the scene at the scene. Position, damage, road or yard conditions, sightlines and marks cannot be reconstructed once vehicles have moved.
  • Powered industrial trucks were among OSHA's ten most cited standards in fiscal year 2025, and site vehicle incidents deserve the same rigour as road ones.
  • Repeat locations matter more than repeat drivers. Where several drivers hit the same corner, the corner is the finding.
  • A report that leads only to driver retraining will not reduce recurrence where the cause was layout, scheduling or sightlines.

What it is

What it is

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.

When to use it

When to use it, and when not to

This captures a vehicle event. Investigation, claims and driver management are separate processes.

Use it for

  • 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

Not 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

Standards

What it is built against

Vehicle incidents fall under road traffic law, workplace transport duties and, on site, equipment standards.

ClauseRequirementWhere it lands
29 CFR 1910.178(l)(4)Refresher training and evaluation after an accident or near miss involving a powered industrial truckFollow up
29 CFR 1910.178(q)Trucks in unsafe condition removed from service until restoredImmediate response
ISO 39001 cl.6.1Road traffic safety risk and performance factors, informed by incident dataCircumstances
ISO 45001 cl.10.2Incident investigation to determine causes and the need for corrective actionFollow up
FMCSA 49 CFR 390.15Accident register and retention of required records for commercial vehicle accidentsEvent
RIDDOR (GB)Reporting of specified injuries and dangerous occurrences, including certain vehicle eventsSeverity and potential
HSE HSG136Workplace transport guidance including investigation of site vehicle incidentsWhere
ISO 45001 cl.8.1.4Contractor coordination, covering visiting drivers and their vehiclesVehicle 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.

Filling it in

Filling it in well

Capture at the scene, record potential as well as outcome, and read locations before drivers.

Capture the scene while it exists

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.

Record potential severity separately

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.

Record location precisely enough to aggregate

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.

Separate reporting from consequence

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.

Audit findings

Common audit findings

Vehicle findings concentrate on reporting behaviour and on location analysis.

FindingClauseWhat fixes it
Damage routinely discovered at inspection rather than reported.ISO 45001 cl.10.2The reporting process is the finding; remove the cost to the reporter.
Potential severity not recorded.ISO 45001 cl.10.2Record what could have happened; damage cost is a poor proxy for seriousness.
Location recorded too vaguely to aggregate.ISO 39001 cl.6.1Record the specific point; clustering is where the actionable findings are.
Site vehicle incidents handled outside the fleet process.1910.178Apply 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.2Where 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.4Include them; they involve the least familiar drivers in your yard.
Photographs not taken before vehicles moved.ISO 45001 cl.10.2Capture at the scene; positions and marks cannot be reconstructed.
Near misses and sudden avoidance not reported at all.ISO 39001 cl.6.1These are the leading indicator and carry no damage to prompt a report.

Worked case

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.

Definitions

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

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.

The agents

What the agents do with it

The report is written at the scene by the person involved. What fails is the reporting cost and the location detail nobody aggregated.

KnowFleet

Captures the report at the scene with photographs and precise location, records potential alongside outcome, and covers site and road vehicles alike.

Ella

Plots incidents by location and surfaces clustering, turning repeated driver conversations into a single design finding.

KnowSafe

Applies potential severity classification and routes serious potential events for investigation proportionate to what could have happened.

KnowMaintain

Removes damaged vehicles from service until restored, and connects infrastructure damage to repair and protection work.

This template lives in KnowSafesafety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.

Meet KnowSafe

Sources

Sources

  • 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

KnowSafe

Also in Incidents

6Browse the whole library
Record

Incident Report

Records any unplanned event that caused harm, damage or loss. Raised as soon as the scene is safe and everyone has been cared for. Completed by the person involved or their supervisor. Carries a case ID that runs through investigation, actions and closure.

Record

Near Miss Report

Records something that could have caused harm but did not. Raised straight away, while the detail is fresh. Completed by anyone who saw it. Near misses with high potential get the same investigation as a real injury, because the only difference was luck.

Record

First Aid Report

Records a minor injury treated on site with no further medical care needed. Completed at the time of treatment by the first aider. Captures what happened, the treatment given and the body part affected. Feeds the same trend analysis as more serious injuries.

Record

Medical Treatment Report

Records an injury needing treatment beyond first aid. Completed by the supervisor once the worker has been seen. Captures treatment, provider and time away from the task. Drives regulatory reporting and links to the health case that follows.

Record

Lost Time Report

Records an injury that keeps a worker away from work beyond the day it happened. Completed by the supervisor with HR. Captures days lost, restrictions and expected return. Requires a full investigation and links to return to work planning.

Record

Property Damage Report

Records damage to equipment, buildings or stock where nobody was hurt. Raised as soon as the damage is found. Completed by the supervisor of the area. Links to the asset affected and to any repair work order, so cost and cause sit together.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.