Registrations

The Registration Coordinator records each participant request under a parent event and organization. A request carries its own revision, requested ticket quantity and dates for registration, decision and check-in. Submission freezes the revision after capacity and evidence checks. An Independent Reviewer decides that submitted scope; a later change needs another check before completion.

• Submit a request. Check the parent event, organization and requested quantity before moving Draft to Submitted.
• Decide independently. The reviewer uses the submitted revision and linked event evidence when approving or rejecting.
• Complete with effects. Approval is followed by persisted capacity and verified provider payment effects before a registration is Completed.

Decide which registration details coordinators capture before submission and who reviews them. Agree how to handle a rejected request, a changed quantity and a registration near the capacity limit. Test the same event with a valid request and a request whose quantity no longer fits.

A participant requests two places in an open workshop. The coordinator records the registration under the parent event and submits its current revision. An independent reviewer checks capacity and evidence, then records the decision for that revision. Approval alone does not complete the registration: persisted reservation and verified payment effects must also agree. A later edit calls for a fresh check.

Use a near-capacity request to separate the decisions. The reviewer can approve a submitted registration, but the Admission Steward still checks the actual reserved quantity before claiming places. Compare the registration’s ticket quantity with the selected event and its existing admission lines. If the request changes after submission, decide the new revision before completion. If payment evidence is uncertain, keep the provider outcome visible rather than treating the approval as a verified capture. This gives coordinators a clear reason to revisit a request and gives door staff a clear admission handoff.

• Submitted registrations — Requests waiting for review, with parent event, quantity and revision.
• Approved registrations — Decided requests that admission staff can compare with reservation and payment evidence.

• Event approval connects the draft and reviewer decision.
• Registration to admission follows the participant request and capacity.
• Event closeout reconciles admission and provider evidence.

Check the record definitions before importing active work.