Skip to content
Back to the glossary

Candidate pipeline

Candidate pipeline: Definition & Guide

Definition

A candidate pipeline is the sequence of stages a person moves through for a specific role, from first contact to a decision. Each stage stands for a real step: not reviewed yet, screened, interviewing, offer, hired, or declined. The pipeline is the board you look at to see where the hire actually is. It is not the same thing as a hiring funnel report. The pipeline is the working list. The funnel is how you count drop-off between those stages.

Frequently asked questions

How many stages should a candidate pipeline have?

Enough to mark the decisions you truly make, and no more. For many small-team roles that is four to six: new, screened, interviewing, offer, and a clear outcome. Add a stage only when a different person owns it or a different question gets answered. If you cannot say what "done" looks like for a column, drop the column.

What is the difference between a pipeline and a talent pool?

A pipeline is tied to a live role and ends in a hire or a no. A talent pool holds people you may want later, including people who are not in any current search. Moving someone into a pool is not the same as advancing them. Mixing the two is how a board fills up with people you like and are not actually hiring.

Browse the full hiring glossary for more recruiting terms.

How a small team uses this

Candidate pipeline: Definition & Guide

Candidate pipeline: Definition & Guide is a working term, not a slogan. On a small team the word shows up when two people are looking at the same candidate and do not share a next step. Use the definition above as the sentence you paste into that conversation. If you cannot point at a field on the record that holds this idea, you are still only using the word.

Write Candidate pipeline: Definition & Guide into the place the work already happens. If it is a stage, the stage needs an owner and a date. If it is a document, the document needs to live next to the person it describes. If it is a metric, the metric needs a source you can open, not a number typed into a slide. Teams lose the meaning of Candidate pipeline: Definition & Guide when it moves from the record into a meeting and never comes back.

A practical check for Candidate pipeline: Definition & Guide: pick one open role and walk a single candidate through it. Note where the information for this term actually sits today. Inbox, chat, a spreadsheet, a person's memory. Then decide the one place it should sit next week. Do not redesign the whole process. Move this one fact. The glossary entry is doing its job if that move is obvious after you read it.

When you explain Candidate pipeline: Definition & Guide to someone new, use the example of a company small enough that everyone can see the failure. A missed reply, a second interview about a question that was already answered, an offer that described a different job. Those are the costs. Software can hold the field. It cannot decide that the field matters. That decision is the hiring manager's, and it is the reason this page exists.

Come back to Candidate pipeline: Definition & Guide when the team argues about a word instead of a candidate. Open the entry, read the failure mode, and ask which sentence in your last note would change if you used the definition. If none would change, you do not have a vocabulary problem. You have a decision you have not written down. Write that decision on the record, in the words this page just fixed.

Read this entry once next to a live role, not as a definition to memorise. Find the sentence you would actually paste into a note. If you cannot find it, the entry is still too abstract for your team, and you should use the failure mode instead. The failure mode is the part that tells you what the word is costing you this week.

Give the word one owner. A term everyone is responsible for is a term nobody updates. The owner is not a department. On a small team it is the person who already touches the record. Their job is to notice when the word in a meeting no longer matches the field. They change one of the two before the next hire.

Do not introduce the word in a slide before it exists as a field. People will repeat the slide. They will not create the field. The glossary earns its place after the field exists and someone is using it wrong. Correcting a live misuse is how the definition sticks. Announcing a vocabulary is how it dies in the same meeting.

When you write a post or a scorecard, use the words from the entries you actually rely on, and ignore the rest. A page that uses six glossary terms is showing off. A page that uses the one term your team confuses, and uses it the way the entry says, will be understood by the next person who opens it. That is the only test.

If two entries seem to describe the same thing, pick one and point the other at it. Duplicate words are how a small team builds two reports for one list of people. Keep the entry that matches the field in the product. Retire the entry that only matches a slide. A hiring glossary is finished when every remaining word is a field someone opens.

Qonir is ATS software for small teams. The job, the candidate, and the stage stay on one record.

Qonir keeps the job, the candidate, and the stage on one record.

Try Qonir for free