Internet Outage 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, Internet Outage Runbook narrows that work to eMS LAN fallback flow when online dashboard operation fails or becomes unreliable. 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 Onsite leads and LAN 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/check-in?id=:eventId.
• Records or contracts involved: Check-in records and Offline 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 Internet Outage Runbook.
2. Assign the operator and reviewer: Use /rego/events/manage/check-in?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 Check-in records and Offline 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 when internet service fails.

1. Step 1 - Stabilize the situation. Confirm whether the outage affects all operators or only one device. This decides whether EMS LAN should take over.
2. Step 2 - Choose the current source of truth. Identify the latest approved LAN snapshot and whether it is safe to use. This prevents switching to stale data blindly.
3. Step 3 - Execute the scenario path. Declare LAN active and route onsite work to the approved LAN devices. This creates one trusted operating mode.
4. Step 4 - Pause at every risk marker. Freeze or control online edits until import and reconciliation. This avoids split-brain records.
5. Step 5 - Capture proof before the team moves on. Keep outage notes with start time, devices used, and record groups operated offline. This supports later import review.
6. Step 6 - Debrief and hand off unresolved work. When service returns, import the final LAN file before treating dashboard counts as live. This restores online truth.

Questions before switching

1. Question 1. Is there an approved LAN snapshot? Write the answer before choosing the next action.
2. Question 2. Is the snapshot recent enough for safe entry decisions? Write the answer before choosing the next action.
3. Question 3. Who declares LAN active? Write the answer before choosing the next action.