When Near-Miss Reports Stop: A Process Safety Warning Sign
A falling near-miss count at a chemical plant usually means operators no longer believe reporting achieves anything. Supervisors can see the signs first.
Fewer reports, same risk
A drop in near-miss reports is often shown to leadership as good news, but at a chemical plant it deserves suspicion, because the hazards of the process do not change from quarter to quarter. If the plant is generating near-misses at about the same rate and recording fewer, it has not become safer and has instead lost sight of itself.
API Recommended Practice 754 treats lower-consequence events and near-misses as leading indicators of process safety, in its Tiers 3 and 4. It is worth separating these from personal-injury statistics, since slips and cuts say little about the likelihood of a major release.
Two ways trust breaks
Reporting declines in two recognizable patterns, and both are rational from the operator's position.
- The report disappears. An operator files it and hears nothing. No action, no explanation. After a few of these, reporting looks like paperwork with no result.
- The report becomes blame. One that mentions a colleague is handled, even informally, as a mark against that person. Crews learn to leave out names, soften details or say nothing.
Neither needs anyone to discourage reporting openly, because the system teaches the lesson by what it does.
A checklist for supervisors
Exhibit 1: Warning signs a supervisor can observe, what each suggests and a first response.
| Warning sign | What it suggests | First response |
|---|---|---|
| Reports arrive in batches before audits | People report when asked, not when things happen | Ask for one observation at every shift handover |
| Descriptions are vague, with no names or times | Fear of consequences for those involved | State plainly that reports are not used for discipline, and keep to it |
| The same few people file everything | Most of the crew has disengaged | Ask others directly what they have seen |
| Issues come up in conversation and never on a form | The formal route is not trusted | Offer to file it with them and follow up |
| Nobody asks what happened to an earlier report | They have stopped expecting an answer | Report back on open items without being asked |
| One unit reports nothing for months | Silence, not safety | Visit, observe and ask |
Rebuilding trust
Three practices do most of the work, and they are simple to state but take persistence to keep up.
- Close the loop on every report. The person who filed it hears what was done, or why nothing was needed.
- Keep reporting apart from performance and disciplinary review. The system that receives a report should not be the one that assesses the reporter.
- Track the reporting rate next to severity and repeat locations. A falling count should start an inquiry.
In one composite engagement, supervisors at a manufacturer had been treating near-miss reports as a mark against their shift. After individual coaching on how to receive a report without blame, reporting more than doubled within six months. Read the safety culture case study.
This article is written for the people closest to the work. For how boards should read the same numbers, see why safety culture metrics can mislead leadership, and for the technical side of process safety at chemical sites, see why process safety management fails quietly.
What a supervisor can do this week
- Check how many near-miss reports from your area last quarter received a reply to the person who filed them.
- At the next shift meeting, describe one report and what was done about it.
- Thank the next person who reports, in front of the crew.
- Raise any report that named an individual and led to discipline with your safety lead.
Find out why reporting has dropped
We can assess reporting culture on your site through confidential interviews and help supervisors rebuild trust in the process.
Contractor Oversight Standards for Publicly Funded Programs
One procurement policy can still produce a different oversight practice on every project. In a public program, a finding at one site is a finding against all of them.
Process Safety and Asset Integrity Beyond the Checklist
A procedure on file and a barrier that works are different things. Bowtie analysis shows which one you have.
Contractor Safety Management for an Outsourced Workforce
Subcontracting the work does not subcontract the duty. Whoever controls the site answers for safety on it.