Catch the weak signals before they become harm
A GoodCatch program captures the near-misses and early warning signs your teams see every day — and turns them into systemic improvements to your workflows and processes. The more your people catch, the safer your organization gets.
Most reporting only captures what already went wrong. By the time an event reaches your safety log, a patient has been affected — and even then, voluntary reporting catches only a fraction of what actually happens. Industry studies estimate that as little as 7% of harmful events ever make it into a hospital's incident system.
But every adverse event is preceded by near-misses, workarounds, and weak signals — the catch a nurse makes at the last second, the label that's almost-but-not-quite wrong, the process that keeps tripping people up. These are the early warnings that tell you where the next harm is coming from. In most organizations, they vanish unrecorded.
A GoodCatch program is built to surface exactly those signals — and to act on them before they become the event you have to report.
What a GoodCatch is
A near-miss — a "close call" — is an event that didn't reach the patient, or didn't cause harm only because someone caught it in time. A GoodCatch is a near-miss that someone reported. The name is deliberate: it credits the person who caught it, and reframes reporting as a contribution rather than a confession.
A weak signal is the faint, easy-to-dismiss early indicator that something in the system is drifting toward failure — a recurring workaround, equipment that's awkward to use safely, a handoff that keeps going sideways. High-reliability organizations are "preoccupied with failure": they treat these small signals as free lessons about the system and chase them down before they line up into harm.
GoodCatch is its own program — distinct from the other things your teams report:
GoodCatch
Proactive near-misses & weak signals → systemic workflow and process improvement
Safety reporting
Adverse events and harm that have already occurred
Well-being reporting
Signals affecting staff well-being and burnout
Quality reporting
Defined quality metrics and regulatory measure programs
How it works
- 1
Capture
Frontline staff report a near-miss or weak signal in under 60 seconds, from any device. The form asks for what matters and nothing more — because every extra field is a report you'll never get.
- 2
Triage
Each report is routed automatically to the right reviewer by type, area, and potential severity — so high-potential catches escalate fast and nothing sits in an inbox.
- 3
Aggregate analysis
Reports are pooled and analyzed together, not one at a time. Pattern detection surfaces the systemic signal hiding inside dozens of small, individually-unremarkable reports.
- 4
Systemic action
Findings become workflow and process changes, prioritized by how durably they remove the risk — design changes first, reminders last (see the action hierarchy below).
- 5
Closed-loop feedback
Every reporter hears back: their catch was reviewed, and here's what changed because of it. This is what turns a one-time reporter into a habitual one.
- 6
Sustain
Dashboards track reporting rate, time-to-feedback, and whether actions actually held — so the program keeps improving instead of fading after launch.
The intelligence is in the aggregate
Any system can collect reports. What separates a high-performing GoodCatch program is what happens next: instead of closing each report on its own, leading programs pool them and analyze the causes together.
That's where the real signal lives. A single near-miss looks like a one-off. Forty near-misses, viewed together, reveal the badly-designed workflow, the confusing label, the staffing pattern that keeps setting people up to fail. Some systemic causes simply cannot be seen one incident at a time — they only appear in the aggregate.
GoodCatch is built around this: continuous pattern and common-cause analysis across every report, so the weak signals add up to a clear picture of where to act.
From signal to systemic fix
The strongest GoodCatch programs don't just tell people to be careful — they redesign the work so the risk is gone. Fixes are ranked by how durably they remove the hazard.
- Forcing functions and constraints
- Equipment, layout, and physical changes
- Automation that removes the error-prone step
- Standardized protocols and checklists
- Redundancies and independent double-checks
- Targeted alerts and reminders in the workflow
- Training and education
- New policies and rules
- "Be more careful" messaging
What top-performing programs get right
A just culture — not a "no-blame" culture. Staff are safe to report honest errors and at-risk behavior, while genuine recklessness is still addressed. People report when it's safe to.
Frictionless capture. Cutting a report form from 16 fields to 7 has been shown to multiply reporting volume several times over. Speed is a feature.
Closed-loop feedback. The fastest way to kill a program is the "black hole" — reports that go in and nothing comes back. Telling reporters what changed is the engine of participation.
Visible leadership follow-through. When leaders act on catches and talk about them, reporting climbs. When they don't, it stalls.
Recognition. Celebrating great catches — by name — signals that catching problems early is exactly what good looks like.
Metrics that prove it's working
Near-miss share of reports
A healthy program is dominated by near-misses and weak signals, not just harm events. The ratio is one of the clearest signals of a strong reporting culture.
Reporting rate
A rising volume of near-miss reports is a leading indicator of a safer organization — you're seeing the early warnings instead of missing them.
Time to feedback
How fast a reporter hears what happened. Faster loops drive more reporting; it's the discipline most programs never measure.
Percent of reports that led to action
The proof the program works: catches that turned into real workflow and process changes.
At UNC Health Care, a proactive reporting culture drove a 5x increase in frontline engagement, with thousands of catches reviewed and acted on — sustained over six years, while safety-and-quality perception climbed 39 percentage points. The organizations that catch the most are the ones that improve the most.
Read the UNC Health Case StudyHow ImprovementFlow runs your GoodCatch program
Configurable near-miss and weak-signal taxonomy — capture the categories and contributing factors that matter for your processes, not a generic form.
Sub-60-second mobile capture from phone, tablet, desktop, or shared kiosk, so reporting fits into clinical workflow instead of interrupting it.
Automatic routing by type, area, and potential severity — high-potential catches escalate immediately, with no manual triage queue.
Aggregate pattern and common-cause analysis that surfaces the systemic signal across many reports — the patterns single-incident review can't see.
Action tracking aligned to the strong-to-weak hierarchy, so fixes are durable design changes, not just another reminder.
Automated closed-loop notifications that tell every reporter their catch was reviewed and what changed — the engine that keeps reporting climbing.
GoodCatches surface on digital huddle boards the moment they're submitted, giving daily huddles current-day intelligence.
Go deeper on near-miss reporting
How to build a GoodCatch program
Executive sponsorship, frictionless capture, tiered review, and closed-loop feedback — the elements of a program that sustains itself.
Near-miss reporting
Why near-misses are the highest-value, most under-reported signal you have — and how to capture them.
Reducing reporting friction
Every extra field is a report you'll never get. How to design for 60-second submission.
Closing the feedback loop
The black hole that kills reporting programs — and how to automate the loop that keeps them alive.
Methods that turn catches into fixes
Learning from defects
A structured method for turning near-misses and defects into systemic understanding.
High reliability
The HRO mindset of preoccupation with failure that underpins every great GoodCatch program.
Just culture
The non-punitive-but-accountable culture that makes honest reporting safe.
Root cause analysis
From a confirmed pattern to its underlying cause and a durable countermeasure.
Analysis tools for the aggregate
FMEA
Find and design out failure modes in a high-risk process before they cause harm.
Fishbone diagrams
Map the contributing factors behind a recurring near-miss pattern.
5 Whys
Drive past the symptom to the systemic cause worth fixing.
Pareto analysis
Find the vital few patterns generating most of your weak signals.
Related solutions
Safety reporting
Capture and act on adverse events and harm that have already occurred.
Quality reporting
Real-time operations and quality metrics your teams build themselves.
Huddle boards
Surface GoodCatches and action items on tiered digital huddle boards.
Improvement projects
Turn confirmed patterns into tracked A3, PDSA, and RCA improvement work.
Start catching what you're missing
Most teams stand up a GoodCatch program alongside safety reporting or huddle boards and expand from there. No enterprise commitment required.