Revision 7T · Full Tutorial Edition · Updated 1 September 2026
PWR-234 · SELF GUIDED full tutorial
Create an organisational record that remains findable, challengeable and current after staff turnover
This lesson teaches organisational memory through one fictional decision record. You will record the decision, evidence, authority, assumptions and dissent; give it an owner, audience, version and review date; test whether a new reader can find and use it; then replace an old instruction without erasing its history.
What you will produceThe learner creates and retrieves a fictional versioned decision record, correctly identifies its authority plus assumptions, then replaces it with a traceable current version.
Full step-by-step individual tutorial · TLU-PWR-234
The learner creates and retrieves a fictional versioned decision record, correctly identifies its authority plus assumptions, then replaces it with a traceable current version.
Use fictional organisations and non-sensitive decision examples.
Create source-bound decision, lesson and succession records.
Mark a record unknown, disputed, expired or superseded rather than forcing certainty.
Qualified help is required for
Records for a real employer, incident, employee, patient, client, whistleblower or regulated activity.
Retention, disclosure, legal hold, confidentiality and access decisions.
Approval of live procedures, training or organisational policy.
Never do this from the page alone
Put real confidential or personal data into the fixture.
Treat a shared folder or report count as proof that knowledge can be retrieved and used.
Delete dissent or silently overwrite an older decision to make the history look clean.
2 · Get ready
Gather what you need and check the starting conditions
What you need
Supplied fictional service packet: version 1, effective 1 March, requires an acknowledgement no later than the end of the next calendar day. Version 2, effective 15 March after a staffing review, requires an acknowledgement no later than the end of the second working day after receipt. The fictional decision owner is Service Director Mira Vale. Version 1 assumed that one coordinator was always available. The preserved dissent note says that users with communication barriers need an escalation route rather than a longer silent wait.
Decision-record template with source, evidence, authority, assumptions, dissent, version, sensitivity, audience, review, expiry and correction.
Retrieval cues, timer, portable export and a second-reader rubric.
Before you start
Use only fictional data and clearly label all outputs as exercise records.
Define the future task the memory must support and who is allowed to use it.
Set the rule that a new version supersedes but does not silently rewrite the historical record.
3 · The method
Follow these steps in order
Name future use
Write the exact question a successor must answer and the information or action the record must support.
Why: Memory is judged at use, not at storage.
Check: The record has one retrieval purpose and a named audience.
Capture decision and authority
State what was decided, by whom, under what mandate and what remains outside that authority.
Why: An instruction without authority may be memorable but invalid.
Check: The mandate and decision owner are traceable to fictional source packet.
Bind evidence and assumptions
Link each important statement to its source; list assumptions, uncertainties and unresolved facts.
Why: Future readers need to know what could make this decision wrong.
Check: The evidence and assumption fields are separate and source-bound.
Preserve dissent
Record the dissenting view, who may review it and what new evidence would reopen this decision.
Why: Disagreement can be critical future memory.
Check: The dissent remains visible without being treated as active instruction.
Add lifecycle and access
Assign the version, date, owner, audience, sensitivity, review or expiry date and accessible format.
Why: An unowned record can remain findable while becoming stale or inaccessible to its intended reader.
Check: Every field has a value or an explicit reason for absence.
Create retrieval cues
Index the record by its function, date and decision—not only by its author or folder—then ask another reader to find it without hints.
Why: Turnover changes names, roles and knowledge of the original folder structure.
Check: A new reader retrieves current record within the declared time.
Apply supersession
Create version 2 from supplied correction, link it to version 1 and mark version 1 inactive while preserving the reason for change.
Why: Silent overwrite loses learning, while duplicate active versions create error.
Check: A search returns version 2 first and labels version 1 as superseded.
Test successor use
Give fictional task and current record to a second reader, then ask them to state the action, authority, key assumption and escalation route.
Why: Findability alone does not prove usable memory.
Check: The reader answers every required field without oral rescue from original author.
Close or retire
If the purpose, authority or currentness ends, archive or delete this record under fictional rule and update all active links.
Why: Inactive knowledge should not keep directing work.
Check: No expired instruction remains in active retrieval route.
4 · Worked example
See the whole method used once
Scenario
A fictional community information service first required an acknowledgement by the end of the next calendar day. Version 2 replaces that rule with an acknowledgement no later than the end of the second working day after receipt.
Walkthrough
The learner stores version 1 with the director's fictional mandate, the one-coordinator staffing assumption and the accessibility dissent note.
They add the search terms “reply deadline,” “acknowledgement standard” and “March staffing review.” A second reader finds the record in 38 seconds without folder instructions.
They create version 2, link it to version 1, make version 2 active and label version 1 superseded with the staffing-review reason.
A successor retrieves version 2, states the exact two-working-day acknowledgement deadline, identifies the staffing assumption and finds the accessibility escalation route.
Result
The active deadline remains clear after simulated staff turnover, while the old rule, its assumption and the dissent note remain traceable. This demonstrates one fictional record, not long-term organisational learning.
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
Recording a decision
Store stated mandate, evidence, assumptions and dissent with this decision.
Save only the final conclusion with no mandate or assumptions.
Future readers cannot judge when a context change invalidates a bare answer.
Indexing decision point
Use function and decision cues tested by a new reader.
Rely on the original author’s folder structure.
The author’s folder knowledge can disappear during turnover.
Updating decision point
Create a linked superseding version and record the reason for change.
Edit old file in place with no reason.
A silent change destroys the provenance needed to understand later corrections.
Claiming memory
Test delayed retrieval and correct use by a second reader.
Count uploaded documents without testing retrieval or correct use.
Volume does not show findability, currentness or action.
6 · Common mistakes
Spot the error and apply the correction
Common mistakes and corrections
Mistake
Fix
The decision record has no owner or review date.
Assign a named role, review date and expiry.
A staffing forecast is stored as fact instead of as an assumption.
Move every condition or forecast into an explicit assumption field.
The dissent note disappears when active version changes.
Preserve the alternative view and cited evidence trigger that would reopen it.
Two versions appear active in different search routes.
Set one current status and redirect active indexes.
Only the original author tests retrieval.
Use a new reader who receives no hints about the original folder structure.
7 · Practice
Turn the steps into a usable skill
First session
Write the future-use question and create version 1 with authority, evidence, assumptions and dissent.
Add the lifecycle fields plus three retrieval cues.
Run a cold retrieval with a second reader.
Apply the version 2 correction and verify that only version 2 is active.
Test the successor’s interpretation, then record one repair.
Repeat plan
Retest cold retrieval after one week and review active records at their declared dates. After a staff, mandate, source or system change, sample one current record plus one superseded record for correct routing.
Progress when
A new reader retrieves and interprets current record without oral rescue.
Assumptions, dissent and authority are visible and reusable.
Supersession removes old versions from active use while preserving history.
Do not progress when
Real confidential, personal, whistleblowing or legally controlled data appears.
No legitimate owner or retention/access rule can be established.
Record is proposed as a live instruction without authorised review.
8 · Check the result
Measure what changed
Delayed retrieval and correct reuse of one fictional organisational record
How: Time the cold retrieval and score current version, authority, evidence, assumption, dissent, action, escalation and superseded-record handling.
Good result: A good result retrieves current record within the declared time and correctly states all eight elements with no stale action.
This does not prove: It does not prove institutional learning, long-term retention, compliance or reduced repeat failure.
Self-check
What future question is this record designed to answer?
Who had authority, what could they not decide?
Which assumption or dissent could reopen this decision?
Can a new reader find version 2 and identify version 1 as superseded?
9 · Stop, adapt or get help
Keep the safety boundary practical
Stop and get help
Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
Stop when original authority, source, access or current version cannot be established; do not publish this record as active.
Use authorised records, legal, privacy, union or whistleblowing routes for real organisational material.
Accessibility and adaptations
Provide structured headings, screen-reader order, plain language, large print and translated summaries while preserving source links.
Use multiple retrieval cues, AAC and asynchronous review; do not require rapid oral recall.
Separate sensitive identity from reusable lesson only through an authorised process, never by improvised redaction.
10 · Evidence and limits
Why these instructions are here
primary research
Guided team self-correction can improve selected team processes, but a short intervention does not prove durable organisational memory.
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
Name future use
Write the exact question a successor must answer and the information or action the record must support.
Why this step exists
Memory is judged at use, not at storage.
Success check
The record has one retrieval purpose and a named audience.
I’m stuck on this step
Reset: Re-read this authored instruction — “Write the exact question a successor must answer and the information or action the record must support.” — and its success check, then attempt only this step.
Possible snag: The result from “Write the exact question a successor must answer and the information or action the record must support.” does not yet meet this declared check: The record has one retrieval purpose and a named audience.
Correction: Return to the start of “Name future use”, reduce complexity or pace, and repeat only the part needed to satisfy: “The record has one retrieval purpose and a named audience.”
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
02
Capture decision and authority
State what was decided, by whom, under what mandate and what remains outside that authority.
Why this step exists
An instruction without authority may be memorable but invalid.
Success check
The mandate and decision owner are traceable to fictional source packet.
I’m stuck on this step
Reset: Re-read this authored instruction — “State what was decided, by whom, under what mandate and what remains outside that authority.” — and its success check, then attempt only this step.
Possible snag: The result from “State what was decided, by whom, under what mandate and what remains outside that authority.” does not yet meet this declared check: The mandate and decision owner are traceable to fictional source packet.
Correction: Return to the start of “Capture decision and authority”, reduce complexity or pace, and repeat only the part needed to satisfy: “The mandate and decision owner are traceable to fictional source packet.”
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
03
Bind evidence and assumptions
Link each important statement to its source; list assumptions, uncertainties and unresolved facts.
Why this step exists
Future readers need to know what could make this decision wrong.
Success check
The evidence and assumption fields are separate and source-bound.
I’m stuck on this step
Reset: Re-read this authored instruction — “Link each important statement to its source; list assumptions, uncertainties and unresolved facts.” — and its success check, then attempt only this step.
Possible snag: The result from “Link each important statement to its source; list assumptions, uncertainties and unresolved facts.” does not yet meet this declared check: The evidence and assumption fields are separate and source-bound.
Correction: Return to the start of “Bind evidence and assumptions”, reduce complexity or pace, and repeat only the part needed to satisfy: “The evidence and assumption fields are separate and source-bound.”
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
04
Preserve dissent
Record the dissenting view, who may review it and what new evidence would reopen this decision.
Why this step exists
Disagreement can be critical future memory.
Success check
The dissent remains visible without being treated as active instruction.
I’m stuck on this step
Reset: Re-read this authored instruction — “Record the dissenting view, who may review it and what new evidence would reopen this decision.” — and its success check, then attempt only this step.
Possible snag: The dissent note disappears when active version changes.
Correction: Preserve the alternative view and cited evidence trigger that would reopen it.
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
05
Add lifecycle and access
Assign the version, date, owner, audience, sensitivity, review or expiry date and accessible format.
Why this step exists
An unowned record can remain findable while becoming stale or inaccessible to its intended reader.
Success check
Every field has a value or an explicit reason for absence.
I’m stuck on this step
Reset: Re-read this authored instruction — “Assign the version, date, owner, audience, sensitivity, review or expiry date and accessible format.” — and its success check, then attempt only this step.
Possible snag: The decision record has no owner or review date.
Correction: Assign a named role, review date and expiry.
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
06
Create retrieval cues
Index the record by its function, date and decision—not only by its author or folder—then ask another reader to find it without hints.
Why this step exists
Turnover changes names, roles and knowledge of the original folder structure.
Success check
A new reader retrieves current record within the declared time.
I’m stuck on this step
Reset: Re-read this authored instruction — “Index the record by its function, date and decision—not only by its author or folder—then ask another reader to find it without hints.” — and its success check, then attempt only this step.
Possible snag: Only the original author tests retrieval.
Correction: Use a new reader who receives no hints about the original folder structure.
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
07
Apply supersession
Create version 2 from supplied correction, link it to version 1 and mark version 1 inactive while preserving the reason for change.
Why this step exists
Silent overwrite loses learning, while duplicate active versions create error.
Success check
A search returns version 2 first and labels version 1 as superseded.
I’m stuck on this step
Reset: Re-read this authored instruction — “Create version 2 from supplied correction, link it to version 1 and mark version 1 inactive while preserving the reason for change.” — and its success check, then attempt only this step.
Possible snag: The result from “Create version 2 from supplied correction, link it to version 1 and mark version 1 inactive while preserving the reason for change.” does not yet meet this declared check: A search returns version 2 first and labels version 1 as superseded.
Correction: Return to the start of “Apply supersession”, reduce complexity or pace, and repeat only the part needed to satisfy: “A search returns version 2 first and labels version 1 as superseded.”
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
08
Test successor use
Give fictional task and current record to a second reader, then ask them to state the action, authority, key assumption and escalation route.
Why this step exists
Findability alone does not prove usable memory.
Success check
The reader answers every required field without oral rescue from original author.
I’m stuck on this step
Reset: Re-read this authored instruction — “Give fictional task and current record to a second reader, then ask them to state the action, authority, key assumption and escalation route.” — and its success check, then attempt only this step.
Possible snag: A staffing forecast is stored as fact instead of as an assumption.
Correction: Move every condition or forecast into an explicit assumption field.
Possible snag: Two versions appear active in different search routes.
Correction: Set one current status and redirect active indexes.
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
09
Close or retire
If the purpose, authority or currentness ends, archive or delete this record under fictional rule and update all active links.
Why this step exists
Inactive knowledge should not keep directing work.
Success check
No expired instruction remains in active retrieval route.
I’m stuck on this step
Reset: Re-read this authored instruction — “If the purpose, authority or currentness ends, archive or delete this record under fictional rule and update all active links.” — and its success check, then attempt only this step.
Possible snag: The result from “If the purpose, authority or currentness ends, archive or delete this record under fictional rule and update all active links.” does not yet meet this declared check: No expired instruction remains in active retrieval route.
Correction: Return to the start of “Close or retire”, reduce complexity or pace, and repeat only the part needed to satisfy: “No expired instruction remains in active retrieval route.”
Stop / get help: Stop if real sensitive data, a live policy or a disclosure enters fictional fixture.
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.
Recording a decision — Future readers cannot judge when a context change invalidates a bare answer.
Correct / safer
Store stated mandate, evidence, assumptions and dissent with this decision.
Wrong / riskier
Save only the final conclusion with no mandate or assumptions.
Indexing decision point — The author’s folder knowledge can disappear during turnover.
Correct / safer
Use function and decision cues tested by a new reader.
Wrong / riskier
Rely on the original author’s folder structure.
Updating decision point — A silent change destroys the provenance needed to understand later corrections.
Correct / safer
Create a linked superseding version and record the reason for change.
Wrong / riskier
Edit old file in place with no reason.
Claiming memory — Volume does not show findability, currentness or action.
Correct / safer
Test delayed retrieval and correct use by a second reader.
Wrong / riskier
Count uploaded documents without testing retrieval or correct use.
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.