Test registration form: what happens at capacity

A registration form holds two counts that can disagree: the places left when the page loaded, and the places left when the form is sent. A stranger can spend several minutes typing names and dates while someone else takes the last place. The form then refuses them at submit, often with a message at the top of the page, and the typed entries may be cleared. The same form can block a parent who uses one email for two children, because its duplicate check looks at the address and not the person. The owner, registering once with their own email, never reaches either rule.

• Read the places left when the page loads, then again just before you submit. Does the count change, and does the form say so?
• Enter two attendees under one email. Does the form accept the second one, or say the email is already used?
• Tap the words beside the consent box on a phone. Does the box tick, or only the small square?
• Leave one attendee's name blank on purpose. Does the error appear beside that field, or only at the top of the page?

The places shown on the page are a copy taken when it loaded. The real count sits on the server, and it changes every time someone else completes a registration. A page that stays open for ten minutes while a parent types can show a place that is already gone. The form then accepts every field and fails at the end, which is the worst moment for a visitor to learn the session is full.

Test it by reading the count at two moments. Load the page, note the places left, then fill in the form slowly and read the count again before you submit. If the form does not refresh, or it refreshes and says nothing, the count is the cause. A fix that checks capacity on submit and keeps the entries on the screen turns a dead end into a clear message.

A duplicate check keyed only on email assumes one person per address. Families, caregivers and group leaders break that assumption often, so the second person is refused with a message such as already registered. The message gives no path forward, and the visitor does not know whether the first registration is theirs or someone else's. A parent who sees a duplicate message needs a path forward, not only a refusal.

Run the test with two attendees under one address, and read the exact words the form uses. Then compare them with what you want a parent to do next: add a second person, use a different address, or call. A rule that checks name and date of birth alongside the email stops a family from being refused for sharing an inbox.

Two small things stop a registration without any clear sign. A consent box whose words are not linked to its square does not tick when the visitor taps the text, and on a phone the tap is the only action they take. A validation message placed at the top of a long form can sit out of view, so the visitor sees an empty field and no reason.

Check both by hand. Tap the consent text, not the box, and see whether the box changes. Leave one required field empty and scroll the page to see where the error is. The confirmation screen needs the same check: a place described as pending is not a confirmed place, and the visitor should be told which one they have. Read the words in full, since a short label like Pending is easy to skim past.

Every new waiver, age rule or capacity change can refuse a registration the form accepted last month. Run a two-person registration after each change, on a phone and a laptop, and again before each new session opens. Use made-up names and an address you control, never a real child's details, and keep them out of any preview others can open.