Scoring an admission instead of guessing it

In most admissions offices the matching of student to course happens in a counsellor's head. An experienced one is usually right. The problem is not accuracy — it is that nothing about the judgement is visible. It cannot be reviewed, it cannot be handed over, it cannot be taught to the person hired last month, and it cannot be done at the speed enquiries arrive.

We built an admission management system around a simple proposition: write the judgement down as a score, and the rest of the pipeline becomes tractable.

Scoring is not automation

A score does not decide anything. It arranges the evidence — academic background, language ability, budget, intended destination, timing — so the counsellor sees the same picture every time, in the same order, with nothing missing.

That distinction is worth defending. The moment a score is treated as a decision, two things go wrong: counsellors stop reading the file, and any bias in the weighting becomes policy instead of a suggestion.

Course matching needs an explanation, not just a ranking

A list of courses ordered by fit is a weak product. A list where each entry says why it is there — this matches the academic profile, this stretches the budget, this one has an intake that fits the student's timing — is something a counsellor can actually use in a conversation with a family.

Students and parents ask "why this one?" Any system whose answer is "the algorithm said so" has made the counsellor's job harder, not easier.

The pipeline is the product

Assessment and matching are the interesting parts to build. The part that determines whether the system is used daily is the pipeline — the plain question of which enquiries are sitting untouched.

What made it work:

• One list, ordered by what needs attention, not by when it arrived.
• Every stage has a next action and an owner. A stage with no named next step is where enquiries go to die.
• History on the record. When a student comes back after four months, the counsellor needs the last conversation, not a blank form.

Enquiries arrive on whatever channel the student prefers

Students message. They message on several platforms, at night, and they expect a reply. An admissions system that only knows about enquiries typed into a web form is describing a fraction of the real pipeline, and the fraction it misses is usually the younger, faster-moving half.

Getting those conversations into the same pipeline as the formal applications is unglamorous integration work and it is where a lot of the value turned out to be.

Handle the data like it matters

An admissions file contains a young person's academic record, identity documents and family finances. The right posture is to collect only what is needed for the decision at hand, restrict who can see it by role, and be able to say exactly who opened a record and when. None of that is difficult. It is simply easier to skip, and it is not the kind of thing anyone should be skipping.