Candidate Pipeline Stages Template for Agencies 2026

Most pipeline templates copy the corporate ATS playbook. Apply, screen, interview, offer, hired. Five clean stages and a 7% conversion rate at the bottom. That structure is fine for an internal team filling thirty roles a year. It's noise for an agency that needs to know which of two hundred candidates across nine searches will actually close this month.

Agency pipelines work differently because the unit of value is different. You're not tracking applications, you're tracking the relationship between a candidate and a role. Same candidate, three roles, three pipelines. That's not a spreadsheet quirk. That's the business model.

This template lays out the seven stages that match how agency desks actually move, the conversion benchmarks each one should hit, and the diagnostic questions to run when one stage is silently killing your fee revenue.

The seven stages that map to real agency work

Forget five-stage funnels copied from Greenhouse marketing pages. Agency pipelines need seven, and the boundaries between them are where money lives or dies.

Stage 1: Sourced

You've identified the candidate as a potential fit but haven't reached out yet. They exist in your database with a role tagged. Common mistake: counting LinkedIn search results in this stage. They don't count until you've actively saved them with intent.

Stage 2: Engaged

You've sent a first message. InMail, email, mutual connection intro, anything. The clock starts here. If a candidate sits in Engaged for more than seven days without a response, they're effectively dead until you re-engage with a different angle.

Stage 3: Qualified

The candidate has responded and you've had a real conversation. You know their motivations, current comp, notice period, and whether the role you're working on is a genuine fit. Crucially: they've agreed to be put forward.

Stage 4: Submitted

The candidate's profile has been formally presented to the client. Resume, your write-up, salary expectation, motivation summary. This is the stage that separates pipeline noise from real candidate inventory.

Stage 5: Interviewing

The client has agreed to meet. This single transition is the most predictive of placement in your pipeline. LinkedIn's talent benchmarks show that candidates who reach interview convert to offer at roughly 30% across industries. Below stage 5, every metric is theatre.

Stage 6: Offer

The client has decided. Either an offer is on the table or one is being prepared. Note: include verbal offers explicitly. The lag between "we'll send paperwork tomorrow" and signed contract is where placements collapse.

Stage 7: Placed

Signed, started, and (for contingent searches) past your guarantee period. If you count placements at signature instead of start date, your replacement rate will eat your margin.

"The most expensive thing in recruiting is a candidate who reaches stage 5 and never moves. They occupy capacity, drain consultant time, and rot the forecast. Find them on Friday, kill them by Monday."

Conversion benchmarks per stage

Every desk has different math, but the shape of a healthy agency pipeline is remarkably consistent. These benchmarks come from a synthesis of SHRM research, agency operator interviews, and our own Yena customer data across roughly nine hundred active desks in 2025.

Run your last twelve months through this. Where you fall below the warning line is your highest-leverage operational fix. Most desks discover the leak is at Submitted to Interviewing, which is almost always a brief problem masquerading as a candidate-quality problem.

The downloadable framework

You can copy this structure into Notion, Airtable, Excel, or any ATS that lets you customise pipeline stages. The point isn't the tool; it's the boundaries between stages and the metrics they unlock.

For Excel, our recruitment tracker template already has a sheet structured this way, with conversion formulas built in. For Notion, the Notion tracker follows the same seven stages.

If you're inside a configurable ATS like Yena, the stages map one-to-one. Yena defaults to a six-stage pipeline (it merges Sourced and Engaged), and the seventh-stage view (Placed plus past guarantee) lives as a saved filter rather than a stage. Either approach works. What matters is that the boundaries you draw match what you actually do, not what an internal-corporate recruiting playbook tells you.

Diagnosing stage-by-stage failures

Each stage has a typical failure mode and a typical fix. Run this when one row in your benchmarks table is consistently red.

Engaged to Qualified is too low

Your outreach quality is the suspect. Check: are messages personalised beyond first name? Are you leading with the role's biggest selling point? Are you sending on Tuesday-Thursday between 7-9am or 5-7pm in the candidate's timezone? Gartner research on response rates puts personalisation as the single biggest lever, more than channel choice or send time.

Qualified to Submitted is too low

You're qualifying candidates who aren't actually willing to be put forward, or you're losing them between qualification and submission paperwork. Either way, the fix is to extend the Qualified conversation by one more cycle: send the role spec, get explicit verbal commitment, then submit within 48 hours.

Submitted to Interviewing is too low

This is almost never a candidate problem. It's a brief problem. Either your client doesn't know what they want, or you didn't extract it well enough at the start. Re-brief the client with three diagnostic questions: "what would make you reject a candidate on paper?", "who has succeeded in this exact role before, and what did they have?", "if we could only test one competency in the first interview, which one?".

Interviewing to Offer is too low

Two suspects. First, your candidates aren't prepared. Send a pre-interview brief covering the company, the interviewer's background, and the likely structure. Second, the client is shopping the market. Ask explicitly: "if this candidate ticks every box you've described, will you hire?" If the answer is anything other than a clean yes, the problem isn't your pipeline.

Offer to Placed is too low

Counter-offers, slow paperwork, or notice-period buyer's remorse. Counter-offers are best handled by anchoring the candidate to their original reasons for moving early in Stage 3, not negotiated against in Stage 6. Slow paperwork is a client problem you should escalate within 48 hours of verbal offer. Notice-period reversals are reduced by maintaining contact through to start date.

Frequently asked questions

Should we add a "Rejected" stage?

No. Rejection is a status, not a stage. Add a Boolean field for "active in pipeline" and filter your views accordingly. Adding a Rejected stage clutters reporting and makes funnel math meaningless.

How do we handle candidates we want to re-engage in six months?

That's a Talent Pool, not a pipeline. Move them out of the role's pipeline entirely, tag them with the reason and a re-contact date, and pick them up via a different workflow. Mixing active pipeline with future pipeline corrupts both.

What if a candidate withdraws at Stage 5?

Mark the submission as Closed-Withdrawn, log the reason in your notes, and run a five-minute post-mortem. The most expensive lesson in agency recruiting is the one you didn't write down. Was it counter-offer, brief mismatch, candidate cold feet, or family circumstances? Each has a different prevention strategy at the next role.

How do agency pipeline stages differ from in-house corporate stages?

The big differences: agencies have a Submitted stage that doesn't exist for in-house teams (because for in-house, the candidate goes straight from Qualified to first interview), agency pipelines tolerate the same candidate appearing multiple times across roles, and agency-side reporting weights stage 4 onwards far more heavily because that's where billable progress lives.

What pipeline stages do enterprise ATS platforms enforce?

Greenhouse, Lever, and Workable use customisable but constrained stage structures designed for in-house hiring. Bullhorn and Vincere are agency-native and let you build the seven-stage structure above directly. We covered the differences in our best CRM for recruitment agencies guide and in the Yena vs Bullhorn comparison.