Check-In Records Reconciliation

Reconcile Before Trusting The Result

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, Check-In Records Reconciliation narrows that work to how to reconcile attendee regos, Dealers Den regos, check-in records, and inclusion claims after LAN import. Because this is a reconciliation 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 Must Match

This page is for proving that two views of the event agree. Read it after imports, exports, offline operation, or manual fixes so the dashboard can be trusted again. The intended readers are Reconciliation operators and Check-in 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/check-in?id=:eventId and /rego/events/manage/inclusion-claim?id=:eventId.
• Records or contracts involved: Attendee regos, Dealers Den regos, Check-in records, and Inclusion claims.
• 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.

Compare Counts, Records, And Proof

1. Choose the two sources being compared: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Check-In Records Reconciliation.
2. Check counts before individual records: Use /rego/events/manage/check-in?id=:eventId and /rego/events/manage/inclusion-claim?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Investigate every mismatch before closing it: Keep Attendee regos, Dealers Den regos, Check-in records, and Inclusion claims in view so the work stays tied to the records or contracts it can affect.
4. Save the summary and owner for unresolved items: 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.

Reconciliation Is Credible 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 after a LAN import touched check-in or claim records.

1. Step 1 - Tie the check to one import. Confirm the latest import entry belongs to the correct event. This anchors reconciliation to one import.
2. Step 2 - Gather real-world notes. Read applied counts for regos, Dealers Den regos, check-in records, and claims. This tells you which lists to inspect.
3. Step 3 - Compare imported records with physical evidence. Open check-in and claim surfaces, then compare totals to onsite handoff notes. This verifies attendee-facing records.
4. Step 4 - Explain every mismatch. Investigate duplicate check-ins, missing claims, cancelled attendees, unpaid records, and dealer mismatches. This catches access and fulfillment errors.
5. Step 5 - Mark the dashboard trustworthy or unresolved. Record final totals and unresolved records in closeout notes. This proves review happened.
6. Step 6 - Store the reconciliation note for audit. Escalate unresolved access or fulfillment issues to the event lead. This prevents silent attendee-impacting errors.

Proof checklist

1. Checkpoint 1. Import summary lists check-in changes. Use it to confirm the work is still on the right path.
2. Checkpoint 2. Dashboard check-in totals match onsite totals or explain the difference. Use it to confirm the work is still on the right path.
3. Checkpoint 3. Inclusion claims match fulfillment handoff. Use it to confirm the work is still on the right path.
4. Checkpoint 4. Dealer rego state is checked if Dealers Den was operated offline. Use it to confirm the work is still on the right path.