Registrations

A registration belongs to a parent event and a hosting organization. Record when it arrived, how many places it requests, and its current status. A team arranging a competition showcase can use the same record for a participant group requesting several admissions or for an individual request. The quantity matters because one registration can consume more than one place.

Submitted requests require a decision before they are treated as approved. The Event Reviewer checks the request and event capacity, then records its outcome in the registration status and decision time. The status shows whether staff should continue processing it, reject it, or mark it completed. A check-in time gives the admission team a separate record of arrival; approval alone does not establish that anyone entered.

• Intake. Draft and Submitted separate an unfinished registration from one ready for review.
• Decision. Approved and Rejected show the review outcome, while decision time supports follow-up.
• Arrival. The check-in time lets staff compare expected attendance with actual event-day activity.

Choose which organization submits or owns each registration and how registration quantities are checked against event capacity. Decide whether the team collects an attendee reference on an admission line, and how that reference relates to a registration. Train reviewers to check the current event and registration revisions before deciding. Assign one person to resolve duplicate or changed requests before admission starts. Decide when a completed registration means the associated event work is finished, since a checked-in guest and a completed administrative record answer different questions.

Suppose a regional awards program receives a group registration for four people. The Registration Coordinator enters the quantity under the correct event and submits it. The Event Reviewer checks the event, capacity and relevant evidence, then records an approved or rejected status and the decision time. The coordinator sees the result in the registration workboard. On event day, the Admission Lead checks the approved request, records the arriving quantity on an admission line, and captures the check-in time. If only part of the group arrives, the admission history should reflect the actual admitted quantity rather than treating the approved registration quantity as attendance.

• Registrations awaiting decision — Open submitted requests with event, organization, quantity and revision.
• Registration workboard — Separate drafts, submitted requests, decisions and completed records.
• Approved registrations for check-in — Prepare the arrival list for the admission team.

Use registration and admission for the operating sequence and event planning and review for the event decision trail. Review the data model before importing registrations.