The Definition of Good Catch

Definition of Good Catch

A good catch is a situation where someone notices a hazard, unsafe condition or error and reports or corrects it before it leads to an injury, damage or other loss. The term emphasizes the positive action of the person who caught the problem, rather than how close the organization came to harm.

Good catches are closely related to near misses. Many organizations use "good catch" for an issue stopped before an event began, such as a frayed sling removed from service, and "near miss" for an event that happened but did not cause harm, such as a dropped tool landing close to a worker. Some use the terms interchangeably. Either way, these reports reveal weaknesses while the cost of learning is still low, which is why healthcare, aviation, energy, construction and manufacturing all encourage them.

How Good Catch Programs Work

What Counts as a Good Catch

• Unsafe conditions: A missing guard, blocked exit, damaged ladder or leaking container noticed before use.
• Errors caught in time: A wrong valve lineup, mislabeled chemical or incorrect lift plan found during checks.
• Process gaps: Procedures that do not match how work is actually done, or steps that are easy to skip.
• Interventions: A coworker stopping a task because conditions changed, using their stop work authority.

The Reporting Cycle

• Make it safe: The person who spots the issue makes the area safe if they can do so without risk.
• Report quickly: They submit a short report with what they saw, where and when, ideally with a photo.
• Review and assign: A supervisor or safety team reviews the report and assigns a corrective action with an owner and due date.
• Close the loop: The reporter is told what was done, and lessons are shared with other teams.
• Look for trends: Reports are reviewed together to find repeat issues and higher-risk patterns.

Why Good Catches Matter

Serious incidents rarely come out of nowhere. They usually follow a series of smaller warning signs, such as worn equipment, workarounds or confusing procedures, that people noticed but did not report. A steady flow of good catch reports gives safety teams a view of those unsafe conditions early, when fixing them is quick and cheap.

Guidance and Standards Related to Good Catches

OSHA and Reporting Protections

No OSHA regulation requires a good catch program. However, OSHA's Recommended Practices for Safety and Health Programs encourage employers to have workers report injuries, illnesses, near misses and hazards, and to act on those reports. Under 29 CFR 1904.35(b)(1)(iv), employers may not retaliate against employees for reporting work-related injuries or illnesses. OSHA's 2018 guidance on safety incentive programs stated that programs rewarding workers for reporting near misses or hazards are always permissible under that rule.

ISO 45001

ISO 45001, the international standard for occupational health and safety management systems, defines an incident as an occurrence that could or does result in injury and ill health, and notes that events with potential but no harm may be called near misses, near hits or close calls. The standard expects organizations to report, investigate and act on incidents, which includes these no-harm events.

Good Practices for Encouraging Good Catches

• Make reporting easy: Offer a quick, mobile-friendly form or a simple card that takes a minute or two to complete.
• Recognize the reporter: Thank people publicly or privately, depending on their preference, and focus praise on the behavior.
• Never punish honest reports: Apply a just culture so people who report their own mistakes are treated fairly.
• Act visibly: Fixing reported issues quickly is the strongest encouragement to keep reporting.
• Build trust:Psychological safety lets workers speak up without fear of blame or embarrassment.
• Measure participation, not just counts: Track good catch reports and closure rates as a leading indicator, but avoid quotas that encourage low-quality reports.

Example of Good Catch

At a distribution center, a forklift operator doing a pre-shift inspection notices that the hydraulic hose on her truck has a bulge near a fitting. She tags the truck out of service and submits a good catch report with a photo. Maintenance replaces the hose that morning and, prompted by the report, checks the rest of the fleet. They find two more hoses showing early wear.

The site safety lead shares the report at the next shift huddle and thanks the operator by name. The maintenance team adds hose condition to the preventive maintenance checklist, and the safety committee notes that hose issues have now appeared in three reports in a year. They contact the equipment supplier about a possible routing problem that causes the wear.

Frequently Asked Questions: Good Catch

What is the difference between a good catch and a near miss?

Many organizations use good catch for a hazard or error found before anything happens and near miss for an event that occurred without injury. Some treat them as the same thing. The key is to define the terms clearly in your own program.

Should good catches be rewarded?

Recognition helps, and OSHA has said that rewarding near miss and hazard reporting is permissible. Keep rewards simple and focused on participation and quality rather than volume.

Do good catches need to be recorded on the OSHA 300 Log?

No. The OSHA 300 Log records work-related injuries and illnesses that meet recording criteria. Good catches involve no injury, so they are tracked in internal systems instead.

Who should report good catches?

Everyone, including employees, supervisors, contractors and visitors. Field and lone workers should have a simple way to report from wherever they are working.