Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-192 · SUPERVISED full tutorial
Take part in a qualified after-action review that turns one verified lesson into a tested system change
An accountable facilitator leads a review of three late handoffs caused by conflicting checklist locations. Learners reconstruct verified events without blame, keep the access failure visible, assign one reversible system change and test recurrence. The resulting evidence concerns that supervised change only; it cannot show that an institution has learned permanently.
What you will produceUnder an accountable facilitator, the learner separates event facts from blame, identifies a system contributor, assigns a reversible change and verifies its effect on later work.
Method8 numbered Power-specific steps
Practice authorityFull method with qualified supervision where stated
Full step-by-step individual tutorial · TLU-PWR-192
Under an accountable facilitator, the learner separates event facts from blame, identifies a system contributor, assigns a reversible change and verifies its effect on later work.
Participant choice — Confirm review authority: The accountable facilitator states scope, confidentiality, reporting duties, affected-person participation and anti-retaliation protections.
Learner failure role — Run under supervision: The authorised team tests the new route, logs deviations and stops if a new safety or access problem appears.
Institutional learning outcome review may inspect “Verified change, recurrence, outcome, retention and affected-person remedy after review” under the configured comparator.
Qualified help is required for
Team-owned gate — Reconstruct the event: Put timestamped actions, conditions and outcomes on a shared timeline; mark gaps rather than filling them with memory.
Provider-controlled rehearsal — Separate conduct from system: Name equipment, workload, handoff, policy and supervision contributors while preserving any required conduct route.
Scheduling owner for Institutional learning: the responsible team. Repeat rule: The qualified facilitator sets the review cadence. For this simulation, run 10 trials, a one-week check and a four-week retention audit; expand scope only after governance, affected-person and safety review.
Never do this from the page alone
Unsafe Institutional learning choice: Begin with “who failed?”
Second failure that ends progression: Write “staff should be more careful.”
Solo use is barred for Institutional learning. Trigger: Pause if confidentiality, consent, evidence integrity or anti-retaliation protection cannot be maintained.
2 · Get ready
Gather what you need and check the starting conditions
What you need
Declared Institutional learning fixture: A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions.
Setup aid for Reconstruct the event: Do not use a fictional exercise to bypass a real mandatory reporting, safeguarding or incident process.
Institutional learning log: Verified change, recurrence, outcome, retention and affected-person remedy after review; retain Institutional learning errors, assistance, stop and fallback.
After-action source sheet: open “Making it safe: the effects of leader inclusiveness and professional status on psychological safety and improvement efforts in health care teams”. Record how inclusiveness relates to safety and improvement work. Use “Influence of surgeon behavior on trainee willingness to speak up: a randomized controlled trial” for the observed speak-up outcome, and TeamSTEPPS for the review frame. Examine participation and follow-through without declaring institution-wide learning.
Complete simulated event log: H1—08:52 Jo opens /Shared/Handoff rev 1 dated 3 March; the 09:00 handoff is sent at 09:08 with no read-back. H2—09:50 Mina opens /Ops/Handoff rev 2 dated 10 March; the 10:00 handoff is sent at 10:06 after searching for the required field. H3—10:52 Rae follows an old bookmark back to rev 1; the 11:00 handoff is sent at 11:07 and the receiver asks which checklist controls. The source register shows both links active and no owner for the old bookmark.
Affected-person and change cards: the fictional recipient says, “I need reliable notice before transfer, not only a completed review.” Proposed reversible change—archive rev 1, redirect both links to controlled rev 2, assign Noor as owner, start 18 March, and roll back to supervised paper read-back if access fails. Audit exactly ten simulated handoffs for correct version, lateness, link failure, read-back and recipient notice; then compare with the three late events above.
Before you start
Confirm the qualified facilitator, data authority and protected reporting route.
Do not use a fictional exercise to bypass a real mandatory reporting, safeguarding or incident process.
Start check for Institutional learning: Every participant knows what is confidential and what must be escalated.
Top-of-sheet stop for Institutional learning: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
3 · The method
Follow these steps in order
Confirm review authority
The accountable facilitator states scope, confidentiality, reporting duties, affected-person participation and anti-retaliation protections.
Why: Every participant knows what is confidential and what must be escalated.
Check: Every participant knows what is confidential and what must be escalated.
Reconstruct the event
Put timestamped actions, conditions and outcomes on a shared timeline; mark gaps rather than filling them with memory.
Why: Each timeline entry has a source or “unknown” label.
Check: Each timeline entry has a source or “unknown” label.
Hear affected perspectives
Invite the person affected by the process, or their authorised representative, to state desired remedy and impact without requiring disclosure.
Why: Their outcome is recorded separately from team convenience.
Check: Their outcome is recorded separately from team convenience.
Separate conduct from system
Name equipment, workload, handoff, policy and supervision contributors while preserving any required conduct route.
Why: The review neither blames one person nor erases accountable behavior.
Check: The review neither blames one person nor erases accountable behavior.
Choose one testable change
With the facilitator, select a reversible change: archive the old checklist and point all handoffs to one controlled version.
Why: The change has an owner, start date and rollback rule.
Check: The change has an owner, start date and rollback rule.
Define the audit
Set numerator, denominator and follow-up: correct checklist used in 10 simulated handoffs, plus late handoffs and user-reported burden.
Why: Success and harm measures are fixed before rollout.
Check: Success and harm measures are fixed before rollout.
Run under supervision
The authorised team tests the new route, logs deviations and stops if a new safety or access problem appears.
Why: Ten trials and any deviations are traceable.
Check: Ten trials and any deviations are traceable.
Close or escalate
Compare recurrence, burden and affected-person remedy; retain, revise or retire the change through the responsible governance route.
Why: A named decision owner signs the next action and review date.
Check: A named decision owner signs the next action and review date.
4 · Worked example
See the whole method used once
Scenario
A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions.
Walkthrough
The facilitator confirms this is a simulation, states the no-retaliation rule and records who owns the review.
The team builds a timeline for three late handoffs and finds two checklist links with different revision dates.
The fictional affected-person card asks for reliable notice before transfer, not merely a completed review.
The team archives the old link, assigns Noor to the controlled copy and sets rollback if access fails.
Ten supervised handoffs use the correct version in 9 cases; one link failure and its correction are logged.
At the follow-up, late handoffs fall from 3/10 to 1/10, access burden is unchanged and the facilitator schedules a four-week retention audit.
Result
The supervised review connects a verified contributor to one measured change and keeps an access failure visible. It does not prove institution-wide learning or eliminate recurrence.
5 · Right and wrong
Compare correct or safer execution with the common wrong version
Right and wrong comparison
Moment
Right / safer
Wrong / riskier
Why it matters
Event record
Build a sourced timeline and mark unknowns.
Begin with “who failed?” during the late-handoff review.
Blame-first review discourages reporting and can miss system causes.
Affected person
Include impact and desired remedy when completing the late-handoff review.
Treat review completion as the only outcome.
A closed meeting does not prove benefit or repair.
Change design
Assign one reversible change with owner and rollback.
Write “staff should be more careful.”
Vague reminders cannot be audited or sustained.
Learning claim
Verify reduced recurrence after implementation when completing the late-handoff review.
Call the institution a learning organisation after one debrief.
Review activity is only a proxy for changed practice.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
Begin with “who failed?” during the late-handoff review.
Ask what happened, under what conditions and with what evidence.
Treat review completion as the only outcome.
Measure remedy and future outcome separately.
Write “staff should be more careful.”
Change one process element and specify the test.
Call the institution a learning organisation after one debrief.
Compare future events, burden and retention.
7 · Practice
Turn the steps into a usable skill
First session
Simulated handoff review: A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions.
Sourced event timeline: Reconstruct the event: Put timestamped actions, conditions and outcomes on a shared timeline; mark gaps rather than filling them with memory.
System-versus-conduct analysis: Separate conduct from system: Name equipment, workload, handoff, policy and supervision contributors while preserving any required conduct route.
Single controlled-link change: Choose one testable change: With the facilitator, select a reversible change: archive the old checklist and point all handoffs to one controlled version.
Ten-handoff access check: Run under supervision: The authorised team tests the new route, logs deviations and stops if a new safety or access problem appears.
Repeat plan
The qualified facilitator sets the review cadence. For this simulation, run 10 trials, a one-week check and a four-week retention audit; expand scope only after governance, affected-person and safety review.
Progress when
Every participant knows what is confidential and what must be escalated.
Each timeline entry has a source or “unknown” label.
Their outcome is recorded separately from team convenience.
The change is implemented as specified, recurrence falls against the declared denominator, no new harm or retaliation appears, and the affected-person remedy is checked rather than assumed.
Do not progress when
Do not continue while this error remains: Begin with “who failed?”
Pause until this correction works: Measure remedy and future outcome separately.
This Institutional learning stop ends the block: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
8 · Check the result
Measure what changed
Verified change, recurrence, outcome, retention and affected-person remedy after review
How: Configured fixture: A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions. The provider logs “Reconstruct the event”, every “Choose one testable change” result, the “Run under supervision” response and Verified change, recurrence, outcome, retention and affected-person remedy after review. For each handoff, the facilitator also logs who requested help, what access support was used, and whether that support changed fact reconstruction or participation; keep those entries beside recurrence so assistance is not mistaken for a system effect.
Good result: The change is implemented as specified, recurrence falls against the declared denominator, no new harm or retaliation appears, and the affected-person remedy is checked rather than assumed.
This does not prove: Boundary for Institutional learning: “Verified change, recurrence, outcome, retention and affected-person remedy after review” describes only A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions. It cannot establish “Run one debrief and become a learning organization”.
Self-check
Without the example, demonstrate: Every participant knows what is confidential and what must be escalated.
Find the fault in this attempt: “Begin with “who failed?”” Apply “Ask what happened, under what conditions and with what evidence.”; what changes?
What evidence in the completed record shows that this is wrong: “Treat review completion as the only outcome.”?
Institutional learning stop decision: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
Pause if confidentiality, consent, evidence integrity or anti-retaliation protection cannot be maintained.
Do not implement an organisational change outside the accountable owner’s authority or without a rollback path.
Accessibility and adaptations
Provide timelines in plain text, visual sequence and spoken summary; allow private or asynchronous contribution.
Offer an independent advocate, interpreter or anonymous reporting route where participation or hierarchy creates barriers.
10 · Evidence and limits
Why these instructions are here
primary research
Registered support for Institutional learning: “Making it safe: the effects of leader inclusiveness and professional status on psychological safety and improvement efforts in health care teams”. It bears on Verified change, recurrence, outcome, retention and affected-person remedy after review inside the Institutional learning fixture. It does not validate “Run one debrief and become a learning organization”.
Constraint for Institutional learning, drawn from “Influence of surgeon behavior on trainee willingness to speak up: a randomized controlled trial”: Evidence is strongest for bounded teams and repeated training tasks, not whole institutions.
TeamSTEPPS boundary for Institutional learning: apply engagement while observing “Verified change, recurrence, outcome, retention and affected-person remedy after review”. Rehearse Reconstruct the event, then use the Institutional learning teach-back and debrief.
Institutional learning boundary: interpret “Verified change, recurrence, outcome, retention and affected-person remedy after review” only for A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions.
A successful result does not establish “Run one debrief and become a learning organization”.
Institutional learning limiting finding: Evidence is strongest for bounded teams and repeated training tasks, not whole institutions.
Institutional learning limiting finding: Self-reported safety, report volume and review completion do not prove correction or affected-person benefit.
Scope remains Institutional learning: A fictional clinic-like training team reviews three late handoffs in a simulation. The event log shows that the shared checklist was stored in two locations with conflicting versions. Recheck the comparator, support and “Verified change, recurrence, outcome, retention and affected-person remedy after review” after any configuration change.
Marco J. Barzallo Salazar; Howard Minkoff; Jyothshna Bayya; Brian Gillett; Helen Onoriode; Jeremy Weedon; Lisa Altshuler; Nelli Fisher · 2014 · Primary research
Progress is saved only in this browser on this device.
Step-by-step learner mode
Each activity includes its success check, a nearby accessible alternative and an “I’m stuck” correction path. Alternatives preserve the target where possible; when they change the task, Titan labels them as related rather than equivalent.
01
Confirm review authority
The accountable facilitator states scope, confidentiality, reporting duties, affected-person participation and anti-retaliation protections.
Why this step exists
Every participant knows what is confidential and what must be escalated.
Success check
Every participant knows what is confidential and what must be escalated.
I’m stuck on this step
Reset: Re-read this authored instruction — “The accountable facilitator states scope, confidentiality, reporting duties, affected-person participation and anti-retaliation protections.” — and its success check, then attempt only this step.
Possible snag: Treat review completion as the only outcome.
Correction: Measure remedy and future outcome separately.
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
02
Reconstruct the event
Put timestamped actions, conditions and outcomes on a shared timeline; mark gaps rather than filling them with memory.
Why this step exists
Each timeline entry has a source or “unknown” label.
Success check
Each timeline entry has a source or “unknown” label.
I’m stuck on this step
Reset: Re-read this authored instruction — “Put timestamped actions, conditions and outcomes on a shared timeline; mark gaps rather than filling them with memory.” — and its success check, then attempt only this step.
Possible snag: Begin with “who failed?” during the late-handoff review.
Correction: Ask what happened, under what conditions and with what evidence.
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
03
Hear affected perspectives
Invite the person affected by the process, or their authorised representative, to state desired remedy and impact without requiring disclosure.
Why this step exists
Their outcome is recorded separately from team convenience.
Success check
Their outcome is recorded separately from team convenience.
I’m stuck on this step
Reset: Re-read this authored instruction — “Invite the person affected by the process, or their authorised representative, to state desired remedy and impact without requiring disclosure.” — and its success check, then attempt only this step.
Possible snag: Write “staff should be more careful.”
Correction: Change one process element and specify the test.
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
04
Separate conduct from system
Name equipment, workload, handoff, policy and supervision contributors while preserving any required conduct route.
Why this step exists
The review neither blames one person nor erases accountable behavior.
Success check
The review neither blames one person nor erases accountable behavior.
I’m stuck on this step
Reset: Re-read this authored instruction — “Name equipment, workload, handoff, policy and supervision contributors while preserving any required conduct route.” — and its success check, then attempt only this step.
Possible snag: The result from “Name equipment, workload, handoff, policy and supervision contributors while preserving any required conduct route.” does not yet meet this declared check: The review neither blames one person nor erases accountable behavior.
Correction: Return to the start of “Separate conduct from system”, reduce complexity or pace, and repeat only the part needed to satisfy: “The review neither blames one person nor erases accountable behavior.”
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
05
Choose one testable change
With the facilitator, select a reversible change: archive the old checklist and point all handoffs to one controlled version.
Why this step exists
The change has an owner, start date and rollback rule.
Success check
The change has an owner, start date and rollback rule.
I’m stuck on this step
Reset: Re-read this authored instruction — “With the facilitator, select a reversible change: archive the old checklist and point all handoffs to one controlled version.” — and its success check, then attempt only this step.
Possible snag: The result from “With the facilitator, select a reversible change: archive the old checklist and point all handoffs to one controlled version.” does not yet meet this declared check: The change has an owner, start date and rollback rule.
Correction: Return to the start of “Choose one testable change”, reduce complexity or pace, and repeat only the part needed to satisfy: “The change has an owner, start date and rollback rule.”
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
06
Define the audit
Set numerator, denominator and follow-up: correct checklist used in 10 simulated handoffs, plus late handoffs and user-reported burden.
Why this step exists
Success and harm measures are fixed before rollout.
Success check
Success and harm measures are fixed before rollout.
I’m stuck on this step
Reset: Re-read this authored instruction — “Set numerator, denominator and follow-up: correct checklist used in 10 simulated handoffs, plus late handoffs and user-reported burden.” — and its success check, then attempt only this step.
Possible snag: The result from “Set numerator, denominator and follow-up: correct checklist used in 10 simulated handoffs, plus late handoffs and user-reported burden.” does not yet meet this declared check: Success and harm measures are fixed before rollout.
Correction: Return to the start of “Define the audit”, reduce complexity or pace, and repeat only the part needed to satisfy: “Success and harm measures are fixed before rollout.”
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
07
Run under supervision
The authorised team tests the new route, logs deviations and stops if a new safety or access problem appears.
Why this step exists
Ten trials and any deviations are traceable.
Success check
Ten trials and any deviations are traceable.
I’m stuck on this step
Reset: Re-read this authored instruction — “The authorised team tests the new route, logs deviations and stops if a new safety or access problem appears.” — and its success check, then attempt only this step.
Possible snag: The result from “The authorised team tests the new route, logs deviations and stops if a new safety or access problem appears.” does not yet meet this declared check: Ten trials and any deviations are traceable.
Correction: Return to the start of “Run under supervision”, reduce complexity or pace, and repeat only the part needed to satisfy: “Ten trials and any deviations are traceable.”
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
08
Close or escalate
Compare recurrence, burden and affected-person remedy; retain, revise or retire the change through the responsible governance route.
Why this step exists
A named decision owner signs the next action and review date.
Success check
A named decision owner signs the next action and review date.
I’m stuck on this step
Reset: Re-read this authored instruction — “Compare recurrence, burden and affected-person remedy; retain, revise or retire the change through the responsible governance route.” — and its success check, then attempt only this step.
Possible snag: Call the institution a learning organisation after one debrief.
Correction: Compare future events, burden and retention.
Stop / get help: Stop and escalate immediately for active danger, safeguarding, legal reporting or serious clinical risk.
Correct versus incorrect execution
These accessible process diagrams are built from the tutorial’s own right/wrong teaching. They are not anatomical illustrations and do not add technique beyond the canonical tutorial.
Event record — Blame-first review discourages reporting and can miss system causes.
Correct / safer
Build a sourced timeline and mark unknowns.
Wrong / riskier
Begin with “who failed?” during the late-handoff review.
Affected person — A closed meeting does not prove benefit or repair.
Correct / safer
Include impact and desired remedy when completing the late-handoff review.
Wrong / riskier
Treat review completion as the only outcome.
Change design — Vague reminders cannot be audited or sustained.
Correct / safer
Assign one reversible change with owner and rollback.
Wrong / riskier
Write “staff should be more careful.”
Learning claim — Review activity is only a proxy for changed practice.
Correct / safer
Verify reduced recurrence after implementation when completing the late-handoff review.
Wrong / riskier
Call the institution a learning organisation after one debrief.
Method-structure checklist
10 of 10 structural checks present
✓ Ordered, Power-specific instructions — present
✓ Every activity has a success check — present
✓ Materials or supplied records are declared — present
✓ Measurement or assessment rule is present — present
✓ Tutorial-specific troubleshooting is present — present
✓ Stopping or escalation boundary is present — present
✓ Every activity has an adjacent alternative — present
✓ Correct-versus-incorrect comparison is present — present
✓ Evidence context is bound to the Power record — present
✓ Planning metadata is present — present
The method-readiness band and presence checklist assess tutorial presentation and are separate from evidence quality for the underlying Power. They are automated editorial aids, not human approval.
Manual editorial sign-off: Pending. This tutorial must not display a human-approved state until an identified editor signs the exact content hash.