Track Multiple University Applications: Consultancy Guide
How to track multiple university applications per student: one record, one deal per application, per-offer statuses, early-warning deadlines, honest counts.
Most students who walk into an Indian study-abroad consultancy don't apply to one university. They apply to three, five, sometimes more, often across two or three countries. If you want to track multiple university applications properly, a single row per student stops working the moment the first offer letter arrives. One application is waiting on a conditional offer, another needs a deposit by Friday, and a third was rejected last week. A single "status" column can't hold all of that at once.
This guide sets out a structure that works in a spreadsheet or a CRM: where each piece of data lives, which statuses belong to each application, how to set early-warning deadlines, and how to report conversions without counting the same student three times.
Key takeaways
- Keep one student record for everything personal, and create one application record (a "deal") for each university and course combination.
- Statuses, deadlines, fees, owners and university-specific documents belong to the application, not the student.
- Decide in advance which application represents the student in reports, usually the one that has progressed furthest.
- Report every metric at a stated grain: students for conversion and enrolment, applications for offer rates and university performance. Never mix the two in one ratio.
Why one row per student breaks down
A spreadsheet with one row per student and columns like "University 1", "University 2" and "Status" looks tidy for about a fortnight. Then these problems start:
- Status collisions. The student is "Offer received" at one university and "Rejected" at another. Whatever you type, the row is wrong for someone.
- Lost deadlines. Deposit, acceptance and confirmation document dates differ per application. One "next deadline" cell hides the rest.
- Inflated numbers. A student with three offers either counts once (under-reporting university outcomes) or three times (inflating conversion).
- Ownership confusion. One counsellor handles the UK files and a colleague handles Canada. One "assigned to" column can't show that.
The fix is structural, not a better spreadsheet formula.
The model: one student record, one deal per application
Split your data into two levels. The student record holds what is true about the person, whichever university they end up at. Each application record, which many CRMs call a deal, holds what is true about one university and course.
| Lives on the student record | Lives on each application (deal) |
|---|---|
| Name, phone, email, parents' contact | University, course, intake (e.g. January or September) |
| Academic history, test scores | Application status and sub-status |
| Passport, marksheets, English test certificate | Offer letter, offer conditions, acceptance |
| Lead source and campaign | Deposit amount, payment status, receipts |
| Overall counsellor relationship | Application-specific owner, if you split work by country |
| Communication history with the family | Confirmation document (CAS, I-20, CoE and so on) and visa status |
Two practical rules make this work day to day:
- Name each application university first. For example, "University A – MSc Data Analytics". When a counsellor scans a student's applications, the university is the part they compare, and short labels cut off whatever comes last.
- Never delete a rejected or withdrawn application. Close it with a reason. Rejection data by university and course is some of the most useful information a consultancy has when it shortlists for next season's students.
If you're setting up a pipeline from scratch, our guide on lead management software covers how the enquiry side should feed into this structure.
Statuses that belong to each application
Every application moves through its own ladder. The names differ between consultancies, but most follow something like this:
| Stage | Typical statuses | What the counsellor is waiting for |
|---|---|---|
| Shortlisting | Shortlisted, documents pending | Final course list, missing documents |
| Application | In progress, submitted, on hold, rejected | University decision |
| Offer | Conditional offer, unconditional offer, offer accepted, offer declined | Student to meet conditions or accept |
| Deposit | Deposit requested, submitted, verified, refunded | Payment and university confirmation |
| Confirmation document | Requested, issued | CAS, I-20, CoE or equivalent |
| Visa | Form started, submitted, approved, refused | Decision from the embassy or immigration authority |
| Enrolled | Enrolled, deferred, withdrawn | Student arrives and registers |
A conditional offer means the place is yours once you meet the stated conditions (final marks, an English test score and so on). An unconditional offer has no outstanding academic conditions. Track the conditions as a checklist on the application itself. "Conditional" on its own tells a manager nothing about what is still missing.
Destination checkpoints, described correctly
The confirmation document step is where a lot of applications stall, and each country handles it differently. Keep your status names generic, like "Confirmation document issued", and note which document it is on the application:
| Destination | Checkpoint document | What to know (checked September 2026) |
|---|---|---|
| UK | CAS (Confirmation of Acceptance for Studies) | The university sends a CAS reference number once it has offered a place. The Student visa application must be made within 6 months of receiving the CAS (GOV.UK). Many universities also ask for a tuition deposit before they issue a CAS. |
| UK undergraduate via UCAS | Firm and insurance choices | A student can accept only one firm choice and one insurance choice and must decline all other offers (UCAS). |
| USA | Form I-20 | Issued by the school's designated school official once the student is accepted into an SEVP-certified school. It is needed to pay the I-901 SEVIS fee and at the visa interview (Study in the States). |
| Australia | CoE (Confirmation of Enrolment) | Unless they fall in a special category, applicants must provide a CoE for all intended courses when applying for the subclass 500 Student visa (Department of Home Affairs). |
| Canada | Letter of acceptance plus PAL/TAL | Most students need a provincial or territorial attestation letter. Since 1 January 2026, master's and doctoral students at a public designated learning institution no longer need one (IRCC). |
Immigration rules change often. Put a "last checked" date next to any country-specific note in your internal playbook, and re-check the official source before you advise a family.
Documents: shared once, labelled by application
Documents split the same way as the data:
- Student-level documents are uploaded once and reused: passport, 10th and 12th marksheets, degree certificates, English test score report, CV.
- Application-level documents belong to one university: tailored SOP, the LORs that university asked for, application fee receipt, offer letter, deposit receipt, CAS or I-20 or CoE, and the visa decision letter.
A simple test: if the document would change had the student chosen a different university, label it with that application, for example in a folder named after the university.
Deadlines with early warnings
Deadlines are where multi-application tracking pays for itself. For each application, record at least:
- Application deadline for the intake
- Offer response deadline (the date to accept or decline)
- Condition deadline (when final marks or a test score must reach the university)
- Deposit deadline
- Confirmation document and visa target dates, working back from the course start date
Give each deadline an early-warning window, such as seven days before a deposit is due, shown to the application's owner rather than left in a shared inbox. When the student reaches the target status, the deadline should close, so nobody chases a deposit that's already paid.
A good deadline is written as a pair of statuses: "from Unconditional offer to Deposit verified by 15 October, warn 7 days before". That wording tells you when the clock starts, what counts as done and when to raise the alarm.
Which application represents the student?
Management asks simple questions: "How many students have an offer?" "How many are at visa stage?" To answer them, every student needs one representative application at any moment. Agree the rule in writing:
- Furthest progressed wins. A student at Deposit verified with University B and Submitted with University A is a deposit-stage student.
- Rejected and withdrawn applications don't represent the student unless every application is closed.
- Break ties consistently. If two applications are at the same stage, pick the earlier-created one, or the student's stated first preference, and apply the same rule every time.
- Respect formal choices. For UCAS students, the firm choice is a natural representative once replies are in.
Without this rule, two managers get two different answers from the same report.
Counting without double counting
Most consultancies get this wrong. Always ask: am I counting students or applications?
An illustrative example: in one intake your team works with 100 students. Between them they submit 260 applications and receive 150 offers, and those offers go to 70 different students. In the end, 40 students enrol.
| Metric | Grain | Correct figure |
|---|---|---|
| Students with at least one offer | Student | 70 of 100 (70%) |
| Offer rate per application | Application | 150 of 260 (about 58%) |
| Enrolment conversion | Student | 40 of 100 (40%) |
| Offers per student who received one | Mixed, labelled clearly | about 2.1 |
The classic mistake is "150 offers from 100 students", a ratio that mixes grains and makes the funnel look far stronger than it is. Run lead-source and counsellor reports at student grain, and university and course reports at application grain.
One more trap: an "at offer stage" count drops once students move on to deposit. For monthly offers, count students whose application reached the offer stage or beyond during the period.
A sample tracker for one student
Here is what one student's file looks like with this structure (hypothetical student and placeholder university names):
| Application | Status | Next deadline | Early warning | Owner | Pending |
|---|---|---|---|---|---|
| University A (UK) – MSc Data Analytics | Unconditional offer | Deposit, 15 Oct | 8 Oct | UK counsellor | Deposit, then CAS |
| University B (UK) – MSc Business Analytics | Conditional offer | Conditions, 30 Sep | 20 Sep | UK counsellor | IELTS result |
| College C (Canada) – PG diploma | Submitted | Decision expected | – | Canada counsellor | Offer, then PAL |
| University D (Australia) – Master of IT | Rejected | – | – | Australia counsellor | Closed, reason logged |
In reports, this student is one student with an offer, represented by University A. At application grain, they add two offers, one pending decision and one rejection to the university-level data.
Common pitfalls to avoid
- Creating a new student record for each application. You get duplicate phone numbers, split communication history and a family receiving three calls from three counsellors.
- Moving the student's overall status by hand. Let it follow the representative application instead.
- Tracking deadlines in personal calendars. They vanish when that counsellor is on leave.
- Using "applications submitted" as a productivity score. It rewards weak shortlisting. Pair it with offers per student.
How Xale handles this
Xale is our product, built around this model. In the study abroad CRM, each student is a lead and each university application is its own deal, with its own stage, owner, payments, internal chat and custom-field values. Documents, including application-specific ones such as a tailored SOP or an offer letter, sit in folders on the student record and are shared by all of that student's applications, so name folders by university. When a deal is linked to a university and course, Xale names it university first, for example "University A – MSc Data Analytics". Each role on a deal keeps its own follow-up, so the UK counsellor and the visa officer don't overwrite each other's reminders (see follow-up management). The full mechanics, including the duplicate-application check, per-application rollback and the admissions funnel, are on the university application tracking CRM page.
The default study-abroad pipeline runs Inquiry → Qualify → Application → Deposit → Visa → Enrolled, with conditional and unconditional offer statuses, deposit statuses and document-pending sub-statuses built in. You can rename or extend any of it. Stage requirements can block a move until the right documents, fields or a move note are in place, and document requirements can instead show as an info-only checklist. Status-to-status deadlines carry early-warning days and close themselves when the application reaches the target status.
For reporting, you can mark a stage as an Anchor Point, for example Deposit, or an Offer stage if you add one to your pipeline. Dashboard and report counts for that stage then include every student whose application reached it or went further, so the number doesn't drop when the student moves on to visa or enrolment. Conversions count each student once, however many applications they hold, and the Admissions tab follows offer, deposit, visa and enrolment application by application. Click any number in CRM reports and analytics and you'll see the exact list of students behind it.
Comparing tools? Our guide to choosing a study abroad CRM lists questions to ask any vendor, including how they count multi-application students.
Frequently asked questions
How many university applications should one student make?
There's no universal number. It depends on profile, budget and destinations, and on system rules (UCAS lets a student hold only one firm and one insurance choice). For tracking, what matters is that each application gets its own record, deadlines and owner.
Should each application have a different counsellor?
Only if your team works by country desk, where a UK counsellor and a Canada counsellor genuinely handle different files. Keep one primary counsellor for the family on the student record, so the parents have a single point of contact, and give each application exactly one owner per role for its deadlines and follow-ups. Two people owning one application is how a deposit deadline gets missed.
What's the difference between a lead, a student and a deal?
A lead is an enquiry that has not been qualified yet. Once qualified, that same record becomes your student, so you never create a second record for the same person. A deal is one university and course application under that student, with its own status, deadlines, owner and documents. One student can hold several deals at once, and reports should say whether they count students or deals.
How do I count conversions when a student has several offers?
Count the student once. A conversion is a student reaching your final stage (enrolled, or deposit paid if that's your definition) through any of their applications. Use application-level counts only for university and course performance, and label them as such.
Can I track multiple university applications in a spreadsheet?
Yes, with two sheets: one row per student and one per application, linked by a student ID. Once you need deadline warnings, several owners and consistent reports, most consultancies move to a CRM. Questions about Xale's setup? Write to hello@xale.in.