EMS LAN Docs

Choose Your Starting Point

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, EMS LAN Docs narrows that work to numbered operator guides for offline EMS export, LAN operation, import, reconciliation, safety, and audit. Because this is a start 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 Section Helps You Decide

This is the map page. Start here when you know the general area but not the exact guide. The page should help you choose the next safe reading path before opening a dashboard screen, file, or service route. The intended readers are Event leads, LAN operators, and Support 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 and /rego/events/manage/offline-snapshot-history?id=:eventId.
• Records or contracts involved: Offline snapshots, Check-in records, Inventory records, POS records, and HR 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.

A Natural Way Through The Section

1. Name the situation in front of you: Begin by naming the EMS LAN situation, the owner, and the exact item involved in EMS LAN Docs.
2. Match it to the closest guide group: 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. Open one guide at a time: Keep Offline snapshots, Check-in records, Inventory records, POS records, and HR roster records in view so the work stays tied to the records or contracts it can affect.
4. Return here when the work changes shape: 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.

Leave This Page With A Direction

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 to choose the right EMS LAN guide before touching files or records.

1. Step 1 - Choose the right doorway. Open the event manage page and confirm the event name, event ID, and onsite operating date. This proves the docs and dashboard work refer to the same event.
2. Step 2 - Read the risk before the task. Read What Is EMS LAN? and Offline vs Online before exporting. This prevents confusion between online dashboard state and LAN-local state.
3. Step 3 - Follow one path at a time. Follow the matching basics page: readiness, export, operate, import, or reconcile. This keeps the workflow in the intended order.
4. Step 4 - Keep proof visible. Open the relevant safety and reconciliation pages when files, money-adjacent records, staff records, or attendee access are involved. This makes risk visible before the next action.
5. Step 5 - Move to the next owner. After any export or import, check LAN Sync History and the affected dashboard surface. This confirms the system recorded what happened.
6. Step 6 - Return here if you get lost. Record who owns the next step, where the approved file is stored, and what remains unresolved. This gives the next operator a clean handoff.

Learning path

• Foundations explain what EMS LAN is and why offline files are sensitive.
• Basics walk through readiness, export, offline operation, import, and reconciliation.
• Surface guides explain the exact dashboard pages used by EMS LAN.
• Runbooks cover event-pressure scenarios like internet outage and failed import.
• Reconciliation guides prove the dashboard is trustworthy after LAN operations.
• Safety and reference pages document file custody, role control, APIs, schema, and certification.

Core rule

EMS LAN is not just “download a file and upload it later.” It is a controlled handoff between online records, offline devices, onsite operations, import summaries, and audit history.