A candidate pipeline is the actively managed group of pre-vetted candidates being moved toward a specific current or near-term role, ready or nearly ready to enter the formal hiring process, not just sitting in a database.

How a pipeline differs from a talent pool in practice

A talent pool is broader and more passive: past applicants, sourced profiles, referrals and career-fair contacts kept on file without active, role-specific nurturing. A pipeline is the opposite, a curated shortlist a recruiter is actively engaging for a live requisition. A pool feeds a pipeline, not the other way round: when a role opens, a recruiter pulls the most relevant names from the pool and actively works them into the pipeline for that specific req.

Frequently asked questions

How many candidates should be in a healthy pipeline?

There’s no fixed number, it depends on the role’s difficulty and expected drop-off through screening and interviews, but a pipeline with only one or two live candidates leaves little room for a decline or a failed interview.

Does every applicant enter the pipeline?

No. Only candidates who pass initial resume screening move into the active pipeline for that role.

Who owns keeping the pipeline moving?

Usually the recruiter assigned to the requisition, coordinating with the hiring manager to keep candidates progressing without long, unexplained gaps.

See how pipeline movement is measured with the recruitment funnel and yield ratio.