Registration review

A registration belongs to an event and an organization. It carries a status, revision, quantity and dates for registration, decision and check-in. The Registration Coordinator prepares the record after the event opens registration. A separate Registration Reviewer decides on submitted scope. That division matters when capacity is tight or a payment event needs closer inspection.

The reviewer should inspect the parent event, its current capacity and the registration quantity before recording a decision. The decision record points to the event and identifies the source revision, reviewer, decision, time and reason. A registration can be approved or rejected after submission; a completed registration follows the later evidence and capacity checks. An approval is a human decision, while completion depends on persisted capacity and verified provider capture evidence.

• Intake. The coordinator prepares a draft registration under the selected event and operating organization.
• Independent decision. The reviewer records the decision and reason against the submitted revision.
• Completion. Operations checks admission scope and verified provider capture evidence before considering the registration complete.

Define who may submit registrations, who may review them and what evidence the reviewer checks. Agree how a rejected registration is handled before another submission. The reviewer should know whether quantity means one attendee or a group booking. Set a clear rule for comparing requested quantity with the event’s available capacity, especially while other registrations and admission lines are being processed.

Choose the authoritative payment provider connection and map its event identifier and reference into payment evidence. A verified flag should reflect a checked provider event, not a copied note. Registration approval and provider capture are different events; the team should review each in its own place.

Use an open conference with limited remaining capacity. Registration Coordinator creates a draft registration for an organization and quantity, then submits it. Registration Reviewer checks the event and the source revision, records an approval with a reason and returns the registration to operations. Admissions Lead can then reserve admission scope without treating the approval as an arrival. When a verified capture is recorded, operations checks the persisted capacity effect before completion.

Run a rejection case too. The reviewer records the reason and leaves the registration rejected. A second attempt should use a new, current revision rather than silently treating the old decision as approval. Confirm that another organization’s registration cannot be mistaken for this one simply because both belong to the same event.

• Registration review queue — Focus on submitted registrations awaiting a decision.
• Active registrations — Follow submitted, approved and completed records with quantity and check-in date.
• Registration status board — Compare draft, submitted, approved and rejected work by event.

See registration decision for the review path and admission for the later capacity and entry checks.