Why spreadsheets break when a student applies to five universities

A single student rarely applies to one university. They apply to four or five, each of which may return more than one offer, and each offer carries its own conditions — English scores, deposits, transcripts, interviews. This is where the spreadsheet quietly gives up.

The one-row-per-student trap

Put one student on one row and you immediately run out of columns. Five applications, each with two offers, each with a five-item checklist, does not fit a grid. Agencies end up with colour codes, extra tabs and notes that only one person understands.

The one-deal-per-application trap

Generic CRMs make the opposite mistake. They treat every application as a separate deal, so the same student appears five times with no shared view. You lose the person inside a list of deals.

What you actually need to see

The right model mirrors reality: one student, holding many applications, each holding one or more offers, each offer holding its own condition checklist. On one screen a counsellor should be able to answer:

• Which universities has this student applied to, and what stage is each at?
• Which offers are in hand, and which are conditional?
• What conditions are still outstanding, and who is chasing them?
• What is the single next action for this student today?

Why it matters commercially

Every outstanding condition that slips is an enrolment at risk. When the whole case is visible in one place, nothing is forgotten, handovers between counsellors are painless, and managers can see where each student really stands.

Edudex is built around this exact shape — one lead, many applications, many offers, clear conditions — so your team can stop maintaining spreadsheets and start moving students forward.