Reviewing a complex case without looking for someone to blame

Complex cases quickly attract convenient stories: the client failed to disclose, the technician failed to look, the administrator failed to warn. The more serious the event, the stronger the temptation to end with one person’s name. Build a timeline and ask what each person knew at each point. Accountability remains, but the review no longer becomes an exercise in humiliation.

Protect the client and preserve the evidence first

If there is an ongoing reaction or suspicion of injury, clinical care and escalation remain the priority. The educational debriefing does not replace or delay a clinical assessment. The device and consumables are kept in a condition that allows for safe investigation of the event.

Materials are collected with the minimum necessary personal data. Photographs, questionnaires and treatment records are not sent to the general chat for the sake of a lively discussion. Participants know the purpose of the meeting, confidentiality rules, and the difference between clinical case management and in-house teaching.

• Has assistance been provided and mandatory escalation completed?
• Are hardware and procedure records saved?
• Who received each important item of information, and when?
• What rules and resources were available at the time of decision?
• Which corrective action will be verified after the review?

Build a neutral timeline

We record the sequence: questionnaire time, new client message, inspection, selected treatment area, test, start of sensations, stop and subsequent actions. Set aside labels such as “inattentive”, “rude” and “obvious”. They do not show what exactly happened and where else the risk could have been intercepted.

If accounts differ, document the discrepancy. A missing entry is a fact about the information, not evidence of bad intent. Device data, protocol photographs, messages and a treatment record help, but no source should be silently supplemented with memory after the fact.

Separate individual decisions from system conditions

The team asks whether the action was consistent with training, manufacturer's instructions, and protocol. Then it checks the environment: whether the directory was available, whether the names of the treatment areas matched, whether the reminder worked, whether there was enough time for consultation, whether it was clear who to call if in doubt.

A system view does not erase personal responsibility; it makes it more precise. Sometimes an employee violated a clear rule. Sometimes the rule existed only in the manager’s head. Corrections in these cases vary, and the phrase “to be more attentive to everyone” does not solve any of them.

Ask about reasoning before judging it

The practitioner gets the opportunity to reconstruct what they saw, what they expected and why they continued or stopped. “What information led you to this choice?” provides more useful information than “Why did you do that?” The second one easily sounds like an accusation and elicits a defensive account instead of an analysis.

After the explanation, the mentor compares the reasoning with the trainee's actual scope of practice. Uncertainty can be acknowledged, but it cannot justify every decision. When information is missing, the next skill is to pause and consult a senior practitioner.

Close the review with an owner and deadline

Each decision gets an owner, a date, and a verification method. For example, the administrator changes the reminder template, the mentor conducts training on warning signs, the person in charge of the equipment checks the log. A change without review often exists only in the minutes of the meeting.

After a set period, the team checks whether the intervention worked and whether it created a new risk. Report the findings without publicly stigmatising anyone: which factors were identified, what changed and how the change will be measured. This turns a difficult case into shared organisational learning rather than a cautionary tale attached to one person’s name.