Registration review

Event Registrations hold the participant request, quantity, organization and linked event. A submitted registration is a request for a decision, with its revision retained for review. The Independent Reviewer records the choice and reason separately, which lets the team see exactly what was authorized before a registration is completed.

• Submission. The Event Owner checks the intended event and quantity before sending the registration for review. Submitted work waits in a dedicated view so it cannot be mistaken for a completed admission.
• Decision. The Independent Reviewer compares the submitted revision with capacity and evidence. An approval applies to that revision; a rejection sends the request out of the active fulfillment path.
• Completion. Admissions Lead completes the registration only after the reserved capacity and verified provider payment effects are persisted. Registration status and an admission scan describe different facts and should be checked together.

Agree who enters a participant request and who decides its submitted revision. Admissions Lead needs a way to check available event capacity and verified payment evidence separately. Rehearse a quantity change after approval: the prior decision cannot complete the revised request, and the reviewer must inspect the new submission.

A participant registers for an open weekend event. The Event Owner checks its linked event and requested quantity, then submits the registration. The Independent Reviewer records an approval for the submitted revision. Admissions Lead checks the capacity reservation and verified capture before marking the registration complete. If the quantity changes after the decision, the previous review cannot authorize the new request.

Admissions Lead can see the request status, quantity and linked event before reserving capacity. A reviewer decision belongs to the submitted revision. After a changed quantity, the team must review the new request and check capacity and capture evidence again before completion.

A completed registration records a different milestone from check-in. Admissions Lead can compare its requested quantity with reserved admission lines; Gate Staff then records the actual arrival. Keeping those steps separate helps the reviewer see whether an approved request was fulfilled and whether a guest was later admitted.

• Registrations to decide — Review submitted quantities and revisions for their linked events.
• Approved registrations — Check the approved request before reserving admission.

Follow Registration to admission for the decisions and evidence that carry this work forward. Review the data model for its record links and roles for access checks.