“I’ve already reported this”: how a hospital ward manager can follow through on a staff concern

A report is the start of a conversation

When a hospital staff member says, “I’ve already reported this,” start by understanding her experience: whom she told, what response she received and what she expected to happen next. Action may have been taken without anyone telling her. Or her report may have reached the right people while the review is still underway. The gap between what has been done and what the person who reported it knows matters to the conversation that follows. Closing a case in the system is not yet a response to the person who raised it. She may report the issue again because she is unsure whether her first message was received at all. The organisation’s first step should therefore be to acknowledge receipt. Whether a lack of response actually discourages further reporting needs to be checked within the team, not assumed.

What the research shows about feedback

A cross-sectional study covering 16,797 responses from 829 work settings examined leadership walkrounds and feedback about actions taken. Where staff received such feedback, they rated safety culture and engagement more highly. This is a useful indication for hospitals, but it does not prove that the feedback itself caused the improvement: it could just as well have been a sign of an organisation that was already functioning better. The finding concerns an association between a communication practice and staff ratings, not the effectiveness of any single message. Even a well-written email cannot, by itself, remove the cause of a safety incident. It can, however, show the person who reported it what is happening with the case and form part of a broader practice of responding to concerns.

Three distinct responses

A response need not wait until the entire case is resolved, because it consists of three distinct messages. First, an acknowledgement tells the staff member that the information was received and who took it on. An update then explains the stage of the review, what information is still needed and when the next message will come. Only the final response sets out the decision, the reasons for it and how its impact will be checked. It can be framed in three sentences: what was established, what decision follows and when the person who reported the issue will learn the outcome of implementing it. Each message should have a clear deadline and reach the right person. That way, an acknowledgement does not masquerade as a solution, and an update about an ongoing review is not mistaken for a decision.

When a case takes time

Some ward issues cannot be resolved immediately. In those cases, separate responsibility for reviewing the issue from responsibility for contacting the person who raised it, and identify who will provide updates. If investigating the problem will take weeks, the staff member should know when to expect the next update and how to get in touch, rather than wait in silence for a final decision. If the timeline changes, tell them in advance and explain the delay. That does not mean disclosing everything: the response should respect confidentiality and state clearly what information can be shared. Even a partial but honest update distinguishes work in progress from a situation in which no one knows what happened to the case.

When the answer is no

Declining a proposed action also calls for a response, not just closure of the report. The manager should explain the criteria used to assess the proposal and which evidence did not support putting it into practice. It is worth distinguishing an inability to act from insufficient grounds for a particular solution. If the problem remains, name it, even if the staff member’s suggestion is not adopted. The conversation can then cover another possible safeguard and explain what it would address. It also helps to specify what new information would allow the case to be reopened. This response does not promise to accept every proposal, but it helps the person who raised the concern understand the decision and see that the concern itself was taken seriously.

How to show that the organisation is learning

According to WHO guidance, the value of incident reporting lies in learning and taking action to reduce risk, not simply collecting reports. The team should therefore hear what changed as a result of the concerns raised, without disclosing the identities of the people involved. A briefing can cover a recurring problem and the solution adopted without linking reports to assessments of individual staff members. The next step is to check whether the solution works where the problem was observed and share the result with those concerned. If it does not work, say so and return to the review. WHO guidance helps structure this kind of learning, but it is not experimental evidence that any one approach to reporting is effective.

Making reporting feel worthwhile again

Making reporting feel worthwhile again can begin with cases that have long gone unanswered. Revisit them and state clearly which will be taken forward, which have been closed and which have been referred elsewhere. Then track the proportion of reports that receive a response and ask staff whether they know what happened to their case. Also watch whether the same problem keeps recurring. A review of 14 interventions concerning psychological safety and speaking up points to the need for action at several levels and visible support from leaders. The findings were mixed, however, and measures often relied on self-reports. Communication training alone therefore provides no basis for promising that staff will report problems more often.

Closing a case in the system does not mean the person who raised it knows what happened. Plan the response from the initial acknowledgement through to explaining the decision and checking its impact.

Using Empatyzer to respond to concerns raised by hospital staff

A ward manager can use Em to practise an initial response to “I’ve already reported this.” Instead of immediately defending against the criticism, they can prepare a sentence that acknowledges the staff member’s previous experience, confirms receipt of the concern and gives a date for the next update. In the “About me” view, they can examine their own defensive reaction to an accusation of inaction before returning to the conversation. Em can also help draft three short messages: an acknowledgement, an update with the next step, and a refusal that explains the decision. If several reports have led to a decision affecting the team, a conversation with Em about the team can help the manager prepare a shared explanation and communicate the resulting change. In each case, the manager establishes the facts, timelines and limits on what information can be shared. The tool helps them find the words, but it does not replace an organisational response or checking whether the promised action actually happened.