A Practical Admissions CRM Guide for International Schools

01

What is an admissions CRM?

An admissions CRM helps schools manage prospective families from initial enquiry through application, decision and enrolment.

It centralises family information, communications, tasks, admissions stages and conversion data. Unlike a form or spreadsheet, it connects each interaction to the right family, assigns responsibility, shows the next action and preserves context across the team.

02

Why do international schools need an admissions CRM?

A CRM becomes important when enquiries, communications and applications can no longer be managed reliably through shared inboxes, spreadsheets and disconnected forms.

Without a shared system, a website enquiry, WeChat conversation, campus visit and application may each live somewhere different. A well-implemented CRM makes good admissions practice visible and repeatable while giving leaders a more accurate view of demand and conversion.

03

Admissions CRM vs SIS: what is the difference?

The CRM manages the relationship before enrolment. The SIS manages the enrolled student's official record and ongoing school life.

The hand-off should happen at a defined point, with clear field ownership, update rules and failure handling.

04

How should a CRM support the admissions journey?

Each stage should be visible, have a clear next action and help families understand what happens next.

1. Website visit and enquiry

   Capture interest, campus, year level, timing, language and source without making the first form unnecessarily long.

2. Follow-up and qualification

   Give the team a clear owner, response target and complete communication history.

3. Campus visit or event

   Support bookings, confirmations, reminders, attendance and useful follow-up.

4. Application

   Present the correct requirements and forms, save progress and show outstanding items.

5. Review and assessment

   Coordinate document checks, reviews, interviews and assessments with appropriate permissions.

6. Offer and acceptance

   Issue decisions, record responses and track conditions, deposits and enrolment requirements.

7. Enrolment hand-off

   Transfer approved data to the SIS and other systems through a controlled, auditable process.

05

12 essential features of an admissions CRM

Schools should prioritise capabilities that make the family journey clear and the school's process dependable, rather than evaluating software by feature count alone.

1. Website enquiry capture

   Create or update the correct record while preserving source, campaign, language and enquiry context.

2. Family and applicant profiles

   Keep guardians and siblings together while allowing each child to follow the right admissions path.

3. Configurable admissions stages

   Model the school's actual stages, requirements and responsibilities.

4. Tasks and follow-up reminders

   Give every open enquiry or application a visible owner and next action.

5. Contextual communication

   Connect approved communications and useful templates to the family record.

6. Visit and event management

   Manage capacity, confirmations, reminders, attendance and post-event follow-up.

7. Mobile-friendly applications

   Help families understand requirements, save progress and upload documents on common devices.

8. Secure document collection

   Track required and outstanding documents while limiting access appropriately.

9. Review and decision workflows

   Coordinate reviews, notes, assessments, decisions and approvals securely.

10. Duplicate record management

    Use matching and merge rules that preserve history across repeat enquiries and siblings.

11. Reporting and source attribution

    Report volume and conversion by source, programme, campus, year level and stage.

12. SIS and system integrations

    Move approved information through documented mappings, ownership rules and error handling.

06

Chinese-language and bilingual requirements

Chinese and English journeys should provide an appropriate experience without becoming separate operational silos.

Forms may need local and international names, phone formats and address structures. Test the complete journey in representative network conditions, including fonts, maps, video, CAPTCHA and uploads. Channels such as WeChat should have defined ownership, consent handling and a way to preserve essential context in the CRM.

07

How should an admissions CRM integrate with the school website?

The integration should create or update the correct family, preserve source and consent, trigger the right workflow and notify an owner when processing fails.

Test missing fields, repeat enquiries, siblings, delivery failures and system outages—not only the successful submission screen. Integration errors need a visible log and an accountable owner. Our school website checklist covers the wider admissions journey, form, data-handling and website checks.

08

How to choose an admissions CRM

Evaluate how well the platform supports real family journeys, data responsibilities and reporting needs. Test these eight areas:

1. Process fit
2. Family experience
3. Team usability
4. Permissions and governance
5. Integration capability
6. Data ownership and export
7. Migration and implementation
8. Training and support

09

A practical admissions CRM implementation plan

A successful implementation begins with process and ownership, not software configuration.

1. Map the current admissions process
2. Prepare and clean existing data
3. Configure workflows and permissions
4. Connect the website and SIS
5. Test realistic family journeys
6. Train users and improve after launch

Avoid reproducing an inefficient spreadsheet process inside a new system. Use implementation to remove unnecessary fields, clarify ownership and make the next action easier.

10

Which admissions metrics should schools track?

Track measures that reveal demand, family progress and operational responsiveness, using shared definitions across teams.

1. Enquiries by source
2. Enquiry-to-visit and visit-to-application conversion
3. Application completion rate
4. Offer acceptance rate
5. Time to first response
6. Time in each stage
7. Withdrawal reasons