OBJECTIVE: Rehearse how a service handles an unresolved consequence after its technical repair is verified. Use a fictional tabletop case or authorized test environment. Do not submit invented claims to a live support process or collect real participants’ private records for this exercise.
1. Establish the Repair Boundary
Write down the capability restored and the evidence supporting that claim. For example: a synthetic credential is accepted by the test gate at a recorded time. Do not expand that result into a claim that the participant experienced no remaining impact.
2. Introduce One Reported Consequence
Add a fictional missed appointment. Keep three fields separate: what the system recorded, what the participant reports, and what remains unknown. The purpose is to test the review route, not to predetermine whether the incident caused the reported consequence.
Use the distinction in Restoration Is Not Recovery to prevent both automatic acceptance and automatic dismissal.
3. Name the Decision Authority
Identify which function can consider the remaining request and what it is authorized to decide. Record the technical team’s limits. A reviewer should be able to explain the handoff without promising compensation, changing an unrelated record, or demanding evidence they have no authority to assess.
4. Test Acceptance and Silence
Walk through the receiving function accepting the case. Then rehearse a missing acknowledgement: who notices, when do they check, and what does the participant see? Do not let an unanswered transfer inherit the technical ticket’s completed status.
Specify a follow-up date appropriate to the exercise. A timestamp is evidence that someone scheduled a check, not evidence that the recipient accepted responsibility.
5. Write a Bounded Closure Record
State what was restored, what impact was reported, what was verified, who accepted the remaining decision, and which questions are still open. Keep the records linked while allowing their statuses to differ.
Compare the result with Mara’s fictional case in The Missing Hours. Place this exercise alongside the accountability review workflow. Success means a clear boundary and an accepted next step, not a guaranteed outcome for every reported consequence.