Talent rediscovery: your next hire may have already applied

Talent rediscovery is the practice of filling new roles from people who already applied: the runner-up from a final round eight months ago, the applicant whose skills missed that job but match this one. You already paid to acquire those profiles, in job ad spend and screening hours, and they already know your company. Done well, it is the cheapest and often the fastest sourcing channel a team has. The catch is legal before it is technical: retention windows and consent decide who you may contact at all.

Why is the database you already paid for the best place to start?

Every profile in your ATS cost something: board fees, employer brand work, recruiter hours spent reading and replying. When a new role opens, most teams write a fresh ad and pay all of it again, while hundreds of people who already raised a hand for the company sit untouched in the same system.

The arithmetic favors looking inward first. Past applicants skip the top of the funnel. They know the company, they were interested enough to apply once, and for the strongest of them you already hold interview notes and assessment results. A rediscovered candidate tends to move through the pipeline faster because half the evaluation already happened, and reply rates beat any cold channel because the relationship is not starting from zero.

One distinction worth keeping sharp: a talent pool is a set you deliberately curate and maintain, while your applicant database is everything that ever flowed in. Rediscovery is how raw history becomes a pool worth the name; the basics of building one are in what is a talent pool.

Who is worth rediscovering?

Not every past applicant deserves a second look. Four segments reliably do:

Segment	Why they convert	Check before reaching out
Silver medalists (final-round runners-up)	Vetted to the last step; lost on timing or marginal fit, not ability	How the rejection was handled, and whether the record is still inside its retention window
Near-miss applicants	Passed screening, cut at shortlist; a known quantity at zero acquisition cost	Whether the new role actually removes whatever blocked them last time
Skills-matured applicants	Applied junior two years ago and kept growing; your file underestimates them	That you refresh the stale facts before scoring, not after outreach
Withdrawn candidates	Pulled out for another offer or bad timing; the interest was real	Why they withdrew, and whether anything material changed on your side

Silver medalists are the headline segment, and the one where past behavior pays off or bites. A finalist who was rejected with a templated one-liner will not answer your re-engagement message; one who got a call and honest reasons often will. How you lose a finalist determines whether you can ever bring them back, which is the whole argument of rejecting a final-round candidate the right way.

Who are you allowed to contact at all?

Here rediscovery differs from ordinary sourcing: the legal question comes before the matching question.

Under GDPR you stored each application for a purpose, normally the specific vacancy. Keeping the data after that recruitment ends requires a retention window the candidate was informed about, or their consent to stay on file for future roles. When the window expires, the profile must go. A candidate who requested deletion, or opted out of further contact, is permanently off the list no matter how well they score against the new role, and a suppression list exists precisely so an enthusiastic recruiter cannot re-add them by accident. How long you may keep CVs, and on which legal basis, is a topic of its own: candidate data retention: how long to keep CVs.

The practical consequence is that your contactable database is smaller than your ATS, and that is the system working as intended. Run rediscovery only across profiles that are inside their window and carry no opt-out. If your tooling cannot filter on those two conditions, repair that before sending a single message, because the worst rediscovery outcome is not silence, it is a complaint to a data protection authority from someone you had no right to hold.

How do you write a message that acknowledges the history?

The most common re-engagement mistake is pretending the history does not exist. A cold-sourcing opener (“I came across your profile”) sent to someone who spent four hours interviewing with you reads as either dishonest or disorganized, and the candidate cannot tell which is worse.

Three parts make the message work:

• Name the history precisely. The role, roughly when, how far they got. It signals you keep records and respected their effort.
• Explain why now. Tie the new role to something specific they showed last time: a skill, a project, a stage they aced. Generic flattery undoes the first part.
• Shrink the ask. Propose a short call, not a fresh application. Never route a former finalist back through the application form, and never ask for information you already hold.

The tone shifts per segment. A silver medalist gets warmth (“you were a very close second, and this role plays to what we saw”). A withdrawn candidate gets a status check (“you chose elsewhere last spring; if anything changed, this one is worth a look”). A skills-matured applicant gets honesty about the gap (“the role you applied for was junior; this one is not”).

How do you make rediscovery routine instead of a one-off dig?

Treat the internal search as the first step of every intake, not an annual archaeology project. When a role opens, the order is search inside, then post outside.

A few habits keep it honest:

• Score past applicants against the new role’s requirements, never against the role they originally applied for.
• Refresh before you judge. A two-year-old profile contains two-year-old facts, and updating them has its own rules: refreshing stale candidate data compliantly.
• Expect duplicates. Rediscovered candidates often re-apply through the front door at the same time, and a clean merge matters for both history and consent state: see deduplicating candidate records in your ATS.
• Log every outcome. A “not interested right now” is pipeline signal; a “never contact me again” must land on the suppression list the same day.

Where does Recruitifly fit?

In Recruitifly, rediscovery is a conversation rather than a query language. Fly, the assistant that works across the whole platform, can search the talent pool, score past applicants against a new job, build a shortlist, and draft re-engagement outreach that references each candidate’s actual history, in the candidate’s own language. Every write is propose-then-confirm: Fly prepares the shortlist and the messages, and you approve each one before anything reaches a candidate. For messages going to people who already trusted you with their data once, we consider that the correct design rather than a limitation.

The compliance frame is part of the platform, not an afterthought: retention windows, consent tracking, deletion requests and suppression lists are built into the GDPR tooling, so who you may still contact lives in the system instead of in anyone’s memory.

Recruitifly is in private beta. If your database is full of strong people nobody has opened since the day they applied, talk to us and bring a live role; rediscovery is best demonstrated on your own data.