Approval queue and waitlist — Registrations → Needs approval / Waitlisted

Who opens it: an organizer or Group Lead with a queue of sign-ups to vet, usually a few minutes at a time between other jobs.

What they came to do: decide on the people waiting — yes, or no with a reason — and know that anyone left waiting for a place will get one, in order, without anyone having to remember.

True when they leave: everyone approved is on their way to a ticket (or to paying for one), everyone rejected has a recorded reason, and the waitlist moves by itself as places free up.

Decisions already made

• The queue is a tab on Registrations, not its own page: it is the same list, filtered to what needs a decision, so everything else about a registration is one click away.
• Approving carries a registration on by default — confirmed with tickets when nothing is owed and nobody is waiting — and an event can switch that off. Rejecting always asks why.
• Bulk decisions go one registration at a time and say which ones could not be decided, rather than all-or-nothing.
• A Group Lead sees and decides only the registrations in their part of the organization.
• Waitlists are per day. A family waits together, and nobody gets a ticket or is asked to pay before they have a place.
• Promotion is automatic and in order; an organizer does not have to watch for cancellations.
• Registrants hear when they are approved, put on the waitlist and given a place; approvers hear when something is waiting for them. The words are the organizer's templates.

Open questions

• There is no "promote this person now" button for an organizer who wants to jump the line.
• A rejected registrant is not emailed.
• Imports do not check day capacity.