For every serious injury on a factory floor there are many smaller events that could have been serious but weren't: a pallet that slipped off the forks, a guard left off and noticed just in time, a chemical splash that missed someone's eyes. These near misses are warnings. Plants that capture and act on them prevent injuries; plants that ignore them wait for the injury to tell them the same thing.
What counts as a near miss
A near miss is an unplanned event that had the potential to cause harm but didn't. It's useful to distinguish it from:
- Unsafe conditions — a hazard that exists but hasn't yet caused an event, such as a damaged floor or a missing guard.
- Unsafe acts — someone working in a way that creates risk.
- Incidents — events that did cause injury, illness or damage.
Many plants collect all of these through the same simple reporting channel and classify them afterwards. What matters is that people report, not that they classify correctly.
Why people don't report
- Fear of blame or discipline — for themselves or a colleague.
- "Nothing happened, so why bother?"
- Reporting takes too long — a long form, a trip to the office.
- Nothing changes after reporting.
- Peer pressure not to slow things down.
Every one of these can be addressed.
Make reporting fast
A report should take a minute or two: what happened, where, when, and a photo if possible. Options include a QR code on notice boards and machines that opens a short form on any phone, a shared tablet in each area, or a simple card dropped in a box and entered by the supervisor. Ask only what's needed to act; details can be collected during follow-up.
Make it blame-free
Leaders set the tone. When a near miss is reported, the first response should be thanks. Investigations should ask what conditions allowed it, not who is at fault. Honest reporting must never lead to discipline; deliberate, reckless violations are a separate matter handled by separate processes. If people see a colleague punished after reporting, reporting will stop overnight.
Triage every report
Someone — often the area supervisor with safety support — reviews each report within a day or two:
- Is there an immediate danger? Make it safe now.
- What is the potential severity — what's the worst credible outcome?
- Does it need a quick fix, or a deeper investigation?
- Who owns the action, and by when?
High-potential near misses — ones that could have caused a fatality or life-changing injury — deserve the same investigation effort as an actual serious injury.
Investigation
For significant near misses, use a simple root cause method such as 5-Why, involving the people who were there. Look beyond the immediate trigger to the underlying conditions: layout, equipment design, procedures, workload, training, maintenance. Actions should address those conditions, using the hierarchy of controls — eliminate, substitute, engineer, administer, then PPE.
Close the loop
The single most important factor in sustaining reporting is feedback. Tell the reporter what was done, ideally in person. Share examples in tier meetings and on notice boards: "You reported, we fixed." When people see their reports lead to real changes, they report more.
Useful metrics
- Number of reports per month, per area — with the goal of steady participation, not zero.
- Percentage of reports with actions closed on time.
- Average time from report to fix.
- High-potential near misses and their investigation status.
- Recurring themes — forklifts, housekeeping, guarding — that point to systemic issues.
Avoid targets that reward low numbers. A team with zero reports is usually not a team with zero hazards.
Keeping momentum
- Recognise good reports — not with large rewards, which can distort reporting, but with genuine appreciation.
- Run occasional focus campaigns: "this month, look for trip hazards".
- Include near-miss review in daily or weekly meetings.
- Have managers do regular safety walks and report what they see themselves.
An example: a metal processing plant
A metal processing plant received only a handful of near-miss reports a year, all on paper. After a forklift collided with a rack, it launched QR-code reporting from phones, committed to feedback within a week and shared fixes in daily meetings. Reports rose to dozens per month within a quarter. Themes quickly emerged — blind corners, pedestrian routes crossing forklift aisles, poor lighting at loading bays — and were fixed with mirrors, marked walkways and lighting. Forklift-related incidents fell sharply over the following year.
Common mistakes
- Long forms that discourage reporting.
- Reports disappearing without feedback.
- Blaming individuals.
- Treating report counts as bad news.
- Fixing the symptom but not the condition.
How software helps
Safety software lets anyone report from a phone in under a minute with photos and location, routes reports to the right owner, tracks actions to closure, notifies reporters of the outcome and shows trends by area and type. See EHS software.
Talk to us about making near-miss reporting easy in your plant.
Contractors and visitors
Contractors, drivers and visitors often notice hazards that employees no longer see. Make the reporting QR code visible at gatehouses, loading bays and contractor areas, and mention it during induction. Their reports go through the same triage and feedback process.
Frequently asked questions
What is a near miss?
An unplanned event that could have caused injury, illness or damage but didn't — by chance or because someone reacted in time.
Why report something that didn't hurt anyone?
Because the same conditions can cause an injury next time. Near misses are free lessons; incidents are expensive ones.
Should near-miss reports be anonymous?
Allowing anonymous reports can help at first, but named reports allow follow-up questions and feedback. Many plants allow both.
How do we avoid blame?
Focus investigations on conditions and systems rather than individuals, thank reporters publicly, and never discipline someone for honestly reporting a near miss.
Is a high number of near-miss reports bad?
Usually not. Rising reports often mean people trust the system. What matters is that hazards are fixed and serious incidents fall.
