Day-Before Event 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, Day-Before Event Runbook narrows that work to final EMS LAN readiness, export, file labeling, and handoff flow before event day. 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 LAN export 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?id=:eventId.
• Records or contracts involved: Snapshot exports and Event operation 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 Day-Before Event Runbook.
2. Assign the operator and reviewer: Use /rego/events/manage/offline-snapshot?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 Snapshot exports and Event operation 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 the day before onsite operation.

1. Step 1 - Stabilize the situation. Confirm event ID, event date, final registration window, and expected LAN usage. This prevents preparing the wrong event.
2. Step 2 - Choose the current source of truth. Check registration list, check-in rules, claims, inventory, POS, roster, shifts, and device assignments. This proves the snapshot will be useful.
3. Step 3 - Execute the scenario path. Export the approved LAN snapshot and label it with event name, event ID, timestamp, and owner. This creates the controlled handoff file.
4. Step 4 - Pause at every risk marker. Confirm no planned online edits will make the file stale before doors open. This reduces conflict.
5. Step 5 - Capture proof before the team moves on. Check LAN Sync History for the export entry. This proves the export was recorded.
6. Step 6 - Debrief and hand off unresolved work. Hand the file to the assigned LAN operator and record the device or storage location. This completes day-before preparation.

Handoff fields

1. Action 1. Write event name and event ID. Confirm the event ID, file, or device state before continuing.
2. Action 2. Write export timestamp and file format. Check the offline proof before moving on.
3. Action 3. Write file owner and device owner. Keep the sync history or import summary visible.
4. Action 4. Write import owner and reconciliation owner. Confirm the event ID, file, or device state before continuing.