Attendee and Dealer Rego

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, Attendee and Dealer Rego narrows that work to local LAN attendee registration and Dealers Den registration management. 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 Registration desk and Dealers Den 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: /admin/:eventId/attendee-rego and /admin/:eventId/dealers-den-rego.
• Records or contracts involved: Attendee registrations, Dealers Den registrations, Payment status, and Email follow-ups.
• 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 Attendee and Dealer Rego.
2. Read the current state before changing it: Use /admin/:eventId/attendee-rego and /admin/:eventId/dealers-den-rego 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 Attendee registrations, Dealers Den registrations, Payment status, and Email follow-ups 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 for local registration desk changes.

1. Step 1 - Open the exact screen for the event. Open Attendee Rego or Dealers Den Rego for the correct imported event. This prevents changing the wrong local record set.
2. Step 2 - Identify what the screen reads and writes. Search for the attendee or dealer, then read payment, status, package, notes, and check-in state before editing. This avoids blind changes.
3. Step 3 - Use one control at a time. Update payment status, dealer status, delete a dealer record only when authorized, or send/preview a local follow-up email. This changes local registration state.
4. Step 4 - Check who or what was affected. Confirm the change affects check-in, dealer access, payment handling, or support queues as expected. This catches downstream impact.
5. Step 5 - Confirm the screen and history agree. Reopen the row or detail and confirm the changed status appears. This proves the local state updated.
6. Step 6 - Leave notes another operator can follow. Tell check-in or Dealers Den staff about the change if it affects onsite access. This prevents desk confusion.

Local-only actions

Action	API family
Load attendee regos	GET /api/rego/event-regos/:eventId
Update payment status	PATCH /api/regos/:regoId/payment-status
Preview/send follow-up email	/api/regos/:regoId/email-preview and /email
Load dealer regos	GET /api/events/:eventId/dealers-den/regos
Update/delete dealer rego	Dealer status and delete endpoints.