School CRM: how to turn more applications into enrolments

When a family is choosing a school, they write to several at once. They ask for information, visit two or three and decide within a few weeks. The school that answers quickly, remembers what was said on the visit and follows up afterwards is usually the one that enrols them.

Applications are rarely lost for lack of interest. They get lost between inboxes, phone notes and a spreadsheet that only its author understands. A school CRM keeps every application in one place, with someone responsible for it and a dated next step.

What a school CRM is

It is the tool a school uses to record and follow every interested family, from the first enquiry to enrolment. It does five things:

• Records each application with its details and the channel it came through: the website, a call, an email, a visit or an open day.
• Shows the stage each family is at and what is needed for them to move on.
• Assigns an owner, so every application has someone looking after it.
• Keeps the history: calls, emails, visits and stage changes, each with its date.
• Measures conversion: how many enquiries become enrolments, by channel and by stage.

Why applications get lost without a CRM

The reasons repeat themselves in schools, nurseries and academies:

• The enquiry lands in the inbox of someone who is on holiday or off sick, and nobody else sees it.
• The family visits, but nobody calls them afterwards to answer questions or offer a place.
• The waiting list lives in a separate sheet and, when a place frees up, it is hard to tell whose turn it is.
• Management knows how many enrolments there are, but not where they come from or where the families who never enrol drop out.

During the admissions season, when the office is serving current families and new ones at the same time, these gaps show more.

The stages of the admissions process

The most common mistake is copying a sales funnel with ten stages that nobody updates. For a school, these are usually enough:

1. New application. The enquiry has arrived and nobody has been in touch yet.
2. Contacted. Someone on the team has replied and answered the first questions.
3. Visit or interview. The family has visited the school or has a visit booked.
4. Place offered. They have been offered a place in a year group and are deciding.
5. Enrolment confirmed. The family has accepted and registration begins.

If the school runs a waiting list or asks for a deposit, each should be a stage of its own. You also need a clear exit, closed, with the reason: chose another school, moved away, no place available. That reason is what later explains why families are lost.

What matters is that every step has a rule the whole team reads the same way. "Contacted" means someone has spoken to the family, not that an automatic email went out.

The form is the front door

If the form on your website is long or confusing, many families never finish it. A few guidelines that work:

• Ask for the minimum on the first screen: name, phone or email, year group of interest and how they heard about the school.
• Leave documents for later, once the family has decided to go ahead.
• Confirm receipt straight away, with a message that says what happens next and when.
• Use one form per campaign: new school year, summer camp, open day. That way you know which action brings each application.

Each form should create the application directly in the CRM. If it arrives by email and someone copies it across, the errors and delays come back.

Owners and response times

An application without an owner ends up without a reply. Assign each one to a member of the team as soon as it arrives and set an internal deadline for first contact, for example two working days.

Once a week, review the applications that have not moved for more than seven days. It is a short meeting: for each one, you decide the next step or close it with a reason.

What to measure every week

Four figures show almost everything:

• New applications by channel. They tell you which actions attract families: the website, open days, recommendations.
• Time to first contact. If it rises, families are waiting too long while other schools reply.
• Stalled applications. Those that have not changed stage for more than a week.
• Conversion from visit to enrolment. If it is low, the problem is in the visit or the follow-up, not in recruitment.

Look at the figures by year group or stage. Nursery and the first year of secondary often move at different speeds.

From CRM to enrolment without retyping

When a family confirms a place, their details need to reach the student record, billing and the family app. If the CRM is a separate tool, the office types the same data again into the management system, and that is where mistakes in names, year groups and bank details appear.

That is why the CRM should be part of the same system the school uses to enrol, invoice and communicate. If you charge a deposit, the bill should come from that same record.

Common mistakes when setting it up

• Too many stages. If nobody knows where to put a family, the board stops reflecting reality.
• Applications without an owner. The whole team can see them and nobody calls.
• Importing the history without cleaning it. Duplicates and applications from three years ago distort the figures from day one.
• Measuring only the number of enquiries. What matters is how many become enrolments and where the rest stop.
• Designing it without the office. They are the ones who will use it every day; if the process does not fit their work, they will go back to the spreadsheet.

For the next step, enrolment itself, there is a guide on moving enrolment online step by step.

How it works in Edena

Edena's school CRM is part of the same platform as student records, billing and the family app:

• Enquiry forms built with a visual editor and published as a link on the school website or in campaign emails.
• Starting stages New, Contacted, Qualified, Proposal, Negotiation and Won, which you can rename or adjust to your process.
• The source of each application (website, phone, email, visit or form) and an assigned owner.
• Activity history with the date and time of every stage change, contact or action.
• Recruitment reports: how many applications arrive, how many move through each stage and each owner's results.
• When an application is marked Won, the family's details are ready for the student's registration. With the Automation module, registration can happen automatically once enrolment is confirmed.

For schools, nurseries and education groups it is a module you switch on over the base platform. For academies it is included in the Finance Pack and the Academy 360 Pack.

Conclusion

A school CRM does not bring in families on its own, but it stops you losing the ones who have already asked. With a few well-defined stages, an owner for every application and a weekly review of the ones that have stalled, the school knows which channel brings enrolments and where families slip away.

If you would like to see it with your own admissions process, book a 15-minute demo.