The first time an event of yours fills up, it feels like pure success — until entry number seventeen arrives for sixteen places and you realise you now run a queue as well as a tournament. Oversubscription is a good problem, but it is still a problem, and the difference between goodwill and grievance is how openly you handle the list.
Every format has a natural capacity: courts × hours ÷ match length, translated into a bracket or group size that actually fits your day. Decide that number first, publish it on the registration page, and let sign-ups run past it into a visible waitlist. A cap announced after entries open always looks like favouritism, whatever the truth.
Withdrawals will come; your job is to make the promotion mechanical:
If your event charges an entry fee, never take payment from waitlisted players up front — collect at promotion, when a real slot exists. If a paid entrant withdraws in time, refund per your published policy and the promoted player's fee replaces theirs. One rule, no exceptions on the day.
A waitlisted player who knows their position and the odds is patient. Silence converts the same player into three emails a day. Show list positions, confirm changes automatically, and the queue manages its own expectations.
ScorePal supports entry limits with automatic waitlisting: when the cap is reached, new registrations queue in order, and a freed slot can be offered down the list in one click — with payment collected only when a place is real. Set your cap at scorepal.co and let the queue run itself.