Capacity-limited events are a consistent pain point for school coordinators. The holiday show auditorium holds 300 people. There are 450 student families plus grandparents, siblings, and friends who all want to attend. Without a fair system, the result is a flood of calls and emails, frustrated parents, and a coordinator fielding complaints for weeks.
The good news: there is a system that works, and families generally accept it as fair when it's explained clearly.
Principle 1: Every student's immediate family gets baseline access
The starting point of any fair capacity system is a guaranteed base allocation for every student's household. Two tickets per student is the most common baseline — enough for two parents or guardians to attend together.
This guarantee should be communicated first and loudly, before anything else about the ticketing process. 'Every family will get at least 2 tickets' is the message that lands. The logistics of how come second.
Principle 2: Claim deadlines prevent speculative holding
A family might accept their 2 tickets even knowing they probably can't attend — 'just in case.' Without a claim deadline, those tickets are locked out of circulation indefinitely.
A 2-week claim deadline creates a natural pressure valve. Families who genuinely want to attend claim promptly. Families who are uncertain either decide yes or let the deadline pass, returning their allocation to the pool.
Communicate the claim deadline prominently and send a reminder 48 hours before it expires. After the deadline, unclaimed tickets go to the lottery pool.
Principle 3: Lottery for overflow, not first-come-first-served
Once the claim window closes, remaining capacity goes into a lottery. Any family — including those who already claimed their base tickets — can enter for additional seats.
Run the lottery at a specific announced time. Use a provably random method — SignUpSpree uses a Fisher-Yates cryptographic shuffle. Announce results within minutes of the draw.
Principle 4: Anti-fraud ticket display
Once tickets are claimed and assigned, forward security depends on the ticket technology. A printed or static QR code can be screenshot and shared. Dynamic HMAC-signed QR codes that rotate every 30 seconds cannot be screenshot-forwarded usefully — the code expires within 90 seconds.
For events where capacity genuinely matters (fire code limits, paid events), anti-screenshot ticket technology isn't optional. It's the difference between knowing your actual attendance and having no idea.
Communicating the system to parents
The system only feels fair if parents understand it before they encounter it. Send a clear, plain-language explanation at least 2 weeks before ticket distribution opens:
- •How many tickets each family is guaranteed
- •How long families have to claim them
- •What happens to unclaimed tickets
- •How the lottery works and when it runs
- •What winners receive and how they're notified
- •Transfer policy
Parents who understand the system before tickets open almost never complain about the outcome, even when they don't get extras. Complaints come from surprises, not from fair processes.
Set up the full allocation → claim → lottery system for your next event.
See ticketing features