Registrations, Waitlist, Refunds, and Transfers

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, Registrations, Waitlist, Refunds, and Transfers narrows that work to registration operations for attendee records, waitlist, upgrades, refunds, transfers, and coupons. 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 Registration staff and Finance 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/regos?id=:eventId, /rego/events/manage/waitlist?id=:eventId, /rego/events/manage/upgrades?id=:eventId, /rego/events/manage/refunds?id=:eventId, /rego/events/manage/transfers?id=:eventId, and /rego/events/manage/attendee-coupons?id=:eventId.
• Records or contracts involved: Registrations, Waitlist entries, Refunds, Transfers, Upgrades, and Coupons.
• 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 Registrations, Waitlist, Refunds, and Transfers.
2. Read the current state before changing it: Use /rego/events/manage/regos?id=:eventId, /rego/events/manage/waitlist?id=:eventId, /rego/events/manage/upgrades?id=:eventId, /rego/events/manage/refunds?id=:eventId, /rego/events/manage/transfers?id=:eventId, and /rego/events/manage/attendee-coupons?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, Waitlist entries, Refunds, Transfers, Upgrades, and Coupons 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 the event registration, registrant, waitlist, upgrade, refund, or transfer surface for the correct event. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. Find the attendee or order by safe identifiers and confirm you have the right record before changing anything. 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. Read current payment, check-in, tier, add-on, inclusion, waitlist, and communication state. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Apply the needed action: approve, move from waitlist, upgrade, refund, transfer, cancel, or correct details. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Record the reason and check whether money, access, capacity, or attendee messages changed. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Save and verify the registration, payment/refund state, capacity counts, and attendee-facing result all agree. This leaves a handoff trail another operator can understand.

Purpose

These pages manage attendee changes after registration exists. They can affect access, money, capacity, and attendee expectations.

High-risk actions

• Refunds.
• Transfers.
• Upgrades.
• Waitlist promotions.
• Coupon creation or application.

Common mistakes

• Promoting waitlist entries without checking capacity.
• Refunding without settlement review.
• Transferring a registration without identity checks.
• Applying coupons that finance cannot explain later.
• Upgrading a rego without updating payment balance.

Verification

• Changes appear on the attendee record.
• Payment balance matches the action.
• Capacity counts remain correct.
• Staff can explain why the action happened.