Candidate pipeline health
A measure of whether each open requisition has enough qualified candidates at the right stages to produce a hire on target. It combines stage coverage ratios, velocity indicators, and aging signals to tell TA teams where pipelines are at risk before they stall.
Michal Juhas · Last reviewed June 14, 2026
What is candidate pipeline health?
Candidate pipeline health describes whether each open req has enough qualified candidates at each stage to hit the hiring target without an emergency restart. A single metric (total candidates in the ATS) tells you very little; what matters is the distribution across stages, how long candidates are sitting idle, and whether new profiles are entering fast enough to replace expected drop-off. Recruiters who monitor health by stage catch sourcing gaps and bottlenecks weeks before they become missed start dates.
In practice
- A TA lead opens a weekly digest from an ATS-to-Slack automation that flags three reqs as amber: no new sourced profiles in 10 days, one candidate aging past the 7-day phone screen SLA. She assigns a sourcing sprint before the hiring managers notice anything is wrong.
- A recruiter reports pipeline health to the hiring manager as a three-column table: stage, count, and days-in-stage. The conversation shifts from "where are we" to "what do you need from me to move these two forward this week?"
- A sourcing team tracks a "funnel health score" for each req, calculated from response rate trends and stage coverage ratios, updated daily from ATS exports. Red scores get a team triage call; green scores get a check-in every Friday.
Quick read, then how hiring teams use it
This is for recruiters, sourcers, TA leads, and hiring managers who need to agree on what a healthy pipeline looks like before a req goes sideways. Skim the first section to align on vocabulary. Use the second when you are building a monitoring workflow or a hiring manager review cadence.
Plain-language summary
- What it means for you: If you only check whether candidates exist in the ATS, you will miss the moment when a req goes from "fine" to "crisis." Pipeline health is the early warning system.
- How you would use it: Check stage counts and time-in-stage for each req at least twice a week. Flag any req where no new profiles entered in the last five days or where any candidate has sat in a stage longer than your SLA.
- How to get started: Pick your three highest-priority open reqs. Draw the current stage distribution on paper. For each stage, ask: if the next two candidates drop out, do I have enough behind them to still fill the role on time?
- When it is a good time: Always, but especially the week a req opens (to verify the sourcing plan is realistic) and two weeks before the target start date (to confirm you have an offer-ready candidate).
When you are running live reqs and tools
- What it means for you: At scale, manual stage checks break down. Pipeline health needs to be automated so TA leads see risk across 20 or 50 open reqs without reading every ATS record.
- When it is a good time: When you standardize your ATS stage naming so health calculations work consistently, when you build a weekly TA ops report, and when hiring manager satisfaction with TA becomes a target.
- How to use it: Wire your ATS to a recruiting webhooks flow that updates a health dashboard or Slack alert when stage counts cross thresholds. Combine with pipeline coverage reporting for the exec view.
- How to get started: Define health thresholds for your three most common role types (individual contributor, manager, technical specialist). Encode them in a scoring rule. Run the rule against last month's closed reqs to validate it would have caught the ones that slipped.
- What to watch for: Health scores that look fine because candidates are sitting in an early stage. Stage coverage is meaningless if no one is advancing. Always check both count and velocity together.
Where we talk about this
On AI with Michal live sessions, pipeline health comes up in the AI in recruiting and sourcing automation tracks, where we build weekly reporting flows and discuss what the health thresholds should be for different role types. Start at the workshops page and bring your current req list and ATS stage structure.
Around the web (opinions and rabbit holes)
Third-party creators move fast. Treat these as starting points, not endorsements, and double-check anything before wiring candidate data.
YouTube
- How to Manage Your Recruiting Pipeline (LinkedIn Talent Solutions) covers stage management fundamentals for in-house teams.
- Recruiting Metrics That Matter (SHRM) walks through conversion-based pipeline measurement with real examples.
- How do you track pipeline health across 30+ reqs? in r/recruiting is a practical thread on dashboards and manual workarounds practitioners actually use.
- What metrics do you use to know a req is in trouble? in r/recruiting collects early-warning signals from experienced recruiters.
Quora
- What is the best way to track recruiting pipeline health? gathers perspectives from in-house TA and agency recruiters with different tooling contexts.
Related on this site
- Glossary: Sourcing funnel metrics, Pipeline coverage reporting, Recruiting stage SLA metrics, Hiring manager funnel review, Workflow automation
- Blog: AI sourcing tools for recruiters
- Guides: Sourcers
- Live cohort: AI in recruiting workshop
- Membership: Become a member
Frequently asked questions
What does it mean when a pipeline is unhealthy?
An unhealthy pipeline has too few candidates to replace expected attrition at each stage. If you have two candidates at the offer stage and none advancing behind them, you have no cushion when one declines. Signs of poor health include a single candidate at any active stage, all candidates aging past your SLA without movement (see recruiting stage SLA metrics), no sourced-but-not-yet-contacted profiles waiting, and a conversion rate at one stage that drops significantly below your benchmark. Each req needs enough volume flowing through the funnel to absorb declines, withdrawals, and failed screens without restarting sourcing from zero.
How many candidates should be at each stage per req?
A common starting ratio for a single req: 30 to 50 sourced profiles, 15 to 20 initial contacts, 8 to 12 responses, 5 to 7 phone screens, 3 to 4 hiring manager interviews, 2 to 3 final rounds, and 1 to 2 offers. Adjust these ratios based on your actual conversion data (see sourcing funnel metrics). High-volume roles and niche technical roles have very different profiles. The ratios matter less than the directional logic: if you cannot project enough pipeline to absorb expected attrition at any stage, start sourcing or screening more now, not after the hire falls through.
Which metrics tell you pipeline health before it becomes an emergency?
Track three leading indicators: stage coverage (number of candidates at each stage relative to your historical need), time-in-stage (how long each candidate has sat in a stage compared to your SLA), and sourcing velocity (how many new profiles entered the pipeline in the last 7 days). A drop in sourcing velocity is the earliest warning signal. Rising time-in-stage usually means a scheduling or decision bottleneck. Stage coverage below threshold signals a sourcing gap. Link these to your weekly hiring funnel report so TA leads see risk before it becomes a missed start date.
How does AI help monitor pipeline health across many open reqs?
AI tools can aggregate ATS stage data, flag reqs where stage coverage or velocity is below threshold, and route alerts to the owner before the situation becomes urgent. Some teams use a GPT-powered prompt that reads exported ATS data and produces a daily digest of at-risk requisitions. Others wire ATS events to Slack via a no-code tool so a health check runs automatically each morning. The model surfaces the problem; the recruiter diagnoses the root cause (sourcing gap, screening bottleneck, hiring manager availability). See no-code recruiting automation and workflow automation for wiring patterns.
How do recruiters communicate pipeline health to hiring managers?
Present a single table or dashboard showing each req, the number of candidates at each active stage, the time-in-stage for the oldest active candidate, and a red/amber/green status. Do not send the full ATS data; filter to what requires a decision. When a req is amber, propose a specific action: "We have three candidates in phone screen this week; if conversion holds we will have two hiring manager interviews by next Wednesday." That shifts the conversation from status reporting to joint problem-solving. See hiring manager funnel review for the meeting cadence that sustains this feedback loop.
How do you connect pipeline health to sourcing priorities?
Map each req to a health status at your weekly TA standup. Any req showing amber on sourcing velocity should immediately trigger a sourcing sprint: revisit the ICP with the hiring manager, check whether the search criteria are filtering out reachable candidates, and activate a secondary channel. Healthy reqs need maintenance, not escalation. Connect the health view to your sourcing funnel metrics dashboard and your talent sourcing playbook so sourcers know exactly what a sprint looks like for each role type. Join an AI in recruiting workshop to practice building this triage rhythm with real requisitions.