Application Tracking · Published July 25, 2026
Statuses describe confirmed stages. Feelings, predictions, and to-do items need their own fields or the pipeline stops being reliable.
A status is useful only when everyone—including future-you—knows what event moves an application into it. “Waiting,” “maybe,” “contacted,” and “ghosted” often combine stage, emotion, age, and next action. Replace them with a small controlled model. Keep the current stage, stage date, outcome, and next action as separate fields.
Use event-based definitions
| Status | Entry rule | Exit rule | |---|---|---| | Saved | Role retained for evaluation | Apply, skip, or expire | | Preparing | Active work on the application | Submit, pause, or skip | | Applied | Submission confirmed | Human response, withdrawal, rejection, or no-response closure | | Recruiter screen | Recruiter conversation scheduled or completed | Advance or close | | Interview | Hiring-team interview process active | Advance, offer, withdrawal, or rejection | | Offer | Verbal or written offer received | Accept, decline, expire, or withdraw | | Closed | Process ended | No routine exit; reopen only on real new contact |
Keep sub-stages only when they change work
For complex searches, split interview into hiring manager, technical or case, panel, and final. For simpler searches, keep one Interview status and record events separately. Add statuses only when they affect preparation, reporting, or next action.
Do not create a new status for every email. “Reference requested” may be a stage or an event depending on the hiring process. Design for decisions, not perfect imitation of every employer workflow.
Retire “ghosted” as a primary status
“Ghosted” expresses a real and frustrating experience, but it lacks a consistent event boundary. Use Applied or Interview as the last confirmed stage, then add last-contact date, awaiting-response flag, and a no-response closure reason after your chosen review threshold.
This preserves what actually happened and still lets you report silence. It also distinguishes an application that never received contact from an employer that stopped responding after several interviews.
Separate status from next action
An application can remain Applied while the next action is “send referral note Friday.” It can remain Interview while the next action is “prepare case” or “wait for decision by Tuesday.” If tasks are encoded as statuses, the pipeline becomes hard to aggregate and dates become ambiguous.
Use owner, action, due date, and completion fields. A waiting state should reference the employer's commitment or your review date, not remove the stage.
Worked cleanup: the “maybe” pipeline
A candidate's tracker uses contacted, waiting, maybe, second call, final?, and ghosted. After cleanup, “contacted” applications return to Applied or Recruiter Screen based on confirmed events. Calls become interaction records. “Final?” becomes Interview with an unknown stage. “Ghosted” becomes the last confirmed stage plus no-response review.
The active pipeline shrinks, overdue actions become visible, and conversion by stage can be calculated without interpreting notes row by row.
Close records with neutral reasons
Use employer rejection, candidate withdrawal, role cancelled, offer accepted, offer declined, duplicate, expired before application, and no response as distinct closure reasons. Record confirmed detail, such as compensation misalignment, only when known. Avoid speculative labels such as “culture mismatch” unless the employer or candidate actually made that decision. Neutral data supports a more honest review later.
Keep closed records out of the active queue but available for review. If an employer reopens the conversation, create a new interaction and intentionally restore the stage; do not silently edit history.
Sources and editorial scope
- CareerOneStop: Create a job-search plan — U.S. Department of Labor-sponsored guidance on organizing a targeted search.
This guide separates verifiable facts from editorial judgment. Product features, platform behavior, hiring practices, and labor-market data can change, so the linked primary sources should be rechecked when a decision depends on them. No resume tool, score, or writing pattern can guarantee an interview or offer. Editorial review: August 20, 2026.
Put the guidance to work
Write entry and exit rules for the statuses you already use, merge ambiguous labels, and move tasks into a separate next-action field.
Practical questions
Is “no response” the same as rejected?
No. Use the last confirmed stage and a no-response closure or flag after a defined review point. The employer's decision may remain unknown.
How many statuses are enough?
Use the fewest that reliably change preparation, next action, or reporting. Many searches work with seven or eight primary states plus interaction records.
Should an offer be a status or outcome?
Offer is a useful active stage while a decision is pending. Acceptance, decline, expiration, or withdrawal closes it with a final outcome.