Near Miss

A near miss is an unplanned event that did not cause injury, illness or property damage but could have under slightly different circumstances. Examples include a falling tool that lands just beside a worker or a forklift that stops inches from a pedestrian. Near misses are warning signs that a hazard exists and controls have gaps.

Safety teams also call them close calls, near hits or "good catches." Because nobody was hurt, they are easy to ignore, which is exactly why a structured near miss reporting process is one of the most useful leading tools in any safety program.

What Is a Near Miss?

There is no near miss definition in OSHA's regulations, and near misses are not recordable on the OSHA 300 Log because no injury or illness occurred. OSHA does, however, publish a near miss report form template that describes a near miss as a potential hazard or incident in which no property was damaged and no personal injury was sustained, but where, given a slight shift in time or position, damage or injury easily could have occurred.

Two elements define a near miss:

• An actual event happened. Something moved, fell, released, slipped or failed. This separates a near miss from a hazard that is simply sitting there.
• There was no loss. No one needed treatment and nothing was damaged, usually because of luck, timing or a last-second reaction rather than a designed control.

Many organizations treat a near miss as a type of incident, classified by its potential severity rather than its actual outcome.

Why Near Misses Matter

Serious injuries rarely come out of nowhere. The same conditions and behaviors that produce a near miss today can produce a lost-time injury or fatality tomorrow. A near miss gives you the full set of facts about a failure without the human or financial cost.

Near misses as leading indicators

Injury rates such as the TRIR are lagging measures: they tell you what already went wrong. Near miss reports are a common leading indicator because they let you act before harm occurs. A rising number of reports often reflects a stronger reporting culture, not a more dangerous workplace.

Cultural value

When workers see that reporting a close call leads to a fixed guardrail or a revised procedure, they trust the safety program more. When reports disappear into a binder, people stop reporting. The way you respond to near misses signals whether safety is a value or a slogan.

Cost avoidance

Every injury that is prevented avoids medical costs, workers' compensation claims, lost production and investigation time. Fixing the cause of a near miss is almost always cheaper than responding to the injury it predicted.

Examples of Near Misses

Near misses happen in every industry. Common examples include:

• A pallet of materials shifts on a rack and falls into an aisle that was empty seconds earlier.
• A worker slips on a hydraulic fluid leak but catches the handrail and is not hurt.
• A delivery truck backs up without a spotter and stops just short of an employee walking behind it.
• An electrician opens a panel believed to be de-energized and finds it live, but does not make contact.
• A chemical container is found unlabeled and nearly gets used for the wrong process.
• A hand tool drops from scaffolding and lands in an area that was not barricaded.
• A driver swerves to avoid a rear-end collision caused by following too closely.

Each of these points to a specific control failure: storage practices, housekeeping, vehicle movement rules, energy isolation, hazard communication, dropped object prevention or driver behavior.

Near Miss vs. Unsafe Condition vs. Incident

These terms are related but not interchangeable, and mixing them up muddies your data.

• Unsafe condition or unsafe act: a hazard that exists but has not yet caused an event, such as a frayed cord or a worker not wearing eye protection. See unsafe act and unsafe condition.
• Near miss: an event occurred, but nobody was injured and nothing was damaged.
• Incident with loss: an event that caused injury, illness or damage. If it meets OSHA's recording criteria, it becomes a recordable injury.

A simple test: if something actually happened and the only thing that prevented harm was chance, it is a near miss. If nothing happened yet, it is a hazard or observation.

How to Build a Near Miss Reporting Program

An effective program makes reporting fast, safe and worthwhile. Follow these steps:

1. Define what to report. Publish a short, plain-language definition with examples relevant to your sites so workers know what counts.
2. Make reporting easy. Offer a short form that takes a few minutes, available on mobile devices and paper. Ask only for what is needed: what happened, where, when, potential outcome and immediate actions taken.
3. Allow anonymous reports. Some workers will only report if they cannot be identified, especially early in a program.
4. Remove fear of discipline. State clearly that reporting a near miss will not lead to punishment. Discipline tied to reporting drives events underground.
5. Triage by potential severity. Rate each report by what could reasonably have happened. A near miss that could have been fatal deserves a full investigation even though nobody was hurt.
6. Investigate the cause. For high-potential events, use root cause analysis to look past the individual and find system weaknesses such as missing guards, unclear procedures or schedule pressure.
7. Assign corrective actions. Give each action an owner and a due date, and prefer controls higher on the hierarchy of controls over reminders and retraining.
8. Close the loop. Tell the reporter what was done. Share lessons learned in toolbox talks and safety meetings.
9. Track trends. Review reports by location, hazard type and potential severity to find recurring problems.

Common Mistakes to Avoid

• Setting near miss reduction targets. Rewarding fewer reports encourages people to stop reporting. Measure reporting rate and closure rate instead.
• Blaming the reporter. If the first question is "who messed up," reporting will stop.
• Collecting reports without action. A backlog of open near misses tells workers their input does not matter.
• Treating all near misses the same. A dropped pen and a dropped steel beam are both near misses, but only one needs a formal investigation.
• Fixing only the symptom. Cleaning up a spill without asking why the leak exists guarantees a repeat.
• Making the form too long. Every extra required field reduces participation.

Best Practices for Near Miss Management

• Recognize good catches publicly, focusing on the hazard found rather than the person at fault.
• Have supervisors acknowledge each report within one shift so reporters know it was received.
• Include contractors and temporary workers in the reporting system.
• Link near miss data with incident, inspection and observation data to see the full risk picture.
• Review high-potential near misses at the leadership level, not only within the safety department.
• Use the same reporting tool for near misses and injuries so data stays consistent.

How SMS360 Helps

The SMS360 Incident Management module gives workers a way to report near misses from a mobile device or desktop, including photos and location details. Safety teams can classify reports by potential severity, assign investigation tasks and corrective actions with due dates, and send reminders until items are closed. Dashboards and reports show near miss trends by site, hazard type and status, so recurring problems are easier to spot and address before an injury occurs.

Frequently Asked Questions

What is the difference between a near miss and an accident?

A near miss is an unplanned event that could have caused injury or damage but did not. An accident, often called an incident with loss, is an event that actually resulted in injury, illness or property damage. Both share the same causes and deserve investigation. The only difference is the outcome, which is often decided by chance rather than by a control that worked as designed.

Do near misses have to be reported to OSHA?

No. OSHA's recordkeeping rule in 29 CFR Part 1904 covers work-related injuries and illnesses, so a near miss with no injury is not entered on the OSHA 300 Log and does not need to be reported to OSHA. Near miss reporting is an internal best practice that OSHA encourages, and it supports the hazard identification expected of an effective safety program.

How do you write a near miss report?

Record the date, time and exact location, then describe what happened in plain, factual language. Note the potential outcome, any people or equipment involved, and immediate actions taken to make the area safe. Add photos if possible and suggest how to prevent a repeat. Avoid assigning blame. The goal is to capture enough detail for someone to understand and fix the hazard.

Is a high number of near miss reports a bad sign?

Usually not. A high or rising number of near miss reports often means workers trust the system and are willing to speak up. A very low number at a busy site is more concerning, because it suggests events are going unreported. Look at the potential severity of reports and how quickly corrective actions are closed, not just the total count.