Recruitment pipeline stages and template

A candidate pipeline is a shared workflow that records where one person stands for one role, from initial sourcing to a final outcome. A recruitment pipeline is the wider view of all those candidates moving through defined stages for a mandate or hiring process.

The practical purpose is simple: a recruiter should be able to open the pipeline and understand what has happened, what must happen next, who owns that action, and what the candidate has been told. It is not a talent pool, a to-do list, or a substitute for recruiter judgment.

This guide uses seven stages—sourcing, screening, submitted, interviewing, offer, placed, and rejected. They match the workflow in the CandidatePulse visual recruitment pipeline, where candidate management software keeps the record and its mandate context connected, but the definitions and template can also be adapted to a spreadsheet or another recruitment system.

What makes a recruitment stage useful?

A stage should describe a real process state, not an intention. “Interviewing” should mean that an interview is confirmed or underway—not merely that somebody needs to schedule one. Tasks describe work to do; stages describe where the candidate is now.

Give every stage four elements:

• An entry condition: the evidence required before a candidate moves in.
• An owner: the person responsible for the next action or escalation.
• A communication expectation: what the candidate should know and by when.
• An exit condition: the event that justifies the next stage or a closed outcome.

Clear definitions matter because vague stages produce misleading reports. They also make communication automation risky: a message triggered by the wrong status can promise an interview that is not confirmed or follow up after the process has ended.

The seven candidate pipeline stages

1. Sourcing

The candidate has been identified for a specific mandate but has not completed qualification. They may have applied, been referred, been found through research, or already existed in a permitted talent pool.

Record why the profile appears relevant, its source, and whether outreach has begun. A candidate should not move to screening simply because a message was sent. Use a meaningful signal—such as a reply, an agreed conversation, or an application ready for review—as the exit condition.

Candidate communication at this stage should explain why the recruiter is reaching out, identify the role accurately, and make it easy to decline. Do not imply interest or suitability that the person has not expressed.

2. Screening

The recruiter is validating mutual interest and the role’s essential requirements. Typical topics include experience, motivation, availability, location, work authorization where relevant, and expectations that can lawfully be discussed.

Define what a completed screen looks like. It may be a structured call plus recorded notes, or an application review followed by confirmation of key facts. Keep assessment criteria related to the role and avoid recording unnecessary sensitive information.

Before leaving screening, the candidate should know the likely next step and when to expect an update. Move them to submitted only when the profile is ready and the agreed submission requirements are satisfied.

3. Submitted

The candidate’s profile has been presented to the client or internal hiring stakeholder. The stage begins when the submission actually occurs—not when the recruiter plans to prepare it.

Record the submission date, who received it, and the feedback window communicated to the candidate. If consent or confirmation is part of your process, obtain it before sharing the profile. Do not tell the candidate an interview is likely unless the hiring stakeholder has made that clear.

The next state should be driven by a real outcome: an interview is confirmed, the submission is declined, the candidate withdraws, or the process is otherwise closed.

4. Interviewing

At least one interview is confirmed or underway. Keep the participants, format, time, location or meeting link, preparation responsibilities, and feedback owner visible to the people who need them.

Multiple rounds can remain within one interviewing stage if each round is recorded clearly. If your operation regularly loses visibility between rounds, add substages or structured fields rather than using ambiguous notes.

Only send confirmed logistics. After each conversation, tell the candidate when feedback is expected—even if the honest update is that the client is delayed. The stage ends when another round is confirmed, an authorized offer process begins, or the process closes.

5. Offer

A formal or authorized offer process is active. An informal indication that the client “likes the candidate” is not enough to enter this stage.

Record the offer date, decision deadline, agreed next contact, and the person authorized to answer questions. Compensation, conditions, start dates, and legal documents should come from approved sources; a generic template must not invent or alter them.

Keep the recruiter available without manufacturing urgency. Exit when the candidate accepts, declines, withdraws, or the offer is formally withdrawn. Each outcome should stop any follow-up that no longer makes sense.

6. Placed

The candidate has accepted and the placement is complete according to the desk’s agreed definition. Decide whether acceptance, signed documentation, start date, or another event is the official placement point, then apply that definition consistently.

Record the outcome and any operational handoff. Onboarding, guarantee periods, invoicing, and post-placement care may belong in separate workflows; do not overload the recruitment stage with every downstream activity.

Placed is a terminal pipeline outcome. Messages written for sourcing, screening, or offer follow-up should no longer be pending.

7. Rejected

The candidate is no longer progressing for this mandate. This includes a hiring decision, an unsuitable match against role-related criteria, a candidate withdrawal, an unresponsive process closed after reasonable attempts, or a role that was cancelled.

Use a small, useful set of internal closure reasons instead of turning the stage into a judgment about the person. Separate “client declined,” “candidate withdrew,” and “role cancelled” if those distinctions help improve the process.

Close candidate communication promptly and respectfully. Share only feedback you are authorized and able to communicate. Rejection is terminal for this mandate, not a permanent label on the candidate or their suitability for other roles.

Copyable candidate pipeline template

Copy this table into your operating document, spreadsheet, or system configuration. Replace the bracketed fields with rules your team can actually follow; delete any column you cannot keep current.

Use this checklist before adopting the template:

• Every entry and exit condition can be verified.
• One named role owns the next action at each stage.
• Candidate updates make realistic commitments.
• Placed and rejected stop obsolete tasks and messages.
• Withdrawal, role cancellation, and client rejection remain distinguishable where useful.
• Access, retention, and note-taking rules fit your privacy obligations.
• The same definitions are used in reviews and reports.

If you operate several searches at once, apply the same core definitions across mandates. The guide to managing multiple candidate pipelines explains how to separate process state from tasks and review the desk by exception.

Define transition rules before automating anything

For each stage change, write a transition rule in this form:

When [verifiable event] happens, [owner] moves the candidate from [current stage] to [next stage], records [minimum evidence], stops [obsolete actions], and sends or schedules [appropriate update] by [realistic deadline].

For example: when the client confirms an interview, the recruiter moves the candidate from submitted to interviewing, records the confirmed round and participants, cancels any “waiting for feedback” follow-up, and sends verified logistics after reviewing them.

That rule is deliberately stricter than “move the card and send an email.” It separates the business event from the software action and identifies what must be reviewed. For a detailed communication workflow, see how to automate candidate follow-up emails without losing recruiter control and the product overview for stage-triggered candidate email automation.

Assign ownership without creating bottlenecks

Ownership should follow the next commitment. A sourcer may own first contact, a recruiter may own screening and candidate updates, an account owner may chase client feedback, and an operations colleague may handle post-placement administration. Smaller desks may assign all those responsibilities to one person, but the pipeline should still make the current responsibility explicit.

Define an escalation path alongside the owner:

• Who follows up when client feedback misses its expected date?
• Who corrects or cancels a message containing outdated information?
• Who can close a stalled candidate or paused role?
• Who checks that terminal outcomes have no pending communication?

A daily review should focus on commitments at risk, not on moving cards for appearance. Start with overdue feedback, failed communication, long inactivity, and offers near a genuine deadline.

Measure flow without reducing candidates to numbers

Pipeline metrics are operational signals. They can reveal friction, but they cannot explain candidate quality or make a hiring decision on their own.

Start with a small set:

• Current inventory: the number of active candidates in each stage, separated by mandate.
• Time in stage: how long candidates wait before a meaningful transition or update.
• Stage conversion: the proportion moving from one defined stage to the next.
• Closure reasons: why processes end, using consistent and relevant categories.
• Communication reliability: whether promised updates were sent, failed, or became obsolete.

Interpret the numbers in context. A specialist role may spend longer in sourcing; a delayed hiring panel may inflate interview time; a role cancellation can lower conversion without reflecting recruiter performance. Look for repeated patterns across comparable mandates before changing the workflow.

Do not optimize only for speed. Rushing screening or pressuring offer decisions can damage accuracy and candidate experience. A healthy pipeline combines clear progress with truthful communication and evidence-based decisions.

Keep candidate communication attached to the stage

Every stage creates a different information need. A sourced candidate needs a relevant reason for contact; a submitted candidate needs honest expectations; an interviewing candidate needs confirmed logistics; and a rejected candidate needs respectful closure.

Templates can help teams keep those basics consistent, but they still require review. The recruitment email sequence templates by pipeline stage provide adaptable starting points. If silence is the main problem, use the process in reducing candidate ghosting with clearer follow-ups to set expectations and treat inactivity as a prompt rather than a label.

A practical rollout for a small recruitment desk

You do not need a complex process redesign to make the pipeline useful:

1. Write the seven entry and exit conditions in plain language.
2. Test them against five recent candidates, including a withdrawal and a cancelled role.
3. Resolve any case where two recruiters would choose different stages.
4. Add the minimum owner, evidence, and candidate-update fields.
5. Run the workflow manually before attaching automated messages.
6. Review exceptions weekly and change definitions only when the same ambiguity repeats.

The goal is not to force every recruitment process into identical steps. It is to make the shared state dependable enough that recruiters, candidates, and hiring stakeholders are not operating from different versions of what happens next.