Reactivating a candidate pool: the 5-step method

If you've read The dormant talent pool: the gold mine nobody exploits, the next question is a practical one: where do you start on Monday morning? Here's the method we've drawn from teams that genuinely turned their talent pool into a source of placements, as opposed to those who've been talking about it for three years without moving.

The idea isn't a six-month transformation project. It's a sequence of five steps, each actionable in a few days, where each one visibly pays off the previous.

Step 1. Measure what already comes out of the pool

Before anything else, stop debating in the abstract. Over the last twelve months:

• How many hires came out of the internal talent pool (a candidate already in the base before the need arose)?
• How many came from cold sourcing (LinkedIn, job board, referral)?
• What's the average time to fill when a placement comes from the pool, versus when it comes from external sourcing?

Most ATSs expose this raw data, badly: you often have to export it and cross-reference it by hand. That's fine, you're not after a perfect dashboard, you're after one number to show the team at kickoff.

The typical order of magnitude: between 5 and 15% of placements come from the pool in teams that have done nothing to wake it up, versus 30 to 45% in teams that have structured their interview data for the past twelve months.

That measurement becomes your baseline. Without it, you'll never know whether the effort you're about to put in pays off.

Step 2. Decide what you capture at each interview

This is the step that takes thirty minutes in a team meeting and changes everything.

An interview produces two kinds of data. The factual (skills, years of experience, mobility, salary expectations) and the qualitative (motivation, blockers, weak signals, market context).

Decide which 6 to 10 pieces of information each interview should produce as output, and which can be reused elsewhere. A few examples found in most teams:

• Key technical skills assessed, with level.
• Format preferences (fully remote, hybrid, on-site).
• Availability (possible start date).
• Salary expectation stated by the candidate.
• Type of role targeted (lead, hands-on, consulting, etc.).
• An explicit dealbreaker, for example "doesn't want to do management."

What sets this list apart from a plain free-text field is that it's shared. Sophie and Karim use the same grid, and the pool becomes consistent from one recruiter to the next.

Step 3. Structure the data at write time, not at read time

This is the technical step. Most teams try to read poorly written interview notes better. That doesn't work, it's the writing you need to change.

Two options depending on your setup.

Option A. Manual discipline

You keep your ATS, and each recruiter commits to filling in the 6 to 10 structured fields at the end of every interview.

Upside: zero cost. Downside: it holds for three weeks, then it drifts. The cognitive load at the end of an interview is too high for it to last. You see the gap widen between senior recruiters (who do it) and juniors (who stop by week 5).

Option B. AI-assisted structuring

The interview is recorded, with the candidate's consent, and an AI Act-compliant system automatically produces the 6 to 10 output fields, for the recruiter to validate in two clicks before pushing them into the ATS.

Upside: the structuring holds over time, because it's no longer an effort. Downside: you need a tool, and a tool that's genuinely AI Act-compliant (see The AI Act and recruitment so you don't get caught out).

This is the layer Hirify adds on top of your existing ATS, with no migration and without changing the candidate flow. The Hub listens to the interview (with consent), structures the output, and pushes the fields into the candidate profile in your ATS. The discipline disappears because there's no longer any discipline to keep up.

Step 4. Make the pool searchable in natural language

Once the interview data is structured at write time, you need to be able to query it in some way other than a static filter.

The test you can put to your current tool:

Find me 5 senior SOC profiles available in January, OK with 2 days on-site, who mentioned an interest in ransomware topics.

No rigid filter can answer that. A natural-language search can, provided the interview data is present, structured, and linked to the candidate profile.

What changes for the team once this building block is in place:

• The starting point for a new need becomes "what do we already have in the base," not "where do we post."
• Managers ask their own questions of the pool instead of going through a recruiter.
• Candidates already met but not placed surface automatically when a role matches. That's the most visible effect from the very first week.

Step 5. Measure the return, and show it

After 8 to 12 weeks, you redo the Step 1 measurement.

For the roles opened since the start:

• How many hires came out of the pool?
• How many short-lists were built faster?
• How many recalled candidates would have been lost if you'd started over from external sourcing?

These are the numbers to show leadership and the team. When the share of hires sourced from the pool goes from 10 to 35%, the discussion stops there, you keep going.

The effect on recruiters is qualitative too. The satisfaction of calling back someone you already know, instead of cold outreach, can't be quantified, but it retains teams better than a bonus.

The classic traps

Trying to structure everything retroactively

Don't try to go back through five years of interview history to structure it. It doesn't pay off and it discourages the team.

Start structuring from now on. The useful base builds up in three months. The old pool stays where it is, you politely forget it.

Confusing a talent pool with a CV library

We say it in the pillar guide, and we'll say it again: a CV is not a talent pool. If you structure only the CVs and not the interviews, you'll stay capped at what a standard ATS already does.

Buying a tool before doing Step 2

If the team hasn't agreed among themselves on the 6 to 10 criteria they want to capture as interview output, any tool will be misused. The grid must come before the tool, never the other way around.

Choosing a non-compliant tool

This is the new classic mistake since the AI Act came into force: picking a US tool that does the job but moves the data off-territory. DPO audit, blocker, six months lost. See the guide The AI Act and recruitment.

Key takeaways

• Measure the baseline before you move. With no starting number, there's no visible progress.
• Decide the 6 to 10 criteria to capture as interview output. Fewer fields, better filled, beats many empty ones.
• Structure at write time, not at read time. Manual discipline doesn't hold; compliant AI assistance replaces it.
• Query in natural language. A talent pool becomes useful when you ask it real questions, not when you apply filters to it.
• Re-measure at twelve weeks to show the team the ROI. That's what anchors the practice.