Somewhere between offer acceptance and arrival, they stalled — a visa document never submitted, a payment never made, a confirmation never returned. The signals were all there, scattered across inboxes and spreadsheets. Nobody was looking at them together, so nobody saw the student drifting until the seat was already empty.
Why stalled students go unnoticed
Pre-arrival pipelines track actions, not absences. Staff see the students who email, submit, and ask questions. The student who goes quiet generates nothing to see — no ticket, no task, no alarm. And quiet is precisely the signal: a student who stopped opening messages in July is telling you something in July, when a phone call could still change the outcome. Discovered in September, the same silence is just a statistic.
Every silent melt costs a recruited, admitted, visa-processed enrollment — the most expensive student to lose, at the moment they were cheapest to save.
What an early warning view shows
Each student's position against the expected timeline: who is on track, who is behind, who has gone quiet. The Progress Tracker shows completion by stage; the Roadmap defines what "on track" means for each intake. Staff intervene by week, not by semester.
Six steps inside SumHubs
You don't have to start from a blank page.
The stalled-student early warning view is a pre-built SumHubs template — configured with your milestones and intake timelines in an afternoon. Request a sample hub to see your pipeline in it.