What Is EMS LAN?

Start With The Idea

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, What Is EMS LAN? narrows that work to plain explanation of EMS LAN and how operators use it during airgapped onsite event operations. Because this is a foundations 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 Page Explains

This is the concept layer. Read it before trying to operate the workflow so the later steps make sense in ordinary language first. The intended readers are First-time LAN operators and Event leads. 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: Offline snapshots and Check-in 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.

How The Idea Builds Toward Action

1. Say the idea in ordinary words: Begin by naming the EMS LAN situation, the owner, and the exact item involved in What Is EMS LAN?
2. Connect the idea to one real screen or source: 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. Name what could change for people or records: Keep Offline snapshots and Check-in records in view so the work stays tied to the records or contracts it can affect.
4. Choose the next practical guide from the related links: 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.

You Are Ready To Continue 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 you are deciding whether EMS LAN applies.

1. Step 1 - Name the real-world problem. Confirm the event needs onsite operation that may not have reliable internet. This proves EMS LAN is being considered for a real operating need.
2. Step 2 - Connect the idea to event records. Identify which flows must work offline: check-in, inclusion claim, inventory, POS, roster, or shifts. This shows what records the snapshot must support.
3. Step 3 - Decide what the operator should do differently. Choose the EMS LAN flow only if operators can control files, devices, and import timing. This avoids casual exports.
4. Step 4 - Find the risk this concept prevents. Ask who can see the file, who can change LAN-local records, and who imports it later. This makes accountability explicit.
5. Step 5 - Write down the proof needed later. Record the EMS LAN decision in the event operations plan. This gives onsite staff a shared source of truth.
6. Step 6 - Move from concept to workflow. Send operators to Pre-Event Readiness before export. This keeps the next step safe.

Simple meaning

EMS LAN is the offline version of key Event Management operations. The online dashboard exports a snapshot. The onsite LAN system uses that snapshot while internet access is unreliable or intentionally avoided. After onsite operation, the LAN result is imported back into the dashboard and reconciled.

What changes

State	Meaning
Online dashboard	Current source records before export.
Exported snapshot	A controlled file containing event operating data.
LAN-local state	Changes made onsite while operating offline.
Imported state	Dashboard updates applied from the returned LAN file.
Reconciled state	Verified dashboard records after import and review.