Skip to content
Book a Demo
Article Admissions

Admission Funnel Guide: Measure Movement, Ageing and Drop-off

An admission funnel is useful only when every stage has a stable definition and the report can identify the records behind the count. Start with observable events, keep cohorts consistent and show ageing beside conversion.

Reviewed for accuracy on 18 August 2026

An admission funnel is useful only when every stage has a stable definition and the report can identify the records behind the count. Start with observable events, keep cohorts consistent and show ageing beside conversion.

Define measurable stages

Use events such as verified enquiry, first meaningful contact, application started, application submitted, documents complete, payment complete, offer released and admitted. Document whether records can move backwards and how reopened applications are treated.

Choose the right cohort

A source cohort answers what happened to enquiries acquired in a period. A stage-activity view answers what work happened during a period. Do not mix them in one conversion rate. Filter by intake, programme, campus and source only when the remaining sample still supports a useful decision.

Add ageing

Show how long active records have remained in their current stage. Median time can hide an old tail, so use ageing bands: within target, approaching target and overdue. Link each band to its record list and current owner.

Diagnose drop-off

A lower transition rate is a signal, not a cause. Review source quality, response delay, follow-up coverage, eligibility, form friction, document pendency, payment failure and programme fit. Compare cohorts and read actual histories before assigning blame.

Build the report

  • Entry volume and transition rate by stage.
  • Current ageing and owner.
  • Source-to-application and source-to-admission outcomes.
  • Exception queues for duplicates, invalid records and withdrawals.
  • Definitions and last refresh time.

Turn findings into action

Assign one intervention, owner and review date for each important bottleneck. Examples include reallocating an aged queue, simplifying a form step or correcting a source mapping. Review whether the next cohort improved.

Questions teams ask

Frequently asked questions

How should a team start using this framework?

Start with one intake or workflow, agree definitions and owners, then review actual records before expanding the framework.

Does the framework require a CRM?

The operating principles can be applied manually, but a governed CRM makes ownership, history, automation and reporting easier to sustain at scale.