Practical guide · Safety management
Near miss reporting: definition, what to report and how to run it
Short answer
A near miss is an unplanned event that did not cause injury, illness or damage but could have. Near miss reporting is the routine of recording these events quickly, finding the cause, and fixing it before the same event turns into a harm. It works only if reporting is easy and safe.
A near miss is an unplanned event that did not result in injury, illness or damage, but had the potential to. A forklift that stops a metre short of a person is a near miss. Near miss reporting means recording such events as soon as they happen, finding why they happened, and acting so they do not recur. Definitions differ: some organizations include events with minor damage, and some treat unsafe conditions found before any event as a separate category. Write your own definition and teach it. The program lives or dies on whether reporting is easy, free of blame, and visibly acted on.
Last updated:
Near miss definition and examples
The common definition is an event that could have caused harm but did not, often by luck or a last-second reaction. The words "close call" and "near hit" mean the same thing. See the near miss glossary entry.
- A pallet slips off the forks and lands where someone was standing a minute earlier.
- A worker trips on a hose across an aisle, catches a rail and does not fall.
- A guard is found open on a running machine, and nobody was near it.
- A forklift and a walker meet at a blind corner and both stop in time.
- A cleaning chemical is decanted into an unlabelled bottle, and the mistake is spotted before use.
All the examples are made up for this page. Notice that the first four are events and the last is a condition caught in time. Sites vary in how they classify the second kind, so decide how you will count each type before you start measuring.
Near miss, incident, hazard and unsafe condition
| Term | Usual meaning | Example |
|---|---|---|
| Hazard / unsafe condition | Something that could cause harm, with no event yet. | A frayed lifting sling in use. |
| Near miss | An event that could have caused harm but did not. | The sling snaps and the load falls with nobody under it. |
| Incident | An event that caused harm or damage, or an event of a kind your rules count. | The load falls and strikes a person. |
A common pattern. Your site's wording comes first.
Which events enter injury recordkeeping is set by the rules in your country. A near miss, by definition, caused no injury, so it is generally not an injury record, but check the current text of the rule that applies to you. For how unsafe acts and conditions relate to events, see the guide on unsafe acts and unsafe conditions.
The near miss reporting process in six steps
- 1
Report
Anyone can report, on paper, by QR code or on a phone, in under a minute. The free near miss report form shows the fields: what happened, where, when, what could have happened, who saw it.
- 2
Make the area safe
If the hazard is still there, fix or fence it now. A report that sits for a week while the hazard stays is the fastest way to lose trust.
- 3
Triage by potential
Rate each report by how bad the outcome could have been, not by what happened. A near miss that could have killed someone outranks a minor trip, even though neither caused harm.
- 4
Find the cause
Ask why it happened and why the barriers did not hold. Use a 5 Whys for a simple one and a fuller root cause analysis for a serious one. Look for the system cause behind the act.
- 5
Act at the strongest level you can
Choose the action from the hierarchy of controls: remove the hazard or add a physical guard before a new rule or a reminder. Give it an owner and a date.
- 6
Close the loop
Tell the reporter what was done. Share the lesson with other shifts and areas, and check later that the fix held.
Worked example: reading a quarter of reports
The figures are invented for this page and are illustrative. A plant of 80 people collects 52 near miss reports in a 13-week quarter. That is 52 divided by 13, or 4 a week, and 52 divided by 80, or 0.65 reports per person for the quarter.
Of the 52 reports, 39 were closed within 14 days. 39 divided by 52 is 0.75, so 75% were closed in time. 13 were still open, 7 of them past their due date. The plant looks at these before the report count, because a rising count with slow closing means people report and nothing happens. Next quarter, the plant sees 52 reports fall to 31 after a supervisor disciplines someone named in a report. The count fell by 21, which is 21 divided by 52, about 40%. It is not an improvement. The reporting went quiet. The right move is to restore trust, not to celebrate.
Other measures to watch: time from report to first action, the share of reports naming a system cause instead of only a person, the share of actions at the top levels of the hierarchy of controls, and the reports from each shift and area. Use your own baseline. No outside number tells you what is right for your plant.
Why people do not report, and what to do
- Fear of blame. If a report leads to a warning, reports stop. Keep reports free of blame and judge the response by just culture rules.
- Nothing happens. Reply to every report, with the action or the reason for none.
- Too much effort. A long form kills reporting. Keep the first report to a few fields.
- No time. Give people time to report on shift, and let supervisors take a verbal report.
- Unclear what counts. Show examples at the huddle and on the report point.
- The wrong target. Targets for the number of reports produce small, trivial ones. Measure closed actions and risk removed, not volume alone.
Anyone should also be able to stop a task they see is dangerous, without waiting for a report. See stop-work authority. Our post on why hazards go unreported lists the barriers in more depth.
How LeanSuite fits
LeanSuite's near miss reporting module lets anyone log a near miss, unsafe act or unsafe condition on their phone in seconds and tracks each corrective action until it is closed. Reporters are notified when their hazard is resolved, forms can allow anonymous reporting, and a hazard report can become a CAPA project with its own root cause analysis. See the best near miss reporting software comparison if you are choosing a system. A paper form or a spreadsheet is enough at low volume, and the free template works for that.
Go deeper
This page is the short version. These guides cover each part in full.
- Near Miss Reporting That Actually Prevents Future IncidentsClosing the loop on each report and reading the report rate.
- Top Reasons to Enforce Near Miss ReportingThe case for making reporting routine.
- Why Manufacturing Hazards Go UnreportedThe barriers that stop people reporting and how to remove them.
- QR Code Safety Reporting: Instant Action and ResponseMaking a report take seconds at the machine.
- Building a Proactive Safety Culture in ManufacturingThe leadership habits behind a reporting culture.
All our articles on this subject are in the safety management topic.
Free templates and tools
- Near miss report formA two-page near miss report from the first report to closure, and an Excel log with status and days open.
- Safety observation card templateFour behavior-based safety cards per sheet, with safe and at-risk checks, the conversation and a tally sheet.
- Incident investigation report templateFacts and a sourced timeline, causes at three levels, actions by the hierarchy of controls, a US recordkeeping screen and a closure check.
- Job safety analysis (JSA) templateJob steps, hazards, risk scored before and after the controls, the hierarchy of controls, PPE and sign-off.
- Risk assessment matrix template (5×5)A color-coded 5 × 5 severity and likelihood matrix, a scoring guide and a risk register.
- Toolbox talk templateA record of a short safety talk: topic, key points, questions raised, actions and an attendee sign-in sheet.
- TRIR and DART rate calculatorOSHA recordable and DART incident rates from your 300A case counts and hours, and what one more case does to them.
Doing this in LeanSuite
Near Miss Reporting
Anyone logs a near miss, unsafe act or unsafe condition on their phone in seconds, and each corrective action is tracked until it is closed.
See Near Miss ReportingSafety Improvement
Keeps employees alert to hazards and gives leaders the visibility to drive safety improvements.
See Safety ImprovementDaily Issue Management
Gives frontline teams one place to flag, track and resolve issues in real time, so the same fires stop coming back every week.
See Daily Issue Management
See it on your own lines
Bring the problem you are working on to a 45-minute demo. Or look around with sample data first, or pilot LeanSuite on your own lines for 90 days, with the setup done by our team.
FAQ
Questions about near miss reporting
A near miss is an unplanned event that did not cause injury, illness or damage but could have, often avoided by luck or a last-second reaction. It is also called a close call. Some organizations count events with minor damage too, so write your own definition.
A near miss caused no harm and an incident did. The cause and the potential can be the same, which is why a near miss is a free warning. Treating a near miss with the same care as an incident is how a plant prevents the incident.
Anyone who sees one: operators, maintenance, visitors, contractors, supervisors. The person closest to the work usually sees it first, so reporting should not be restricted to supervisors.
Company policy often requires it. Whether a law or a customer requirement does depends on your country, industry and contracts, so check the current text of the rules that apply to you. A near miss is generally not an injury record.
Make it quick, keep it free of blame, answer every report and show what was fixed. Fear, effort and silence after a report are the main reasons people stop. Measure closed actions and time to close, not only the number of reports.
Related guides and tools
- Free near-miss report form with a one-minute short version
- Just culture: why people report near misses only when it is safe to
- Stop-work authority: acting on a near miss before it becomes an injury
- Near-miss reporting software compared
- TRIR and DART calculator for tracking the injury rate your near-miss reports should lower
- Frontline worker app without company email: how operators submit reports
More method guides
- The 6 Ms of production
- Poka-yoke
- Model area 90-day plans
- Moving from Excel to one system
- Reducing machine downtime: a worked month
- Andon and jidoka
- Cycle time vs lead time, worked through
- Root cause analysis
- How many operators a line needs
- Reducing scrap and rework: a worked month
- Unsafe acts and unsafe conditions
- Just culture
- Stop-work authority
- Material review board (MRB)
- What is an NCR?
- Problem solving methods
- Quad chart
- OEE calculation
- Quality assurance vs quality control
- SOP meaning and format
- Job hazard analysis
- Fishbone diagram
- Pareto chart
- Histogram
- Control chart
Or browse the topics, the full library and the lean glossary.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.