Completing a simulation and genuinely learning from it are two different activities, and the gap between them is almost always review quality rather than the simulation itself. An unexplained numerical score tells you very little; a transcript, read with the right method, tells you exactly what to fix.
Reviewing the first two minutes
The opening of any consultation or encounter sets up everything that follows, and it is worth reading closely and separately from the rest. Did agenda-setting genuinely happen, or was it assumed. Did the encounter start naturally, or did it feel rushed straight into task completion. A weak opening frequently explains problems that surface later in the transcript, a patient's actual concern never fully surfacing because it was never properly invited in the first place.
Identifying unanswered patient concerns
Read specifically for what the patient tried to raise and what actually got addressed. A transcript frequently reveals a concern mentioned once, briefly, and never returned to, easy to miss when you were the one managing the whole encounter in real time and considerably more visible reading it back afterward. This gap, a concern raised and left hanging, is one of the most common and most fixable patterns transcript review reveals.
Comparing claimed versus demonstrated reasoning
What you believe you were thinking during the encounter and what the transcript actually shows are not always the same thing. Read for whether your stated reasoning in the encounter, if the case included explaining your thinking aloud, genuinely matches the decisions and questions you actually asked, or whether there is a gap between the reasoning you intended and the reasoning the transcript actually demonstrates.
Finding safety-critical omissions
Deliberately search the transcript for the specific safety-critical elements the case type was designed to test, whether that is a specific piece of history, a red-flag question, an escalation, or explicit safety-netting. These omissions carry disproportionate weight in real assessment, and they are also the easiest category of error to miss in your own immediate impression of how an encounter went, precisely because everything else may have gone smoothly.
Marking moments of premature closure
Read for the specific point where you moved to conclude the encounter, and ask honestly whether that moment was actually earned or simply reached because time felt short or the conversation felt finished. Premature closure is a genuinely common pattern, ending data gathering before a concern was fully explored, or ending management discussion before checking the patient's actual understanding, and it is considerably easier to spot in a transcript read calmly afterward than in the moment itself.
Selecting one communication and one clinical target
Resist the temptation to try fixing everything the transcript reveals at once. Choose exactly one communication target, a specific habit or pattern worth addressing directly, and exactly one clinical target, a specific knowledge or reasoning gap worth closing before your next attempt. This deliberate narrowing is what makes review actionable rather than overwhelming, and it is considerably more effective than a vague intention to generally improve.
Using Tutor
Take the specific targets your review identified directly into a Tutor session, working through the underlying misconception or habit explicitly rather than simply noting it and moving on. This is where a diagnosed weakness actually becomes a genuine correction, closing the specific gap your own review just identified.
Repeating a varied case rather than memorising the original one
The final and most important step: your next attempt should be a genuinely different case testing the same underlying construct, not a repeat of the exact same scenario. Repeating the identical case risks testing memory of that specific encounter rather than genuine, transferable correction, exactly the pattern-memorisation trap this cluster's broader coverage warns against throughout. A varied case tests whether the correction actually generalises, which is the only result that genuinely matters.
Why this method beats an unexplained score
A single numerical result tells you that something needs improvement without telling you what, where, or why. This eight-step method converts a completed simulation into specific, actionable information: what happened in the opening, what concern went unaddressed, where reasoning and action diverged, what safety-critical element was missed, where closure came too early, and, critically, exactly what to work on next and how to test whether that work actually held.
Frequently asked questions
How long should a proper transcript review take?
Considerably less time than the encounter itself for most cases, since the method above is a structured scan for specific patterns rather than a line-by-line re-read of everything, though a case revealing a significant safety-critical omission deserves closer, slower attention than one that went smoothly throughout.
Should I review every simulation this thoroughly?
The full method is most valuable for cases where something clearly went wrong or where you are genuinely uncertain how the encounter actually went; a case that felt straightforward and confident still benefits from at least a quick scan for unaddressed concerns and safety-critical elements, since confidence in the moment does not always match what the transcript actually shows.
Why not just repeat the exact same case until I get it right?
Because getting a repeated identical case right increasingly reflects memory of that specific encounter rather than genuine, transferable skill; testing the correction against a different case of the same underlying type is the only way to know whether the improvement will actually show up in a genuinely unseen encounter, which is what the real examination will be.