EMS LAN Data Records

Use This Reference Carefully

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 Data Records narrows that work to records exported, changed, imported, reconciled, and audited by EMS LAN. Because this is a reference 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 Reference Collects

This page is for checking details. Use it to confirm names, routes, records, fields, or certification points before relying on memory. The intended readers are Support leads 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.
• Records or contracts involved: Attendee regos, Dealers Den regos, Check-in records, Inventory records, POS records, and HR 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 To Find The Right Entry

1. Search for the exact name or route: Begin by naming the EMS LAN situation, the owner, and the exact item involved in EMS LAN Data Records.
2. Read the surrounding note, not only the matching line: 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. Compare the reference with the live screen, file, or service evidence: Keep Attendee regos, Dealers Den regos, Check-in records, Inventory records, POS records, and HR records in view so the work stays tied to the records or contracts it can affect.
4. Save the evidence that proves the entry was checked: 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.

Confirm The Reference Still Matches Reality

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 tracing which records EMS LAN can affect.

1. Step 1 - Identify the thing being verified. Identify the event and the import or export entry being reviewed. This anchors the record trace.
2. Step 2 - Translate the technical name into plain language. Read the applied summary and source metadata. This tells you which record groups changed.
3. Step 3 - Match the route, file, or record to real workflow. Open the affected surface and verify the record group listed below. This confirms dashboard state.
4. Step 4 - Collect enough evidence to avoid guessing. Treat attendee access, fulfillment, stock, POS, staff shifts, and audit history as high-impact records. This keeps review serious.
5. Step 5 - Confirm implementation and docs agree. Record whether each record group passed reconciliation or needs follow-up. This creates proof.
6. Step 6 - Send the result to the right owner. Hand unresolved record questions to the correct owner. This prevents forgotten issues.

Record map

Record group	EMS LAN use
Attendee regos	Exported for lookup and imported when state changes.
Dealers Den regos	Exported and imported for dealer onsite operations.
Check-in records	Created or changed during LAN check-in.
Inclusion claims	Changed when fulfillment is recorded.
Inventory stock rows	Changed by offline inventory operation.
POS transactions	Created by offline sales operation.
POS transaction items	Item lines for offline sales.
HR roster entries	Changed by staff roster operation.
Shift tracking state	Changed by live shift operation.
Snapshot audit entries	Created on export and import.