Reviewing surgical quality when you cannot be in the room

Most weeks I review surgical sessions I was not in the room for. Different country, different time zone, sometimes a surgeon I have never met in person.

Remote review gets treated as a weaker copy of being there. I stopped accepting that framing a while ago. A reviewer in the room misses context too, relies on memory too, and hands over feedback that changes nothing just as often. What decides the quality of a review is whether the evidence was designed before the work began.

Distance is a constraint you can plan around. Unplanned evidence is the thing you cannot.

Define the review question first

A request to review the session is too broad. It invites a tour of whatever evidence happens to exist and produces comments nobody can compare across months.

So the question comes first. Are we checking adherence to a standard? Hunting the cause of a recurring variation? Confirming readiness for more independent work? Testing whether the last round of feedback was applied? Each question needs different evidence. Without one, more photos and more forms only add noise.

Build an evidence chain, not an evidence pile

The evidence should tell the sequence of the work, from planning through execution to documentation and outcome, in an order the reviewer does not have to guess at. Which item came first and which version is final should never be a puzzle.

A chain needs consistent labels, known capture points and enough context to interpret what is visible. It also has to respect privacy. Include only what the judgement requires, keep it in approved storage, and strip identifiers that add nothing to the decision.

Plan

What was intended, and which standard applied?

Execution

What observable evidence shows how the work was performed?

Record

What was documented, by whom, at what point in the pathway?

Follow-through

What action followed the session, including correction or monitoring?

Ask for context without inviting excuses

Evidence without context misleads. Context without structure turns into a defence of every variation, and I have sat through enough of those to know how they end.

I ask for the same short frame every time: what was expected, what changed, when it became known, what was decided, and what constraint shaped that decision. The frame keeps the review fair without letting the standard move after the event.

Context does not erase a gap. It classifies one. Knowledge, judgement, process design, resource, or documentation, and the classification decides who owns the fix.

Separate observation, interpretation and action

The fastest way to lose a surgeon’s trust from a distance is to jump from a partial image to a verdict about competence.

So the feedback is built in three layers, written in that order. The observable fact. The interpretation, with its confidence stated. The action. When someone pushes back, we can find which layer the disagreement actually lives in, and that is usually the difference between an argument and a correction.

Say what was seen, what it may mean, and what happens next. The moment those blur into one verdict, the conversation becomes about the verdict.

Observation

Describe only what the available evidence supports.

Interpretation

Connect the observation to the standard and state any uncertainty.

Action

Name the correction, the support, the owner and the next review point.

Calibrate the reviewers

A shared checklist does not produce consistency. People read the same scale differently, weigh evidence differently, and hold different thresholds for escalation.

Calibration is slower and it works. The same material reviewed independently, judgements compared, the differences argued out in the open. The goal is not agreement for its own sake. It is shared meaning about what each standard looks like when it appears in evidence.

Keep the agreed examples. After a few cycles they become the real reference, and they are worth more than the scoring label they sit under.

Design feedback that can travel back into work

A long review report proves effort and changes nothing. What travels is a short list of prioritised actions, a reason attached to each, and a named point of re-check.

I separate four kinds of gap because they need four kinds of owner: a risk needing immediate control, a skill needing practice, a process needing redesign, and a record needing cleaner evidence. Hand all four to the same person and three of them will wait.

The loop closes when the next session’s evidence tests whether the feedback was applied. If it does not, the review was a letter, not a control.

Know what remote review cannot prove

Some judgements need the room: direct observation, physical context, an angle nobody captured. A responsible reviewer says so plainly instead of stretching thin evidence to reach a conclusion.

Absence of evidence is not evidence of failure, and a polished submission is not proof that the unobserved work was strong. Record the limit, request what is missing, and when the question cannot be answered remotely, get on the plane.

Remote review works when the question is defined before the session, the evidence forms a chain, the reviewers mean the same thing by the same words, and the feedback shows up in the next session’s work. The distance stays. The guesswork is optional.