Past placements
Known relationship, known delivery history and often the strongest context. Refresh current availability and preferences before assuming fit.
Do not reactivate your database until you know which records are worth reactivating.
Candidate reactivation works best as an operating system, not a one-off blast. The first job is to identify which existing candidates are current enough, searchable enough and relevant enough to reconnect with.
Check reactivation readinessNo candidate data is collected.
What candidate database reactivation actually means
Reactivation is the structured reuse of candidate relationships already held in your ATS or CRM. It usually starts with people who have a known connection to the agency: past placements, previous submissions, strong shortlists, recurring role families or candidates whose availability may simply have changed.
It is not the same thing as exporting every old email address and running a generic campaign. The quality of the underlying data, the relevance of the segment and the context of the previous relationship all matter.
Candidate reactivation readiness check
Tick what is true today. This is a directional operating check, not an industry benchmark.
Prioritise segments before you prioritise volume
Previous submissions
Candidates already considered for relevant work. Review why the earlier process ended and whether the present role changes the decision.
Strong shortlists
People who were credible but not selected. They can be valuable when similar demand returns.
Recent dormant candidates
Profiles with useful context but no recent activity. Re-engagement can primarily refresh status rather than pitch a role immediately.
Old low-context records
Low priority until contact data, relevance and relationship context can be established. Age alone is not a reason to contact.
Duplicate or fragmented records
Clean or merge first. Reactivating duplicates can create a worse candidate experience and further damage recruiter trust in the ATS.
A six-step reactivation workflow
- Choose the demand first. Start from recurring roles, active desks or a clearly defined talent segment rather than from the entire database.
- Build the candidate segment. Use role history, skills, geography, previous submissions and relationship history to narrow the population.
- Run a data-quality gate. Check duplicates, contactability, stale fields and whether recruiters can understand the previous relationship.
- Reconnect to refresh, not assume. Availability, salary expectations, location and role interest may all have changed.
- Write the new information back. Reactivation should improve ATS quality instead of creating another spreadsheet or side list.
- Measure downstream reuse. Track whether reactivated candidates progress into conversations, shortlists, submissions or placements rather than measuring messages sent.
The data-quality gate comes before outreach
If the team cannot trust contact details, skills, location or previous activity, reactivation can amplify the very database problem you are trying to solve. Before scaling outreach, check whether the target segment is:
- reachable enough to contact appropriately
- searchable by the fields recruiters actually use
- free from obvious duplicate or fragmented profiles
- specific enough to connect to real current demand
- supported by enough relationship history to make renewed contact intelligible
If these conditions fail, improve database utilisation and data quality before increasing campaign volume.
How reactivation relates to sourcing cost
Every agency still needs external sourcing. The operational question is whether recruiters are repeatedly paying in time or media spend to rediscover candidate supply that is already present internally.
Useful measures include recruiter sourcing hours, monthly sourcing spend, new candidates added, candidate reuse and the share of relevant roles where recruiters searched existing records before starting a new external search.
Do not treat reactivation as a guaranteed savings percentage. Measure whether the process actually changes sourcing behaviour and candidate progression in your own operation.
When not to scale candidate reactivation yet
- The team cannot reliably identify who was contacted and why.
- Duplicate records make ownership or communication history unclear.
- The database is not searchable enough to create relevant segments.
- Recruiters do not have a clear process for updating refreshed information.
- The proposed audience is simply "everyone inactive" rather than a defined candidate group.
Fixing these foundations first usually produces a better system than adding more automation on top of weak data.
Privacy and candidate relationship matter
Reactivation is not a universal permission to contact every historical record. Applicable privacy, consent and electronic-communication rules depend on jurisdiction and on the nature of the candidate relationship. Build the workflow so that recruiters can understand the contact history and apply the rules that govern the agency's market.
Frequently asked questions
Should we reactivate every inactive candidate?
No. Start with segments where current demand, usable data and prior relationship context make renewed contact relevant.
Does reactivation replace new sourcing?
No. It reduces avoidable repeated sourcing where the agency already has suitable candidate relationships. Net-new sourcing remains necessary for coverage gaps and changing markets.
What should we measure first?
Measure whether recruiters can identify useful segments, refresh candidate data and reuse those candidates downstream. Message volume alone is not a useful success metric.
Measure whether your database is ready to create more reuse
The Candidate Database Health audit uses aggregate operating numbers only. No candidate records or CVs are uploaded.