Building a candidate pipeline that survives the hire
Most pipelines die at offer-accept. A pipeline that persists is a data asset — and it makes the next hire dramatically faster.
Written for: Talent acquisition leads and hiring managers with recurring roles
Start from role families, not requisitions
A requisition is a moment. A role family is a pattern you hire against repeatedly — and it is the right unit for a pipeline.
- Group roles that share a requirement spine (e.g. mid-level RN, field service engineer, enterprise AE)
- Write the spine once as observable evidence
- Let individual requisitions differ only in the variable parts: location, seniority band, shift, language
Capture evidence once, reuse it forever
If your only record of a candidate is a CV file and a rejection reason, the pipeline is not reusable. Structured evidence is what makes rediscovery possible.
- Extract the facts: credentials, systems, scope, sector, dates
- Record the reason for every decision, including near-misses
- Tag the constraint that blocked a hire — timing, band, location — because constraints expire
Keep warmth honest
- 1
Set a decay clock
Treat any candidate untouched for six months as cold until re-confirmed.
- 2
Re-confirm, do not assume
Availability, salary expectation and location all move. Ask before you shortlist.
- 3
Give a reason to reply
A specific role beats a generic keep-in-touch note every time.
Never present stale availability as current
Showing a hiring manager a candidate who is no longer available costs more credibility than an empty shortlist.
What to measure
| Metric | What it tells you |
|---|---|
| Warm pool per role family | Whether the next opening starts from zero |
| Rediscovery rate | How often a hire comes from an existing candidate |
| Near-miss reasons | Whether your bar or your band is the real blocker |
| Decay rate | How fast your pool goes stale without contact |
Frequently asked questions
- How large should a pipeline be?
- Size matters less than freshness and fit. A small pool of re-confirmed, well-evidenced candidates outperforms a large stale list.
- Is a pipeline just a CV database?
- No. A database stores documents; a pipeline stores structured evidence, decisions and constraints, which is what makes it searchable later.
- Who owns the pipeline in a subscription model?
- You should. If a vendor keeps the pipeline when the contract ends, you were renting outcomes rather than building an asset.
- How do we handle candidates who said no?
- Record why. Compensation, timing and location objections expire — and those candidates are often the fastest second-time hires.
How TaaSFlow implements this
- Structured evidence is extracted per candidate and kept with the record
- Role-fit rediscovery surfaces existing candidates against new openings
- Decision reasons and near-miss constraints are captured, not discarded
- Availability is re-confirmed before a candidate is presented
Related guides
Where to go next