The change that mattered
An admission enquiry form is the narrowest point in a school's entire funnel. Everything upstream — the site, the photography, the philosophy page, the local search work — exists to deliver a parent to it, and if it loses them there, all of that spend was wasted on someone who had already decided to enquire.
For Little Lumos, a Reggio Emilia-inspired preschool in Kakinada, we rebuilt the admission enquiry as ten questions completing in under thirty seconds. This is a teardown of that decision: what we kept, what we cut, and why. You can see the case study for the summary; this is the reasoning underneath it.
One caveat upfront, because it matters for how you read this. The honest claim is a measured completion time and a reduction in drop-off. We are not going to attach an invented percentage to it.
The starting position
The conventional school admission enquiry asks for everything the office will eventually need: child's full name, date of birth, gender, blood group, parents' full names, occupations, full postal address, both phone numbers, email, previous school, programme of interest, how you heard about us, and a free-text message.
Every field is individually defensible. The office genuinely needs all of it eventually. That is precisely the trap: the form gets designed around what the school needs at enrolment rather than what is needed to start a conversation, and the two are completely different problems.
On a phone, that form is roughly forty separate interactions with a keyboard, several of them requiring information the parent has to go and find.
The question we used instead
For every field, one test: is this needed to make the first follow-up contact competently?
Not "will we need it" — almost everything passes that. Not "is it useful". Only: can the office pick up the phone and have a good first conversation without it?
That test cut the form roughly in half in about twenty minutes, and it produced arguments worth having.
What we kept, and why
Child's first name. The first follow-up call should be about a named child, not "your enquiry".
Child's age. Not date of birth. Age determines programme eligibility, which is the first thing the office establishes. Date of birth is enrolment data and asking for it upfront reads as intrusive from a school you have not yet visited.
Programme of interest. Routes the enquiry and tells the office what the parent is imagining.
Parent's name. One parent, not both. You are calling one person.
Phone number. The primary channel, and for this audience it is also the WhatsApp number.
Email. For the prospectus and anything with an attachment.
Preferred start period. Term, not date. Distinguishes a parent enquiring for next month from one planning eighteen months out, and those get completely different conversations.
Locality. Not full address. Whether they are within the catchment, which affects transport and likelihood. Two taps rather than four fields.
How they heard about the school. The only field on the form serving the school rather than the parent, and it is optional. It pays for itself in marketing attribution.
A short optional message. Parents with a specific concern — a shy child, a dietary requirement, a mid-year move — will tell you, and that is the highest-value information on the form. Optional, and not first.
What we cut, and what happened to it
Full postal address. Needed at enrolment. Not needed to return a call. Replaced by locality.
Date of birth. Replaced by age. Collected at enrolment, when the parent has already chosen you and providing it feels routine rather than invasive.
Blood group and medical details. Genuinely important, entirely wrong for an enquiry form. It signals form-filling rather than conversation, and it is sensitive data you should not be collecting before there is a reason to.
Both parents' names and occupations. Occupation in particular reads as means-testing, whatever the intent.
Second phone number. One is enough to make a call.
Previous school. A good question for the visit, not for first contact.
None of this data disappeared. It moved to the point in the process where the parent has already decided and providing it is unremarkable. The form's job is to start a conversation; the conversation collects the rest.
The mechanics that made thirty seconds possible
Reducing fields is most of the win. Four implementation details did the rest.
Correct input types. A numeric keypad for the phone number, an email keyboard for email. Every mismatched keyboard costs seconds and causes typos that then cost the office a failed callback.
Selection instead of typing. Programme, start period and locality are all choices from a short list. Tapping is faster than typing and it eliminates the data cleanup of free-text variants.
One column, no surprises. Everything visible, nothing revealing itself as you go. On a form this short, a progress indicator adds ceremony without reducing effort.
Fast to load. A form that takes four seconds to appear has lost people before the field count mattered at all. This is where form design meets performance, and the two are usually owned by different people.
How to apply this to your own form
Do it in this order. It takes an afternoon.
- Open your form on a mid-range phone and complete it honestly. Time yourself. Do not use your own desktop and do not use autofill.
- List every field and apply the test. Is this needed to make the first follow-up contact competently? Be strict. The arguments this produces are the useful part.
- Move everything that failed to a later stage. It is not deleted, it is deferred.
- Convert what remains to selections wherever a short list exists.
- Fix the keyboards. Numeric for phone, email for email.
- Measure before and after. Completion rate and per-field abandonment. Without a baseline you are comparing a number to an impression, and every redesign feels like a success.
Point six is the one most often skipped and the only one that tells you whether any of it worked. Our conversion work always starts by instrumenting the current state, because the alternative is redesigning on instinct.
What happens after the form
A thirty-second form creates a new obligation, and it is worth being honest that this is where most of the benefit is actually won or lost.
The reason short forms work is that they move the effort from the parent to you. They have told you less, so the first call has to do more work — and it has to happen quickly, because the parent who enquired at nine in the evening is comparing three schools and the first competent callback tends to win.
Two things follow from that. The enquiry has to reach whoever calls, immediately, rather than sitting in an inbox somebody checks each morning. And the person calling needs the enquiry in front of them: name, age, programme, locality, and whatever the parent wrote in the optional message. That last field is where the real information usually is, and it should be the first thing the caller reads rather than the last.
This is the part schools most often under-build. A fast form feeding a slow follow-up process converts worse than a long form feeding a fast one, because the parent's experience is the total of both. When we scope this work we look at the whole path from submission to first contact, not the form in isolation — which is also why lead capture and routing usually comes up in the same conversation.
The objection worth taking seriously
The reasonable counter-argument is that a longer form filters out unserious enquiries, so the office spends less time on people who were never going to enrol.
This is true, and it is the wrong trade for most schools. A long form filters on willingness to fill in a long form, which correlates with patience and with having a laptop, and not at all with how good a fit the family is. You lose committed parents who were enquiring from a phone on a commute and keep the ones who happened to be at a desk.
If qualification is genuinely the problem, do it in the follow-up call, where a trained person can ask two questions and know more than twenty form fields would have told them. The form's job is to get you that call.
Why this generalises
The specifics are a preschool. The principle applies anywhere the form is the narrow point: clinic appointment requests, venue enquiries, quote requests on an industrial site.
The mistake is universal and it is organisational rather than technical. Forms are specified by the department that will use the data, so they collect what that department needs at the end of the process. The person filling it in is at the beginning, deciding whether to engage at all.
Ask what you need to have a good first conversation. Collect the rest during it. More on what we build for schools, or the case study for the short version.
