An approval queue, not a DM pile
Approve or decline slot requests in bulk instead of scrolling messages. When someone drops, the waitlist promotes itself and notifies the next player.
The DM problem
Sign-ups arrive as messages across three channels and two platforms. You copy names into a sheet. Someone asks whether they got in; you scroll back to check. Someone drops out an hour before start and you go looking for a replacement by hand. None of this is organising a tournament — it is transcription.
The queue
Requests land in one list with real states rather than a mental model: pending, approved, declined, waitlisted, withdrawn. You can see at a glance how many are waiting on you and how many slots remain.
- Bulk approve and bulk decline, for the common case where most requests are fine.
- Instant join when you want first-come-first-served — requests are confirmed automatically until slots run out.
- Skill tier and an experienced-organizers filter as pre-filters, so mismatched entrants are discouraged before they apply rather than declined afterwards.
- Solo and team requests in the same queue; a team request occupies the slots its roster needs.
- Participant export to CSV when you need the list somewhere else.
The waitlist is your attendance insurance
Amateur events lose entrants between registration and start; that is normal and not worth fighting. What is worth fixing is having to notice and respond to it manually.
When a confirmed player withdraws or is removed, the next player on the waitlist is promoted automatically and notified. You do not have to be watching, and you do not have to remember who asked first.
Overselling is structurally impossibleThe slot count is changed in exactly one place in the codebase, always under a database row lock. Two organizers approving the last slot at the same moment cannot both succeed — one of them gets the slot and the other gets told it is gone.
Common questions
- Can I approve everyone at once?
- Yes — bulk approve and bulk decline both work on a multi-selection. Or set the event to instant join and skip approval entirely.
- What happens when a confirmed player drops out?
- The next player on the waitlist is promoted automatically and notified. No action needed from you.
- Can two people take the same last slot?
- No. Slot changes happen under a row lock, so concurrent approvals cannot oversell an event.
Run the event, not the spreadsheet
One queue, bulk decisions, and a waitlist that manages itself.