Import and Reconcile 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, Import and Reconcile Runbook narrows that work to scenario runbook for importing returned LAN state and proving dashboard records after onsite operation. 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 Import operators 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?id=:eventId and /rego/events/manage/offline-snapshot-history?id=:eventId.
• Records or contracts involved: Import summaries and Audit history.
• 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 Import and Reconcile Runbook.
2. Assign the operator and reviewer: Use /rego/events/manage/offline-snapshot?id=:eventId and /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 Import summaries and Audit history 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 onsite operation ends.

1. Step 1 - Stabilize the situation. Confirm the returned file is final, from the approved LAN device, and belongs to the correct event ID. This prevents importing the wrong state.
2. Step 2 - Choose the current source of truth. Read handoff notes for check-in, claims, inventory, POS, roster, shifts, and known issues. This tells you what counts to expect.
3. Step 3 - Execute the scenario path. Import the returned snapshot through the LAN Snapshot page. This applies LAN-local changes to the dashboard.
4. Step 4 - Pause at every risk marker. Compare applied summary counts to handoff notes before closing the import page. This catches obvious mismatch early.
5. Step 5 - Capture proof before the team moves on. Open LAN Sync History and then each affected reconciliation page. This proves the import was recorded and reviewed.
6. Step 6 - Debrief and hand off unresolved work. Declare reconciled only after all affected record groups pass checks or have tracked follow-up. This closes the LAN workflow.

Required proof

1. Checkpoint 1. Latest import appears in LAN Sync History. Use it to confirm the work is still on the right path.
2. Checkpoint 2. Applied counts match expected record groups. Use it to confirm the work is still on the right path.
3. Checkpoint 3. Reconciliation notes list unresolved issues. Use it to confirm the work is still on the right path.