In short
Track the application, not the student. Each one gets its own record with a stage, deadline, document checklist and named owner. A student with eight applications has eight states at once, and one status field cannot hold that.
This is the most common mistake when a consultancy outgrows a spreadsheet. One row per student, one column called Status. By November it reads "3 sent, 2 waiting on transcript, TU Delft needs the essay" and nobody can filter it.
A stage model that survives contact with reality
A stage should say where the work is, and each move should be something a person does. Five is usually enough:
- Step 01
Shortlisted
University and course agreed. Nothing prepared yet. Record the entry requirements and the deadline here, so the rest of the plan is built backwards from them.
- Step 02
In preparation
Documents being collected, personal statement being drafted. This is where applications quietly stall, so review it weekly.
- Step 03
Submitted
Sent, with the date recorded. Anything the portal issued (a reference number, a login) goes on the record, not in an email.
- Step 04
Decision pending
Waiting on the university. Set the date you will chase, not the date you hope to hear.
- Step 05
Offer / rejected / withdrawn
Closed. An offer starts a new set of obligations (deposit, acceptance deadline, accommodation), and those are tasks, not stages.
What to record on each application
- University and course, spelled the way the university spells them.
- The submission deadline, and separately your own finish date, usually two weeks earlier.
- The documents this university wants. They differ, and assuming otherwise is how a submission slips.
- Who on the team owns it. One name, not a team.
- Notes from any contact with the admissions office.
In EduCRM each application sits on the student's record and on a drag-and-drop board. Open the student to see all of theirs, or the board to see everything in preparation. See application tracking.
How to stop deadlines arriving as a surprise
Deadlines are a scheduling problem, not a reminder problem. A reminder three days out is useless if the transcript takes two weeks. Two habits fix most of it:
- Put the document-gathering date in the calendar, not the submission date. Work backwards through everything that means waiting on someone else.
- Review the board once a week at a fixed time. Filter to applications in preparation with a deadline inside six weeks. That list is the week's work.
Because sessions, deadlines and follow-ups share one calendar, that review is one screen. More in managing documents and deadlines.
See the application board
Open the live demo and drag an application between stages. It resets every 24 hours.
Keep reading
Frequently asked questions
How many applications should one student have?
That is a counselling decision, not a software one. What matters is that the system supports several open applications per student at different stages. EduCRM does.
Should visa steps be application stages?
Usually not. A visa depends on an accepted offer, so it comes after the application closes. Most consultancies track visa steps as dated tasks against the student.