A CRM helps prep school admissions teams track every enquiry and maintain consistent contact with prospective families, without relying on spreadsheets or shared email inboxes. This guide covers how prep schools typically use a CRM and what to prioritise when getting started.
Connect your website enquiry form to the CRM so every new contact enters your pipeline automatically. Include fields for the child’s age and current school year. Add a field for preferred entry date too.
Create stages for the process: Enquiry received, then Assessment scheduled and Assessment complete. After that come Offer made and Place confirmed. Waitlisted is the final stage for families without a current place. Every prospect sits in exactly one stage.
Set a workflow to send a confirmation email within minutes of a new enquiry. Follow up at day 3 and day 7 if no response. This keeps the school present without manual chasing.
Record school visits and email threads in the CRM. Call notes go in the same record. Any team member can then see the full history without asking a colleague.
Track enquiry volume by month and the conversion rate from enquiry to offer. Offer-to-enrolment rate is also worth watching. Review these before each intake to spot patterns early.
Why do prep schools need a CRM for admissions?
Prep school admissions run on relationships and timing. A family researching a school in January may not be ready to apply until March. If the school has no system to stay in touch in the intervening weeks, that family drifts to a school that does.
A spreadsheet tracks names and dates but cannot send automatic follow-ups or alert a staff member when a family goes quiet. It also cannot give the Head of Admissions a real-time view of where every application stands. A CRM does all of those things from one place.
Most prep schools also manage multiple intake cohorts at once: one set of families applying for this September, another group in early conversations about the following year. A CRM separates these without confusion and makes it possible to communicate differently with each group.
What should a prep school admissions pipeline look like in a CRM?
The pipeline reflects the school’s actual admissions steps. A typical prep school pipeline might include these stages:
- Enquiry received: family has made contact but not yet visited
- Open day or tour booked: family has a visit scheduled
- Visit completed: family has seen the school
- Assessment or interview scheduled: child has a formal assessment date
- Assessment completed: result pending
- Offer made: place offered, waiting for acceptance
- Place confirmed: deposit received, child enrolled
- Waitlisted: no current place but on the waiting list
Each stage should have a clear next action. If a family has completed a visit but no assessment is scheduled, the admissions team should see that and act. A well-configured CRM makes this visible without manual checking. For a deeper look at pipeline structure, see our guide to setting up an admissions pipeline.
How does a CRM handle communication with prospective families?
A CRM for admissions tracks every touchpoint with a family in a single record. That includes emails sent and received. Phone calls logged and notes from school visits also appear there. Shared documents also appear in the record. When a family calls about their application, any team member can open the record and see the full context immediately.
Automated sequences do the routine contact. A family that submits an enquiry form receives a confirmation email in seconds. Three days later, a follow-up message goes out. Seven days after that, a reminder about the next open day is sent automatically. These go out automatically, regardless of how many enquiries came in that day or whether the admissions officer is in a meeting.
For families further along in the process, automation gives way to personal contact. An offer letter or a call to discuss a waitlist position should come from a person rather than a workflow.
What should prep schools look for in an admissions CRM?
The most important feature is a clear pipeline view that shows every active enquiry and where each one stands. Without that, the team falls back on memory or a spreadsheet. Both create gaps.
Next, look for automation that works without technical expertise. Admissions coordinators are not developers. If setting up a follow-up sequence requires writing code or building complex integrations, it will not get used.
Integration with your website contact form is essential. If enquiries have to be manually copied into the CRM, the system breaks every time someone forgets to do it. The connection between form submission and CRM record should be automatic.
For schools using HubSpot, the admissions CRM setup is typically completed in a few days. The pipeline and automation sequences can be configured without custom development. Reporting is also included.
How does a CRM help with open day management?
Open days are a critical conversion point for prep schools. A CRM lets you send targeted invitations to families at the enquiry or visit stages, track who registers and send automated reminders. After the event, follow up with non-attendees.
After an open day, the CRM can automatically move attendees to the next pipeline stage and trigger a personalised follow-up sequence. Non-attendees can receive a different message: a link to a virtual tour or an invitation to a smaller group visit.
Over time, tracking open day attendance in the CRM lets you see what percentage of attendees convert to applications. That data is useful when planning the number of open days and the size of each one.
Can a CRM help with sibling applications?
Yes. Most CRM platforms let you link contact records to a family record or company record. This means a family with two children can have separate child records that are connected to the same parent contact. The admissions team can see that a sibling is already enrolled and flag the new application for priority review. Parent communication for both children runs from a single record.
Without a CRM, sibling applications are typically managed by memory or a note in the spreadsheet. A CRM makes the connection explicit and ensures it is not missed during a busy intake period.
Frequently asked questions
Do prep schools need a school-specific CRM or will a general CRM work?
A general CRM like HubSpot works well for prep school admissions. The pipeline and automation workflows can be configured for admissions without needing school-specific software. Reporting is built in. Talk to us about how other schools have set it up.
How long does it take to set up an admissions CRM?
A basic setup covering pipeline stages and enquiry form integration typically takes 3-5 working days. The automated welcome sequence is usually configured at the same time. More complex setups with multiple intake cohorts or custom reporting take longer.
What data should a prep school track in its CRM?
Key data points include enquiry source and intended entry year. Open day attendance, assessment date and offer status should also be recorded. The final enrolment decision completes the record. These feed the reports that help the school plan each intake.
Can a CRM handle enquiries from international families?
Yes. A CRM can tag contacts by country and send localised email sequences. International enquiries can also be routed to a specific team member if the school handles them separately. Response time is especially important for international families, who often apply to several schools simultaneously.
Want to improve your admissions and enrollment process?
Talk to us