Run a tabletop and record observed recovery gaps
See this course’s project requirements
A tabletop continuity plan with critical services, dependencies, outage tolerance, minimum staffing/records, alternate delivery decisions, recovery evidence and a rehearsal log.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Save essential-function priority record and life-safety boundary; include the original-case decision evidence and a separate changed-case result.
- Save dependency/backup verification matrix; include the original-case decision evidence and a separate changed-case result.
- Save minimum-notice workaround with authority and time assumptions; include the original-case decision evidence and a separate changed-case result.
- Save communication plan with approval/receipt/test fields; include the original-case decision evidence and a separate changed-case result.
- Save tabletop gap and within-target bounded conclusion; include the original-case decision evidence and a separate changed-case result.
- Save continuity priority/dependency/workaround/notice/tabletop/resumption packet; include the original-case decision evidence and a separate changed-case result.
Review and revise
Use these criteria to check your work and choose what to improve.
- The final packet uses the supplied task-specific constraints and all six records agree.
- Every result can be traced to an identifier, input, calculation or stated decision rule.
- Changed-case practice updates dependent records and keeps holds or uncertainty visible.
- The packet states the learner role, authority boundary and specific next verification needed before real work.
Want more background?
The idea in everyday life
Original fictional workplace practice; paper or a local document is sufficient. The rules and records below are supplied for this exercise, not asserted universal workplace policy. Laurel tabletop simulation outage 09:00; approved F1 draft 09:30; backup route available 11:00; verification 11:30. Inject 11:10:role list missing partner group. Exercise policy F1 minimum notice includes staff, learners, partners. Partner route verified 12:30. RTO4 hours→13:00.
A tabletop tests decision and record sequences using provided scenario injects; it does not perform physical emergency response or prove production resilience.
Run a tabletop and record observed recovery gaps — worked practice
A tabletop tests decision and record sequences using provided scenario injects; it does not perform physical emergency response or prove production resilience.
Laurel tabletop simulation outage 09:00; approved F1 draft 09:30; backup route available 11:00; verification 11:30. Inject 11:10:role list missing partner group. Exercise policy F1 minimum notice includes staff, learners, partners. Partner route verified 12:30. RTO4 hours→13:00. Use paper or a local document. Preserve the original case and make a separate changed-case record.
1. Step 1
Reconstruct draft/route/verification timeline.
You should see: Initial sequence 09:00→11:30,150 min.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
2. Step 2
Apply inject to correct the minimum service result.
You should see: Partner group missing; initial minimum service incomplete.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
3. Step 3
Record actual simulated full minimum restoration.
You should see: All required groups by 12:30,210 min after 09:00.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
4. Step 4
Save tabletop gap and within-target bounded conclusion.
You should see: Partner dependency gap; 3.5 hours fits 4, target is not real outage proof.
Keep the stated identifier, unit and policy alongside this result so another reader can check it.
What to finish
Save tabletop gap and within-target bounded conclusion; include the original-case decision evidence and a separate changed-case result.
Watch for this
Calling partial recovery complete by ignoring a required group or using a tabletop as proven live continuity.
How can I tell I understand it?
Using the supplied identifiers, I can save tabletop gap and within-target bounded conclusion. My changed-case record names the revised condition and explains which dependent decision it changes.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. The direct-access limitation is preserved; official search-retrieved context supports the stated scope only.
Access: Official primary-page summary was available in web search; direct page retrieval was blocked in this environment. Full page and interactive operation are not claimed.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Source & access notes · checked 2026-10-01
Public agency or educational context; no source exercises are copied and no simulated threshold is presented as an official rule. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Source & access notes · checked 2026-10-01
Occupational task and responsibility context; the exercise policies and quantities are original fictional inputs. Page title and relevant content inspected; no interactive controls or credential process tested.
Access: Readable official page retrieved with the web reader on 2026-10-01.
Reuse: All teaching cases, data, worked steps and questions are original. Link and limited paraphrase for context; no copied source exercises.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.