The largest loss is at the stage nobody owns
Melt is treated as an outcome rather than as a stage with an owner, which makes it invisible until the intake report.
The students who disappear between deposit and registration had already chosen you. Something in the following weeks made the decision reversible again.
Enrolment teams spend heavily on generating enquiries and comparatively little on the stage where the most students are lost. Melt between deposit and registration is a well-documented phenomenon and, in most institutions, an unmanaged one.
This paper examines why the largest loss goes unmanaged, argues that the constraint is visibility during the cycle rather than communication quality, and sets out the reallocation that frequently produces more improvement than any technology change.
If you read nothing else, read these. The analysis that follows sets out the evidence for each.
Melt is treated as an outcome rather than as a stage with an owner, which makes it invisible until the intake report.
Enquiries, applications and deposits sit in different systems with different definitions, so the picture is assembled after the intake number is fixed.
What happens next, when, who to contact, what other students found difficult. It reduces anxiety, which is what melt is made of.
Most institutions allocate territory effort by history. Reallocation by yield costs nothing.
Uncertainty, mostly. A student who has deposited has weeks or months before arrival, during which nothing much happens except administrative requests: a form to complete, a document to supply, a payment to arrange.
Institutions that manage this well fill the gap with communication that reduces anxiety rather than adding tasks. Institutions that do not fill it discover that the gap fills itself with second thoughts, competing offers and family conversations.
For first-generation students in particular, the value is in demystifying a process everybody else appears to understand. This is straightforward content to produce and it is rarely produced, because it falls between admissions, student services and marketing and nobody owns it.
Melt cannot be managed if it cannot be seen in real time, and in most institutions it cannot. Enquiries sit in one system, applications in another, deposits in a third, and registration in the student information system. The picture is assembled after the cycle, at which point the intake number is whatever it is.
Instrumenting the funnel properly means modelling every stage rather than the three that are easy, setting registration automatically from the student information system, and treating deposited-not-registered as a named stage with a named owner and a weekly review.
That last point is the whole intervention. A metric with an owner and a weekly cadence gets acted on; the same metric on a dashboard does not.
Instrumenting the funnel also reveals where counsellor time actually produces conversion, which is usually not where it is currently spent.
Most institutions allocate territory effort by history — the regions that have always been covered, at the intensity they have always been covered. Measured yield frequently tells a different story, and reallocating against it produces improvement at no additional cost.
We raise this because it is the finding institutions act on most readily and the one least often included in a technology business case. It is also the argument for instrumenting the funnel that survives a budget review most reliably.
Every paper in this series ends with a framework you can run internally. We would rather you used it and reached your own conclusion than took ours on trust.
Five steps. The third is where the recoverable value is.
Every stage from enquiry to registration, with dates captured on transition.
Registration set automatically from the student information system.
Melt as a named stage with an owner and a weekly review during the window.
Behaviour-triggered, practical content; non-response routes to a person.
Counsellor effort by measured yield rather than by territory history.
The same argument lands differently across an executive team. These are the three versions worth separating.
Microsoft's own documentation for the product behaviour described above. We would rather you verified the basis than accepted our summary of it.
On these references: each entry names a Microsoft Learn article or documentation area by title, because deep links change while titles are stable. Searching the title on learn.microsoft.com will reach the current version. Where we have cited a figure or a product behaviour, it is Microsoft's statement rather than ours; where we have given a number of our own it is labelled as such in the text.
We will map your current funnel data sources and show what real-time stage conversion and melt tracking would look like, using your programmes and terminology, before a cycle opens.
Institutions typically have less endpoint coverage than they believe, concentrated in devices owned by departments rather than by central IT.
The pattern that predicts withdrawal is visible in hindsight in almost every case. The question is whether anybody saw it while there was still time.
Describe the situation in your own words.