When the Incident Reports Go Quiet
A decline in reported concerns is usually presented as good news, and sometimes it is. A process may have improved. It is also possible that staff have stopped believing that reporting leads to anything. From the dashboard, the two situations look exactly alike, which is why I am cautious whenever I see a report count fall without an explanation.
Leaders rely on incident reports, near-miss reports, huddles, surveys, and complaints to understand what is happening in their organizations. Those channels are only as reliable as the culture around them. If raising a concern feels risky, takes too long, or seems pointless, the information never arrives. Leaders often learn the most useful things from staff who trust that raising a problem will not be held against them. That trust is worth looking for in any organization.
Why a low count is hard to interpret
AHRQ’s Surveys on Patient Safety Culture place event reporting within a larger set of conditions, including how the organization responds to error, how openly people communicate, staffing and work pace, teamwork, and leadership support. I find that framing useful because reporting does not happen in isolation. It reflects workload, local norms, and what happened the last time someone spoke up.
So before treating a falling count as success, it is worth asking whether staff are in fact encountering fewer risks, and whether they still feel free to say so when they encounter one. A survey can help answer the second question, provided the results are tied to an action plan and measured again later.
The first response sets the tone
How a leader responds to one concern affects whether the next one is raised. Curiosity tells the team that information is welcome. Defensiveness or a quick search for fault tells them to keep future concerns to themselves. A constructive response does not require agreeing with the person’s interpretation. It can begin with clarifying what was observed, what risk they see, and whether anything needs to happen right away, and it should end with the concern being documented and routed to someone who owns the next step.
A learning culture still has accountability. Reckless behavior and repeated disregard for safeguards call for an appropriate response. Many problems, however, involve unclear processes, competing demands, weak handoffs, or policies that do not match the actual work, and a fair review considers those conditions alongside individual choices.
Make reporting easier than working around the problem
When the official reporting path requires an unfamiliar login and a long narrative in the middle of a busy shift, only the most serious events get reported. I recommend a few clearly defined routes: immediate escalation for urgent concerns, a brief form for near misses, and a huddle log or improvement queue for recurring irritations. The form should ask for what is needed to understand and act, such as the time, the place, what was observed, and what was done. Asking the reporter to identify the root cause before submitting discourages reporting and introduces assumptions too early.
Shared language helps as well. AHRQ’s TeamSTEPPS program offers communication tools that give staff an agreed way to raise a concern in a busy or hierarchical setting. The specific phrase matters less than the team’s agreement that certain words will be taken seriously, and leaders need practice responding to them just as staff need practice using them.
Close the loop where people can see it
Nothing weakens reporting faster than silence afterward. Confidentiality may limit what can be shared, but an organization can nearly always acknowledge the report, explain the next step, and later describe what was learned or changed. Closing the loop does not mean adopting every suggestion. It means showing that the report entered a real process.
For measurement, review report counts alongside the time it takes to review a report, the share of reporters who received feedback, and whether the same concerns keep returning. I would also look across teams and shifts where numbers allow, since one organization can contain several quite different local cultures. A quiet dashboard may well reflect a safer operation. That conclusion is worth confirming with the people doing the work before anyone relies on it.
Sources
- AHRQ: About the Surveys on Patient Safety Culture Program
- AHRQ: SOPS Hospital Survey
- AHRQ: TeamSTEPPS 3.0
About the author
Sherry Sayari, MPH, is an Operational Standards Evaluator who has led population health, community outreach, and social services programs. More on the About page.
