Most schools know how many enquiries they receive. Far fewer can say what happened to a specific one. A family visits, leaves a phone number, and weeks later nobody in the office can tell whether they were contacted, came for a campus visit, sat an interaction, or quietly enrolled elsewhere.

Admissions is not one event. It is a sequence of small decisions, each with a different owner, and each one a place where a family can be lost without anyone noticing.

Treat admissions as a funnel, not a form

A funnel is simply a list of stages a family passes through, with a count at each stage. That is all. It does not need a data warehouse or a consultant.

A workable starting shape for most schools:

  • Enquiry — the family expresses interest, by phone, walk-in, website form, referral, or an advertisement response.
  • Contacted — a staff member has spoken to the family at least once and recorded the outcome.
  • Campus visit or interaction — the family has seen the school, met staff, or attended a scheduled session.
  • Application or assessment — formal steps have begun, documents requested, or an interaction arranged.
  • Decision — offer made, accepted, waitlisted, or declined, with a reason recorded.
  • Enrolment completed — fees, class placement, and parent access are set up and the student is on the rolls.

The stages matter less than the discipline of moving every enquiry through them. A school with five well-owned stages learns more than one with fifteen half-used statuses.

The drop-off points schools usually find

When a school first counts its own funnel, the leaks are rarely where leaders expected. The common ones:

Enquiry to first contact. The office has the number but the person responsible is on leave, the walk-in register is still paper, or the website form lands in a mailbox nobody monitors daily. An enquiry that goes unanswered for two days is functionally a lost enquiry, whatever the family decides.

First contact to visit. The call happened, but nothing was promised and no date was agreed. There is no note of what the family said about their budget, their preferred grade, or their concern about transport. The next call starts from zero.

Visit to application. Families leave a satisfying campus visit intending to apply, then stall on paperwork: a birth certificate, a transfer certificate, a previous report card they must fetch from another school. If nothing tracks who owes which document, the application sits untouched and the family assumes the school is not interested.

Application to decision. This is often the longest silent gap. Documents are pending, an assessment is scheduled and then postponed, and no one tells the family where they stand. Silence in an admissions process reads as rejection.

Decision to enrolment. The offer was made and accepted, but fee setup, class allocation, or portal access is pending. Families who have paid and heard nothing back become anxious, and anxiety is what makes a family keep a second option open.

Enrolment to first day. A smaller but expensive leak: the transition from accepted student to actual student is handled by a different team with different records.

Instrument the funnel with what you already have

You cannot fix drop-off you cannot see, and you do not need new software categories to see it. You need records that carry state.

Capture the source on every enquiry. Walk-in, referral, website, phone, advertisement, or event. Source is what eventually tells a school which effort actually produced enrolments rather than traffic.

Give each stage a timestamp, not just a status. The date of first contact, the date of the visit, the date the application completed, the date of the decision. A timestamp turns a list into a funnel, because you can measure the gap between stages.

Log every contact attempt, including the failed ones. “Called, no answer, will retry Tuesday” is a record. A blank screen is not, and it hides the fact that a family was never actually contacted.

Record the reason for every decision. Declined, waitlisted, withdrew, price, distance, seat not available, chose another school. A short controlled list of reasons is worth more than paragraphs of notes, because it can be counted.

Instrument the documents, not only the person. An application waiting on a transfer certificate should appear as a stalled item with an owner and an age in days.

Keep the count honest across channels. If enquiries arrive through three places and two of them are notebooks, your funnel is partly fictional. It is better to have one incomplete but consistent flow than several complete ones that disagree.

A connected academic and student records flow helps here mainly because the same enquiry, applicant, and enrolled student record is carried forward instead of retyped at each stage.

Give every stage an owner and a clock

Instrumentation fails when the data is complete but nobody is accountable for acting on it.

For each stage, name a role, a response expectation, and a closure state. First contact might belong to the front office with a same-or-next-working-day expectation. Document follow-up might belong to admissions staff with a weekly review. Fee and class setup might belong to accounts and academics respectively. The point is not the org chart; it is that a stalled record has a name attached to it.

Then hold a short weekly review of exceptions, not a monthly review of totals. The useful list is small: enquiries with no contact attempt, applications stalled more than a defined number of days, accepted students without fee or class setup, and visitors who never progressed. Totals tell you how the season is going; exceptions tell you what to fix this week.

Read the funnel honestly

A funnel count invites three easy mistakes.

Treating every enquiry as equally serious. A brochure request from a parent two years away should not sit in the same pipeline as a family seeking a seat this term. Filter by intended year of entry and stage before drawing conclusions.

Confusing volume with conversion. More enquiries at a lower completion rate can be worse than fewer, better-qualified ones. Track both counts and conversion between stages.

Blaming the family. Most drop-off is a process failure, not a demand failure. If a third of applicants stall on the same document, the problem is the document request, not the families.

And measure time, not just counts. The number of days from enquiry to first contact, and from completed application to the decision, are the two figures admissions leaders most often cannot produce — and the two that families feel most acutely.

A reasonable place to start

Pick one intake and one month. Count the enquiries, then count how many reached each stage. Record timestamps and an owner at every transition. Review exceptions weekly, and note two or three reasons why families stalled.

The first pass of this exercise is usually approximate, and that is fine. A school that can describe its own funnel, name the biggest leak, and say who owns it is already making better admissions decisions than one relying on the final enrolment number alone. Detailed reasons belong in private records; any reporting shared more widely should stay aggregate.

Admissions funnel checklist

  • Stages are few, clearly named, and mutually exclusive.
  • Every enquiry carries a source.
  • Every stage carries a date, not only a status.
  • Unsuccessful contact attempts are recorded.
  • Reasons for decline, withdrawal, and waitlisting come from a controlled list.
  • Stalled documents have an owner and an age in days.
  • Time between stages is measured, not just totals.
  • A weekly exception review has a standing owner.
  • Aggregate funnel reporting never exposes an individual family’s details.

Related reading: How to digitise school admissions without re-entering student data and Connect college admissions, programmes, and student services.