Key takeaways
- In one NHS survey, 71.7% of staff who filed a report got no feedback on the action taken, and about four in ten then held back later reports.
- Feedback can be brief: who owns the report and what was done is enough to break the black-box perception.
- Feed back at three levels: to the reporter, to the unit at huddles and to leaders as themes.
- Treat an event as unfinished until the reporter has heard what happened, and track time to feedback.
What happens when reporters hear nothing
Lack of feedback is one of the most consistently reported barriers to incident reporting. In a survey of doctors and nurses in six hospitals, it was the most common barrier named: 57.7% of doctors and 61.8% of nurses agreed it put them off. In a later survey at NHS hospitals, 71.7% of staff who had filed a report received no feedback on the action taken, and about four in ten had held back from reporting a later incident because of how earlier reports were handled.
Often the review did happen. The event was analyzed, an action assigned and a fix made, but nobody told the person who reported it. The organization learned; the reporter's experience was that nothing happened. The second fact is the one that shapes whether they report again.
What good feedback looks like
A UK study of feedback from incident reporting found that effective systems combine information (telling staff what was found) with action (visibly fixing things), and feed back at every level of the organization, not just to the reporter. Feedback doesn't need to be elaborate. A brief update such as "reviewed, and pharmacy is separating the two products on every unit" is enough to break the black-box perception.
- To the reporter: confirmation the report was received, who owns it and what was done.
- To the unit: what was learned and what changed, shared at a huddle.
- To the organization: themes across units and the fixes they led to, shared with leaders and committees.
ImprovementFlow
Safety Reporting
Safety Reporting closes the loop by design: named reporters receive feedback on what was done, and everyone who submits sees what happens next, including people who chose to stay anonymous.
Make feedback the default
If feedback depends on a manager remembering to send it, it will lose to clinical priorities on busy days. Design the process so that closing the loop is part of closing the event: an event isn't finished until the reporter has been told what happened.
What to do this quarter
- 1Agree a feedback standard with reviewers, for example an acknowledgment within two working days and an outcome when the event is closed.
- 2Write three or four short message templates so feedback takes a minute, not a meeting.
- 3Add one "you reported, we fixed" story to each unit huddle.
- 4Measure the share of reporters who heard back, and report it with your other safety measures.
How ImprovementFlow supports this
ImprovementFlow Safety Reporting is built to close the loop: named reporters receive feedback on what was done, and everyone who submits sees what happens next, including people who chose to stay anonymous.
