The fastest way to kill your reporting culture: never follow up
Reporters who submit safety events and hear nothing back stop reporting. The pattern is consistent and well-documented: initial reporting volume reflects genuine safety awareness; volume decline reflects learned futility. When workers conclude that their reports go into a black box — reviewed by no one, acted on by no one, acknowledged by no one — they stop investing the time and psychological effort of reporting. The silence communicates 'this doesn't matter' more clearly than any explicit message could.
Feedback doesn't need to be elaborate to change behavior. A brief, automated status update — 'your report has been reviewed and assigned to the facilities team' — is enough to break the black-box perception. Reporters don't need a detailed response to every submission; they need evidence that the submission was received, reviewed, and handed to someone who can act on it. The bar for effective feedback is lower than most organizations assume.
Many organizations process safety events thoroughly but never communicate back to submitters. The review happens, the corrective action is assigned, the fix is implemented — and the person who spotted the problem and took the time to report it never learns any of it. The organizational learning is real. The reporter's experience is that nothing happened. Both things are true simultaneously, and the second one is what shapes future reporting behavior.
How ImprovementFlow addresses this
Automate the feedback loop so it happens by default rather than as an extra step. ImprovementFlow's GoodCatch automatically notifies reporters when their event is reviewed, when a corrective action is assigned, and when the action is marked complete. Each notification is brief and informational — a status update, not an essay. The automation ensures consistency: feedback doesn't depend on a manager remembering to reach out, and it doesn't skip events during busy periods.
Even simple status updates change the experience of reporting in ways that drive sustained engagement. The reporter who submits a near-miss and receives 'reviewed — facilities team will inspect the equipment this week' has a fundamentally different relationship with the reporting system than one who hears nothing. The first reporter is likely to submit again. The second is likely to conclude that reporting is not worth their time.
Make closed-loop feedback the default, not an aspiration. Design the system so that failing to provide feedback requires deliberate action, not the reverse. When notifications are automatic, the effort required is to suppress them — and there are few legitimate reasons to do so. When feedback requires a manual step, the effort required is to remember and execute it, and during busy periods that effort loses to clinical priorities every time.
At UNC Health Care: sustained reporting growth over 6 years, with frontline engagement increasing 5x — driven by consistent follow-through and visible action on reported events.
Start with what you need today
Most customers begin with safety reporting or huddle boards and expand from there. No enterprise commitment required.