How to Build an Admissions Enquiry Form That Captures the Right Information

An admissions enquiry form is often the first structured interaction a prospective student or parent has with your institution. Forms that ask for too much push people away before they have engaged. Forms that ask for too little leave your admissions team chasing basic information by email before they can qualify the lead. The goal is a form that captures exactly what your team needs to start a meaningful conversation and creates as little friction as possible for the person filling it in.

What information does an admissions team actually need at first contact?

The answer varies by institution, but the principle is the same: collect what you need to route the enquiry and initiate a useful follow-up. At first contact, that typically means name and a way to reach the person: email address and the programme they are enquiring about. Nothing more.

The most common mistake is treating the enquiry form like an application form. Programme preferences and funding sources are useful data points, but asking for them at the first touchpoint reduces completion rates and signals to the prospective student that the process will be demanding before they have seen any value.

What fields belong on the form?

First name and last name (required): Keep these as separate fields for CRM purposes. A single “full name” field creates segmentation and personalisation problems downstream.
Email address (required): The primary contact channel for most follow-up sequences. Validate the format on the form to reduce typos entering your CRM.
Phone number (required or optional depending on your follow-up model): Required if your team follows up by call. Optional if your nurture is email-first. Do not make it required if you will not actually call.
Programme of interest (required, dropdown): A dropdown list of your programmes is more CRM-friendly than a free-text field. It allows automatic routing and pipeline assignment in HubSpot or your admissions CRM.
Intake period (optional, dropdown): Useful for prioritising hot leads (those enquiring for the next intake) versus early-stage enquiries. Keep it simple: “Next intake”, “6 months”, “12 months or more”, “Not sure”.
Country of residence (optional, dropdown or auto-detect): Relevant for institutions with international programmes, visa guidance, or language support. Helps route to the right team.
How did you hear about us? (optional): A short dropdown for attribution purposes. Keep the list under eight options or leave it off entirely if you have better attribution data from UTM parameters.
Message or question (optional, short text): A free-text field that invites the prospective student to say something specific. Not required, but when filled in it gives your admissions team a starting point for a personalised first response.

What fields should stay off the enquiry form?

Avoid adding fields that belong later in the admissions process. Academic qualifications and financial declarations are application-stage data, not enquiry-stage data. The same applies to passport details and employer information. Including them on a first-contact form increases form length without improving your ability to follow up effectively.

Also avoid asking the same information twice. If your CRM auto-fills the contact’s country from their IP address or from a UTM parameter, do not ask for it again on the form.

How does the form connect to your CRM?

A well-designed enquiry form feeds directly into your admissions CRM as a new contact record, with the form fields mapped to the right CRM properties. In HubSpot, each dropdown value becomes a contact property that can trigger workflows and assign the contact to a pipeline stage automatically.

For this to work cleanly, your form fields need to match your CRM property structure before you build the form. Designing the form and the CRM mapping at the same time saves significant cleanup later. See what is an enrollment CRM and the admissions CRM guide for more on how the data flows from form submission to pipeline management.

How do you reduce abandonment on admissions enquiry forms?

Form length is the primary driver of abandonment. Every field you add reduces completion rate. A form with five to seven fields consistently outperforms one with twelve or more, all else being equal.

Progress indicators help for multi-step forms, but a single-page enquiry form rarely needs one. More impactful is the placement and context of the form: a form embedded below a relevant programme page converts better than one on a generic “contact us” page, because the visitor already has context for why they are submitting their details.

On mobile, tap-friendly inputs matter. Dropdown menus are easier on mobile than free-text fields. Phone number fields should use `type=”tel”` to trigger the numeric keyboard. Date fields should use a date picker rather than three separate dropdowns.

What happens after the form submits?

The thank-you page or confirmation message is often overlooked. It should tell the prospective student what happens next: who will contact them and within what timeframe. “Our admissions team will be in touch within one business day” sets a clear expectation. “Thank you for your enquiry” does not.

In your CRM, the submission should trigger an automated acknowledgement email. Depending on the programme field, the relevant admissions officer should also be notified. The contact should enter the appropriate pipeline stage so nothing falls through the gaps.

Frequently asked questions

Should the enquiry form ask for the student’s academic level or grades?

Only if your admissions team uses this information to qualify the lead at the enquiry stage. If minimum grade requirements exist and an unqualified enquiry would not proceed past a first conversation, a simple qualifying question (for example, “Do you meet the minimum entry requirements?”) is reasonable. Full academic transcripts belong on the application form, not the enquiry form.

How many form fields is too many?

There is no universal number, but five to seven fields is a reasonable target for a first-contact enquiry form. Each additional required field adds friction. If your completion rate is low and your form has more than eight required fields, removing one or two fields and observing the change in completion rate is a worthwhile test.

Can the same form work for both domestic and international enquiries?

In most cases, yes. A well-structured form with a country field and a programme dropdown can serve both audiences. If the follow-up process differs significantly (for example, visa guidance for international students), use the country field to trigger the appropriate CRM workflow rather than building separate forms. Separate forms for each audience create maintenance overhead and can result in inconsistent data capture.

To see how a form like this connects to a full admissions CRM workflow, visit our HubSpot for schools page or talk to us about how to set it up.