Check-In and Claim

Use This Dashboard Area Safely

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 and Claim narrows that work to eMS LAN guide for check-in workspace and inclusion claim operation. Because this is a surfaces 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 The Screen Controls

This page explains a specific surface. Treat every button, field, filter, and table as a way to view or change real records, not just as a visual layout. The intended readers are Check-in operators and Fulfillment staff. 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: Check-in records and Inclusion claim 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.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the EMS LAN situation, the owner, and the exact item involved in Check-In and Claim.
2. Read the current state before changing it: 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. Use the smallest action that matches the task: Keep Check-in records and Inclusion claim records in view so the work stays tied to the records or contracts it can affect.
4. Check the list, detail view, history, or public page afterward: 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.

Before You Leave The Screen

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 check-in or claim runs under EMS LAN.

1. Step 1 - Open the exact screen for the event. Confirm the device is on the correct event and mode: check-in or claim. This prevents applying the wrong action.
2. Step 2 - Identify what the screen reads and writes. Check attendee identity, registration status, payment state, warnings, and claim eligibility. This protects access and fulfillment.
3. Step 3 - Use one control at a time. Mark check-in or claim only after the record matches the person in front of staff. This changes LAN-local attendance or fulfillment state.
4. Step 4 - Check who or what was affected. Stop for duplicates, unpaid records, cancelled records, refunded records, or already-claimed inclusions. This prevents incorrect entry or handoff.
5. Step 5 - Confirm the screen and history agree. Confirm the row shows the expected checked-in or claimed state before serving the next attendee. This catches immediate mistakes.
6. Step 6 - Leave notes another operator can follow. At shift handoff, report counts and unresolved warnings to the lead. This gives the next operator context.

Records changed

• Check-in records show who entered and when.
• Inclusion claim records show what was fulfilled.
• Import later updates the online dashboard with LAN-local changes.