Offline vs Online State

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, Offline vs Online State narrows that work to how online dashboard records, exported snapshots, LAN-local changes, imports, and reconciled records differ. 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 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 and /rego/events/manage/offline-snapshot-history?id=:eventId.
• Records or contracts involved: Event records and Snapshot audit entries.
• 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 Offline vs Online State.
2. Connect the idea to one real screen or source: 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. Name what could change for people or records: Keep Event records and Snapshot audit entries 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 to avoid mixing online and offline truth.

1. Step 1 - Name the real-world problem. Confirm whether the event is currently operating online, offline, or in reconciliation. This tells staff which system should be trusted.
2. Step 2 - Connect the idea to event records. Check the latest export time and whether any online edits happened after export. This identifies possible conflicts.
3. Step 3 - Decide what the operator should do differently. During LAN operation, keep onsite changes in the LAN system until import. This avoids split decisions.
4. Step 4 - Find the risk this concept prevents. Before import, identify records that may have changed online and offline. This prevents silent overwrites or count confusion.
5. Step 5 - Write down the proof needed later. After import, compare import summary, sync history, and affected surfaces. This proves the dashboard caught up.
6. Step 6 - Move from concept to workflow. Tell staff when the dashboard is the trusted source again. This ends the offline operating window.

State comparison

State	Operator meaning	Main risk
Online	Dashboard records are live.	Internet failure can stop onsite work.
Exported	File is a point-in-time copy.	It can become stale.
LAN-local	Offline devices hold onsite changes.	Dashboard does not know yet.
Imported	Dashboard applied returned LAN changes.	Counts must be checked.
Reconciled	Operators verified records and audit.	Missing review hides mistakes.