Prebriefing and Debriefing

How to establish the learning contract, then use a structured debrief to turn simulation performance into reflection, feedback, and a concrete plan for future practice.

Debriefing is the learning engine

Simulation does not teach only because learners perform in a realistic room. Learners also need time to notice what happened, compare it with the target performance, examine why their actions made sense in the moment, and decide what they will do differently next time. Debriefing is the structured conversation that turns the scenario into that learning.

That work begins before the case runs. A useful debrief needs a case objective, a scenario moment where that objective becomes visible, and a plan for how the facilitator will move from performance to reflection. Without that plan, the debrief easily becomes a list of missed steps, a mini-lecture, or a discussion of whichever moment felt most dramatic.

Before the learners enter the room, the facilitator should be able to answer:

Which objective will this debrief prioritize?
Which scenario moment is likely to reveal the learner’s reasoning?
What result, action, or team pattern should the facilitator watch for?
What learner frames might explain that action?
What future behavior or mental model should learners leave with?

Protect real time for this work. A short case with a rushed debrief is usually a poor trade, especially when the objective involves clinical reasoning, teamwork, communication, or prioritization under pressure.

Prebriefing sets the learning contract

The prebrief creates the conditions for both the simulation and the debrief. Learners are being observed in an artificial environment, often while making time-pressured decisions in front of peers. A good prebrief lowers avoidable threat without lowering standards.

A practical prebrief should address:

Purpose: Why this session exists and how it connects to the curriculum.
Basic assumption: Participants are capable, committed, and trying to improve.
Fiction contract: The environment will not be perfectly real, and everyone agrees to work with its limitations in good faith.
Confidentiality and assessment: What stays in the room, what may be documented, and whether the session is formative or summative.
Environment: Room layout, monitor behavior, manikin or standardized patient limitations, available equipment, medication handling, and how to call for help.
Roles and expected behavior: Whether learners should act clinically, verbalize unavailable actions, delegate tasks, touch the patient, or request data.
Debrief process: Learners should know that the debrief will include reactions, reconstruction of key events, analysis, and summary.
Participation norms: The group will critique behaviors, decisions, and systems rather than personal worth.

The prebrief is also where the facilitator prevents predictable friction. If the case requires learners to examine the manikin, say so. If medications are simulated, clarify how ordering and administration should occur. If a distressed caregiver or embedded participant will create pressure, explain that the role is there to support the objective, not to trick or humiliate anyone.

Use PEARLS as the default scaffold

PEARLS gives a flexible structure without forcing every debrief into the same script. For this curriculum, treat it as the default map: reactions, description, analysis, and summary. The phases keep the conversation organized, while the facilitator still chooses the right analysis strategy for the moment.

Phase	Purpose	Facilitator moves
Reactions	Let learners clear emotion and name immediate concerns.	Ask how the case felt, listen, acknowledge frustration or surprise, and note topics worth returning to.
Description	Build a shared account of what happened.	Reconstruct only the events needed for the objective; clarify facts without relitigating the whole case.
Analysis	Explore performance, reasoning, teamwork, and standards.	Select a small number of high-yield moments and choose self-assessment, focused facilitation, or directive feedback/teaching.
Summary	Convert the discussion into future practice.	Ask learners to state takeaways, refine or correct them, and name one or two actions they will carry forward.

Do not skip reactions because they feel inefficient. Learners may be stuck on a technology issue, worried about judgment, frustrated with themselves, or surprised by the case. If that response is ignored, it often returns later and blocks deeper reflection.

Do not let description consume the debrief. The facilitator only needs enough shared narrative to anchor the analysis. Once the key moment is clear, move into why it happened and what will change.

Choose the analysis strategy

The analysis phase is where most of the teaching happens. PEARLS is useful because it does not require one method for every problem. The facilitator can blend three strategies depending on the objective, time, learner level, and clarity of the performance gap.

Strategy	Use when	Facilitator move	Watch out for
Learner self-assessment	Learners can identify useful strengths or gaps, or you need to learn what matters to them first.	Ask what went well, what they would change, and why.	Do not accept vague answers such as communication was bad; ask for specific behaviors.
Focused facilitation	The reasoning, team process, or mental model behind the action is unclear.	Use questions, advocacy-inquiry, alternatives, and comparison to surface frames.	Do not hide your concern behind vague questions that make learners guess what you mean.
Directive feedback or teaching	The issue is technical, time is short, or the reason for the gap is already clear.	State the performance gap and provide the needed standard, tip, or correction.	Do not turn the entire debrief into a lecture when reflection would reveal a more important frame.

These strategies can happen in sequence. For example, after a pediatric drowning case, the facilitator might begin with self-assessment, use focused facilitation to explore how the team approached post-intubation hypoxemia, then teach briefly about drowning physiology, DOTTSS, or PALS bradycardia management if the knowledge gap is clear.

The practical question is not “Which debriefing method do I like?” It is “What does this objective and this performance gap need right now?”

Ask questions that deepen reflection

Facilitators often ask descriptive and evaluative questions first: “What happened?” “What went well?” “What was challenging?” Those questions are useful, but they may not be enough. If the debrief stays there, learners can describe events and judge performance without examining reasoning or planning future practice.

Use questions that deliberately move the group deeper:

If the conversation is stuck at…	Ask instead…
Description	What information were you using at that point?
Evaluation	What made that feel like the right priority?
Action review	What else could the team have tried, and what tradeoffs would that create?
Individual performance	How did the role structure affect what happened next?
A missed step	If this happens again, what cue will tell you to change course earlier?

Good questions are not simply open-ended. They invite learners to examine data, assumptions, alternatives, teamwork, and future action. They also stay anchored to observable moments in the case. A question such as “How was communication?” is too broad. “When the blood pressure fell and two people spoke at once, how did the team decide who owned medication dosing?” gives the group something specific to analyze.

Give feedback with good judgment

Debriefing with good judgment starts from two commitments that can feel in tension: the facilitator owes learners honest feedback, and the facilitator also owes them respect. Avoiding the concern does not protect learners. It leaves them unclear about the standard. Attacking the learner does not teach either. It creates defensiveness and shame.

The better move is direct, empathic curiosity. State what you saw. State why it matters from your clinical or educational point of view. Then ask how the situation looked to the learner at the time.

Avoid vague “guess what I am thinking” questions:

Less useful	More useful
How do you think that went?	I noticed the child stayed hypoxemic after intubation, and the team moved quickly through several fixes. I was concerned we did not pause to share a clear differential. What were you most worried about at that point?
Anything else you could have done?	When the team had no assigned medication role, I saw several orders discussed but not completed. How did the team understand ownership at that moment?
Was that the right choice?	I heard the group discuss nitrates while the patient was hypotensive with an inferior STEMI pattern. I was worried about worsening preload dependence. How were you interpreting the blood pressure and ECG together?

Good judgment also means making generous assumptions. Assume learners were trying to do the right thing from inside their own view of the situation. Normalize the difficulty when appropriate: a well-designed case should put learners at the edge of their current practice. Then make the performance gap discussable without making the learner the problem.

Link results, actions, and frames

A debrief map should connect three things:

Results: What happened in the scenario, such as delayed epinephrine, persistent hypotension, role confusion, or smooth escalation.
Actions: What learners did or did not do.
Frames: The knowledge, assumptions, priorities, emotions, and team norms that made those actions seem reasonable in the moment.

Results and actions are visible. Frames are not. The facilitator uses visible performance to open a conversation about reasoning. This matters because the same action can come from different frames. A team may delay epinephrine because they are anchored on asthma, uncertain about dose, worried about medication harm, socially pulled by a caregiver, or unclear who owns medications. Each frame requires a different teaching response.

Use this sequence:

Name the result or action.
State why it mattered.
Ask what the learner was seeing, thinking, prioritizing, or assuming.
Explore alternatives or missing cues.
Close with the future behavior.

Keep team debriefs diagnostic

Team debriefing should improve the next performance episode. It is not a group confession and it is not a tour of every error. Keep the process diagnostic, specific, and actionable.

Use this checklist:

Debrief soon after performance while the event is still available to memory.
Focus on a few critical performance issues rather than every possible point.
Use objective examples from the case: words spoken, timing, role assignment, orders, handoffs, and physiologic responses.
Discuss team processes such as leadership, closed-loop communication, backup behavior, workload distribution, and shared mental model.
Decide whether feedback belongs at the team level, individual level, or both.
Give process feedback more often than delayed outcome feedback.
Record conclusions and goals so the next session can revisit progress.

The facilitator’s job is to protect the learning environment while still protecting the clinical standard. In a team case, that often means moving from “Who made the mistake?” to “What did our team structure make easier or harder?”

Debrief the pediatric drowning case

The pediatric drowning exemplar has a clean debrief hook: after intubation, the child remains hypoxemic and the team has to decide whether to keep suctioning, adjust ventilation, disconnect and bag, evaluate tube position, assess for pneumothorax or bronchospasm, deepen sedation, and call for help. The debrief should explore how the team shared its mental model as the child deteriorated.

PEARLS phase	Debrief map
Reactions	What felt most stressful when the child stayed hypoxemic after intubation?
Description	Reconstruct the airway plan, intubation, post-intubation oxygen saturation drop, troubleshooting sequence, and bradycardia transition.
Analysis strategy	Use focused facilitation around the team’s shared mental model; add directive teaching if the team lacks a structured post-intubation hypoxemia approach or misses PALS bradycardia criteria.
Summary	Future move: state the hypoxemia differential out loud, assign roles, disconnect and bag when appropriate, call PICU/ECMO early, and start CPR for pediatric bradycardia with poor perfusion.

Advocacy-inquiry sequence:

I saw the saturation fall after intubation, and I heard several fixes discussed at once. I was concerned that the team did not have a shared sequence for post-intubation hypoxemia. What was your working differential at that moment?

Follow-up:

When oxygenation worsens after the tube is in, what words could you use to pause the team and move through the next steps together?

Debrief the STEMI on the Ward case

The STEMI on the Ward exemplar supports a junior-learner debrief around early structure, ECG interpretation, phone escalation, and medication judgment. The key issue is often less about memorizing STEMI treatment and more about turning a ward call into a concise assessment, avoiding unsafe nitroglycerin when the patient becomes hypotensive, and activating help.

PEARLS phase	Debrief map
Reactions	What felt hardest about being called to the ward for chest discomfort?
Description	Reconstruct the first assessment, ECG request, ECG interpretation, blood pressure trend, medication discussion, phone call, and cardiology activation.
Analysis strategy	Use learner self-assessment to identify the first priorities, then focused facilitation around the learner’s working model of hypotension and inferior STEMI.
Summary	Future move: organize the ward assessment, get an ECG early, name STEMI clearly, avoid preload-worsening treatment when hypotensive, and escalate to senior/cardiology resources.

Advocacy-inquiry sequence:

I noticed nitrates were discussed while the patient was hypotensive with an inferior STEMI pattern. I was concerned that this could worsen right-sided preload-dependent shock. What was your working model of the hypotension at that moment?

Follow-up:

When chest pain treatment and blood pressure physiology point in different directions, how will you decide which physiology should drive the next order?

When the scenario does not go as planned

A difficult simulation can still produce useful learning, but the facilitator has to protect the objective and the learners.

If learners perform poorly, be respectful and direct. Participants often know when things went badly. Critique the behavior, decision, or team process rather than the person. Integrity still requires naming unsafe or incorrect performance; otherwise the debrief may accidentally endorse it.

If technology fails, decide whether to pause, narrate missing data, restart, abort, or redirect. Then be transparent in the debrief. Do not let learners spend the whole conversation litigating the manikin if the educational objective can still be salvaged.

If a learner resists the scenario or debrief, reconnect to clinical relevance: “When you have seen this issue with a real patient, how have you handled it?” If behavior disrupts the group, name the participation norm and redirect. In rare cases, a private conversation after the session is more appropriate than continuing to manage the behavior in front of peers.

Improve the debriefer

Debriefing expertise develops through deliberate practice, observation, coaching, feedback, and repeated attempts. Basic structures can be learned quickly. Skilled facilitation takes longer.

After running a session, debrief the debriefer:

Did the prebrief establish the learning contract clearly?
Did the debrief follow reactions, description, analysis, and summary?
Did the analysis stay aligned with the objective?
Did the facilitator choose the right strategy for the performance gap?
Did questions uncover reasoning or only review actions?
Were judgments stated clearly and respectfully?
Did the team leave with a concrete future action or recorded goal?

Quality tools such as DASH and OSAD can support more formal debriefing assessment, but the essential habit is simpler: watch debriefs, ask for feedback, practice specific moves, and make debriefing quality part of the simulation program’s routine improvement work.

Working product

By the end of this module, you should have a prebrief checklist, a debrief map linked to one case objective, and at least one advocacy-inquiry exchange with a follow-up question. Those products make the simulation teachable: learners know how to engage, facilitators know what to watch for, and the debrief has a clear path from experience to future practice.

Sources Used

Eppich W, Cheng A. “Promoting Excellence and Reflective Learning in Simulation (PEARLS): Development and Rationale for a Blended Approach to Health Care Simulation Debriefing.”
Fanning RM, Gaba DM. “The Role of Debriefing in Simulation-Based Learning.”
Husebo SE, Dieckmann P, Rystedt H, Soreide E, Friberg F. “The Relationship Between Facilitators’ Questions and the Level of Reflection in Postsimulation Debriefing.”
Rudolph JW, Foldy EG, Robinson T, Kendall S, Taylor SS, Simon R. “Helping Without Harming: The Instructor’s Feedback Dilemma in Debriefing - A Case Study.”
Salas E, Klein C, King H, Salisbury M, Augenstein JS, Birnbach DJ, Robinson DW, Upshaw C. “Debriefing Medical Teams: 12 Evidence-Based Best Practices and Tips.”
Local exemplar cases: pediatric-drowning and stemi-on-the-ward.