Extended definition
Pipeline stages are how recruiting work gets structured into measurable, manageable units. Without them, candidates exist in undifferentiated piles — applied, in process, decided.
With them, every candidate has a current state, a defined next action, and an owner responsible for movement. Stages are usually configured in the ATS and feed the funnel analytics that drive recruiter management — pass-through rates, time in stage, drop-off patterns.
The right number of stages is enough to capture meaningful state changes without producing administrative overhead. Most TA functions use 6-10 stages depending on role complexity.
How pipeline stages work
A typical pipeline has 7 core stages:
- Sourced — Candidate identified but not yet contacted. Stage exit happens when outreach is sent.
- Contacted / applied — Candidate has been reached out to or has applied. Exit happens when they respond or are dispositioned.
- Recruiter screen — First conversation with recruiter to assess basic fit and motivation. Exit happens when recruiter decides to advance, hold, or decline.
- Hiring manager interview — First substantive interview with the hiring manager or initial assessor. Exit happens after the interview is scored and a decision is made on advancement.
- Onsite / loop — Full interview loop with the panel. Exit happens after all interviews complete and the debrief produces a hire/no-hire decision.
- Offer — Offer extended, in negotiation. Exit happens at acceptance, decline, or withdrawal.
- Hired — Offer accepted, paperwork complete, start date confirmed. Often paired with a separate “started” stage that triggers when the candidate begins.
Stages have entry criteria (what triggers a move into this stage), exit criteria (what triggers a move out), and an explicit owner for each stage. Without these definitions, candidates stagnate at boundaries — sitting in “in screening” for two weeks because nobody owns the movement out.
Some pipelines add additional stages — phone screen separate from recruiter screen, technical assessment as its own stage, executive interview as a final round. The exact stage configuration should match the actual process; configured stages that the team doesn’t follow are worse than fewer stages with higher fidelity.
Why pipeline stages matter
Pipeline stages are the structural foundation of every funnel metric. Pass-through rates, time in stage, drop-off patterns, recruiter throughput — all depend on accurate stage tracking.
Functions with weak stage discipline produce noisy data that can’t drive decisions. Functions with strong stage discipline can identify bottlenecks within days, run weekly reviews on aging candidates, and produce reliable forecasts on time-to-fill and offer-stage volume.
Beyond the analytics, stage discipline also produces clearer candidate communication — each stage has expected actions and timelines that recruiters can communicate confidently.
Common mistakes and misconceptions about pipeline stages
- Configuring too many stages — Pipelines with 15+ stages produce administrative overhead without proportional insight. Most funnels work cleanly with 6-10 stages; more usually means the team won’t update fidelity.
- Failing to update stages in real time — Stages updated weekly during a batch review aren’t operationally useful. Stages need to update as candidates actually move — usually within hours of the state change.
- No defined owners per stage — Stages without explicit ownership produce candidates who sit at boundaries because nobody owns movement. Each stage needs a named role accountable for progression.
- Using stages inconsistently across recruiters — If one recruiter uses “screened” to mean “passed screen” and another uses it to mean “screen scheduled,” the data is meaningless. Stage definitions need to be shared and enforced.
- Confusing pipeline stages with hiring process steps — Pipeline stages are candidate-state markers in the ATS. Process steps are workflow activities. They overlap but aren’t identical — a single process step can have multiple pipeline stages, and vice versa.
Frequently asked questions
What is a pipeline stage?
A pipeline stage is one defined step of the hiring funnel that candidates move through — sourced, applied, screened, interviewed, offered, hired. Each stage has entry criteria, exit criteria, and an owner who moves candidates through it. Without them, candidates exist in undifferentiated piles — applied, in process, decided.
How many pipeline stages should you have?
Most well-run pipelines use 6-10 stages. Fewer than 6 usually misses important state distinctions; more than 10 produces administrative overhead the team won't maintain. The right number balances diagnostic value against update fidelity. Configure stages the team will actually update.
Who owns each pipeline stage?
Different stages have different owners. Sourced and contacted stages are typically owned by sourcers or recruiters. Screening is recruiter-owned. Hiring manager and onsite stages are jointly owned by recruiter and hiring manager. Offer is recruiter-led. Each stage needs a single accountable role for progression.
What's the difference between a pipeline stage and a hiring process step?
Pipeline stages are candidate-state markers tracked in the ATS — where this candidate is right now. Process steps are workflow activities — what the team does at each phase of the search. They're related but not identical. Stages serve analytics; steps serve operational design.
How do you avoid candidates getting stuck in pipeline stages?
Through clear stage ownership (each stage has a named accountable role), defined SLAs (each stage has a target time-in-stage), automated alerts when candidates exceed thresholds, and weekly aging-candidate reviews. Without these mechanisms, candidates accumulate at stage boundaries and dropout rates climb.