Accountability and Data Safety

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, Accountability and Data Safety narrows that work to why EMS LAN files, devices, audit history, and reconciliation carry serious responsibility. 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 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-history?id=:eventId.
• Records or contracts involved: Snapshot files, Audit history, and Attendee 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 Accountability and Data Safety.
2. Connect the idea to one real screen or source: Use /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 Snapshot files, Audit history, and Attendee 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 before giving anyone a LAN file or device.

1. Step 1 - Name the real-world problem. Confirm the event, export time, file owner, device owner, and import owner. This names who is responsible.
2. Step 2 - Connect the idea to event records. Check what data the LAN flow contains: attendees, staff, dealers, inventory, POS, check-in, and audit. This explains the privacy risk.
3. Step 3 - Decide what the operator should do differently. Give the file only to approved LAN operators and only through the approved handoff method. This limits copying.
4. Step 4 - Find the risk this concept prevents. Ask what happens if the file is lost, stale, copied, or imported wrong. This prepares the escalation path.
5. Step 5 - Write down the proof needed later. Confirm LAN Sync History after export and import. This proves the dashboard has an audit trail.
6. Step 6 - Move from concept to workflow. Delete, archive, or retain local files according to policy after reconciliation. This closes the data exposure window.

Accountability questions

1. Question 1. Who exported the file? Answer this before handing it to LAN operators.
2. Question 2. Which device used the file? Answer this before event-day operation begins.
3. Question 3. Who imports the returned file? Answer this before the LAN operating window opens.
4. Question 4. Who reconciles counts? Answer this before closeout.
5. Question 5. What happens if the file is lost or copied? Answer this before the file leaves the dashboard operator.

Why this matters

EMS LAN changes can affect real entry access, inclusion claims, staff shift records, inventory counts, POS records, and finance follow-up. Future event leads need to understand what happened without relying on memory.