Check-In and Offline Snapshots

Use This Dashboard Area Safely

Use this guide when event setup, attendee operations, staff work, payment-adjacent tasks, public pages, or closeout records need a controlled path. In this guide, Check-In and Offline Snapshots narrows that work to check-in workspace, registrants, regos, scanner-safe state, offline snapshots, and snapshot history. Because this is a surfaces page, read it as part of the Event Management learning path rather than as an isolated checklist.

Event records become real-world instructions: what attendees see, what staff do, what money or inventory must reconcile, and what future organizers inherit. 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 leads 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/check-in?id=:eventId, /rego/events/manage/registrants?id=:eventId, /rego/events/manage/regos?id=:eventId, /rego/events/manage/offline-snapshot?id=:eventId, and /rego/events/manage/offline-snapshot-history?id=:eventId.
• Records or contracts involved: Registrations, Check-in records, and Offline snapshots.
• Main care point: Watch for changing one part of the event without checking attendees, staff, finance, communications, public information, and closeout records.
• Proof worth keeping: event ID, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff.

Read The Screen From Top To Bottom

1. Confirm you are on the right event, report, route, or file: Begin by naming the Event Management situation, the owner, and the exact item involved in Check-In and Offline Snapshots.
2. Read the current state before changing it: Use /rego/events/manage/check-in?id=:eventId, /rego/events/manage/registrants?id=:eventId, /rego/events/manage/regos?id=:eventId, /rego/events/manage/offline-snapshot?id=:eventId, and /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. Use the smallest action that matches the task: Keep Registrations, Check-in records, and Offline snapshots 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, dashboard state, public page, attendee record, payment or refund state, check-in count, roster note, export, and reviewer signoff so the next operator can see what changed and why it was safe to continue.

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 attendees, staff, money, public pages, communications, and post-event records.
3. Proof is findable: The handoff points to evidence that the next operator can see what changed and why it was safe to continue.

End-to-end operator runbook

Use this numbered runbook when you need to operate this area without getting stuck. Read the purpose of each step, do the action in order, and use the final sentence as the checkpoint before continuing.

1. Step 1 - Anchor the work to one event. Open Check-In for the correct event and confirm live data loads. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Before event day, generate or refresh offline snapshots only when policy allows and store them securely. Pause here and confirm the attendee, staff, money, and public-page impact still matches the event plan.
3. Step 3 - Change only the intended event setting or record. Test scanner devices, search behavior, warning states, and offline/LAN fallback before attendees arrive. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. During check-in, verify identity and registration state before marking an attendee as checked in. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. If online service fails, switch to the approved offline process and keep one lead responsible for reconciling later. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. After the event, compare offline records, live check-in totals, and snapshot history, then remove old exports according to policy. This leaves a handoff trail another operator can understand.

Purpose

These surfaces help staff verify attendees, check people in, review registration details, and prepare for weak internet conditions.

What to verify before event day

• Check-in route loads for the correct event.
• Scanner/search workflow works.
• Registrants and regos show expected state.
• Offline snapshot export is signed and downloadable.
• Snapshot history is readable.
• Staff know what to do if internet fails.

Common mistakes

• Exporting snapshots too early and using stale data.
• Not syncing check-in changes after offline use.
• Letting unauthorized staff view full attendee details.
• Ignoring payment warnings at the door.

Certification notes

TASK003 specifically certified offline snapshot signing in production after SUPABASE_JWT_SECRET was configured on the hosted API.