Candidate Pipeline

How it works

A candidate pipeline is the full set of candidates currently active for a specific requisition, organized by stage — applied, screened, interviewing, offer extended — showing exactly where every candidate stands right now.

A pipeline is really a sequence of defined stages, with rules (sometimes automated, sometimes manual) that move a candidate from one to the next: an applicant becomes "screened" once a recruiter or an automated filter clears them, becomes "interviewing" once a slot is booked, and so on. The value of the pipeline view isn't the stage labels themselves — it's that every candidate's current stage, last contact, and next action due are visible in one place, updated in real time, instead of living in one recruiter's memory or a spreadsheet that's already stale by the time someone else opens it.

In staffing & high-volume hiring

At high volume, the pipeline view is the thing that actually gets used minute to minute: a recruiter running a dozen open requisitions needs to see, at a glance, which candidates are waiting on a reply, which are scheduled for an interview tomorrow, and which have gone stale without a status change in days. Without a shared, real-time pipeline view, that picture only exists in one recruiter's head — which is exactly what breaks when two recruiters touch the same requisition or someone's out sick.

Common mistakes

• Defining too many pipeline stages, which turns a quick status check into a scavenger hunt through granular sub-stages that don't actually change what happens next for a candidate.
• Letting candidates sit in a stage indefinitely with no "stale" flag or reminder, so a pipeline view that should show real-time status instead shows outdated positions nobody's acted on.
• Running parallel, undocumented tracking (a personal spreadsheet or notes app) alongside the shared pipeline, which recreates the exact single-point-of-failure problem a shared pipeline is meant to solve.