Incident Reporting: What Happens After You Submit

Ask a group of surgical trainees when they last submitted an incident report and you will get a short, uncomfortable pause. Ask the theatre nursing team the same question and you will get answers measured in days.

That gap is not because nursing staff encounter more problems. It is because surgeons have learned, correctly, that submitting a report is an act with no visible consequence — the form goes somewhere, nothing comes back, and the same thing happens again three months later. Combine that with a suspicion that reporting is a way of getting someone into trouble, and the rational response is to stop.

This post explains where a report actually goes, what happens to it, and how to write one worth reading. It sits within our governance series.

What the system is for

An incident report is not a complaint, not a disciplinary instrument, and not a substitute for telling the patient. It exists to build a picture across many events that no individual can see.

That aggregate function is the point, and it is why reporting the small stuff matters more than it feels like it should. A single missing implant tray is an irritation. Forty reports of missing implant trays across six months is a procurement problem with a name, an owner and a business case — and the fortieth report is worth nothing without the first thirty-nine.

Report the near misses

The strongest argument for reporting is that the most valuable events are the ones where nobody was harmed.

Near misses are the free lessons: all of the information about how the system nearly failed, none of the harm. A department that only reports harm is studying its failures at the most expensive possible moment.

Where a report actually goes

The mechanics vary by system, but the shape is consistent.

1. You submit to the local system (Datix or an equivalent).
2. It reaches a local manager — usually the ward, theatre or department lead — within a day or so.
3. It is graded for actual and potential harm. Grading drives everything downstream.
4. It is triaged: low-harm reports usually go to aggregate review; higher-harm events trigger a proportionate response, which may be a full systems investigation, a swift review, or a thematic look across similar events. In England this is governed by PSIRF, which replaced the old automatic threshold-driven RCA.
5. It is reviewed in a governance meeting — departmental, divisional or both.
6. Themes are extracted across many reports, which is where the real value sits.
7. It flows to a national system in most jurisdictions.

In England the national layer is the Learn from Patient Safety Events (LFPSE) service, which has fully replaced the National Reporting and Learning System — NRLS was decommissioned on 30 June 2024. NRLS had been receiving around 2.2 million reports a year, though under 1% came from primary care, and part of LFPSE's purpose was to make recording workable across all care settings rather than mainly acute hospitals.

Accurate as of July 2026. National reporting systems differ by jurisdiction and are actively changing — confirm the current arrangement where you work.

Anonymous is not the same as confidential

A distinction that matters and is constantly muddled.

Confidential reporting means your name is recorded but handled carefully and not shared beyond those who need it. This is the default in most local systems, and it is what you almost always want.

Anonymous reporting means nobody knows who submitted it. It sounds safer. It is usually worse, because nobody can come back to ask the question that makes the report useful — what exactly happened next? — and an anonymous report can rarely be investigated properly.

If your department is one where people feel they must report anonymously, the anonymity is not the problem. It is the symptom.

How to write one that gets acted on

Most reports are unusable. The difference is small and entirely learnable.

Do:

• State what happened, factually and chronologically. Times, sequence, who was present in role terms.
• Say what the consequence was, actual and potential. "Caught before insertion" is critical information.
• Describe the conditions — staffing, workload, time of day, equipment, interruptions. This is what makes the report analytically useful rather than just a record.
• Include what recovered it. If someone noticed, say what prompted them. That is the barrier that worked and it is worth protecting.
• Suggest what would prevent it. You were there; you have the best view of this in the entire process.

Don't:

• Name individuals or attribute blame. Use roles.
• Speculate about cause. "Antibiotics given late" is a fact; "because the anaesthetic assistant wasn't paying attention" is a guess that derails the analysis.
• Put patient identifiers in the free text. Use the structured fields. Free-text identifiers are a data protection problem.
• Write it as a complaint about another department. It will be read as one and dismissed.
• Wait. Report while you remember the detail.

A usable report reads roughly like: "Prophylactic antibiotics administered 40 minutes after knife-to-skin. Case started 25 minutes late following an emergency add-on; the antibiotic was not drawn up during the delay and the checklist pause was completed while the patient was being positioned. No harm identified. Suggest antibiotic preparation is added to the trolley set-up rather than being a separate step."

That report can be acted on. "Antibiotics late again" cannot.

Reporting is not candour, and not a substitute for it

A recurring and serious error. Submitting an incident report does not discharge your obligation to tell the patient what happened. They are separate duties on separate timescales, and the patient conversation is usually the more urgent of the two. See Duty of Candour.

Why surgeons under-report, honestly

Worth naming the real reasons rather than the polite ones.

• No feedback. The single largest cause. A report that vanishes teaches you not to write the next one.
• Fear of blame — for yourself or, more often, for a colleague you would rather protect.
• Time. The form is long and you are between cases.
• Cultural signal. If no consultant in the department reports, no trainee will.
• Belief it is for nurses. Widespread, unspoken, and wrong.

The fixes are structural, not exhortative: departments where reporting is healthy have consultants who visibly report their own complications, a standing agenda item that reads back what came of previous reports, and a named person who closes the loop with the reporter. That last one is the highest-yield intervention available and almost nobody does it.

If you are the one being reported

It happens, and it is not an accusation. A report describes an event, not a verdict on a person.

• Do not respond defensively or approach the reporter to discuss it.
• Engage with the review, and describe the conditions you were working under honestly.
• Do not alter any record. Add a dated addendum if something needs correcting.
• Get advice from your indemnity provider if the event is serious.
• Get support. Being at the centre of an incident is genuinely harmful, and departments are consistently worse at this than they think.

Speaking up when the system does not respond

Where a genuine safety concern is not acted on, escalation routes exist — a departmental or divisional lead, a designated speaking-up role, the medical director, and ultimately external regulators. Most jurisdictions provide legal protection for staff raising genuine safety concerns.

This is a route to use when the ordinary process has failed, and using it in good faith is a professional duty rather than disloyalty. Document what you raised, to whom, and when.

What good looks like

You can assess your own department against this quickly:

• Consultants report their own complications, visibly
• Near misses are reported at least as often as harm events
• Every report gets an acknowledgement and, where appropriate, a reply
• The governance meeting opens by reading back what happened to previous reports
• Themes are presented to the department, not just filed upward
• Nobody has ever been disciplined for reporting in good faith, and everyone knows it

The summary

Report the near misses, describe the conditions rather than the people, suggest the fix, and do it while you remember. Confidential beats anonymous. Reporting does not replace telling the patient.

And if you have any influence over how your department runs: close the loop. Tell people what happened to their report. Nothing else you can do will raise reporting rates as much, and every theme the department ever identifies depends on someone bothering to file the first thirty-nine.