Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-238 · SELF GUIDED full tutorial
Turn one fictional near miss into a safe report, a verified correction and feedback to the reporter
This lesson teaches the complete error-learning loop. You will record direct observations, take only authorised immediate controls, route a fictional near miss, separate system contributors from blame, assign a corrective action, verify whether risk changed, report back and update current memory. Report count is not treated as learning.
What you will produceThe learner completes a fictional near-miss record with observation, route, contributors, action owner, verification, reporter feedback and a demonstrated reduction in the matched repeat error.
Full step-by-step individual tutorial · TLU-PWR-238
The learner completes a fictional near-miss record with observation, route, contributors, action owner, verification, reporter feedback and a demonstrated reduction in the matched repeat error.
Use fictional cases to practise observation and reporting structure.
Describe system contributors such as design, workload, tools, training, incentives and supervision.
State that accountability is unresolved and belongs to an authorised process.
Qualified help is required for
Real incident reporting, safeguarding, whistleblowing, investigation, discipline, legal notification and confidentiality.
Immediate response to clinical, security, safety or public-harm events.
Approval and verification of organisational corrective actions.
Never do this from the page alone
Enter a real disclosure or confidential incident into the fixture.
Promise anonymity, legal protection or absence of retaliation.
Stop at “human error,” or excuse established misconduct by saying only “the system failed.”
2 · Get ready
Gather what you need and check the starting conditions
What you need
Fictional near miss: an outdated paper script nearly gives a caller the wrong opening time.
Observation/report template, contributor map, action register, verification plan and reporter-feedback card.
v1 and v2 scripts, matched repeat-call cards and a second-reader check.
Before you start
Label all materials fictional and keep them out of live reporting systems.
Write the legitimate real-world routes that would replace this exercise if an actual concern arose.
Separate immediate safety action, fact finding, contributor analysis and accountability roles.
3 · The method
Follow these steps in order
Record direct observations
Write what was seen, heard or found, when and where; separate interpretations and unknowns.
Why: Early blame labels narrow investigation before the observation timeline is complete.
Check: Another reader can distinguish fact, inference and missing information.
Apply only authorised immediate control
In the story, pause use of the outdated script and point users to the current source; do not improvise a wider intervention.
Why: Immediate containment should reduce risk without prejudging cause.
Check: The specific exposure is controlled and action authority recorded.
Route the report
Use the fictional current channel, urgency and recipient; timestamp acknowledgement and preserve the reporter’s preferred contact.
Why: A report that disappears cannot support learning.
Check: Named ownership and next update are recorded.
Map affected roles and prior signals
Identify who could be affected, earlier similar reports, inaccessible routes and whether the issue could recur elsewhere.
Why: A single event may reveal a broader condition.
Check: The scope is evidence-based, not assumed universal.
Analyse system contributors
Examine version design, placement, update process, workload, training, incentives, supervision and interface conditions.
Why: “Carelessness” rarely explains why an error was possible or repeated.
Check: At least three testable contributors are recorded.
Keep accountability distinct
Mark whether conduct, competence or duty questions require an authorised process; do not decide them in the learning worksheet.
Why: Systems analysis and accountability can coexist.
Check: No person is blamed or cleared without the proper role and evidence.
Design the corrective action
Choose an owner, resource, due date, expected effect, possible adverse effects and the exact mechanism changed.
Why: “Remind staff” is often too weak and untestable.
Check: The action removes or controls the stale-version route.
Verify with matched work
Use a new fictional call card and cold user to test whether the current script is found and used; compare with baseline.
Why: Completion status is not risk reduction.
Check: The repeat test measures the target error and unintended burden.
Report back and update memory
Tell the fictional reporter what changed and limits, update the current procedure, supersede old copies and set review.
Why: Feedback and memory close the loop.
Check: Reporter, users and future staff can find the verified current state.
4 · Worked example
See the whole method used once
Scenario
A fictional volunteer nearly tells a caller that the centre closes at 18:00 because an old paper script remains beside the phone; the current time is 16:00.
Walkthrough
The learner records the exact script, desk and near-miss facts and separates the inference that other desks may also have copies.
They pause the old script in the story, acknowledge the fictional reporter and inspect the update process, shared drive and printing routine.
The contributor map shows no owner for destroying old printouts; the action assigns an owner, adds a version banner and removes active v1 copies.
A new volunteer uses a matched call card and finds v2 in 20 seconds, then the reporter receives the result and the action review date.
Result
The matched test supports reduced stale-script risk in this fictional route. It does not prove organisation-wide safety, culture change or absence of retaliation.
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
Writing the report
Keep observed facts, inferences and unanswered questions in separate fields.
Write “careless volunteer used bad information.”
Premature blame obscures mechanism and evidence.
Finding cause
Examine version ownership, placement and update design.
Stop at “human error” without tracing conditions, controls or recovery signals.
A label does not explain why stale material remained usable.
Closing action
Verify the target error in matched work.
Mark closed when a reminder email is sent.
Completing an action card does not show the near-miss mechanism changed.
Handling accountability
Route conduct questions to authorised process.
Use system language to excuse all behaviour or punish before facts.
Learning and legitimate accountability require distinct evidence.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
A direct observation and causal inference share one field.
Use separate columns and quote the direct observation.
The near-miss report receives no named acknowledgement.
Require named receipt, next update and timed fallback.
The correction says be careful without changing a mechanism.
Change the mechanism, assign resources and define a verification test.
The action closes before its verification test passes.
Keep action open until matched verification and adverse-effect review.
The reporter receives no outcome or safe follow-up.
Add a report-back owner and safe communication route.
7 · Practice
Turn the steps into a usable skill
First session
Record the fictional near miss using observation/inference/unknown fields.
Apply the narrow immediate control and route the report.
Map contributors and keep accountability questions separate.
Design one mechanism-level correction and run a matched verification.
Report back, update v2 memory and schedule review.
Repeat plan
After at least 48 hours, use a different fictional near miss with a different contributor. Once a month in the fixture, audit whether closed actions retain verification and whether old versions reappear.
Progress when
Reports receive acknowledgement and preserve safe contact.
Contributors extend beyond individual attention without erasing legitimate accountability.
Corrective actions change a mechanism and pass matched verification.
Do not progress when
A real incident, disclosure, safeguarding concern or legal deadline appears.
Confidentiality, retaliation risk or the correct reporting route is unclear.
The learner is asked to investigate, discipline or promise protection.
8 · Check the result
Measure what changed
Completion of the report-to-verified-correction loop
Good result: A good result completes all stages and eliminates the planted stale-script error in two matched fictional trials without creating a new access problem.
This does not prove: It does not prove safety culture, legal compliance, immunity from recurrence or protection for a real reporter.
Self-check
Which sentences are direct observations and which are interpretations?
What immediate control was authorised and how narrow was it?
Which mechanism did the correction change?
What matched evidence supports closure and how was the reporter informed?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
Stop if confidentiality or retaliation risk cannot be protected by the legitimate route.
Seek union, regulator, legal, whistleblowing or professional advice for real concerns; Titan cannot receive or investigate them.
Do not require public confrontation, eye contact or immediate detailed disclosure.
Test that corrective actions and feedback remain accessible to the people who use and report the process.
10 · Evidence and limits
Why these instructions are here
primary research
A cluster-randomised safety-culture intervention increased reporting without consistent broader safety-culture benefit, so report volume is not learning.
Reporting, learning, accountability and legal protection are separate functions.
A verified local correction does not establish organisation-wide outcome improvement.
Report count cannot establish learning or safety.
Cluster trials found increased reporting without consistent safety-culture or clinical benefit, and one patient-feedback intervention had poor action-plan implementation.
Rebecca Lawton; Jane Kathryn O'Hara; Laura Sheard; Gerry Armitage; Kim Cocks; Hannah Buckley; Belen Corbacho; Caroline Reynolds; Claire Marsh; Sally Moore; Ian Watt; John Wright · 2017 · 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
Record direct observations
Write what was seen, heard or found, when and where; separate interpretations and unknowns.
Why this step exists
Early blame labels narrow investigation before the observation timeline is complete.
Success check
Another reader can distinguish fact, inference and missing information.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write what was seen, heard or found, when and where; separate interpretations and unknowns.” — and its success check, then attempt only this step.
Possible snag: A direct observation and causal inference share one field.
Correction: Use separate columns and quote the direct observation.
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
02
Apply only authorised immediate control
In the story, pause use of the outdated script and point users to the current source; do not improvise a wider intervention.
Why this step exists
Immediate containment should reduce risk without prejudging cause.
Success check
The specific exposure is controlled and action authority recorded.
I’m stuck on this step
Reset: Re-read this authored instruction — “In the story, pause use of the outdated script and point users to the current source; do not improvise a wider intervention.” — and its success check, then attempt only this step.
Possible snag: The result from “In the story, pause use of the outdated script and point users to the current source; do not improvise a wider intervention.” does not yet meet this declared check: The specific exposure is controlled and action authority recorded.
Correction: Return to the start of “Apply only authorised immediate control”, reduce complexity or pace, and repeat only the part needed to satisfy: “The specific exposure is controlled and action authority recorded.”
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
03
Route the report
Use the fictional current channel, urgency and recipient; timestamp acknowledgement and preserve the reporter’s preferred contact.
Why this step exists
A report that disappears cannot support learning.
Success check
Named ownership and next update are recorded.
I’m stuck on this step
Reset: Re-read this authored instruction — “Use the fictional current channel, urgency and recipient; timestamp acknowledgement and preserve the reporter’s preferred contact.” — and its success check, then attempt only this step.
Possible snag: The near-miss report receives no named acknowledgement.
Correction: Require named receipt, next update and timed fallback.
Possible snag: The reporter receives no outcome or safe follow-up.
Correction: Add a report-back owner and safe communication route.
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
04
Map affected roles and prior signals
Identify who could be affected, earlier similar reports, inaccessible routes and whether the issue could recur elsewhere.
Why this step exists
A single event may reveal a broader condition.
Success check
The scope is evidence-based, not assumed universal.
I’m stuck on this step
Reset: Re-read this authored instruction — “Identify who could be affected, earlier similar reports, inaccessible routes and whether the issue could recur elsewhere.” — and its success check, then attempt only this step.
Possible snag: The result from “Identify who could be affected, earlier similar reports, inaccessible routes and whether the issue could recur elsewhere.” does not yet meet this declared check: The scope is evidence-based, not assumed universal.
Correction: Return to the start of “Map affected roles and prior signals”, reduce complexity or pace, and repeat only the part needed to satisfy: “The scope is evidence-based, not assumed universal.”
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
05
Analyse system contributors
Examine version design, placement, update process, workload, training, incentives, supervision and interface conditions.
Why this step exists
“Carelessness” rarely explains why an error was possible or repeated.
Success check
At least three testable contributors are recorded.
I’m stuck on this step
Reset: Re-read this authored instruction — “Examine version design, placement, update process, workload, training, incentives, supervision and interface conditions.” — and its success check, then attempt only this step.
Possible snag: The result from “Examine version design, placement, update process, workload, training, incentives, supervision and interface conditions.” does not yet meet this declared check: At least three testable contributors are recorded.
Correction: Return to the start of “Analyse system contributors”, reduce complexity or pace, and repeat only the part needed to satisfy: “At least three testable contributors are recorded.”
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
06
Keep accountability distinct
Mark whether conduct, competence or duty questions require an authorised process; do not decide them in the learning worksheet.
Why this step exists
Systems analysis and accountability can coexist.
Success check
No person is blamed or cleared without the proper role and evidence.
I’m stuck on this step
Reset: Re-read this authored instruction — “Mark whether conduct, competence or duty questions require an authorised process; do not decide them in the learning worksheet.” — and its success check, then attempt only this step.
Possible snag: The result from “Mark whether conduct, competence or duty questions require an authorised process; do not decide them in the learning worksheet.” does not yet meet this declared check: No person is blamed or cleared without the proper role and evidence.
Correction: Return to the start of “Keep accountability distinct”, reduce complexity or pace, and repeat only the part needed to satisfy: “No person is blamed or cleared without the proper role and evidence.”
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
07
Design the corrective action
Choose an owner, resource, due date, expected effect, possible adverse effects and the exact mechanism changed.
Why this step exists
“Remind staff” is often too weak and untestable.
Success check
The action removes or controls the stale-version route.
I’m stuck on this step
Reset: Re-read this authored instruction — “Choose an owner, resource, due date, expected effect, possible adverse effects and the exact mechanism changed.” — and its success check, then attempt only this step.
Possible snag: The correction says be careful without changing a mechanism.
Correction: Change the mechanism, assign resources and define a verification test.
Possible snag: The action closes before its verification test passes.
Correction: Keep action open until matched verification and adverse-effect review.
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
08
Verify with matched work
Use a new fictional call card and cold user to test whether the current script is found and used; compare with baseline.
Why this step exists
Completion status is not risk reduction.
Success check
The repeat test measures the target error and unintended burden.
I’m stuck on this step
Reset: Re-read this authored instruction — “Use a new fictional call card and cold user to test whether the current script is found and used; compare with baseline.” — and its success check, then attempt only this step.
Possible snag: The result from “Use a new fictional call card and cold user to test whether the current script is found and used; compare with baseline.” does not yet meet this declared check: The repeat test measures the target error and unintended burden.
Correction: Return to the start of “Verify with matched work”, reduce complexity or pace, and repeat only the part needed to satisfy: “The repeat test measures the target error and unintended burden.”
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
09
Report back and update memory
Tell the fictional reporter what changed and limits, update the current procedure, supersede old copies and set review.
Why this step exists
Feedback and memory close the loop.
Success check
Reporter, users and future staff can find the verified current state.
I’m stuck on this step
Reset: Re-read this authored instruction — “Tell the fictional reporter what changed and limits, update the current procedure, supersede old copies and set review.” — and its success check, then attempt only this step.
Possible snag: The result from “Tell the fictional reporter what changed and limits, update the current procedure, supersede old copies and set review.” does not yet meet this declared check: Reporter, users and future staff can find the verified current state.
Correction: Return to the start of “Report back and update memory”, reduce complexity or pace, and repeat only the part needed to satisfy: “Reporter, users and future staff can find the verified current state.”
Stop / get help: Stop the fixture and use emergency or authorised reporting routes if a real risk, incident or safeguarding concern appears.
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.
Writing the report — Premature blame obscures mechanism and evidence.
Correct / safer
Keep observed facts, inferences and unanswered questions in separate fields.
Wrong / riskier
Write “careless volunteer used bad information.”
Finding cause — A label does not explain why stale material remained usable.
Correct / safer
Examine version ownership, placement and update design.
Wrong / riskier
Stop at “human error” without tracing conditions, controls or recovery signals.
Closing action — Completing an action card does not show the near-miss mechanism changed.
Correct / safer
Verify the target error in matched work.
Wrong / riskier
Mark closed when a reminder email is sent.
Handling accountability — Learning and legitimate accountability require distinct evidence.
Correct / safer
Route conduct questions to authorised process.
Wrong / riskier
Use system language to excuse all behaviour or punish before facts.
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.