The short version: A good catch is a hazard someone spotted and shut down before it hurt anyone. The frayed sling swapped out, the missing guard flagged, the leaning pallet rack roped off. The incident that never happens leaves no scar and no paperwork, which is exactly why it is easy to overlook. The sites that surface the most good catches did not get lucky. They built a culture where the person who speaks up walks away glad they did.
Ask a crew about the worst thing that happened last quarter and you will hear about the injury. Ask about the best thing and you will get blank looks. But the best thing probably did happen. Someone caught something.
A good catch is a win that hides. There is no ambulance, no lost-time entry, no photo for the toolbox talk. Just a worker who saw a problem and dealt with it, and a day that ended the way every day is supposed to. The trick is learning to see those moments, count them, and build more of them.
What a good catch actually is
Safety folks draw a line between a near miss and a good catch, and it is worth keeping straight. A near miss is the close call that already happened: the dropped wrench that missed a foot. A good catch is the step in front of that, the moment someone recognized an unsafe condition and acted to stop the event before it started, as EHS Today frames it in its breakdown of the two.
That distinction matters because of what you do with each. A near miss is a warning you were handed. A good catch is a warning your crew went out and grabbed. The first tells you the hazard exists. The second tells you your people are hunting it.
The turnaround that ran on reporting
The cleanest proof that this works is old and famous, and it holds up. When Paul O'Neill took over as CEO of Alcoa in 1987, he made safety the whole story. Every injury had to reach him within 24 hours, paired with a root cause and a plan so it would not repeat.
Here is the part that turned it into a good-catch engine. Once workers saw that reports moved, they stopped waiting for injuries. They started raising warnings when they spotted a potential problem, and those warnings traveled up the same fast channel. The reporting line built for incidents became the line people used to flag hazards before anything happened.
The numbers followed. Alcoa's lost-workday rate fell from 1.86 to 0.23 over O'Neill's tenure, and kept sliding to 0.085 by 2013, per EHS Today's account of his safety leadership. The company got safer not because it wrote better rules, but because it made speaking up the fastest, most respected thing an Alcoa worker could do.
What makes catches surface
You do not buy a good-catch culture. You remove the reasons people stay quiet, and you add reasons to speak. The pattern is short and it barely changes across industries:
- Make it easy. A card at the workstation, a text line, a word to a supervisor who is actually on the floor. If reporting takes longer than fixing, nobody reports.
- Kill the blame. Ask what the setup allowed, not who slipped. The moment a catch earns a lecture, the next one goes unspoken.
- Close the loop out loud. Every catch gets an answer, and when something changes because someone spoke up, post it. Visible action is what tells the next person it is worth their breath.
None of that needs a platform. A stack of index cards and a lead who reads them the same shift beats an app that mails reports into a void. The tool is not the culture. The response is.
Celebrate the catch, not just the streak
Most sites still measure safety by what went wrong: recordables, lost days, the board that resets to zero. Those matter, but they only ever count failures. A good-catch program flips the lens. It counts the saves.
So when a picker flags a rack that is one bad bump from going over, or a maintenance tech tags out a machine with a guard that never got put back, say so by name. Thank them where the crew can hear it. That thirty seconds of recognition is not soft. It is the cheapest safety investment on the property, and it pays out in every catch it makes more likely.
The incident that never happened will never make a headline. But it is the whole game. A site that catches fifty small things a month is a site reading its own warnings, and the crew doing the catching is the reason everyone clocks out whole. That is a win. Start acting like one.
