Event Overview and Lists

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, Event Overview and Lists narrows that work to how to use the Event Management entry routes, event list, registration list, and manage overview. 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 Event leads and Partner admins. 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, /rego/events, /rego/regos, and /rego/events/manage?id=:eventId.
• Records or contracts involved: Events and Registrations.
• 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 Event Overview and Lists.
2. Read the current state before changing it: Use /rego, /rego/events, /rego/regos, and /rego/events/manage?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 Events and Registrations 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 /rego or /rego/events and confirm you are in the right partner dashboard. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Use filters, search, and status indicators to find the correct event. 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. Open the manage page and confirm the event name and ID before making changes. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Check list warnings, empty states, unauthorized messages, and stale data before assuming an event is missing. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Return to the list after changes and confirm the event status, dates, or visibility updated as expected. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Use /rego/events/new only when you are creating a new event, not when you cannot find an existing one. This leaves a handoff trail another operator can understand.

Purpose

The overview and list routes help staff find events, open the correct event, and move into event-scoped operations.

Route	Use
/rego	Registration dashboard entry point.
/rego/events	Event list and event selection.
/rego/events/new	New event creation.
/rego/regos	Cross-event registration view.
/rego/events/manage?id=:eventId	Event-scoped management overview.

Common mistakes

• Opening a manage route without checking the event ID.
• Assuming a missing event means it does not exist instead of checking partner scope.
• Switching partner scope and trusting old visible data.
• Treating /rego/regos as an event-specific list when it may be cross-event.

Verification

• Event list loads for the correct partner.
• Manage overview links preserve the event ID.
• Missing, invalid, and unauthorized IDs show safe states.
• Browser back/forward does not leave stale event data.