After you lodge, the file is with the institution and moves through status changes you can read if you know what they mean. The assessment period is not a fixed number — it is set by the course, the intake, the completeness of your file, and the institution’s workload — so tracking is about recognising normal progress versus a genuine stall. This guide explains the statuses, what drives the timeline, and how to follow up without slowing your own file.
What the status values usually mean
Application portals use varied labels, but the stages they mark are consistent:
- Received / submitted: the institution has the application; nothing has been assessed yet.
- Under assessment / in review: an officer is checking documents and eligibility.
- Further information requested: the file is on hold pending something from you (see below).
- Conditional offer: an offer subject to conditions (see the conditional offer guide).
- Unconditional offer: the offer is firm; next is acceptance and the CoE.
- Unsuccessful / declined: the application did not meet the requirements.
A status sitting on “under assessment” for a while is normal; it is not, by itself, a stall. The signal is whether it moves at all and whether the institution has asked you for something.
What determines the assessment period
The time to an outcome is shaped by factors the institution controls and you can anticipate:
- Course and level — some programs assess in a central pool, others in a faculty with its own cycle; the path affects speed.
- Intake and season — peak application periods near major intake deadlines are busier, so files lodged then may take longer.
- Completeness — a file with every required document and a clear academic record moves faster than one that triggers queries. A missing certified copy or unclear transcript is what turns a normal wait into a stall (see the certification and transcript guides).
- Conditions already met — an unconditional-ready file is quicker than one needing English or result verification.
Because these vary, a realistic period is the one the institution’s own guidance suggests for your course and intake; treat that as the baseline, not a fixed statutory time.
What a request for further information looks like
When the institution needs more, it usually:
- Sets a status of “further information” or similar.
- Sends an email naming the specific missing or unclear item.
- Gives a deadline to supply it, after which the file may lapse or be assessed as is.
The most common requests are for certified copies, clearer transcripts, English score delivery, or explanation of a gap (see the relevant guides). Respond to the exact item asked for, with the format requested, before the deadline. A vague or partial response extends the stall.
How to follow up without harming the file
Follow-up is reasonable; over-follow-up is not. The line:
- Wait the institution’s stated period for your course and intake before chasing; chasing inside it rarely speeds anything and can add noise.
- Follow up once, briefly, referencing your application ID, the date lodged, and the current status — not a demand for a decision.
- Respond fast to any request — that is the follow-up that actually moves the file.
- Use the official channel — the portal message or the admissions email — not a social media tag or a visit that the process does not use.
- Keep records of your follow-ups so you can show you engaged appropriately if the file later needs escalation.
The goal is to show engagement, not urgency. A file is not helped by daily messages.
Escalating a genuinely stalled file
If the stated period has clearly passed, a requested item was supplied and ignored, or the status has not moved despite a complete file:
- Reference your application ID and the dates of lodging and any response you sent.
- State specifically what you supplied and when, so the institution can locate it.
- Ask for the file’s current position, not for a favourable outcome.
- Keep it within the institution’s process; escalation outside it does not advance the assessment.
This is about unblocking a stuck file, not compelling a decision. The institution decides outcomes; you can only ensure the file is complete and visible.
Worked example: a stalled file unblocked
A student lodged and the status sat on “under assessment” for longer than the institution’s stated period for her course. She waited the stated period, then sent one brief follow-up referencing her application ID and lodgement date, asking for the file’s position.
The institution replied that a document — a certified transcript — was unclear and had been requested, but the email had gone to her spam. She supplied a fresh certified copy the same day. The file moved to an offer within the next week.
The stall was not a slow assessment; it was an unanswered request she had missed. Her single, dated follow-up referencing the ID is what located the issue. A daily stream of messages would not have helped; the one targeted follow-up did.
The example shows the value of waiting the stated period, then a precise follow-up, and of watching the inbox (including spam) for requests. A stalled file is often a file waiting on the applicant, not the institution.
Common questions
- When should I first chase? After the institution’s stated period for your course and intake; earlier rarely helps.
- What if I missed a request email? Supply the exact item requested, in the format asked, as soon as you see it.
- Is a status stuck on “under assessment” a problem? Not by itself; it is normal until the stated period passes.
- Should I call or email? Use the institution’s official channel — the portal message or admissions email — not social media.
- How do I escalate without harming the file? Reference your ID and dates, state what you supplied and when, and ask for the position; stay within the process.
A checklist for tracking the file
Keep the file moving with this routine:
- Record the lodgement date and application ID the moment you submit; you will reference them in every follow-up.
- Note the institution’s stated period for your course and intake as the baseline, not a fixed law.
- Check the portal on a fixed schedule — weekly for most, not hourly — so you notice a status change without obsessing.
- Watch the email (and spam) for requests; a missed request is the usual cause of a stall.
- Respond to any request in the format asked, before the deadline, with exactly the item named.
- Log every status change and message so you can show engagement if escalation is needed.
- Wait the stated period before the first chase; one precise follow-up beats a daily stream.
This routine is what separates a tracked file from a forgotten one. The institution assesses; you keep the file complete and visible.
Edge cases worth checking
A few situations change how tracking should be handled:
- A representative is named. If a representative lodged for you, confirm you are copied on every request; a request sent only to them that you miss is still your stall (see the agent versus direct guide).
- Multiple applications at once. Each has its own ID and its own clock; track them in a table so one offer’s deadline does not hide behind another’s status.
- A conditional offer arrives mid-track. A status change to conditional is not the end — it starts the conditions clock; see the conditional offer guide for what to do next.
- A request arrives after the stated period. Even late, respond to the exact item; a late request still needs your answer to move the file.
- The status disappears or errors. If the portal shows nothing or an error, contact admissions with your ID rather than assuming the file is fine; an invisible file is not the same as a moving one.
How tracking connects to the next stages
The point of tracking is not the status itself but the hand-offs it triggers. A move to “conditional offer” hands off to meeting conditions; an “unconditional offer” hands off to acceptance, deposit, and CoE (see the application fee and deposit and CoE guides); a refusal hands off to understanding why and whether a new application or a different course fits. Treating each status as a gate to the next step — rather than a verdict to wait on — is what keeps the whole application moving from lodgement to enrolment.
Tracking is a habit, not an event. The applicants who reach enrolment without drama are the ones who checked on a schedule, answered requests the day they landed, and kept their own log — not the ones who lodged and waited. A small, steady routine beats a burst of panic follow-ups after the deadline has passed. If a status has not moved for a while, the routine tells you whether that is normal for your course or a signal to send the one precise follow-up that actually locates the issue. The file is yours to watch either way; the institution will not chase you to check on your own application.
What to do next
After lodging, note the institution’s stated assessment period for your course and intake as your baseline, and record your lodgement date and application ID. Check the portal on a fixed schedule rather than constantly, and watch for a “further information” status or email — respond to the exact item, in the requested format, before the deadline. If the stated period passes with no movement and your file is complete, send one brief follow-up referencing your ID and dates. Keep a log of every status change and message so you can show engagement if the file needs escalation.