The problem this fixes
Most clubs collect the same information three or four times a year. A paper pack in September, another one before Easter, a fresh medical form at the start of the summer, and a scribbled note at the door when grandma is collecting on Thursday.
The parent resents it, the office keys it in twice, and the one detail that matters, the inhaler or the person who must not collect, is on a form in a folder rather than on the register.
The fix is a single registration held against the child, completed once online, reused by every future booking, and edited by the parent when something changes.
1. Separate registration from booking
These are two different jobs and putting them in one form breaks both.
Booking is short: pick the days, pay, done. Registration is long: medical, dietary, emergency contacts, permissions, collection arrangements.
Make the booking flow ask only for what it needs to sell a place, then require registration to be complete before the first session. Your platform triggers it, the confirmation email links to it, and a reminder chases anyone who has not finished it by the week before.
2. Write the field list once
Work out what you actually need, and nothing more. A workable set for a club:
Child. Name, date of birth, school and year group, home address, photograph if you use one on the register.
Contacts. Parent or carer names, relationship, mobile, email, and at least one emergency contact who is not the first parent.
Medical. Doctor's practice, allergies, medical conditions, medication held at club and who may administer it, dietary requirements, and anything about the child that helps staff care for them well.
Collection. Who is authorised to collect, a password or code for anyone not on the list, whether the child may walk home alone and from what age, and any court order or arrangement staff must know about.
Permissions. Photographs and social media, off-site walks and trips, sun cream and first aid, and emergency medical treatment.
Declaration. Behaviour policy, fees and cancellation terms, the privacy notice, and a signature with a date.
3. Ask the sensitive questions carefully
Medical and safeguarding information is special category data in most privacy regimes, and collection arrangements can be genuinely delicate. Two rules follow.
Ask for it inside your booking platform, where it is stored against the child record with access control, rather than in a website form that emails a copy to a shared inbox.
And say on the form why you are asking, who sees it, how long you keep it, and who to contact to change or delete it. That is a short paragraph, not a legal essay, and it belongs next to the questions rather than only in a policy page.
4. Set what is required and what is optional
Every required field costs completed registrations. Be strict about the safety-critical ones, medical, emergency contact, collection, permissions, and let the rest be optional.
Where the platform allows conditional questions, use them. Only ask which medication is held if the parent has said the child has a condition. A form that shortens itself gets finished on a phone in a school playground.
5. Make renewal an update, not a retype
Once a year, and before any new holiday programme, ask parents to confirm the registration rather than complete it again. Prefill everything, ask them to check it, and record the date they confirmed.
That is the difference between a five minute annual task and a form abandoned halfway. It also gives you a defensible record of when each detail was last checked, which is exactly what an inspector or an insurer asks about.
6. Get the pick-up change route right
The most common real-world variation is a one-off change of collector. Give it a named route rather than leaving it to a text to a staff member's personal phone.
A short form on the site or in the app, submitted by the registered parent, with the collector's name and the password, arriving somewhere staff will see it before the end of the session. Publish the deadline for same-day changes and what you do if nobody has told you, which is that the child is not released.
7. Put registration on the website as a page, not a PDF
The registration page explains what will be asked, how long it takes, that it only has to be done once, and what happens next. Then one button into the platform.
A downloadable PDF pack is the thing you are replacing. If you have to keep a paper route for a handful of families, keep it, but do not let it be the default the website offers.
8. Test the whole route, twice
Register a test child on a phone, on mobile data, and again from an in-app browser. Check that the record appears on the register, that the medical note is visible to the staff member running the session, and that a second booking for the same child does not ask for any of it again.
Then delete the test child and confirm it is actually gone.
Where this sits
Registration and consent collected once and reused for every booking is one of the six things we build into an after-school and holiday club website, alongside the programme pages and the fees and funding page, and the same pattern runs through our other childcare websites. Packages are on pricing. This is orientation rather than legal advice; your regulator and your insurer set the record-keeping you must meet, and the website's job is to make meeting it take five minutes instead of a folder.