How to build a talent pipeline for roles you hire again and again
On this page
- Decide which roles deserve a pipeline
- Define the profile before you collect names
- Work out how big the pipeline needs to be
- Where pipeline candidates come from
- Set up the pipeline in your ATS
- Keep in touch without spamming
- Privacy, consent and retention
- When a role opens: the refresh call
- Measure whether the pipeline pays for itself
- Questions people ask
To build a talent pipeline, choose the roles you hire repeatedly or cannot afford to fill slowly, define the profile for each, add people you have actually spoken to into a tagged pool in your ATS, and keep in touch on a schedule with something useful each time. A pipeline is working when a new requisition for that role produces first interviews in days instead of weeks.
This page covers the planning and upkeep. Finding people in the first place is covered by Boolean search strings for recruiters and how to source candidates on LinkedIn.
Decide which roles deserve a pipeline
Pipelines take ongoing work, so build them only where they pay back. Score each role family against four questions, from your own hiring records.
| Question | Build a pipeline if |
|---|---|
| How often do we hire this role? | Several times a year, or on a predictable cycle |
| How long does it take to fill from scratch? | Longer than the business can wait |
| How small is the qualified market? | Licensed, specialist or local roles with few candidates |
| What does a vacancy cost? | Revenue, safety or client commitments depend on it |
For an agency, add a fifth: which clients reliably send this kind of job order? A pipeline for a role only one unreliable client hires is a list, not an asset. Most teams end up with two to five pipelines, not twenty. The hiring plan template shows where the repeat demand is.
Define the profile before you collect names
A pipeline built from "anyone who might fit" cannot produce a fast shortlist. Write a one-page profile per pipeline and agree it with the hiring managers who will use it.
PIPELINE PROFILE: [Role family] Owner: [recruiter] Reviewed: [date]
Hired for: [teams / clients] Expected hires next 12 months: [ ]
Must-haves: 1. [license, certification, system or skill]
2. [ ]
3. [ ]
Level bands: [e.g. junior / mid / senior, with what separates them]
Locations: [on-site sites, commuting radius, remote rules]
Pay range: [current range per band]
Where they are: [employers, job titles used, associations, schools,
communities, events]
Knockouts: [shift pattern, travel, clearance, driver's license]
Pipeline target: [number of warm contacts, by band]The "where they are" line becomes your sourcing plan. The pipeline target comes from arithmetic, not ambition, as shown below.
Work out how big the pipeline needs to be
Estimate how many warm contacts you need so that enough are available when a role opens. The example uses invented rates; replace them with your own once you have six months of data.
| Step | Example figure | Result |
|---|---|---|
| Hires expected per opening | 1 | 1 |
| Interviews needed per hire (your data) | 4 | 4 interviews |
| Share of warm contacts open to a move when you call | 1 in 5 | 4 × 5 = 20 warm contacts |
| Share of those who are still a fit after a refresh screen | 2 in 3 | 20 × 1.5 = 30 warm contacts |
So, in this example, about 30 warm contacts per opening produce four interviews without new sourcing. If openings overlap, scale up. If your pipeline cannot reach that size in a small market, the pipeline still shortens time-to-fill; it just will not replace sourcing.
Where pipeline candidates come from
The best sources are people who already know you. Cold sourcing fills gaps.
- Silver medalists: finalists you did not hire. They have been assessed, they know the team, and many are worth a call when the next opening comes. Ask them directly at rejection whether you may keep in touch.
- Past applicants who were close: strong at screen but short on one requirement that time may fix, such as a certification in progress.
- Referrals for future roles: ask your best employees or placed candidates who they would want to work with again, even if you are not hiring today.
- Former employees or contractors who left on good terms.
- Community presence: associations, licensing courses, trade schools, meetups and hiring events where the profile gathers. See how to run a hiring event.
- Sourced candidates who replied "not now, but maybe later". That is a pipeline candidate, not a dead lead.
Set up the pipeline in your ATS
A pipeline in a spreadsheet dies the day its owner goes on vacation. Keep it in the system of record with a small, fixed set of fields.
| Field | Values | Why |
|---|---|---|
| Pipeline tag | One per role family | Pull the list in seconds when a role opens |
| Warmth | Ready now / 3–6 months / 6–12 months / long term | Decides contact frequency |
| Level band | From the profile | Matches people to openings |
| Last meaningful contact | Date | Shows who is going cold |
| What they want next | Short text, in their words | Makes the next call specific |
| Consent to keep in touch | Yes, with date and how given | Privacy and retention |
| Review or delete by | Date | Stops the pipeline becoming an archive |
"What they want next" is the field recruiters skip and the one that makes the next contact useful. The recruiting agency tech stack page covers how outreach and scheduling tools should write back to the ATS so these fields stay current.
Keep in touch without spamming
Contact frequency follows warmth. Every touch gives the candidate something, and at least one per year is a real conversation.
| Warmth | Contact | What to send or say |
|---|---|---|
| Ready now | Every 2–4 weeks | Specific roles, or an honest "nothing yet, here's when I expect one" |
| 3–6 months | Every 6–8 weeks | Market update for their role: pay movement, who is hiring |
| 6–12 months | Every quarter | Short personal check-in; ask if anything has changed |
| Long term | Twice a year | A useful resource, a congratulation on a new certification or role |
Subject: Quick check-in, and what [role] pay looks like in [area]
Hi [First name],
When we spoke in [month] you said you'd think about a move once
[their condition: the project finishes / you finish the certification].
Has that changed?
In case it's useful: the [role] offers I've seen in [area] this quarter
have been around [range you can stand behind]. [One line on demand.]
No role to pitch today. If your plans shift, reply here and I'll call.
[Your name]Only quote pay figures you have actually seen or can source. A made-up market update is worse than no update.
Privacy, consent and retention
Not legal advice. Keeping candidates' details for future roles is processing of personal data. Laws such as the GDPR and UK GDPR, and US state laws such as the CCPA as it applies to job applicants, can require notice, a lawful basis, limited retention and responses to deletion requests. See CCPA and job applicant data and how long to keep interview notes, and confirm your obligations with a qualified adviser.
- Tell candidates you would like to keep their details for future roles, and record their answer.
- Set a review-or-delete date on every pipeline record, and act on it.
- Keep only what you need to contact and match them. Interview notes about a past process do not belong in a pipeline record.
- Make it easy to opt out, and honor it across every tool, not only the ATS.
When a role opens: the refresh call
A pipeline candidate was assessed months ago, for a different opening. Before you submit or schedule them, run a short refresh call. It takes ten to fifteen minutes and catches the changes that sink a process later.
REFRESH CALL: [Candidate] Pipeline: [ ] Last spoke: [date]
1. "Last time you mentioned [what they want next]. Is that still
what you're looking for?"
2. "What has changed in your role since we spoke?" (new scope,
promotion, certification, manager)
3. Must-haves for THIS opening, asked with an example, not a yes/no.
4. Pay: current and expected, asked again. Do not reuse old numbers.
5. Notice, location, work setup, and any other processes.
6. "Can I put you forward to [client/team] for [role]?"
Record the answer and the date.Treat the answers as a new screen, and write the submittal or summary from this call, not from the old notes. Question 4 is the one recruiters skip, and pay expectations often change between calls.
Measure whether the pipeline pays for itself
- Share of hires from the pipeline for each role family.
- Time from opening to first interview for pipeline candidates versus newly sourced ones.
- Pipeline freshness: the share of records with a meaningful contact in the last six months.
- Conversion when called: of pipeline candidates contacted about a real role, how many were interested and still a fit. Feed it back into the sizing table above.
Review each pipeline quarterly with the hiring managers who use it. If a pipeline has produced no interviews in two quarters, either the profile is wrong or demand has moved; fix the profile or retire the pipeline.
Pipeline mistakes and the fix
| Mistake | Fix |
|---|---|
| Adding everyone who applied | Only people you have spoken to and who meet the profile |
| Mass newsletters instead of contact | Personal messages, at a frequency set by warmth |
| No "what they want next" recorded | Ask it on every call and write it in their words |
| Submitting from old notes | A refresh call before every submission |
| Records kept forever | A review-or-delete date on every record |
Questions people ask
What is the difference between a talent pipeline and a talent pool?
A talent pool is a group of people with relevant skills, often large and loosely qualified. A pipeline is the part of that pool you have actually spoken to, assessed to some degree, and keep in touch with for a specific kind of role, so it can produce an interview quickly.
How many candidates should a pipeline hold?
Work backwards from demand. If you hire a role four times a year and roughly one in five warm pipeline candidates is available and interested when a role opens, you need about twenty warm contacts to have four ready conversations each time. Use your own conversion data once you have it.
How often should I contact pipeline candidates?
Often enough that they remember you and rarely enough that it does not feel like spam: a personal check-in every three to six months for most people, and more often for a small group you expect to hire soon. Every message should give them something, such as market pay information or a relevant role.
Can I keep candidates' details indefinitely for a future pipeline?
Not necessarily. Privacy laws such as the GDPR limit how long you keep personal data and require you to tell people what you do with it, and US state laws add their own rules. Set a retention period, tell candidates you will keep their details for future roles, and confirm your obligations with a qualified adviser.