Job Application Statuses Explained: Submitted, In Review, and Closed

A job application status becomes actionable when you identify the record it describes and what that employer says it means. “Submitted,” “In Review,” and “Closed” do not form one universal hiring ladder. Record the visible label, check the employer's explanation, and keep the next step unknown until a message or instruction establishes it.

Use recent roles on LandOffer.ai for discovery while preserving the records for applications already sent. LandOffer publishes this guide and offers job-search tools. It uses official employer and government documentation checked October 8, 2026, plus a fictional worked example. Public documentation describes a process; we have not inspected any candidate account or predicted an interview from a portal label.

Identify the record before interpreting the word

First establish whether you are looking at a job posting, an individual application, a saved draft, or a personal tracker. A closed announcement can be different from a rejected application. A board's “Applied” badge may describe an action recorded on that board rather than an employer's receipt. A personal “Waiting” column is your organizational choice.

The USAJOBS status guide explicitly distinguishes job status from application status. Its job label can describe the announcement's hiring process, while “Track this application” leads to the agency's application record. That federal example shows why the object matters; it does not define labels in private employers' systems.

Write down the employer and requisition beside the label. Add the surface where you saw it and the checked date. If the screen shows a generic profile without a specific opening, do not assume every application shares the same state. The relevant question is what the record establishes about this particular application.

Submitted is a receipt question, not a selection claim

“Submitted” often suggests a completed candidate action, but use the employer's definition and actual record. Look for a requisition-linked entry, submitted date, confirmation message, or other evidence provided by that workflow. Keep the file you selected in your own history. A receipt does not tell you whether someone has read the resume or whether you meet the requirements.

Separate an uploaded attachment from a submitted application. A document can be saved in a profile while required questions remain unfinished. If the application says “Draft” or offers a final submission action, investigate that state rather than recording an application based only on the upload.

An absent email is also incomplete evidence. Check the account and employer's instructions before retrying. Some workflows provide other confirmation routes. If the record remains ambiguous, write “submission unconfirmed” with the missing evidence. That description identifies a check without inventing either success or failure.

Keep two facts separate in your tracker: you attempted submission and you have not confirmed receipt. Keeping those separate makes the next action easier to choose.

In Review needs an employer-specific definition

Read the help text linked from the employer's actual careers site. Harvard's employer FAQ defines its “New” status as received but not reviewed, and “In Review” as active review by the hiring team. Those definitions are useful for Careers@Harvard. They do not establish what another employer means by the same phrase.

Even when a definition confirms review, it does not establish who reviewed which document, what judgment they made, or whether an interview will follow. The record may show that the process is active while leaving the next decision unknown. Keep “in review” separate from “shortlisted,” “passed screening,” or “interview expected” unless an explicit message supplies that information.

The portal label is one piece of evidence. A recruiter message requesting an assessment or interview creates a new action with its own deadline. Record that communication directly. Do not replace it with an inference drawn from how quickly a label changed.

If the employer publishes no definition, save the exact wording. Your private note can say “meaning not defined on the page checked.” You can leave the meaning unresolved and still choose a useful evidence check.

Closed can describe several different things

Check the noun attached to “Closed.” Is the job no longer accepting applications? Is your individual application no longer under consideration? Is a personal tracker card merely archived? Those are different states, even if the interface uses similar styling.

A removed posting does not by itself explain the employer's decision about an existing application. It also does not establish whether a role was filled, canceled, paused, or replaced. Use an employer message or defined application state when one exists. Otherwise keep the closure fact limited to the page you checked.

An explicit rejection can be recorded as such. You do not need to soften a direct decision into “still waiting.” Conversely, do not create a rejection because an announcement closed while your application record remains active. Preserve both records if they disagree, with dates and sources.

Your own archive is a maintenance action. Moving a card out of the active queue reduces reminders; it does not change the employer's application. Keep the historical receipt and final known state available for later reference.

A completed interpretation ledger

Estelle Chen is a fictional backend engineer reviewing three invented application records. Arcwell, Ashbank, Umberlane, their requisitions, messages and definitions below are authored teaching inputs. They are not real portal observations or examples of a particular ATS vendor.

Fictional record checked October 8	Information actually supplied in the example	What remains unknown	Chosen next action
Arcwell AW-712: Submitted	Account entry links the application to AW-712 and gives an October 3 submitted date	Whether materials have been reviewed; any next decision	Preserve receipt and selected file; check again at the planned review
Ashbank AK-729: In Review	Employer help defines the label as materials currently being reviewed	Screening result, interviewer, response date	Keep active; no new submission or shortlist claim
Umberlane UL-733: job Closed, application Received	Announcement no longer accepts applications; individual record still says Received	Whether the application remains under consideration or role was filled	Preserve both labels; use employer guidance if a clarification is needed

Within the invented records, the decisions are already resolved; no candidate portal was operated for this example. AW-712 retains its October3 receipt, AK-729 stays in active waiting, and UL-733 in a record with separate job and application states. None supplies an interview invitation. Estelle therefore schedules no interview preparation deadline based solely on these labels.

The ledger also prevents repeated submissions from becoming the response to uncertainty. UL-733's closed announcement cannot accept a new application in this example. AW-712 already has a receipt. AK-729 needs no candidate action unless the employer asks for one.

Repair a tracker that has turned labels into predictions

Estelle's original private tracker entry for AK-729 says:

Shortlisted. Recruiter reviewing; interview probably next week. Send another resume to get noticed.

The stated fictional record supports review, but not a shortlist, assigned recruiter, interview date, or request for another attachment. The completed replacement is:

Employer application label: In Review. Checked October 8. Employer help defines active material review. No interview or additional-material request received. Next action: review account and messages October 15, unless an earlier instruction arrives.

October 15 is Estelle's chosen reminder, not an employer deadline or response prediction. The replacement leaves enough context to resume the search without reinterpreting the label each day. It also avoids making a second application look like an update mechanism.

For UL-733, Estelle replaces “rejected because job closed” with “job Closed; application Received; checked October 8; individual outcome unknown.” That revision lets Estelle keep the job closure and individual application state separate, so the next check targets the missing decision. The first entry invented a personal decision from an announcement state.

Let explicit requests change your priorities

Review messages and tasks alongside the status. A request for a missing document, an assessment, or an interview has more actionable detail than an unchanged label. Save the sender, requisition, requested action, due date and time zone if provided. Read the actual instructions before replying or completing anything.

An application can have a familiar status while a task requires action. Conversely, a status change can appear without requiring any action from you. Do not equate visible movement with a candidate obligation. When the record includes a task, that task should become the next action in your tracker.

If messages conflict with the page, keep both until the employer clarifies. A direct invitation is not erased because an older portal view still says Submitted. A rejection message should not be ignored because your personal board remains In Review. Record the source and date so you can explain the discrepancy accurately.

IBM's application FAQ describes checking application status in its candidate portal and receiving emails as status changes. That is an employer route to consult, not a guarantee that every system synchronizes immediately.

Choose a review rhythm without guessing a response date

Set reminders around known commitments. If the employer gives a date for an update, retain it. If it supplies no timeline, choose a review interval that fits your search and available time. The reminder is a time to check evidence, not a claim that the employer should have made a decision by then.

Avoid turning repeated refreshes into new application work. If nothing changed, note that the same state was checked and continue with other reviewed leads. A quiet portal does not identify the reason for the silence. Application volume, team availability, process design and hiring decisions remain outside your direct observation.

Where a permitted contact exists, a concise question can ask whether any action is needed or whether an updated timeline is available. Follow the employer's contact instructions. A support route intended for technical access or accommodations may not be a status-update channel.

Estelle's weekly review leaves AK-729 active, keeps AW-712's receipt, and checks whether UL-733 has an individual decision. It also returns to suitable new opportunities rather than assigning an invented probability to each label.

Compare a change without inventing a hidden sequence

In a second fictional check, Estelle sees that AW-712 changed from Submitted on October8 to In Review on October12. She saves the later label and checked date, retaining the earlier receipt. The employer has still sent no task or decision. Her revised next action remains a scheduled evidence check rather than an interview expectation.

For UL-733, imagine a later explicit message saying the application is no longer under consideration. That new message establishes an individual outcome the closed announcement alone did not. Estelle records the message date and stops the status reminder. This is a different decision from archiving because the bookmark disappeared.

The sequence illustrates how an evidence record can become more specific over time. It does not show how quickly actual employers work, or that every application must pass through these labels. If AW-712 instead moved directly to a rejection, the ledger would record that event without inventing an unobserved review stage. Preserve what was seen and communicated, not a complete story reconstructed from a few snapshots.

Preserve the last known state when you move on

You can stop actively monitoring an application without declaring an employer decision. If you decide to archive it in your own system, record that as your choice and retain the final verified employer label. This preserves the difference between personal prioritization and the hiring process.

Keep the exact title, requisition, submission date, selected resume, last checked state and any contact history together. A future repost, recruiter message or new opening can then be compared with the actual earlier record. An archive should reduce current clutter while leaving enough history to avoid accidental duplicates.

Choose one application record today. Identify the object, find the employer's definition if available, and write one known fact and one unresolved question. Then choose a check, response, or archive action from that evidence. You can browse recent roles on LandOffer.ai while continuing to track existing applications with the same care. Save that known fact and unresolved question beside the next action. The note supports your review; it does not determine a hiring outcome.

Sources and Further Reading

• Harvard employer application FAQ: employer-specific status definitions and access route.
• USAJOBS job and application status guide: distinct job and application records.
• IBM application process FAQ: candidate-portal status checking.