What Does "Application Under Review" Actually Mean?
Updated · 10 min read · By Anthony Castrio, Cofounder of ApplyAll
How we checked this
- The status-label glossary summarizes how candidate-facing statuses typically behave across the major applicant tracking systems (Workday, Taleo, iCIMS, SuccessFactors, Greenhouse, Lever, and others). It is drawn from operating application submissions at volume, not from vendor documentation, and the page says throughout that wording varies by employer configuration.
- The ATS portal figure on this page is a synthetic illustration, captioned as such. We do not publish screenshots of real candidate portals — every real one belongs to a real applicant.
- The Talent Board candidate-experience finding is cited from its published research; we did not re-run the survey.
The short answer
"Application under review" almost always means your application has been accepted into the active pool for that role and has not yet been decided on. It does not confirm that a human has read it, and it is not a shortlist. The phrase is a workflow stage inside the employer's applicant tracking system, written by software and shown to you because someone switched candidate-facing statuses on. It tells you where your file sits in a queue. It says nothing about whether anyone liked what was in it.
Deflating? A little. But it beats the alternative reading by a mile. Job seekers routinely treat a status change as feedback, refresh the portal daily, and interpret a stalled label as a rejection nobody had the courage to send. (We submit applications at volume for a living — we've watched more of these statuses than anyone should. They move for reasons that have nothing to do with the candidate, constantly.) Understanding what actually generates these strings makes them much easier to ignore.
Senior Data Analyst
Data Analyst II
Where the words come from
Every mid-size or larger employer runs hiring through an applicant tracking system — Workday, Oracle's Taleo, iCIMS, SAP SuccessFactors, Greenhouse, Lever, SmartRecruiters, Ashby and Workable are among the common ones. Each system models a requisition as a pipeline of stages, and every application sits in exactly one stage at a time. The label you see is a candidate-facing name mapped onto the internal stage.
Three consequences follow, and they explain most of the confusion:
- The labels are configurable. The same internal stage can be shown as "Under review" at one employer and "In progress" at another, and some employers rename stages to match their own process. There is no industry-wide dictionary, which is why comparing your status to a friend's at a different company tells you nothing.
- Not every system shows you anything. Systems oriented toward recruiter workflow, Greenhouse and Lever among them, often expose no candidate-facing status at all — you get a confirmation email and then nothing until a human writes to you. Absence of a status portal is not a bad sign; it is a product difference.
- Stages advance when a person clicks, or not at all. Nothing forces a recruiter to keep dispositions current. Applications sit in a review stage long after the practical decision has been made, which is why a status can freeze for months and then jump straight to a rejection.
What each status actually means
Below is how the most common candidate-facing labels typically map to what is happening internally. Wording differs by employer configuration, so read these as the usual meaning rather than a guarantee.
| What you see | What it usually means | Signal strength |
|---|---|---|
| Application received / Submitted | The system accepted your submission. Nothing else has happened yet. | None |
| Under review / In review / Under consideration | You are in the active pool for the requisition and have not been dispositioned. May or may not have been opened by a person. | Very weak positive |
| In progress / In process | Common in Workday and SuccessFactors portals. Usually the same idea as "under review" — an open, undecided application. | Very weak positive |
| Interview / Scheduling | A real decision has been made about you. This is the first status in the family that reliably means a human acted on your file. | Strong positive |
| On hold / Paused | Usually about the requisition rather than you: budget, headcount re-approval, or a hiring manager change. Can resolve weeks later. | Neutral |
| No longer under consideration / Not selected | Rejected for that requisition and the record is closed. | Definitive |
| Position closed / Requisition filled | The role is gone, often to another candidate or to an internal hire. Not a judgement on your application. | Definitive |
How long it sits there
Days to months, and the honest answer is that the variance is enormous. Three structural reasons account for most of it.
Batch review. Many teams do not read applications as they arrive. A recruiter blocks out time, works the pile, and shortlists in one pass. Between those passes every application in the pool sits at "under review" regardless of quality, which is why responses to a single posting tend to arrive in clusters rather than a steady trickle.
The requisition has its own life. Roles get re-scoped, paused, re-approved, and reassigned. A hiring manager's two-week absence stops a pipeline dead. None of that is visible to you, and none of it changes your status.
Closing out applications is optional work. Sending rejections costs recruiter time and generates replies. Candidate-experience researchers such as the Talent Board have documented for years that a large share of applicants never receive any communication at all, and a stale "under review" is what that looks like from the candidate's side.
As a working expectation: if a status has not moved in three to four weeks, treat the application as unlikely to produce a response, while keeping in mind that roles do come back to life when a first-choice candidate declines. Our guide on how long it takes to hear back after applying breaks the timelines down by employer type.
Does a status change mean anything?
It means movement. It does not tell you direction. This is the single most useful thing to internalize about status portals, and it cuts against how everyone naturally reads them.
When your application moves from "received" to "under review", something in the workflow advanced — but in most configurations that stage covers everyone still in the pool, including candidates who will be rejected an hour later. Conversely, a status that never changes is perfectly compatible with a recruiter having read your file, liked it, and being unable to schedule anything until a hiring manager returns from leave.
The one reliable exception is any status that names a concrete next step: interview, assessment, scheduling, reference check, offer. Those require a person to have made a decision about you specifically. Everything upstream of them is queue position.
What to do while it says that
- Stop checking daily. The portal is not a feedback channel, and refreshing it converts a background process into a source of daily disappointment. Once a week is generous.
- Treat every application as closed the moment you submit it. Assume nothing will come of it, keep applying, and let responses be a pleasant surprise. This is not cynicism, it is the only posture that keeps a pipeline moving.
- Follow up once, well, at around two weeks. To a named recruiter or hiring manager, referencing the specific requisition, a few lines long, and carrying one new and relevant piece of information rather than only a status request. Sent to a generic careers inbox, follow-ups almost never do anything.
- Do not read tea leaves in the portal. Job seekers trade theories about what it means when a posting is removed, when your name disappears from a list, or when a status reverts. These are usually artifacts of how the system was configured, not signals.
- Keep your own record. Portals lose history, postings vanish, and you will want to know which company, which requisition, and which date when someone finally calls.
The uncomfortable truth underneath all of this is that a single application, whatever its status says, is a low-probability event. The way to stop caring what "under review" means is to have enough applications in flight that no individual one carries the weight of your week — see how many jobs you should apply to for how to work out what "enough" is for your search. And if every status in your portal has been frozen for weeks across many applications, that is a different problem with a different fix: run the four-gate diagnostic before you send another batch.
Frequently asked questions
Does "under review" mean a human has read my application?
Not necessarily, and often not yet. In most applicant tracking systems the status is a property of the requisition workflow rather than a record of anyone opening your file — it typically means your application has been accepted into the active pool and has not been dispositioned. A human may be reading it that afternoon or the stack may be sitting untouched until the hiring manager blocks out review time.
Is "under review" better than "application received"?
Slightly, but read it as movement rather than as good news. Moving from a submitted or received state into a review state usually means the application cleared whatever automatic checks the employer configured and is now in the pool a recruiter works from. It does not mean you were shortlisted, and in systems where the review stage covers everyone in the pool it carries almost no signal about your individual chances.
How long does an application stay "under review"?
Days to months, and the spread is genuinely that wide. Many teams review in batches rather than continuously, so applications pile up in the review stage until someone sits down with the list. Requisitions also get paused, re-scoped, or filled internally without every application being closed out, which is why statuses can sit frozen long after the decision was effectively made.
What does "no longer under consideration" mean?
That one is unambiguous: you were rejected for that requisition and the record has been closed. It is the one status in this family that is a decision rather than a stage. It says nothing about other roles at the same employer, and at large companies rejections are frequently role-specific rather than company-wide.
Should I email the recruiter to ask about my status?
One short, specific follow-up after a couple of weeks is reasonable and occasionally useful; repeated status chasing is not, and it will not move you up a queue. If you follow up, reference the exact role and requisition, keep it to a few lines, and add one piece of new information — a relevant shipped project, a new certification — so the message has a reason to exist beyond asking.
Why did my application status change back to "under review"?
Usually because something happened to the requisition, not to your application. Statuses revert when a role is reposted or re-scoped, when an offer to another candidate falls through and the pool is reopened, when a recruiter corrects a mis-click, or when the employer reconfigures its workflow stages — all of which rewrite candidate-facing labels as a side effect. A reversion is genuinely ambiguous: it can precede a revival of your application or mean nothing at all. Treat it as movement without direction, the same way you should treat every status short of a concrete next step.
Why do some job applications never show a status at all?
Because not every applicant tracking system exposes a candidate-facing status portal, and not every employer that has one turns it on. Systems oriented toward recruiter workflow — Greenhouse and Lever are common examples — often give candidates only a confirmation email, with no page to check afterward. The absence of a status is a product difference, not a signal about your application. If you applied and received a confirmation, the application exists; whether you can watch its queue position from outside changes nothing about how it is processed.
Anthony Castrio, Cofounder of ApplyAll. Anthony cofounded ApplyAll and works on the systems that source, rank, and submit applications for customers every day. He fact-checks the pricing, ratings, and policy claims in these guides against the primary source before anything publishes. LinkedIn
Editorial process: drafted with AI assistance, fact-checked against primary sources, and edited by a named human. Spot an error? [email protected].
Related questions
- How Long Does It Take to Hear Back After Applying?
One to three weeks is typical, but the number that predicts your wait is not your application — it is which stage the requisition was in when you hit submit. Here is the week-by-week read on silence.
- Applied to 100+ Jobs and No Response? Here's What's Actually Wrong
Silence after 100 applications is a pipeline problem, not a verdict on you. The six leaks that cause it, ranked by how often we see them — plus a 30-minute audit that tells you which one is yours.
- Why Am I Not Getting Interviews? A Diagnostic You Can Actually Run
Four gates, tested in a fixed order: is it landing, are you aimed right, do your materials survive screening, and is your volume big enough to read? Most people rewrite their resume at gate three when gate one is broken.
What changed since our last check
- August 20, 2026 — Added a synthetic candidate-portal illustration (clearly captioned as an illustration) showing the queue-position vs decision distinction the page is about, two FAQs (status reversions, and why some employers show no status at all), this verification box, and a voice pass. No factual claims changed.
- August 13, 2026 — First published.
First time hearing about ApplyAll?
We apply to hundreds of jobs for you. Real humans, not bots.
A real person reviews and submits every application for you — no bot spam, no forms to fill. One-time payment, not a subscription. If you don't get at least one relevant interview within a month of your applications completing, you get a 100% refund.