Near Misses Can Predict the Future. Let’s Use Them.

Near misses often share the same attributes that later appear in serious events. The difference is that consequences do not progress to the extreme, sometimes due to luck, sometimes due to timing, sometimes due to conditions that are not yet aligned. 

In many operations those signals appear as near misses. Small deviations. Minor leaks. Equipment behaving slightly outside normal conditions. Events that are recorded but rarely escalate beyond routine corrective action. 

That is exactly why near misses matter. They are early evidence that barriers are weakening. 

The challenge is volume. Teams need a consistent way to decide which near misses warrant a formal incident investigation and which ones should be addressed through faster corrective pathways. 

A near miss is not a housekeeping issue. It is a signal that protective barriers are beginning to weaken. 

How escalation happens in practice 

I supported a client after a plant fire that caused major equipment damage. The initiating event was a heating-oil release. The oil was above its flash point, vapors formed and ignition sources were present. 

During the investigation, the site identified that similar leaks had been occurring for weeks. They were treated as routine cleanup and maintenance. 

Those earlier events mattered because they showed recurring loss of containment in a system operating in a temperature range that changed the hazard profile. As the condition repeated, the probability increased that one occurrence would coincide with vapor accumulation and an ignition source. 

The near misses were evidence of barrier weakness, not isolated housekeeping issues. 

Why some near misses do not get investigated 

When near misses fail to trigger an investigation, it is rarely because people do not care or are indifferent to safety. Most often, the decision process is unclear or does not work well in practice. 

Supervisors and engineers operate under constant production pressure. Investigations require time and resources, and events without consequences rarely appear urgent. 

Experience also plays a role. As organizations lose operational knowledge, it becomes harder to recognize how small deviations can escalate under slightly different conditions. What once triggered concern can gradually start to look routine. Beyond basic reporting, employees may also lose clarity on who needs to be informed and owns the escalation. 

Repeated events without consequences reinforce the same effect. When a deviation occurs frequently without causing harm, the organization can begin to interpret the pattern as evidence of safety rather than evidence of luck. Over time, the abnormal becomes normal. 

These are solvable problems, but only if the organization treats “what do we investigate?” as a defined control, not an informal judgment call. 

Establish a baseline, then add triage 

A useful baseline for near-miss classification is API Recommended Practice 754 (API RP 754). It supports consistent definitions and reduces debate about what “counts.” 

Even with good definitions, most sites still need a decision step between “recorded near miss” and “formal investigation.” This is where a consistent triage process delivers outsized value. 

A review group model that improves decision quality 

The most effective approach I have seen is a standing near-miss review group that screens events and decides which ones require deeper work. 

The group should include experienced operations, maintenance and engineering personnel who understand process behavior across operating modes and can recognize when a small deviation indicates a broader control problem. 

The group’s purpose should stay narrow and well-defined: determine whether the near miss has credible potential for a more severe outcome and therefore should be fully investigated. 

Screening works best when criteria are consequence-focused and applied consistently. A short set of questions can cover most decisions: 

• If the same event recurred under slightly different conditions, could the outcome plausibly be much more severe (credible worst case)?
• Is this event part of a pattern that suggests drift, recurring equipment issues or repeat exposure to the same hazard? 

If the answer to either question is yes, escalation to a formal investigation is usually justified. If the answers are no, the event may still require action, but the response can often be handled through maintenance, management of change screening, procedure updates, training or targeted coaching. 

The triage record is a control. It creates transparency and improves consistency over time. 

A brief triage decision record becomes an important control because it creates transparency, supports consistency over time, and helps identify trends that individual supervisors may not see. 

Seeing the pattern before the incident 

Near misses are one of the clearest indicators of system performance available to operating organizations. They reveal where barriers are weakening, where equipment reliability is drifting and where operating conditions are beginning to move outside expected boundaries. 

Most facilities already collect this data. The real advantage comes from recognizing which signals point toward credible escalation pathways. 

Organizations that develop this capability gain something valuable: time. They can see the pattern forming before the incident occurs. 

Explore Related Insights