Near miss reporting in manufacturing usually counts safety events. It rarely records the quality errors that were caught at the last second, which are the cheapest lessons your plant will ever get.
Jamal Caught It With the Part in His Hands
Jamal had the bracket in his hands when he saw it. The work instruction at his station said revision C. The traveler said revision D.
He swapped the sheet, finished the job and told no one. Nothing had gone wrong. The form for reporting it takes twelve minutes, and nobody had ever asked him about a thing that didn’t happen.
The next operator on that station got the same wrong sheet, because nothing in the system knew the first one had been caught.
What Is a Near Miss in Manufacturing?
A near miss is an error that was caught before it became a defect, an injury or an escape. In a plant, that means the wrong revision, the skipped check, the part that almost went in backwards.
In my experience, most near miss reporting programs were built for safety, and they do that job. The quality version is mostly invisible. No scrap, no rework, no customer return. Just an operator who noticed, and a document that still says the wrong thing.
This Isn’t a Jamal Problem
In my experience, plants often have a Jamal, and supervisors know it. The catch happens, the fix is quiet, and the record never exists.
I found little evidence on why people stay quiet, so I’ll be careful here. A 2024 survey of 45 employees in the explosives manufacturing industry, published in Progress in Engineering Application and Technology, found inconsistent near miss reporting and many people unaware of their organization’s reporting programs. It named insufficient knowledge and skills as barriers to reporting, and in that sample embarrassment was a minor obstacle. One small study in one industry won’t speak for your plant. Even so, it suggests the bigger gap may be awareness and skill rather than people hiding things.
What Did Aviation Build for Near Miss Reporting?
Aviation built a channel where the person closest to the event can say what happened without being blamed.
NASA’s Aviation Safety Reporting System has received 2,321,050 incident reports between April 1976 and December 2025. Its briefing lists three terms: voluntary, confidential and non-punitive. NASA’s briefing puts the principle this way: the best approach is simply to ask those involved.
A plant isn’t an airline, and I’m not suggesting you copy the system. But the principle travels. People report when reporting is easy, safe and visibly useful. The FAA’s maintenance human-factors group says in its procedural non-compliance guidance that person-centered “blame-and-train” mitigations do not effectively reduce failure to follow procedures. We covered that in our piece on measuring SOP compliance.
Why Don’t Forms Capture Near Misses?
Because the form costs more than the event. If a near miss took thirty seconds to catch and fix, a twelve-minute form loses every time. That is my view from watching floors, not a measured finding.
The deeper problem is where the information lands. Even when a form gets filled in, it goes to a log. A log counts events. It doesn’t change the sheet at Jamal’s station, so the next operator still gets revision C.
This is the same trap behind human error as a root cause: stopping at “the operator caught it” misses that the document let it happen.
How to Run Near Miss Reporting That Changes Procedures
The goal isn’t more reports. It is fewer repeats. Here is the sequence, in five moves:
- Ask out loud, in a short huddle. “What almost went wrong this week?” Five minutes, one shift, no forms.
- Write down every answer and assign no blame. The moment someone is named, the next week’s answers dry up.
- Sort each answer by what the document failed to do. In my experience, four buckets cover most cases: a missing step, a wrong revision, ambiguous wording, or an undocumented tolerance.
- Fix the document within a week. One named owner. If the fix is a poka yoke instead, our piece on poka yoke in manufacturing shows how to choose.
- Tell the person what changed. The authors of that explosives study recommend regular feedback to encourage reporting. In my experience, it is the move most plants skip, and the one that keeps the answers coming.
What the Market Sells Instead
Mostly dashboards. Incident-management modules built for safety that count events by category and plot them by month. A trend line of near misses is useful for an audit. It doesn’t tell you which line of which sheet to change.
Counting reports isn’t the same as learning from them. A plant can post a record number of reports and still hand revision C to the next operator.
How Our AI Agent Captures a Near Miss
At SenseiLab, Jamal wouldn’t fill in a form. He would tell our AI agent what he saw, which sheet it was, and what he did, in his own words and in about two minutes. The agent structures it into a procedure change. The supervisor validates it before it reaches the floor, and the station check, compare the sheet to the traveler before the first piece, becomes part of the SOP.
There is no new tool for him to learn and no writing assignment. The near miss goes from his head to the document while it is still fresh.
Run the Five-Minute Near Miss Huddle This Week
You can start without us.
- Pick one shift and one line. Gather them for five minutes.
- Ask: What almost went wrong in the last seven days?
- Write each answer on a whiteboard, with no names.
- For each, ask: What would the sheet have to say to stop this?
- Pick the two easiest fixes and change those documents by Friday. Tell the shift on Monday.
You will probably get at least three answers. Many are a step missing from a document, and the same two or three will repeat. Those repeats are your first draft of what to fix.
Frequently Asked Questions About Near Miss Reporting
What is near miss reporting in manufacturing?
Near miss reporting is recording an error that was caught before it caused a defect, an injury or an escape. The most useful reports also say which document or step allowed the error to happen.
Why don’t operators report near misses?
Often because nothing went wrong, the form takes longer than the event, and nothing visibly changes afterward. One small study points to varying understanding and limited knowledge of the reporting program.
How do you turn a near miss into a procedure change?
Ask what the document failed to do, sort the answer into a missing step, wrong revision, ambiguous wording or undocumented tolerance, then fix the sheet within a week and tell the person who reported it.
How do we reduce errors caused by wrong revisions at the station?
Compare the work instruction to the traveler before the first piece, and remove the old revision from the station when a new one is released. Our article on how to measure SOP compliance in manufacturing shows how to check whether the document itself is fit for use.
About the author: Diego Echenique, MBA, is CEO & co-founder of SenseiLab, with 20+ years in manufacturing operations. LinkedIn: linkedin.com/in/diegoechenique
