Key takeaways
Short answer: A near miss and an incident sit on the same chain of events, separated mainly by outcome. An incident is an unplanned event that actually caused harm, damage, or loss — an injury, equipment damage, a spill, a stoppage. A near miss is an unplanned event that had the potential to cause that harm but did not, often only because of luck or a last-moment intervention. The underlying hazard and sequence can be identical; what differs is whether the bad outcome occurred. That is why near misses matter so much: they are free warnings — leading indicators of the incident that has not happened yet — and acting on them is how you prevent it. It connects closely to leading vs lagging indicators.
An incident is an unplanned event that actually resulted in harm, damage, or loss — it is the bad thing happening. In a workplace-safety context, an incident covers injuries to people, but the term extends to equipment damage, material spills, fires, property damage, and process upsets that cause loss. The defining feature is consequence: something went wrong and there was a real, adverse outcome. Incidents are what safety and operations management have traditionally counted and reported — recordable injuries, lost-time accidents, damage events — because they are concrete, visible, and often legally reportable. They are, by their nature, after-the-fact: by the time you are counting an incident, the harm has already occurred. This makes incidents lagging indicators — they tell you about safety performance that has already happened, like a scoreboard of failures. They are essential to track (you must know what actually went wrong), but managing safety by incidents alone means you are always learning from harm that has already been done, reacting to outcomes rather than preventing them. An incident is the realized failure; the question is whether you had to wait for the harm to learn the lesson.
A near miss is an unplanned event that had the potential to cause harm, damage, or loss but did not — the bad thing almost happened. A tool falls from height but hits no one; a forklift and a pedestrian nearly collide but stop in time; a machine guard is found open before anyone is hurt; a chemical is almost mixed wrongly but caught at the last step. The hazard was real and the sequence was in motion, but the adverse outcome was averted — sometimes by a deliberate intervention, often simply by luck (no one happened to be standing there). The crucial point is that a near miss usually shares the same underlying cause and chain of events as an incident; the difference is only whether the final harm occurred. This makes near misses extraordinarily valuable: they reveal the hazard and the failure path without anyone being hurt — a warning delivered for free. They are leading indicators, pointing to incidents that could happen, giving you the chance to act before the harm is realized. A near miss is the failure path made visible without the cost of the failure.
The unsettling truth at the centre of this distinction is how often the only thing separating a near miss from a serious incident is luck. The falling tool that hit no one and the falling tool that caused a head injury are the same event — same dropped object, same height, same failure to secure it — distinguished only by whether someone was beneath it. The near collision and the actual collision share a cause; chance decided the outcome. This is why treating near misses as non-events ("nothing happened, so nothing to do") is so dangerous: it ignores that the same conditions, replayed, could just as easily produce harm. The hazard does not care whether last time was lucky. Recognizing that outcome is often a matter of chance reframes near misses from "lucky escapes to forget" into "incidents that have not happened yet" — warnings about a hazard that will, given enough repetitions, eventually produce harm. The safety value of a near miss comes precisely from this: it is an incident's cause without the incident's cost, and luck is not a control you can rely on.
The near-miss-versus-incident distinction maps directly onto leading versus lagging safety indicators. Incidents are lagging indicators: they measure harm that has already occurred, telling you about past failures after the fact. Near misses (along with hazard observations and unsafe-condition reports) are leading indicators: they reveal hazards and failure paths before harm is realized, giving you the opportunity to intervene. A safety program that relies only on incident statistics is steering by the rear-view mirror — it improves only after someone has been hurt. A program that captures and acts on near misses is forward-looking — it removes hazards before they cause harm. This is the same logic that underlies the well-known safety-triangle idea: for every serious incident, there are typically many minor incidents and a far larger number of near misses and unsafe conditions beneath it. The near misses at the base of that triangle are warnings about the serious events at the top. Acting on the broad base of near misses is how you prevent the rare but severe incident — which is exactly why near misses, the events where nothing bad happened, can matter more for prevention than the incidents themselves.
Over a month, a packaging line logs the following. A pallet is stacked too high and a box falls, narrowly missing a worker — a near miss. Twice, operators notice a guard interlock is slow to engage and report it — near misses (unsafe conditions). A worker reaches into a jam without locking out the machine but withdraws safely before it cycles — a near miss. Then, the following week, a different worker reaches into a similar jam and the machine cycles, causing a hand injury — an incident. Look at the chain: the injury incident was foreshadowed by the lockout near miss the week before; the same hazard and behaviour, with luck the first time and harm the second. Had the near miss been reported, investigated, and acted on — reinforcing lockout discipline, fixing the jam-prone mechanism — the incident might never have occurred. The near misses were not noise; they were the early chapters of the incident's story. The lesson is that the unhurt events carried the same information as the injury, available a week earlier and at no human cost. Capturing and acting on them is the difference between preventing the injury and merely recording it.
Because near misses are free warnings, the single most important practice is to capture them — and that depends on culture. Near misses are easy not to report: nothing bad happened, reporting takes effort, and in a blame-oriented culture, admitting a near miss can feel like admitting fault, so people stay quiet. The result is that the most valuable safety data — the warnings before harm — goes uncollected, and the organization learns only from incidents, after people are hurt. Building a strong near-miss reporting culture means making reporting easy, expected, and explicitly blame-free, treating each report as a welcome gift of information rather than an admission of failure, and visibly acting on reports so people see that speaking up leads to fixes rather than punishment. The payoff is large: a high near-miss reporting rate is itself a sign of a healthy safety culture, and the stream of reports gives a continuous supply of hazards to eliminate before they cause incidents. Counterintuitively, rising near-miss reports can accompany falling incidents — because the hazards are being caught and fixed at the near-miss stage. Reporting is what converts the potential of near misses into actual prevention.
Safety and OEE are linked more directly than they first appear. Safety incidents cause downtime — an injury, a spill, or equipment damage stops the line for response, investigation, and recovery — so incidents are a real loss to the Availability factor, on top of their human cost. Near misses, acted on, prevent those stoppages before they happen, protecting both people and uptime. The leading-versus-lagging logic is also exactly the same mindset that drives OEE improvement: just as near misses are leading indicators that prevent incidents, condition monitoring and early fault detection are leading indicators that prevent the breakdowns which would otherwise destroy Availability. In both cases, acting on the warning before the failure beats reacting to the failure after it. A culture that captures near misses and a system that captures developing equipment faults are the same discipline applied to safety and to reliability — catch the signal early, fix the hazard, and avoid the costly event. This shared logic ties near-miss reporting to the broader practice of preventive action.
Fabrico captures downtime and its causes against live OEE — including the stoppages that safety incidents create — so the production impact of safety events is visible alongside their human cost. By making downtime reasons explicit, it helps connect safety-related stoppages to the Availability losses they cause, reinforcing the case for catching hazards at the near-miss stage before they become incidents that stop the line. The same early-warning discipline that prevents safety incidents prevents equipment breakdowns, and Fabrico shows the cost of both. Book a demo to see how safety and reliability losses show up in your OEE.
An incident is an unplanned event that actually caused harm, damage, or loss. A near miss is an unplanned event that could have caused harm but did not, often only because of luck or a last-moment intervention. The hazard and chain of events can be identical; the difference is whether the bad outcome occurred.
Because they are free warnings — leading indicators of incidents that have not happened yet. A near miss usually shares the same cause as an incident, so acting on it removes the hazard before anyone is hurt. The events where nothing bad happened often carry the same information as an injury, earlier and at no cost.
Near misses are leading indicators — they reveal hazards before harm is realized, allowing prevention. Incidents are lagging indicators — they measure harm that has already occurred. A safety program that acts on near misses is forward-looking, while one relying only on incidents learns only after someone is hurt.
Because near misses are easy not to report — nothing bad happened, and in a blame culture, reporting can feel like admitting fault. Building a blame-free, easy, visibly-acted-on reporting process is what captures this valuable data. A high near-miss reporting rate is itself a sign of a healthy safety culture.
Safety incidents cause downtime — an injury, spill, or equipment damage stops the line for response and recovery — so they are a real loss to the Availability factor on top of their human cost. Acting on near misses prevents those stoppages, protecting both people and uptime.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
