A Report Is Not a Fix

The failure has a shape, and once you have seen it you will recognize it in almost every hospital that has tried this.

Month one. You build the form. It is short, it is anonymous or near enough, and you introduce it well. You say the right things about blame, you mean them, and people believe you. Reports start coming in. Some of them are genuinely useful. There is a small, real sense of momentum.

Month three. The reports are in a folder. Someone means to get to them. That person is the practice manager or the medical director, and they have not stopped doing any of their other work to make room for this. The folder is not ignored, exactly. It is deferred.

Month six. Reporting has quietly stopped. Nobody announced it. Nobody complained. The form still exists and technically still works. It just doesn't receive anything anymore, and when you ask why, people are vaguely apologetic and can't quite say.

Most safety systems fail at the last step, not the first. And the diagnosis is almost always the same: a report is not a fix. Capturing a signal is the opening move, and it is exactly where most hospitals think the work ends.

Why the collapse is rational

It is tempting to read the month-six silence as apathy, or as evidence that the team wasn't ready. It is neither. It is a correct inference.

Your team ran an experiment. They spent scarce time and took a small social risk to tell you something. Then they watched to see what happened.

Nothing happened.

The conclusion they drew, that reporting costs something and returns nothing, is not cynicism. It is accurate. They will not repeat the experiment, and importantly, they now know something about the system that they will pass on to every new hire without ever saying it aloud.

This is worth being blunt about because of what it implies: launching a reporting system you cannot follow through on leaves you worse off than not launching one. You haven't just failed to gain a safety system. You have actively demonstrated to your team that raising things is futile, and you have burned the credibility you would need for a second attempt.

The five steps, and why skipping any one breaks it

Closing the loop is a sequence. It is not complicated, but it is unforgiving. Each step depends on the one before, and a gap anywhere causes the whole thing to leak.

1. Look at contributing factors, not the event

This is where most reviews go wrong in the first five minutes.

A wrong dose is what happened. It is a label, not an explanation, and you cannot fix a label. The look-alike vials, the interrupted count, the missing second check, the handoff compressed into ninety seconds at shift change: those are why, and they are the only part you can actually change.

The test is simple. If your analysis produces a sentence with a person as the subject and a failure as the verb, you have described the event, not its causes. Keep going.

2. Decide on a specific change

Something concrete about how the work is done.

Not "reinforce the importance of double-checking." Not "remind staff to be vigilant." A change you could photograph, or point to in a workflow, or notice the absence of. Move the concentration to a different shelf. Add a hard stop in the software. Standardize to one concentration so the calculation disappears. Protect the medication round from interruption with a physical signal.

If you cannot describe what a visitor would see that is different, you have not decided on a change yet.

3. Give it an owner and a date

A fix that belongs to everyone belongs to no one.

This is the step that quietly kills more improvement work than any other, and it is entirely administrative. One named person. One date. Written where someone will look at it again. Not because people are unreliable, but because a hospital generates enough urgent work to bury any task that lacks a name attached to it.

4. Verify it actually worked

Weeks later, someone checks. Two questions, both concrete:

• Is it being used? Not "was it announced," but is the new thing actually happening, at 3 a.m., when the person doing it wasn't in the meeting where it was decided?
• Did the signal stop recurring? This is where captured near misses earn their keep. If the same catch keeps appearing, your fix is decorative.

If it held, say so. If it didn't, adjust, and treat that as a normal outcome rather than a failure. Most first attempts are partly wrong. The hospitals that improve are not the ones that guess correctly; they are the ones that check.

5. Tell the team what changed

This is the step that pays for all the others.

When people see that a report led to a real, visible fix, they report again. The loop closes and then re-opens on its own, because you have demonstrated that the transaction works. When reports vanish into a void, people learn that speaking up is a waste of breath, and that lesson is far more durable than any poster.

The feedback does not need to be elaborate. A standing item in rounds. A short note by the drug cabinet. "Three of you flagged the look-alike vials. They've been separated as of Monday." Thirty seconds, and it does more for your reporting rate than any relaunch.

One caution: feed back changes, not statistics. "We received 47 reports last quarter" tells the team you counted. "The vials moved because of what you told us" tells them it mattered.

The parts nobody warns you about

Not every report deserves a fix. Some are duplicates, some are one-offs, some describe things outside your control. Trying to action everything is how the folder becomes unmanageable. What every report deserves is acknowledgement and a decision: actioned, monitored, or closed with a reason. Reports that receive a visible "we looked at this and here's why we're not changing anything" do far less damage than reports that receive nothing.

Volume is not the goal. The published veterinary work on quality improvement has spent real effort just establishing shared definitions of what these activities are, which tells you how young this field is in our profession. It is easy to mistake activity for improvement. Ten signals with five closed loops beats two hundred with none.

The reporter is often the best source of the fix. They were there. Ask them what they would change. This costs nothing, produces better fixes, and does something else valuable: it converts the reporter from someone who raised a problem into someone who solved one.

What to do this week

Take the last ten reports and mark each one. Actioned, monitored, or closed, with a reason. If most are unmarked, you have found your leak.

Close one loop visibly. Pick a single signal, make one concrete change, and tell the team you did it because of their report. The first closed loop is worth more than the next fifty forms.

Put a name and a date on every open item. Today. This is the cheapest high-yield step in the entire sequence.

Add feedback to an existing meeting. Do not create a new one. Two minutes in rounds, standing item, every time.

Reporting opens the loop. Closing it is the work.

A question for your team

Of the last ten signals your people raised, can you name what changed because of them?