Designing a Good Catch Program That Doesn’t Undermine Reporting Culture

A hospital that has done the hard work of building a non-punitive event-reporting system faces a second, less obvious design problem: what to do when someone catches a problem before it reaches a patient. Celebrating a good catch — a near miss or an unsafe condition someone stopped before it caused harm — seems like an easy win for safety culture. Done carelessly, it can quietly undo the same trust the reporting system spent years building: a recognition programme that turns into a competition, or that implies only “good” catches are worth the safety office’s attention, teaches staff a different lesson than the one intended.

This guide is about designing the recognition layer itself — not the underlying event-reporting system that captures the catch in the first place. If you haven’t yet built or redesigned the intake system a good catch programme sits on top of, see our companion guide on designing a hospital incident-reporting system people actually use, which covers non-punitive intake design, anonymity models, and the reporting-rate metric in depth. Written for hospital patient-safety officers, quality directors, risk managers and infection preventionists who own or are building a good catch recognition programme — not for staff learning how to submit a single nomination.

What counts as a good catch

A good catch is a near miss or an unsafe condition someone identified and stopped before it reached a patient — not any report, and not an event that did reach a patient with or without harm. AHRQ’s Common Formats for Event Reporting, the closest thing to a national taxonomy for hospital event data, draw exactly this distinction: a near miss is an event or condition that had the potential to cause harm but didn’t, because it was caught or because of chance, while an unsafe condition is a circumstance with the potential to cause harm that hasn’t yet produced an event at all. Both belong in a good catch programme; an event that reached the patient does not, regardless of whether harm resulted — those events belong in the standard event-reporting and review workflow, not the recognition track. Keeping that boundary clear matters more than it looks: blur it, and a good catch programme starts either recognising people for events that actually caused harm (which reads as tone-deaf to anyone involved) or, worse, becomes a backdoor for logging harm events as “catches” to avoid the more serious review process.

Why recognition is riskier than it looks

Recognition sounds like the easy, purely positive half of a safety programme — the reward for a system that otherwise asks people to report their own and their colleagues’ mistakes. In practice it carries real design risk, for three specific reasons:

• Recognition can imply blame elsewhere. Celebrating the person who caught a mislabeled syringe can read, to the person who mislabeled it, as public identification of their error — even when no names are used for the original condition. A programme that doesn’t think through how a catch is described in public recognition risks recreating exactly the blame dynamic the underlying reporting system was designed to remove.
• Competitive framing invites gaming. Any structure that turns catches into a scored or ranked contest — a leaderboard, a per-unit quota, a prize for the “most” catches in a period — creates a direct incentive to submit marginal or trivial items to hit a number, which degrades the signal the safety office actually needs and can crowd out attention to the catches that mattered.
• Recognition can eclipse the more important signal. If good catch stories become the visible, celebrated face of the reporting system while harm-event reports stay invisible by design (as they should, for confidentiality reasons), staff can absorb the message that reporting is really about winning recognition for stopping problems — not about the harder, less rewarding work of reporting when something actually went wrong. A programme that isn’t deliberately kept subordinate to harm-event reporting can end up working against the culture it was meant to reinforce.

None of this argues against recognition — positive reinforcement is a real and well-established lever in safety culture work. It argues for building the programme with the same structural discipline used to make event reporting non-punitive in the first place: the incentives have to survive contact with real behaviour, not just read well in a policy document.

Submission mechanics: a lightweight, separate track

A good catch nomination should never be the same form as a formal event report. Folding recognition into the event-reporting intake form does two kinds of damage: it adds friction and ambiguity to a form that should stay fast (see the ease-of-entry discussion in the incident-reporting guide linked above), and it forces the reporter to decide, at the moment of filing, whether they’re reporting a problem or nominating themselves or a colleague for recognition — a decision that has nothing to do with what the safety office actually needs from that report.

Design the nomination path as its own short form, separate from the event-reporting channel:

• Who can nominate. Allow both self-nomination and peer nomination. Peer-only nomination systematically under-recognises the people least likely to be noticed by colleagues — often the same staff who are already least likely to file a formal report.
• What the form asks for. A short narrative of what was caught and how, plus enough detail for the review committee to assess it — not the full clinical documentation a formal event report requires. If a nomination reveals something the safety office needs to investigate further as an unsafe condition, route it into the standard event-review workflow at that point; don’t try to make the nomination form double as an investigation intake.
• Where it can be submitted from. The same low-friction channels that work for event reporting — an EHR-embedded link, a QR code, a paper fallback — reduce abandonment for recognition nominations the same way they do for event reports.

Review cadence and criteria-based selection

A committee, not a single manager, should review nominations, and it should meet on a fixed, predictable cadence rather than reactively. A monthly review with a quarterly spotlight (a small number of catches highlighted more broadly, in a newsletter or huddle) is a common working rhythm: frequent enough that recognition stays close in time to the catch, infrequent enough that the review itself doesn’t become a rubber stamp.

Composition matters as much as cadence. Include the patient safety office, but also rotate in frontline staff from different units and shifts — a committee made up entirely of safety-office staff tends to reward catches that map cleanly onto existing taxonomy, and can miss catches that matter clinically but don’t fit a familiar category. Rotate membership on a fixed schedule (annually, or every few cycles) so the committee doesn’t calcify into the same small group making the same judgment calls indefinitely.

Select against a published rubric, not a popularity vote or a manager’s discretionary pick. A workable rubric weighs a small number of criteria explicitly: the severity of harm plausibly avoided, whether the catch reveals a systemic issue worth fixing rather than a one-off, and whether the underlying insight is replicable — useful to other units, not just interesting as an isolated story. Publishing the rubric itself, not just the fact that one exists, is part of what keeps the process from feeling arbitrary to staff who submit and don’t get selected.

Recognition mechanics that stay non-punitive and non-competitive

How a catch is celebrated matters more than how often. A few structural choices keep recognition from drifting into the competitive or punitive territory described above:

• Favour broad, low-stakes recognition over rare, high-value prizes. A programme that gives everyone who’s selected a small, consistent token — a mention at a huddle, a certificate, a modest gift — spreads the incentive structure widely. A programme built around one large annual prize concentrates the incentive on a small number of people and makes the selection process itself a higher-stakes, more contested event.
• Never publish a per-unit or per-individual leaderboard. Ranking units or people by catch count is the single fastest way to convert a recognition programme into a numbers game. If leadership wants to track participation breadth (see the metrics section below), do it as an internal management metric, not a public ranking.
• Keep recognition decoupled from performance reviews and compensation. Tying good catch recognition to an individual’s performance evaluation or pay reintroduces exactly the disciplinary-channel proximity that non-punitive reporting design works to remove elsewhere — see the discussion of separating the reporting channel from the disciplinary channel in the incident-reporting guide. A good catch programme that feeds into raises or ratings stops being a culture lever and starts being a metric people manage to.
• Respect the reporting system’s anonymity model. If a hospital’s underlying event-reporting system is confidential rather than attributed, don’t force a nominee to be named publicly as a condition of recognition — offer an anonymous or low-visibility recognition option (a private note, a confidential acknowledgment) alongside the public one, and let the person choose.
• Describe the catch, not the failure it prevented, in blame-neutral terms. Public recognition text should focus on what the person did — noticed, verified, paused, escalated — rather than narrating the mistake or condition in enough detail that colleagues can identify who or what created it.

Guardrails against gaming

Beyond the mechanics above, a few explicit rules keep a good catch programme from producing the wrong incentives once it’s running:

• No quotas, at the unit or individual level. A quota (even an informal, unstated expectation of “a few catches a month per unit”) reliably produces submissions manufactured to meet the number rather than genuine catches.
• Don’t reward volume as its own end. A per-submission incentive (a small reward for every nomination filed, regardless of committee review) creates an incentive to submit marginal items. Reserve recognition for nominations the committee actually selects against the published rubric, not for the act of submitting alone.
• Don’t let a rising submission count alone stand in for programme health. A count going up can mean the programme is working, or it can mean the criteria have drifted and trivial items are being nominated. Pair volume with the quality and breadth metrics below before drawing a conclusion either way.
• Revisit the rubric periodically, out loud. A criteria set that goes years without review tends to either calcify around whatever got selected early on, or drift as committee membership turns over. A scheduled annual review of the rubric, with the reasoning documented, keeps selection defensible.

Keeping good catches subordinate to harm-event reporting

The single most important design discipline for a good catch programme is deliberately keeping it secondary, in messaging and visibility, to the harm-event reporting system it sits alongside. Good catches are genuinely worth celebrating, but they are not the primary purpose of a hospital’s event-reporting infrastructure — catching and correcting harm events, including the ones that reached a patient, is. If staff communications, huddle time, or leadership attention give disproportionately more airtime to good catch stories than to what the organisation learned from an actual harm event, the programme is sending a subtle signal that reporting is really about earning recognition rather than surfacing what needs to be fixed. Build the communication cadence so that harm-event learning (aggregated, de-identified, per the closed-loop practice described in the incident-reporting guide) gets at least as much visibility as good catch recognition, not less.

Metrics that show a good catch programme is working

The reporting-rate metric used to evaluate the underlying event-reporting system doesn’t transfer cleanly to a recognition programme layered on top of it — a good catch programme needs its own, different signals:

• Breadth of participation, not just volume. Track how many distinct units, shifts and roles are represented among nominations and selections over a rolling period, not just the total count. A programme where nominations come from the same one or two units month after month isn’t reaching the rest of the organisation, regardless of how many total submissions it produces.
• Selection rate against the rubric, tracked over time. If the share of nominations the committee actually selects starts drifting sharply up or down, that’s a signal either the rubric has loosened (drifting up) or nominations have become routine box-checking the committee is quietly filtering out (drifting down, alongside falling submission quality).
• Harm-event reporting rate holding steady or rising alongside good catch activity. This is the cross-check for the subordination discipline above: if good catch submissions climb while harm-event reports flatten or fall, that’s evidence attention is shifting toward the more rewarding track at the expense of the more important one, and worth investigating directly rather than treated as two unrelated numbers.
• Staff perception of non-punitive response. AHRQ’s Surveys on Patient Safety Culture (SOPS) instruments include survey items specifically on how staff perceive the organisation’s response to reported problems. A good catch programme that’s working should show up as a positive contributor to that broader perception over time, not just as its own isolated participation count.

A good catch programme is a genuine, well-established tool for reinforcing a hospital’s safety culture — but it’s a layer built on top of the harder, structural work of non-punitive event-reporting design, not a substitute for it. Build the recognition mechanics with the same discipline used to keep the underlying reporting system non-punitive, and the programme reinforces the culture it was meant to support instead of quietly working against it. For the broader framework this sits inside, see our guides on high reliability organizing principles and how hospitals classify behaviour after an adverse event — the downstream process a good catch programme deliberately stays separate from — and, for how good catch stories can feed team-level communication, safety huddle structure and cadence.

Frequently asked questions

What is a “good catch” in patient safety?

A good catch is a near miss or unsafe condition — something with the potential to cause patient harm — that a staff member identified and stopped before it reached the patient. It’s distinct from an event that reached the patient, whether or not that event caused harm; those belong in the standard harm-event reporting and review workflow rather than a recognition programme.

Should a good catch programme use a leaderboard or per-unit competition to drive participation?

No. Ranking units or individuals by catch count is one of the most reliable ways to convert a recognition programme into a numbers game, incentivising marginal or manufactured submissions to hit a count. Track participation breadth internally as a management metric instead of publishing a competitive ranking.

Should good catch recognition be tied to a performance review or a financial reward?

Generally no. Tying recognition to performance ratings or compensation reintroduces the same proximity to the disciplinary and evaluation channel that non-punitive reporting design works to remove elsewhere in the reporting system. Favour broad, low-stakes, non-monetary recognition instead of individual financial rewards tied to catch count.

How often should a good catch review committee meet?

A monthly review cadence, with a quarterly spotlight highlighting a smaller number of catches more broadly, is a common working rhythm — frequent enough that recognition stays close in time to the catch, infrequent enough that review doesn’t become a rubber stamp.

How is a good catch programme different from the underlying incident-reporting system?

The incident-reporting system is the intake and taxonomy infrastructure that captures every event, including harm events, and routes them for review. A good catch programme is a narrower recognition layer built on top of that system, specifically for near misses and unsafe conditions someone stopped — it should use its own lightweight nomination form and committee process, not the formal event-report intake.