Export LAN Snapshot

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, Export LAN Snapshot narrows that work to numbered workflow for exporting ZIP or GZIP EMS LAN snapshots safely. 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 LAN export 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 snapshot export and Snapshot audit history.
• 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 Export LAN Snapshot.
2. Read the visible state before editing anything: 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. Make only the change this guide describes: Keep Offline snapshot export and Snapshot audit history 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 to export a controlled LAN snapshot.

1. Step 1 - Start from the live event record. Open /rego/events/manage/offline-snapshot?id=:eventId and confirm the event ID and event name. This prevents exporting the wrong event.
2. Step 2 - Gather prerequisites before touching files or devices. Confirm readiness, file owner, device owner, and whether ZIP or GZIP is required. This makes the file handoff deliberate.
3. Step 3 - Carry out the operator action slowly. Select Download LAN snapshot ZIP for the standard LAN app or Download GZIP JSON only when that format is required. This creates the export file.
4. Step 4 - Watch for side effects on people and records. Label the file with event name, event ID, export time, and format before handoff. This avoids stale or anonymous files.
5. Step 5 - Verify the result in the right place. Open LAN Sync History and confirm an export entry appears with actor, format, and timestamp. This proves the dashboard recorded the export.
6. Step 6 - Hand off the result with context. Hand the file only to the approved LAN operator and record where it went. This closes the export step.

Format choice

Format	Use when	Notes
ZIP	Standard offline LAN app handoff.	Preferred operator format.
GZIP JSON	Support lead or integration workflow requires it.	More technical and easier to mishandle.

Common mistakes

• Exporting from the wrong event tab.
• Keeping multiple files with similar names.
• Handing the file to a person who is not the LAN operator.
• Forgetting to check sync history after export.