Pre-Event Readiness

Work Through The Task

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, Pre-Event Readiness narrows that work to checks before exporting an EMS LAN snapshot for onsite operation. Because this is a basics 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 Task Changes

This is a practical workflow. Read it from top to bottom the first time: the early checks set scope, the middle steps make the change, and the final checks prove the result. 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 and /rego/events/manage/check-in?id=:eventId.
• Records or contracts involved: Event records, Registration records, and Staff roster records.
• 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.

Follow The Work In Order

1. Confirm the exact scope before opening the tool: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Pre-Event Readiness.
2. Read the visible state before editing anything: Use /rego/events/manage/offline-snapshot?id=:eventId and /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. Make only the change this guide describes: Keep Event records, Registration records, and Staff roster records in view so the work stays tied to the records or contracts it can affect.
4. Verify the result where another operator would look: 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.

Finish With Proof

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 before the first LAN export.

1. Step 1 - Start from the live event record. Open the correct event and confirm the event ID appears in the URL. This prevents cross-event export mistakes.
2. Step 2 - Gather prerequisites before touching files or devices. Check registration status, check-in readiness, inclusion claim plan, inventory, POS, roster, and shift tracker setup. This confirms the export will contain useful data.
3. Step 3 - Carry out the operator action slowly. Assign export owner, LAN device owner, onsite lead, import owner, and reconciliation owner. This gives every phase a responsible person.
4. Step 4 - Watch for side effects on people and records. Decide when online edits freeze or require event-lead approval while LAN is active. This reduces conflicts.
5. Step 5 - Verify the result in the right place. Confirm all readiness notes are recorded in the event operations plan. This gives staff a shared checklist.
6. Step 6 - Hand off the result with context. Continue to Export LAN Snapshot only after readiness is signed off. This protects the export.

Readiness checklist

1. Checkpoint 1. Event ID and public event are correct. Use it to confirm the work is still on the right path.
2. Checkpoint 2. Registration list and check-in entries are ready. Use it to confirm the work is still on the right path.
3. Checkpoint 3. Inclusion claim rules are understood. Use it to confirm the work is still on the right path.
4. Checkpoint 4. Inventory and POS setup are ready for onsite use. Use it to confirm the work is still on the right path.
5. Checkpoint 5. Roster and live shift tracker are ready. Use it to confirm the work is still on the right path.
6. Checkpoint 6. File custody and import ownership are assigned. Use it to confirm the work is still on the right path.