Admissions operations
Where Admissions Actually Stall Between Enquiry and Enrolment
Every school knows how many enquiries came in this season. Very few can say, on a given morning, which cases have stalled, who owns each one, and what it is waiting for. That difference — between counting the pipeline and owning the cases inside it — is where admission seasons are quietly won and lost. This is a walk through the gap, stage by stage.
Schools count enquiries; seasons are lost after them
Most schools run admissions like a campaign. There are hoardings before the season, a stall at the local fair, a listing on a portal, a referral drive among current parents. The enquiry register fills, and the number in it becomes the measure of how the season is going. That number is real, but it measures effort, not outcome. The quiet truth of most admission seasons is that the school did not lose families at the enquiry stage. It lost them afterwards, one case at a time, in a gap nobody was watching.
Walk the real chain and the gap becomes visible. An enquiry is captured. It is followed up, or it is not. Documents arrive partially. Verification waits on someone. The fee is discussed but not confirmed. A seat is allocated, but registration never happens. A confirmed seat is not an enrolment — the family can still drift away at every one of those steps. And at every step, the case can stop moving without anyone being responsible for the fact that it stopped. Nobody notices until the season closes and the numbers come up short.
This post walks that gap stage by stage: where cases actually stall, why good staff cannot see it happening, and what to do about it. It is written for admissions heads, front-office teams, registrars and principals — and for university and multi-school admissions offices, who face the same gap between bigger systems. None of it requires buying admissions management software to act on. Most of it can begin this week, with the register you already keep.
Enquiries arrive through five doors, and each one leaks
An enquiry is simply a family showing interest — a name, a class, a way to reach them. Capturing that sounds trivial, which is exactly why it leaks. Enquiries do not arrive through one door. In most schools they arrive through five, and each door records the enquiry differently, in a different place, seen by different people. Before any question of follow-up even arises, the school already has a fragmentation problem sitting at its own front desk.
None of these channels is wrong. The problem is that five capture points and no single register mean the school cannot answer a basic question: how many open enquiries do we have right now, and who is speaking to each one? The same family can enquire twice and be counted twice. Worse, a family can enquire once and be followed up by nobody, because each channel quietly assumed that somebody watching another channel had it.
- The website form goes to an inbox. It is answered on the day somebody checks that inbox — which, during peak season, is not every day.
- The phone call is taken by whoever is at the front desk. The details survive as a line on a pad, or in someone’s memory.
- The walk-in gets the fullest conversation and often the thinnest record: one line in a visitor register, with no note of what was promised.
- The WhatsApp message lands on whichever number the parent found — sometimes a staff member’s personal phone, where it stays.
- The listing-portal lead sits inside the portal’s own dashboard, waiting for someone to remember to log in and copy it out.
Cases stall at handovers, not at first contact
A handover is the moment a case passes from one person to another — front desk to admissions counsellor, counsellor to accounts, accounts back to the office for registration. Handovers are where admissions stall, because a handover usually transfers the work without transferring the ownership. The owner of a case is the one named person answerable for its next step. When a chit moves from one desk to another, the task moves with it. The answerability, very often, does not.
Picture the ordinary version. A parent calls on Tuesday. The receptionist takes the details, promises a call back, and leaves a note for the counsellor. The counsellor is taking a campus tour, sees the note on Thursday, and calls a number that goes unanswered. She means to try again. Friday brings a walk-in rush. The note migrates to the bottom of a tray. The parent, hearing nothing, visits the school two streets away — which called back the same evening.
The uncomfortable part is that everyone in that story did their job. The receptionist recorded the call. The counsellor attempted the callback. No individual failed, and yet the case failed, because tasks were being completed while the case as a whole belonged to no one. That is the pattern to look for in your own office. Not careless staff — completed tasks, and abandoned cases in the spaces between them.
After the yes: where confirmed admissions quietly stall
Now look past the yes. A family agrees to admission, and most schools relax, because the hard part feels done. It is not. Between the yes and the child actually sitting in a classroom lies a paperwork chain, and every link in that chain can hold the case silently. These are the cases that hurt most at season’s end, because the family had already chosen you — and the school still lost them.
Each of these is a small, reasonable pause, which is precisely what makes them dangerous. A case waiting on a transfer certificate looks fine on Monday and fine on Friday. It only looks like a loss in retrospect, when the family confirms elsewhere because the other school finished its paperwork first. The office rarely decides to drop these cases. It simply never decides anything about them at all — and a season can absorb only so many of those non-decisions.
- Documents partially received: the transfer certificate is awaited from the previous school, and the folder waits with it — sometimes for weeks, with no reminder set for anyone.
- Verification pending: checking the birth certificate or previous marksheets is nobody’s stated job, so the file sits between the front office and the academic head.
- Fee confirmation: the parent asked for a few days to arrange the payment. The note recording that promise stays on one desk, and nobody follows up when the days pass.
- Seat allocation: the section allotment waits on a sign-off from the principal — who does not know the file is waiting.
- Registration: the family believes the admission is complete; the school believes the family will come in to finish it. Both wait.
A stalled admission needs an owner, a position and a closure
Here is the reframe that changes how a season is run. A stalled admission is an exception — a case that has left the normal path and now needs individual attention, not another pass through the routine. An exception needs three things. A named owner: one person, by name, answerable for the next step. A current position: what the school currently believes about the case, and what it is awaiting — a document, a payment, a decision, a call back. And a recorded closure: the case ends as enrolled, declined with a reason, or withdrawn — never by simply going quiet.
Notice what this is not. It is not a reporting format, and it does not need software to begin. A notebook with three columns — owner, position, closure — run honestly in the daily front-office huddle will recover cases this season. What it needs is the discipline to insist that no open case is ownerless, and that no case is allowed to end in silence. Silence is the enemy: a case that has gone quiet is not lost yet, but nobody is fighting for it either.
Counting stages is not the same as recovering cases
A funnel is a count of how many cases sit at each stage — so many enquiries, so many visits, so many confirmations. Funnels are genuinely useful. They tell leadership how the season is moving and where the pipeline narrows. But a funnel measures volume, and volume is anonymous. It can tell you the verification stage is slow. It cannot tell you which families are stuck there, who is speaking to each one, or which of them could still be recovered this week.
An exception queue is the other half: the live list of individual open cases that have stalled, each with its owner and its current position. The funnel is for the review meeting; the queue is for tomorrow morning. The distinction matters because seasons are lost case by case, not stage by stage. By the time a funnel shows a stage narrowing, some of the cases inside it are already beyond reach. A queue surfaces each case while it is still recoverable — while the family is still waiting, not yet gone.
What to measure while the season can still be saved
You cannot manage a gap you do not measure, so measure the gap directly — not the volume around it. A handful of measures cover most of it, and none requires special software. What they require is a single register of open cases, which is worth building for its own sake. Review the measures weekly at first, then daily as the season peaks, and always with names attached: a measure with nobody answerable for it becomes just another report.
Deliberately, there are no benchmark figures here. What counts as an old case differs by board, city, class and fee band, and any number this post invented would be wrong for your school. Set your own thresholds this week, then compare yourself against your own last week. Movement against your own baseline is the only benchmark that means anything — and the only one nobody can argue with in a staff meeting.
- Age of open cases at each stage: for every open case, how long has it sat where it is now? Sort the list oldest first, and start each morning at the top.
- Cases with no owner: how many open cases have no named person answerable for the next step? The honest first answer is usually uncomfortable — which is the point.
- Cases with no contact in N days: choose your own N, the number of days without the school and the family speaking that you consider unacceptable, and list every case past it.
- Closures without a recorded reason: how many cases ended by going silent? Every silent closure is a lesson the school paid for and never collected.
In higher education, the gap runs between systems you already own
For a private university or a multi-school group, the same gap wears different clothes. The systems already exist and mostly work: an application portal collects applications, an ERP holds the student record, a payment gateway takes the fees. The gap runs between them. A payment succeeds at the gateway but is not reflected against the application, so the applicant is chased for money already paid. A verified application waits for seat allocation in another office’s system, owned by nobody that either office can name.
The instinct is to replace one of the systems, and it is usually the wrong instinct. The portal, the ERP and the gateway stay authoritative — they are not the problem. The problem is that nobody governs the case as it crosses between them. So the wedge is an exception queue that sits across those systems: every stalled case with a named owner and a current position, while each underlying system keeps doing its job. That is the shape of the higher-education route described at squarecampus.com/launch-partners/higher-education/ — one bounded workflow, run alongside what already exists.
Do this even if you never buy SquareCampus
SquareCampus is built as a School Operating System — an institutional decision layer where a stalled case is an exception with a named owner, a current position, and a closure recorded on an auditable timeline. It coexists with what an institution already runs: the existing ERP, payment portal or identity provider stays authoritative, and a later rollout may consolidate selected fragmented tools if and when the institution chooses. Nothing has to be ripped out to close the admissions gap. The platform page at squarecampus.com/platform/ describes the model, and the rollout approach at squarecampus.com/rollout/ describes how it arrives without disturbing a live season.
But the honest close is this: the discipline matters more than the software. If you never buy anything from us, do the exercise anyway. Gather every enquiry from every channel into one register. Give every open case a named owner and a written position. Refuse silent closures. Measure the age of whatever is open. Do this and you will find recoverable cases almost immediately, because most stalled admissions are not lost — they are waiting for somebody to notice them. Software makes the discipline durable; it cannot substitute for it.
Bring one stalled case to a demo
Bring last season’s enquiry register and one admission that went quiet. We will walk it end to end — capture, handovers, ownership, closure — and show how an exception queue would have carried it.