Why Client-Side Checks Are Not Enough
Many form tools check the limit when the page loads: if places are available, the form is shown. The problem: minutes pass between loading the page and submitting. If others register in that time, the limit is long reached at submission – but the registration goes through anyway. For popular events with a fixed registration start, exactly this happens en masse: everyone loads the page at 10 a.m. sharp, everyone sees free places, everyone registers.
The Real Problem: Simultaneous Registrations
Even a server-side check can be flawed if implemented naively. The classic mistake: count first ("1 place left"), then save. If two registrations arrive almost simultaneously, both read "1 place left" – and both are saved. The result is an overbooking nobody notices until the start list is too long. The solution is an atomic check at database level: counting and reserving must be a single, uninterruptible step – for example via database transactions with locks or unique constraints on start numbers.
How It Worked at UNICON 22
For the unicycle triathlon at UNICON 22 – the Unicycling World Championships 2026 in Steyr – I built the registration application with a limit of 180 places, allocated in order of registration. The check ran server-side and atomically: each registration was validated and reserved against the current state within a transaction. In addition, the complete registration process was tested under realistic conditions before launch – including what participants see when the limit is reached exactly during their registration. Honesty in the error case is part of it: a clear "the limit has been reached" message is better than a confirmation that has to be withdrawn later.
What Event Organisers Should Look For
When selecting or commissioning a registration system, ask concretely: Is the limit enforced server-side? What happens with simultaneous registrations? Is there a tested handling of the "last place" edge case? And: has the process been played through completely before the registration start? A form tool without these guarantees may be fine for small, relaxed registrations – for limited places with a rush, it is a risk.
The experience in this article comes from working on the digital platform of UNICON 22. View the case study →
Does this match your situation?
Briefly describe your starting point – you will receive an honest assessment of whether and how your project can be implemented sensibly.
Get your project assessed