Post-Event Closeout Runbook

Use This During Live Operations

Use this guide when event work may happen on local devices, offline files, or LAN-only tools instead of the live online dashboard. In this guide, Post-Event Closeout Runbook narrows that work to eMS LAN closeout steps after import, reconciliation, and file cleanup. Because this is a runbooks page, read it as part of the EMS LAN learning path rather than as an isolated checklist.

EMS LAN keeps an event moving when internet access is unreliable, but it also creates a second place where event records can change. Read the page for the decision it helps a person make, then use the steps and checks as a steady path from context to action to proof.

What This Runbook Stabilizes

This page is for a pressured moment. Use the sequence to slow the work down, assign ownership, protect records, and leave a clear next step. The intended readers are Event leads and Reconciliation operators. If the guide names a dashboard route, service area, export, or record type, treat that name as a pointer to real operational responsibility.

• Primary surface or service: /rego/events/manage/offline-snapshot-history?id=:eventId.
• Records or contracts involved: Audit history and Closeout notes.
• Main care point: Watch for losing track of which file, device, person, or import is trusted while attendee, staff, inventory, POS, or check-in records change offline.
• Proof worth keeping: event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note.

Move From Situation To Handoff

1. Name the live situation: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Post-Event Closeout Runbook.
2. Assign the operator and reviewer: Use /rego/events/manage/offline-snapshot-history?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Perform the smallest safe action: Keep Audit history and Closeout notes in view so the work stays tied to the records or contracts it can affect.
4. Write the handoff before the next person takes over: Before handing off, save proof such as event ID, snapshot filename, export time, device owner, import summary, sync-history entry, reconciliation count, and supervisor note so the next lead can tell which file and device state are trusted.

The Runbook Is Complete When

You are ready to use the rest of this page when the purpose, owner, affected information, and proof are all clear enough for a second person to review.

1. Scope is named: The work is tied to the correct page, event, report, route, file, person, or record.
2. Impact is understood: The operator can explain the effect on offline files, check-in access, staff rosters, inventory counts, POS totals, and import history.
3. Proof is findable: The handoff points to evidence that the next lead can tell which file and device state are trusted.

End-to-end operator runbook

Use this numbered runbook after LAN reconciliation.

1. Step 1 - Stabilize the situation. Confirm the event has a final import entry and reconciliation notes. This proves closeout is not starting early.
2. Step 2 - Choose the current source of truth. Review open issues for check-in, claims, inventory, POS, roster, shifts, and file custody. This identifies remaining obligations.
3. Step 3 - Execute the scenario path. Close or assign every open issue and document the owner. This prevents unresolved LAN work from disappearing.
4. Step 4 - Pause at every risk marker. Confirm no old snapshot files remain on uncontrolled devices or chat threads. This protects sensitive data.
5. Step 5 - Capture proof before the team moves on. Confirm final dashboard counts and audit history match closeout notes. This proves the record is understandable later.
6. Step 6 - Debrief and hand off unresolved work. Tell event leadership the EMS LAN workflow is closed or list the blockers. This completes the operating cycle.

Closeout checks

1. Checkpoint 1. Import audit exists. Use it to confirm the work is still on the right path.
2. Checkpoint 2. Reconciliation is complete or assigned. Use it to confirm the work is still on the right path.
3. Checkpoint 3. Local files are deleted, archived, or controlled. Use it to confirm the work is still on the right path.