An after-action review for a surgical team is a short, structured conversation held soon after a list ends, in which the people who did the work compare what was planned with what actually happened and agree who will change what. I would treat it as an operating routine with a facilitator, a one-page record and a written action, not as a debrief that happens when someone has spare time. For aesthetic services in India that want international patients to trust them, it is one of the quieter disciplines that separates a busy theatre from a team that improves.
01
Where the method sits, and what it is not
NHS England's patient safety learning response toolkit lists the after action review among its learning response methods, alongside the swarm huddle, the multidisciplinary team review and the patient safety incident investigation. NHS England says its AAR report template was designed with the Health Services Safety Investigations Body, human factors specialists and end users, and the toolkit as a whole is built on SEIPS, which NHS England describes as a framework for understanding outcomes within complex socio-technical systems.
That systems orientation is what I would borrow: examine the work before looking for an individual to blame. A review is not a clinical audit of the surgeon. Clinical decisions belong to qualified clinicians, and any question about them goes to the clinical lead through the governance route the service already has. The operations question is narrower and more useful to answer on a Tuesday evening: did the list run the way the team planned it, and if not, what in the system made the difference?
02
Attach it to the end of the list
The WHO Surgical Safety Checklist asks the whole team to pause at three points: before anaesthesia, before incision and before the patient leaves the operating room. That final pause concerns the patient on the table. I would leave it exactly as it is and hold the after-action review later, once the last patient of the list has been handed over and nobody is being pulled away.
Fifteen minutes is the budget I would set. Longer than that and people start drifting out; shorter and the conversation stays on the surface. The WHO also encourages adapting its checklist after local consultation, provided a modified version drops the WHO logo and credits the original. I would apply the same honesty to this review: adapt the questions to the theatre, and say plainly which parts are local.
03
Four questions, in order
I would ask four questions and keep them in sequence, because skipping ahead to fixes is the usual way these conversations fail.
What did we plan? The published list, the expected start, the instruments and consumables prepared, the staffing agreed the day before.
What happened? Facts only, taken from the people who saw them. The first case started late. A tray arrived incomplete. The information sheet for an overseas patient was in the wrong language.
Why was there a difference? Here the SEIPS habit matters. Ask about the task, the tools, the environment and the organisation before anyone asks about a person. A late start caused by a transport booking made at the wrong time is a scheduling design problem, not a punctuality problem.
What will we keep, and what will we change? Every change gets one owner and one date. Something that worked well also gets written down, because the next team needs to know it was deliberate.
A review that ends without an owner is only a conversation.
04
Who speaks, and who holds the pen
The facilitator should not be the most senior clinician in the room. I would train theatre coordinators and operations staff to facilitate, and ask the most junior person present to describe what happened first. Seniority tends to settle the story early; hearing the scrub team and the runner before the lead surgeon gives a fuller picture of the work as it was done.
A separate person keeps the record: date, list, the four answers in a few lines each, and the actions. The record is about the system. It does not carry patient identities, and it is not a disciplinary document. If a staff member leaves the review worried that honesty will cost them, the next review will be quieter and less accurate.
05
Across a network, read the actions rather than the scores
A single theatre can improve on its own. A network of clinics needs something more: a shared log where every action from every review lands in the same place. The pattern worth finding is repetition. If three sites record the same consumable arriving short, that is a procurement issue, and asking each theatre to fix it locally wastes three teams' effort.
I would resist one temptation firmly. Ranking teams by how many problems their reviews surface punishes the teams that are candid. The measures I would watch instead are whether reviews happen after each list, whether actions close by their date, and whether the same finding keeps returning after it was supposedly fixed.
Training at network scale follows from that. Certify a small group of facilitators, observe each of them running a review, and sample their records each month against a short standard: four questions answered, actions owned and dated, clinical questions routed to the clinical lead. A facilitator whose records repeatedly lack owners needs coaching before they run more reviews.
06
What an overseas patient gains from a meeting they never attend
A patient who travels to India for an aesthetic procedure will never sit in a theatre review. They will feel its effects anyway: a list that starts when promised, equipment that is ready, information in a language they read, and a handover that does not depend on one person remembering. Those are small operating facts, and they are the ones an international patient notices.
If India is to earn a reputation for aesthetic medical travel that rests on more than price, it will be through teams that can show, in their own records, that they notice problems and close them. The first review in any theatre will feel slow and a little awkward. I would hold it anyway, keep it to fifteen minutes, and judge it a month later by a single test: whether the action written at its end has been done.
Sources
Questions people ask
What is an after-action review for a surgical team?
It is a brief, structured conversation held soon after a theatre list ends. The people who did the work compare what was planned with what happened, discuss why any difference arose and agree a small number of changes. Each change is written down with an owner and a date, so the review produces work rather than only discussion.
Does an after-action review judge the surgeon's clinical decisions?
No. Clinical judgement belongs to qualified clinicians and is examined through the clinical governance route the service already uses. The review I propose looks at the work system around the operation: scheduling, equipment, consumables, information and handovers. If a clinical question surfaces, the facilitator records it and passes it to the clinical lead rather than settling it in the room.
How do you run after-action reviews across many theatres without it becoming paperwork?
Keep each record to one page and pool the actions in a single network log. Review that log for repeats rather than counting how many problems each team raised, because counting punishes candour. Train and certify a small group of facilitators, sample their records regularly and check whether the actions written at the end of each review were actually completed.