Your ATS holds thousands of candidates you spoke to once and never again. That is not a talent pool, that is an archive. Below is how to turn it into something you can activate: the segmentation you need, what to write after a year of silence, which moments to automate, and how to read pool health.
Why a pool without contact evaporates
Candidate data has a shelf life. A mobile number stays usable for years, a work email address disappears the moment someone changes employer. Availability is even more volatile: someone who could start immediately in March is locked into a one-year contract by June. Certificates expire, travel willingness changes after a move.
Suppose: 8,000 records, and each year 20 percent of email addresses go bad. After two years of silence you are left with roughly 5,100 reachable people about whose start date you know nothing. Note: these are assumptions to show the calculation, not industry figures. The direction is the point, not the number.
Something else decays that sits in no field at all. Someone who has heard nothing for twelve months no longer sees you as his recruiter, but as an agency that called once. So you start just below zero.
Database or pool: the difference comes down to three things
Everyone calls their candidate file a talent pool. It only earns the name once all three of these exist.
- Segmentation: you can select a subgroup without a consultant scrolling through notes.
- A contact rhythm: it is fixed who gets approached when, including when there is no vacancy.
- A reason to stay in it: salary insight for his region, a free certificate renewal, or the promise that you only call when it genuinely fits.
That third point is skipped most often. Without something in return, the candidate is on a list he never asked to be on. With it, it becomes the place he sends his new number to.
Segmentation that makes activation possible
The test: can you select, within two minutes, everyone who becomes available next month, holds a valid safety certificate and lives within 45 minutes of Eindhoven? If not, your pool is not activatable, however large. These fields make it possible.
- Job family instead of job title: a picklist of ten to fifteen families, not free text.
- Home town plus travel radius in minutes. Kilometers mean nothing around congested cities, travel time does.
- Availability as a date field that expires by itself and asks for confirmation.
- Certificates with their own expiry date each: safety passport, forklift, first aid, welding methods.
- Shift and weekend willingness as separate yes/no fields. Often that is the first filter.
- Placement history with evaluation: client, duration, rating and reason for leaving.
- Date of last verified contact: the last time someone replied, not your last mailing.
Those last two are the most underrated. Placement history with an evaluation gives you a top segment of people you have already placed, by far your cheapest source. And without a date of verified contact you cannot measure pool health.
Data hygiene and the notes field that ruins everything
The classic pattern: a consultant hears that someone wants shift work, no weekends, and comes free on 1 November, and types it into the notes field. Fine for him, worthless for your pool: you cannot filter on it. A year later that knowledge is only recoverable by reading thousands of notes, which nobody does.
The minimum: anything you might ever select on lives in a structured field with a picklist or a date. Notes stay for nuance, never as the only place a fact exists. Make three fields mandatory when closing any placement (end date, evaluation, reason for leaving) and each quarter set aside records with no verified contact older than eighteen months.
If your ATS and CRM are separate islands, every correction disappears into one of the two. See the article on connecting your ATS and CRM for recruitment automation.
Re-activation: what to write after a year of silence
'We have a great vacancy for you' fails for three reasons: it is about you, great cannot be verified, and you ask the biggest step of someone who does not yet know who you are. A re-activation message has one goal: a reply that refreshes your data.
Example 1: the verification question
Subject: is this still right? Hi Sanne, we spoke last March about a service engineer role in Tilburg. Our records say you were willing to travel up to 45 minutes and hold a valid safety certificate. Is that still true, and are you committed somewhere until a set date? Two lines back is enough.
Example 2: the ending assignment
Hi Mark, our records say your assignment ends late September. We now have two assignments around Zwolle that line up with what you did before it, both day shift. Shall I send them, or do you have something already? If you do, I will keep quiet until next year.
Example 3: the expiring certificate
Hi Ali, your safety certificate expires in November. We run a group training every quarter and there are still places. Want one? You commit to nothing and you do not have to work through us, I just think it is a waste if it lapses.
All three mention a detail proving you know him, ask for something small and offer a way out. That last part actually raises reply rates, because saying no becomes cheap. And a no with a date attached is worth more than silence.
Triggers that beat manual campaigns
A quarterly mailing is timing based on your calendar. A trigger is timing based on his situation. Four moments worth automating.
- End of assignment minus six weeks: he is already thinking about what comes next and has signed nothing yet.
- Certificate expiry minus ninety days: a concrete, non-commercial reason, and you are the only one keeping track.
- Seasonal ramp minus eight weeks: work back from when your clients scale up, not from their phone call.
- Rejected at the final interview, plus three months: already screened, already motivated, fell short on one point.
Automating here does not mean a robot has the conversation, but that on day minus 42 the system puts a task with the right context in front of the right consultant. You can combine it with automated selection too; see AI sourcing in secondment practice.
Your pool as a paid audience, not just a mailing list
Most agencies use their pool purely as an email list. You can upload the same records to ad platforms as a customer list; the data goes encrypted and is matched against profiles. Part will not match, but the rest you reach without depending on an opened email.
The channels reinforce each other. Someone who saw your name pass by that week is more likely to open an email from that same agency. In reverse, your pool gives the platform the best basis for a similar audience: people you have actually placed, not everyone who once clicked. Segment those audiences as tightly as your mailings, by job family and region.
Consent and privacy, briefly
Record per candidate on what basis you approach him, when it was given and which channels it covers: email, phone and advertising use separately. Put a term on it with automatic re-confirmation instead of quietly keeping data forever, and make an opt-out work in one click everywhere, including your ad lists. This is not legal advice; have your retention periods reviewed by a lawyer.
Pool health: four numbers instead of headcount
Headcount is the vanity number everyone quotes. Twenty thousand records mean nothing if you place nobody from them. Measure this, per quarter and per segment.
- Reachability: the share of records with verified contact in the past twelve months.
- Freshness: the share with an availability date that is not in the past.
- Response rate on re-activation, including the no's, because those refresh your data too.
- Share of placements from the pool: what part of this quarter's placements came from existing records.
That last number ties to your margin: put the cost per placement of your regular campaigns next to it. Running the numbers on your recruitment funnel works exactly the same way.
Conclusion
A talent pool is not an asset but a habit. Segmentation decides whether you can select, data hygiene whether that selection is right, the contact rhythm whether anyone still picks up. Start small: pick one job family, get seven fields in order, send one verification question and measure the response.
Want your pool to produce candidates instead of storage costs? See on our services page how we set this up for staffing and secondment agencies, and bring your current file along to the conversation.






