Candidate database reactivation means re-engaging past applicants, silver-medallists, and archived contacts already sitting in your ATS — turning a write-only archive into your cheapest and often fastest sourcing channel by using AI to surface still-relevant people before you spend a penny on finding strangers.
Every recruitment team has two sourcing budgets. There's the visible one: the LinkedIn seats, the job board credits, the sourcing tool subscriptions. And there's the invisible one that nobody tracks: the thousands of candidates already in the ATS who cost real money to find, screen, and store — and who are currently doing nothing for anyone.
Candidate database reactivation is the practice of spending the invisible budget before the visible one. It's also, in most firms, the single highest-return sourcing motion available. This guide covers why, how to do it well, and where AI makes the difference between "theoretically a good idea" and "actually the first search you run on every mandate."
Why Your Dormant ATS Database Is Your Best Sourcing Asset
Your ATS database is the most cost-effective sourcing channel you have, because every candidate in it was already paid for — through the job board fee, the sourcing hours, the screening call, the ATS licence itself. The acquisition cost is sunk. Re-engaging them costs one message.
Beyond economics, reactivated candidates tend to respond at noticeably higher rates than cold outreach. They already know your firm, they survived at least one screen, and you have a legitimate reason to contact them: a role that fits what they were looking for. Compare that to a cold InMail to someone who's never heard of you and you're already ahead on every probability.
"We found the candidate for our toughest Q1 mandate in our own database. She'd finished second eighteen months earlier and we hadn't spoken since. She was placed within three weeks."
The silver-medallist pattern is particularly reliable. The candidate who came second for a role is often the best candidate you could source for a similar role six months later — more experienced, still interested in the type of position, and now with a positive memory of your process rather than no memory at all.
Why Most Databases Age Instead of Compound
The gap between "database as asset" and "database as graveyard" comes down to one structural problem: most ATSs are optimised for intake, not retrieval. Adding a candidate is frictionless. Finding the right one six months later, when their original tags no longer describe what the role actually needs, is a different problem that the ATS was never built to solve.
Standard ATS keyword search fails database reactivation in three specific ways:
- Tags decay. A candidate tagged "senior consultant" when they joined your database three years ago may now be a Director. The tag hasn't updated. The search misses them.
- Labels are inconsistent. Different consultants apply different tags. "BD Manager," "Business Development," and "Head of Growth" can all describe the same function, but a keyword search only returns one of them.
- The role description wasn't the search query. You describe the role to the hiring manager in plain language. You then have to translate that into a boolean string that matches the specific tags your team happened to use years ago. That translation step loses candidates at every stage.
How AI Makes Database Reactivation Reliable
AI sourcing software changes the database reactivation problem because it reads profiles semantically rather than matching keywords. You describe the role — in plain language, the same way you'd brief a colleague — and the system finds candidates whose experience means the right thing, regardless of what words were used on their CV or what tags were applied when they were entered.
The practical effect: candidates who would never surface in a keyword search become visible again. The consultant who titled themselves "transformation lead" shows up for a "change director" search. The engineer with "distributed infrastructure experience" surfaces for a "platform architect" role. People who were entered with incomplete tags — which is most of any large database — get a second chance to be found.
| Approach | How it matches | What it misses |
|---|---|---|
| ATS keyword search | Exact terms, applied tags | Synonyms, outdated titles, under-tagged records |
| Manual database browse | Recruiter memory + scrolling | Anyone the recruiter doesn't happen to remember |
| AI semantic search | Meaning of the role + meaning of the profile | Candidates whose profiles are genuinely sparse or empty |
A platform like Yena runs the database search as the first step on every new mandate — not an optional extra — so reactivation becomes the default, not the exception. The external search only starts where the database runs out.
Building a Reactivation Workflow That Actually Runs
The idea of reactivating your database is easy to agree with and hard to sustain without a process. Here's a repeatable structure:
Step 1: Set the database-first rule
No external sourcing search begins until the database has been queried for the new role. This needs to be a team norm, not a personal habit. If your sourcing platform doesn't enforce it automatically, add it as a mandatory step in your mandate-intake process.
Step 2: Score and filter the results
A list of fifty database matches isn't yet useful. Score them on skill fit, recency of last contact, and whether their situation has likely changed (long tenure → higher switch likelihood; recent promotion → lower). The top ten to twenty get a personalised message. The rest go into a pipeline watch list.
Step 3: Respect the GDPR clock
Reactivating old records requires a lawful basis to contact someone. For most agencies in Europe, that means either refreshing consent or running a legitimate-interest assessment. The practical answer: run a reactivation email to dormant segments — "we have roles that may suit you; click here to stay in touch" — and purge non-responders after a defined window. The GDPR for recruitment agencies guide covers what that looks like operationally.
Step 4: Refresh the data at first contact
Don't trust that an eighteen-month-old profile is still accurate. Use the reactivation message itself to invite an update: "Are you still open to opportunities in X? Would love to hear where you've landed." The conversation updates the record; the database compounds.
Step 5: Track your reactivation rate
Set a target: at least one candidate from your own database on every shortlist you present. Track it by consultant and by practice area. If a team's reactivation rate is near zero, the problem is either bad data hygiene or a missing workflow step — both fixable.
What Good Data Hygiene Looks Like
Reactivation only works if there's something worth reactivating. A few structural habits protect database quality over time:
- Mandatory fields at intake. Current title, current employer, and last-contacted date should be required, not optional. A record without these is effectively unsearchable.
- Regular enrichment passes. Once or twice a year, run your database through an enrichment tool to update email addresses, detect LinkedIn profile changes, and flag people who have joined companies you're trying to fill for — they're now off-limits, and knowing that early saves awkward conversations.
- Post-process notes. Every time a candidate reaches interview stage, someone should update the record with what the outcome was and why. That context is what turns a silver-medallist into a fast-track reactivation two mandates later.
- Retention-schedule automation. Set your ATS to flag records that haven't been touched in a defined period (typically two to four years, depending on your GDPR policy) for either re-consent or deletion. A clean database of engaged candidates beats a bloated one full of outdated ghosts.
"We did a data hygiene pass on five thousand records and found that about a third were candidates who would have been immediately relevant to mandates we'd already filled externally. The cost of bad data wasn't abstract — it was measurable."
Reactivation Metrics Worth Tracking
You can't improve what you don't measure. The numbers that matter for a reactivation programme:
- Database search rate — what share of new mandates were run against the database before external search? Should be 100%.
- Reactivation shortlist rate — what share of presented shortlists include at least one database candidate?
- Reactivation reply rate vs cold reply rate — the difference tells you exactly how much your existing relationships are worth.
- Database placement rate — what share of successful placements came from candidates already in your ATS? Track this quarterly.
For more on the metrics that actually predict placement revenue, the talent sourcing strategy guide covers how the find–rank–reactivate loop performs against each of those indicators.
FAQ
What is candidate database reactivation?
Candidate database reactivation is the practice of re-engaging past applicants, silver-medallists, and archived contacts already in your ATS rather than cold-sourcing strangers for each new mandate. Because these candidates already know your firm, they tend to reply at noticeably higher rates than cold outreach — and they cost nothing to discover.
How quickly does a candidate database become outdated?
Faster than most teams realise. Job titles shift, companies are acquired, people relocate, and career goals change — often within 12-18 months. A candidate who was not right eighteen months ago may be exactly right today, and their contact details may have changed too. GDPR retention schedules add another layer: records that have not been touched for years may legally need to be deleted.
What makes AI better at database reactivation than a standard ATS keyword search?
Standard ATS search matches keywords and manually applied tags. AI search understands the meaning of a profile — so a candidate tagged "project manager" still surfaces for a "programme director" search if their actual experience fits. It also surfaces people whose tags were poorly applied or never updated, which is most records in most databases.
How do you handle GDPR when reactivating old candidate records?
You need a lawful basis to contact someone — typically legitimate interest or a re-consent request sent before you pitch a role. Good practice: run a reactivation email campaign asking people to confirm they want to hear from you, then purge those who do not respond. Only contact records that passed that gate.
What reactivation rate should I expect?
It varies by how warm the relationship was, how recent the last contact was, and the quality of your message. Database reactivation typically outperforms cold sourcing significantly — but the right benchmark for your firm is your own historical data, not an industry average from a vendor's marketing page.