A pipeline converts the inherently chaotic process of evaluating multiple candidates for multiple roles into a managed workflow. Each stage represents a decision gate: candidates who meet the criteria for that stage advance; those who don't are rejected with a record of why. The result is a structured funnel with visibility into conversion rates at every point.
Pipeline stages vary by organisation and role type, but a typical setup includes: Application Received → CV Review → Phone Screen → Hiring Manager Interview → Technical/Skills Assessment → Final Interview → Offer → Hired. Each stage can carry its own evaluation criteria, scorecard questions, and required approvals before a candidate advances.
In an ATS, pipelines are usually visualised as a Kanban board — columns represent stages, cards represent candidates, and drag-and-drop movement reflects progression decisions. This visual representation makes it immediately obvious where bottlenecks are forming: a column with 30 candidates and no movement indicates a scheduling delay, an overloaded interviewer, or an unclear decision framework.
Talent pools — candidates who were strong but not selected for a specific role — can be preserved in the pipeline as a future hiring resource. When a similar role opens, these candidates can be surfaced and re-engaged rather than starting the sourcing process from scratch.
Key Points: Candidate Pipeline
- Stage definition: Pipelines are configured per job or per job type, with stage names and required actions defined in advance.
- Kanban visualisation: Cards-on-columns layout gives instant visibility into candidate status and pipeline volume at each stage.
- Conversion tracking: Stage-to-stage conversion rates reveal where candidates are being lost and whether the funnel is calibrated correctly.
- Collaborative access: All members of the hiring team see the same pipeline, eliminating the 'email the recruiter to find out where we are' problem.
- Talent pool preservation: Strong candidates who weren't selected can be held in a talent pool, tagged, and re-engaged for future openings.
How Candidate Pipeline Works in Treegarden
Candidate Pipeline in Treegarden
Treegarden's candidate pipeline uses a drag-and-drop Kanban board where each job has its own configurable stages. Recruiters can set up custom pipeline stages per job type, attach evaluation scorecards to each stage, and configure automated emails that trigger when candidates are moved. The AI Recruiter feature lets hiring managers query the pipeline in natural language — "show me candidates in final interview for the Product Manager role" — without navigating through filters. Bulk actions allow moving, rejecting, or emailing multiple candidates simultaneously.
Related HR Glossary Terms
Frequently Asked Questions About Candidate Pipeline
The right number of stages depends on the role complexity and the decision-making structure of the organisation. For high-volume roles — customer service, retail, entry-level positions — three to four stages is typically sufficient: application review, screening call, interview, offer. For specialist or senior roles, five to seven stages is common, adding layers like skills assessments, panel interviews, or executive sign-off. The risk of too many stages is excessive time-to-hire and candidate dropout — strong candidates who are in demand will disengage from processes that feel unnecessarily prolonged. Each stage should have a clear purpose: if you can't articulate what information that stage produces that the previous stage didn't, it should be eliminated.
A candidate pipeline is active and job-specific: it contains candidates who are currently being considered for a specific open role, moving through defined evaluation stages toward a hiring decision. A talent pool is passive and reusable: it contains candidates who have been previously sourced, screened, or interviewed — potentially for roles that are now closed — and retained for future consideration. Talent pools are valuable because they contain candidates who have already been partially qualified. When a new role opens that matches a talent pool candidate's profile, the recruiter can reach out directly rather than starting a new sourcing cycle. An ATS should support both: an active pipeline view for current openings and a searchable talent pool for future pipeline seeding.
Candidate dropout occurs at predictable friction points: when the application process is too long or complex, when communication goes silent for extended periods, when scheduling is difficult or takes multiple rounds of back-and-forth, and when the overall process feels disorganised or disrespectful of the candidate's time. Data consistently shows that top candidates — who are in demand and have multiple options — have the lowest tolerance for slow, poorly-organised processes. Reducing dropout requires: a streamlined application form that asks only for information needed at that stage; automated acknowledgement emails so candidates know their application was received; clear communication about next steps and timelines at every stage; and calendar integration that allows candidates to self-schedule interviews rather than waiting for a human to find a time.
Pipeline health is measured through a set of conversion metrics that track candidate movement between stages. The key metrics are: application-to-screen rate (what percentage of applicants pass the initial CV review), screen-to-interview rate (what percentage of screened candidates are advanced to interview), interview-to-offer rate (what percentage of interviewed candidates receive an offer), and offer acceptance rate (what percentage of offers made are accepted). Secondary metrics include time-in-stage averages (how long candidates spend at each stage before advancing or being rejected) and dropout rate by stage (how many candidates self-withdraw at each stage). Comparing these metrics across job types, departments, and time periods reveals where the pipeline is underperforming and what interventions are most likely to improve conversion.