Registration Lifecycle

Follow The Record Over Time

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, Registration Lifecycle narrows that work to how attendee registration moves from selection to approval, payment, changes, check-in, cancellation, or archive. Because this is a lifecycles 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 Changes Across The Lifecycle

This page follows a record from one state to another. Read it as a timeline so handoffs, reversals, and closeout work stay understandable. The intended readers are Registration staff 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/regos?id=:eventId and /rego/events/manage/registrants?id=:eventId.
• Records or contracts involved: Registrations and Attendee records.
• 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.

Track Each State Change

1. Find the current state: Begin by naming the Event Management situation, the owner, and the exact item involved in Registration Lifecycle.
2. Read what must be true before the next state: Use /rego/events/manage/regos?id=:eventId and /rego/events/manage/registrants?id=:eventId to connect the words on the page to the screen, file, service route, or record that people actually use.
3. Watch for side effects when the state changes: Keep Registrations and Attendee records in view so the work stays tied to the records or contracts it can affect.
4. Keep the history clear for the next reviewer: 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.

The Lifecycle Is Clear When

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. Registration begins when an attendee enters the public event registration flow. This anchors the work to the correct scope before any record changes.
2. Step 2 - Read the operational context first. The attendee selects tier, add-ons, inclusions, group options, and required policy acknowledgements. 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. The system creates or updates registration and attendee records, then moves through payment, waitlist, pending, confirmed, cancelled, transferred, or refunded states. This keeps the event state understandable before another setting changes.
4. Step 4 - Check attendee, money, staff, and public impact. Operators review exceptions such as failed payments, duplicate records, waitlist moves, upgrades, transfers, and cancellations. The next operator should be able to see why this step was taken.
5. Step 5 - Verify the dashboard and public result. Check-in consumes the confirmed registration state and records attendance. Check the related event records before continuing.
6. Step 6 - Leave a clear event handoff. Closeout verifies every registration has a final status and no hidden money or access issue remains. This leaves a handoff trail another operator can understand.

Lifecycle overview

Stage	Meaning	Verify
Started	Attendee begins or submits registration.	Required fields exist.
Pending/review	Staff or payment still needs review.	Status and notes are clear.
Approved	Attendee can attend if other conditions are met.	Tier, balance, and policy acceptance are correct.
Changed	Upgrade, transfer, coupon, or edit changes the record.	Balance and audit trail make sense.
Checked in	Attendee arrives and is verified.	Check-in record exists.
Cancelled/refunded	Attendance no longer proceeds or money is returned.	Reason and payment effect are recorded.
Archived	Event is closed out.	No unresolved obligations remain.