Near Miss vs. Near Hit: What’s the Difference and Why It Matters

One of the many interesting controversies in safety and health is what to call what many call a “near miss.” Some say near miss; others say near hit; still others prefer terms like incident, event, or close call.

Some might think it’s a meaningless point or simply a semantic issue. Others think the specific term we use for this is very important.

“Near miss” and “near hit” describe the same event: something that could have caused injury or damage but didn’t. “Near miss” is the standard term used in OSHA guidance and most safety programs. “Near hit” is an informal synonym that some teams prefer because it sounds more logical. Either works, as long as your team picks one.

Below, you’ll learn why the standard term says “miss,” how a near miss differs from an incident, accident, hazard, and good catch, and why the term you choose affects what workers report.

Main Takeaways

• A near miss is an unplanned event that could have caused injury, illness, or damage but didn’t. “Near hit” means the same thing.
• “Near miss” comes from World War II military use, where “near” meant “close,” as in a bomb that missed its target but landed close by.
• ISO 45001 treats “near miss,” “near hit,” and “close call” as interchangeable names for an incident where no one was hurt.
• A near miss differs from a hazard and a good catch because an event actually happened, and from an accident because no harm resulted.
• Pick one term, define it on your forms, and use it everywhere. Confusion over what counts is one reason workers skip reporting.

What Is a Near Miss?

A near miss is an unplanned event at work that could have caused injury, illness, or property damage but didn’t. Something actually happened, like a falling object or a vehicle swerving, but luck, timing, or a quick reaction kept anyone from getting hurt.

A wrench falls from scaffolding and lands where a worker stood seconds earlier. A forklift stops inches short of a pedestrian at a blind corner. In both cases, no one was hurt, but the next time could end differently.

A near hit is the same event under a different name. ISO 45001, the international standard for occupational health and safety management systems, notes that an incident where no injury or ill health occurs may be called a “near-miss,” “near-hit,” or “close call.” OSHA’s guidance uses “near miss” and “close call.”

Near Miss vs. Near Hit: Which Term Is Correct?

Both terms are correct, and both describe the same event. “Near miss” is the more widely accepted term, and “near hit” is a common, logical alternative. What matters is that your team uses one of them consistently.

Why Is It Called a Near Miss?

The objection is fair: if something nearly hit you, why call it a “miss”? The answer is in how “near” works in the phrase. It means “close,” not “almost.” A near miss is a miss that came dangerously close.

The term became common during World War II, when military reports used it for a bomb that missed its target but landed close enough to cause damage. Merriam-Webster dates the first known use to 1940. After the war, the phrase moved into everyday language and dropped the idea that damage occurred.

Why Some Safety Pros Prefer “Near Hit”

Many safety professionals argue that “near hit” says what actually happened: something nearly hit a person or piece of equipment. They also say it puts the focus on the threat instead of the lucky outcome, which can help workers take close calls seriously.

That’s a reasonable view. The tradeoff is consistency. “Near miss” is the term most standards, regulators, reporting forms, and software use, so switching can create confusion when data is shared across sites or with outside partners.

Which Term Should Your Team Use?

Use “near miss” as the official label on forms, in training, and in investigations, unless your organization has a strong reason to standardize on something else. If crews already say “near hit,” let them keep saying it, but log the event as a near miss.

Our own online training course on near miss best practices uses the term “near miss” for the same reason.

How a Near Miss Differs From an Incident, Accident, Hazard, and Good Catch

These terms describe different points on the same timeline, from a condition that could cause harm (a hazard) to an event that did (an accident). Classifying each one correctly decides what gets reported, investigated, and fixed.

Use this table to classify any event quickly.

Near Miss vs. Incident

A near miss is a type of incident where no one was hurt and nothing was damaged. When people contrast the two, “incident” usually means an event that did cause harm. The dividing line is the outcome, not how serious the hazard was.

For example, a worker slips on a wet floor and breaks a wrist. That’s an incident with an injury. The same worker slips, catches the handrail, and walks away. That’s a near miss. Same hazard, different outcome.

Under ISO 45001, “incident” covers events with and without harm, which is why a near miss counts as a type of incident. Many organizations still use “incident” informally to mean an event with harm. OSHA also prefers “incident” over “accident” because most workplace injuries are preventable.

Good Catch vs. Near Miss

The difference is timing. A good catch happens before anything goes wrong, like a worker noticing a frayed cord and tagging it out. A near miss happens after something goes wrong, like that frayed cord sparking next to a worker who isn’t burned. Both are leading indicators, and both deserve a report.

Omaha Public Power District (OPPD), for example, configured Vector EHS Management to capture near misses, good catches, and safety observations as separate report types, so each one gets the right follow-up.

Is Near Miss vs. Near Hit Just a Semantic Debate?

The word itself matters less than using it consistently. When workers aren’t sure whether something counts as a near miss, a hazard, or “nothing worth reporting,” many say nothing. Unclear terms quietly cut the number of reports, and every missed report is a missed warning.

Why Near Misses Deserve a Report

OSHA doesn’t require employers to record near misses on the injury and illness log. But OSHA’s recommended practices tell employers to investigate injuries, illnesses, incidents, and close calls or near misses to find the hazards behind them.

The stakes are real. In 2024, a worker died from a work-related injury every 104 minutes in the U.S.

How you respond to reports matters too. A 2024 cross-sectional survey in the Journal of Occupational Health found a link between response and accident odds. Workers whose companies responded inadequately to near miss reports had 1.53 times the odds of an occupational accident, and workers who got no response had 1.75 times the odds, compared with workers whose companies investigated and made fixes.

How to Remove the Guesswork for Workers

• Put one term on every form, with a one-line, plain-language definition next to it.
• Show two or three real examples from your own site in training, so workers recognize a near miss when it happens.
• Accept every report, even if it’s filed in the wrong category. Reclassify it later instead of sending it back.
• Tell reporters what changed because of their report, so they keep reporting.
• For the full reporting process, see why near miss reporting is important, and for what happens after a report comes in, see how to create an incident investigation plan.

Pick One Term and Report Every Close Call With Vector Solutions

You now know what a near miss is, why the standard term says “miss,” and how to tell it apart from hazards, good catches, incidents, and accidents. Whether your crews say near miss or near hit, the goal is the same: every close call gets reported.

Start with one step. Choose one term, add a plain-language definition to your reporting form this week, and walk crews through two real examples.

Vector Solutions helps safety teams turn that consistency into results. Vector EHS Management captures near misses, good catches, and incidents in one system and connects each one to corrective actions, so every report leads somewhere.

FAQs About Near Misses and Near Hits

Should We Use “Near Miss” or “Near Hit” on Our Forms?

Use “near miss” as the single label on forms, in training, and in investigations, since it matches OSHA guidance and most safety software. If crews already say “near hit,” keep it as a nickname but log the event as a near miss. Add a one-line definition to the form so no one has to guess.

Is a Near Miss Considered an Incident?

Under ISO 45001, yes. A near miss is an incident where no injury or ill health occurred. In everyday use, many teams reserve “incident” for events that caused harm and call the rest near misses. Either approach works as long as your definitions are written down and used consistently.

How Do I Classify an Event When I Can’t Tell if It’s a Near Miss or an Incident?

Ask whether anyone was injured or made ill, or whether anything was damaged. If so, it’s an incident with harm; if not, it’s a near miss, even if the hazard was serious. Set a written threshold for gray areas like minor property damage, and when in doubt, report it first and let the investigator reclassify.

What Should I Do When a Near Miss Report Turns Out to Be a Hazard or Good Catch?

Log it anyway and move it to the right category on the back end. Don’t send reports back for being filed wrong, since that teaches workers that reporting is risky. Respond the same way to every report: assign an owner, fix the condition, and tell the reporter what changed.

How Do I Know if Our Near Miss Reporting Is Working?

Track report volume, the time from event to report, and the share of reports that led to a completed corrective action. Rising volume with fast follow-up usually means workers trust the process. A falling count isn’t proof of safety and often signals underreporting.

Can We Track Near Misses on Paper or Spreadsheets?

Paper and spreadsheets can work for a single site with few reports. They get harder to manage once you need mobile reporting, follow-up across locations, and trend data. Whatever you use, a shared definition and a consistent process matter more than the tool.