An old candidate database is not a ready-made campaign list. One person changed industries, another asked not to hear from your agency again and a third would genuinely welcome the exact mandate sitting on your desk. The useful question is who can be contacted now—and why.
When is a candidate eligible for reactivation?
A candidate is eligible for reactivation only when the agency can explain the current recruitment purpose, relevant lawful basis, original data source, current record quality, applicable contact restrictions, appropriate channel, genuine role fit and accountable human review.
Segment the candidate database into ready to review, needs update, restricted and not appropriate to contact. Do not assume that age, an old consent field or a high matching score alone determines permission.
The European Data Protection Board explains that retaining CVs for future hiring can rely on consent or, in suitable circumstances, a documented legitimate-interest assessment. In either case, candidates must be informed about the purpose; the correct choice depends on the facts.
Start with a specific recruiting reason
Reactivation should connect a real hiring need or clearly explained relationship purpose to the candidate’s existing context.
Identify the mandate, role family or genuinely relevant market conversation before generating a contact list. A candidate who discussed finance leadership is not automatically relevant to every executive vacancy. Record the candidate evidence that supports the connection and the colleague accountable for deciding whether it is appropriate.
Distinguish role-related contact from general promotional messaging. Rules for communication channels and marketing can differ across jurisdictions, and a general recruitment relationship does not automatically permit every kind of outreach. Ask local advisers when the classification or applicable channel rules are uncertain.
Check the lawful basis and candidate information
An old profile is usable only within a documented purpose and appropriate legal basis.
Review how the record was obtained, what the person was told, the purpose for retaining it and whether the agency relies on valid consent or an assessed legitimate interest. The EDPB recognises that either can be relevant depending on the circumstances; legitimate interest requires a balancing exercise, not a generic checkbox.
Where data was collected indirectly, check whether the candidate received the necessary information at the right time. A profile scraped into a database without a documented source or privacy notice should not be treated as a straightforward reactivation opportunity just because a parser can identify an email address.
Apply objections and channel restrictions first
Suppression is a gate, not a detail to review after an email sequence is queued.
Check withdrawal, objection, do-not-contact preferences, communication channel restrictions and candidate-specific client boundaries. Evaluate the scope carefully: a person may decline marketing while remaining in an active conversation about one named role. If the stored history is unclear, stop and seek an appropriate human decision.
Inspect related systems too. A recruiting CRM may show a restriction while a synced mailing list or historical spreadsheet still presents the address as active. Verify suppression before exporting, enriching or scheduling outreach, and ensure a newly recorded objection updates the actual sending workflow.
Assess freshness without assuming an expiry rule
Candidate data freshness depends on the decision being made, not on a universal number of months.
Check when employment history, location, seniority, contact method, availability and role preferences were last confirmed. A career history from last year may remain useful evidence; a personal email, salary expectation or willingness to relocate may require verification before it influences contact.
Separate factual age from legal retention. Neither GDPR nor general recruitment guidance gives one universal reactivation deadline. Establish review periods suited to your agency’s purpose, candidate expectations and relevant jurisdiction, then document exceptions rather than inventing a blanket rule.
Review role evidence and candidate preferences
A person should be contacted because the opportunity makes contextual sense—not because the database contains keywords.
Compare role scope, level, industry, location, language, compensation context, work arrangement and previously stated constraints. An AI match or resume parser can surface possible evidence, but a recruiter should examine why the candidate was suggested and whether the original information is still credible.
Avoid assumptions based on sensitive information or weak proxies. A surname, graduation year, photo or inferred family situation is not an appropriate shortcut for determining interest. Record enough professional context to justify the conversation without turning irrelevant personal characteristics into screening rules.
Choose an appropriate contact channel and cadence
The safest practical channel depends on the relationship, candidate preference, local communication rules and message purpose.
Respect known channel preferences and prior communication history. A business address, personal address, phone number and professional-platform message create different expectations. Check whether the address remains current and whether a particular message type triggers additional requirements under local law.
Use restrained follow-up. A relevant first message can explain why the recruiter is reaching out, how the person can respond and how to stop further contact. An unanswered message is not consent for endless reminders, and silence should trigger a review or stop condition rather than an escalating sequence.
Put a person between matching and sending
Human review should confirm candidate relevance, restrictions and message accuracy before any outbound contact.
Present the reviewer with the brief, supporting candidate evidence, original source, most recent verification, current preferences and contact-status result. Make uncertain or conflicting facts obvious. The reviewer should be able to exclude the candidate, request an update or correct the draft before anything is sent.
Track what happens after a permitted message: reply, correction, objection, successful conversation or no response. Feed corrections back into the candidate record and stop future contact when the person objects. Give the next recruiter enough context to understand the decision without keeping irrelevant personal details. Review failed matches with the original brief, because a precise correction is often more valuable than another hundred unqualified database suggestions. The goal is a healthier recruiting relationship, not the largest possible campaign volume.
An AI-generated candidate score is a prompt to review relevance. It is neither proof of identity nor permission to contact the person.
Candidate reactivation eligibility matrix
Give recruiters a clear decision at each gate before the candidate enters any outreach or follow-up workflow.
| Eligibility gate | Question to answer | Outcome when unclear |
|---|---|---|
| Recruitment purpose | Is there a specific, relevant role or relationship reason? | Do not queue a generic campaign |
| Lawful basis | Can the agency explain and document the current processing basis? | Refer to the privacy owner for review |
| Candidate information | Was the person informed about the purpose and data source? | Resolve transparency before contact |
| Objection or suppression | Does any system contain a relevant opt-out or restriction? | Block outreach and investigate scope |
| Record freshness | Are decision-relevant details current enough for this role? | Verify appropriate fields or defer |
| Role fit | Is there real professional evidence supporting the contact? | Remove unsupported matches |
| Communication channel | Is the channel suitable and permitted in context? | Select a safer route or ask for advice |
| Human approval | Has an accountable recruiter checked the complete context? | Hold the message until reviewed |
Limits of any reactivation checklist
A checklist cannot decide the correct lawful basis, national marketing rules or individual candidate expectations on its own. Those decisions depend on the agency’s notices, relationship history, jurisdiction and specific facts.
A relevant historic profile is not proof that a person wants to move jobs. Executive-search teams should prioritise careful relationship context; businesses looking for unrestricted high-volume messaging need a different operating model and should assess the associated risks separately.
Candidate reactivation eligibility FAQ
These answers distinguish usable recruiting relationships from stale database volume.
Does GDPR impose a universal talent-pool expiry date?
No. Retention and contact suitability depend on the documented purpose, lawful basis, candidate information, jurisdiction and review policy. An agency should set defensible periods rather than reuse an invented universal limit.
Do we always need consent to contact a former candidate?
Not necessarily. The EDPB explains that consent or a properly assessed legitimate interest may support storing CVs for future recruitment, depending on context. Channel-specific and national rules still need separate review.
Can an AI match automatically trigger outreach?
It should not bypass objections, lawful-basis checks, data freshness, candidate preferences or human approval. A match is evidence of possible relevance, not a contact permission.
What if a candidate never replies?
Follow the agency’s limited, documented cadence and review whether further contact remains appropriate. Silence does not refresh consent, establish interest or justify unlimited follow-up.
Official candidate-pool and processing guidance
These European sources explain candidate CV storage, legal bases and rights. Assess local communication rules separately before contacting anyone.
- European Data Protection Board: FAQ on storing candidate CVs for future recruitment
- European Data Protection Board: Process personal data lawfully
- European Data Protection Board: Respect individuals’ rights
Make candidate sourcing more selective
Audit candidate relationship management · Define clear candidate ownership · Review your talent sourcing strategy · Explore Yena candidate sourcing
Start with candidate context, not campaign volume
Review how Yena helps recruiters organise candidate evidence, relationship history and sourcing decisions around a real search mandate.
See Yena candidate sourcing