LESSON 2 OF 2 · Real-life skills
Check the result and leave a clear handover
Write an honest finish record with evidence, an unresolved item and a next action.
1. Before you start: Use the fictional evidence cards. No email, account or provider is connected.
Allow about 15 minutes for reading and practice.
2. Why it matters
“Done” can hide a missing check. A useful handover tells the next person exactly what remains.
3. Worked example
Evidence A: the helper removed the app in the fictional scenario.
Evidence B: a prepared request has not been sent or approved.
Evidence C: no provider renewal confirmation is available.
Supported conclusion: preparation is complete; renewal status is unverified. The organiser must review the next action.
4. Guided practice
- Read the three evidence cards.
- Record whether the renewal is confirmed, unverified or blocked.
- Select the evidence that supports your status.
- Choose the smallest permitted next action and its owner.
- Read and download the handover. Check that it claims no unverified result.
Opening your practice…
5. Try it yourself
Prepare a handover for the organiser. State the gap clearly without claiming that any real action occurred.
Use the fictional scenario only. State what your evidence proves and what still needs a check.
These are your review notes. They are not a scored test.
SOMETHING TO KEEP
6. Your useful output
Keep the evidence record and reusable handover template. Adapt the blank template outside this practice when appropriate.
Preview the written output
Check the result and leave a clear handover Fictional learning exercise. No real action or service connection. Practice completion: not marked complete Renewal status selected: not selected. Evidence: not selected. Next action: not selected. Evidence supplied: A app removed, B draft not sent or approved, C no provider confirmation. Supported conclusion: unverified. Your explanation and next action: Not recorded yet. Success criteria reviewed: [ ] Renewal status is marked unverified. [ ] The missing provider confirmation is named. [ ] The next action is owner review through the official provider. [ ] The record says that this is a simulation and nothing was sent. Next step: Use the real-life library to apply this pattern to another fictional admin task. TASK AND EVIDENCE TEMPLATE Task: [name a bounded task] Owner: [one responsible role] Allowed preparation: [scope] Approval needed before: [action] Current state: [prepared / approved / submitted / verified / blocked] Evidence: [source, date and what it proves; no credentials] Still unknown: [gap] Next action and owner: [smallest permitted step] Success criteria: [observable result] Stop if: [missing access, evidence or approval] Keep app removal, subscription changes and account closure separate.
7. Common mistakes and recovery
Treating a draft as a completed action creates a false record.
Use separate states: prepared, approved, submitted and verified.
Repeating an action can create duplicate requests.
Check the existing result first. Name the blocker and the owner.
A handover says “check later” without naming who or what.
Name the responsible role, evidence gap and next permitted action.
8. Optional self-check
Skip this if you prefer. It never affects your practical completion.
9. Your next step
Use the real-life library to apply this pattern to another fictional admin task.
Mark completion when your practical work is ready. You do not need to take the check.
Pilot progress and drafts save in this browser. Optional check answers are stored separately.
Saving and privacy
Use fictional details only. Nothing from these pilots is sent to a service.
This browser storage is separate from existing course recovery codes. Clearing site data, private browsing or changing device can lose it. Preview and public site storage are separate.
Download useful outputs before leaving. Use one tab per lesson. A progress copy is a readable record; this preview does not import it.