Candidate rediscovery: how to re-engage the candidates already in your ATS
By Drippay, Inc.Published 8 min read
Candidate rediscovery is filling an open role from people already in your ATS or CRM: past applicants, runners-up on similar roles, contractors whose assignments are ending, and sourced or imported profiles that never converted. Talent rediscovery is the same idea, usually as an ATS feature name; candidate re-engagement is the follow-through of getting a rediscovered candidate to reply.
This guide covers how rediscovery works inside an ATS and through connected tools, a workflow to run on a real req, re-engagement messages, the data habits that decide whether it works, and how to measure it.
What is candidate rediscovery?
A recruiting database holds people the firm has met in some way: some interviewed and lost on timing, some applied and were never reviewed, some were imported from a job board or a previous system and have no history at all. Rediscovery goes back to those records when a new req opens and asks who might fit before a new search starts.
The appeal is that an internal record can carry history an external profile never will: what the person was interviewed for, why they were not placed, what they were paid. The cost is real too. Searching takes recruiter time or software, contact details expire, and any history has to be reconfirmed before it is trusted. The vocabulary overlaps, so here is how this guide uses it.
| Term | What it means | Typical starting point |
|---|---|---|
| Candidate rediscovery | Searching your own ATS or CRM for people who may fit a new req | A live req and a database of past applicants and sourced profiles |
| Talent rediscovery | The same idea, usually the name an ATS vendor gives its feature | Filters over past applications inside the ATS |
| ATS candidate rediscovery | Rediscovery run over ATS records, natively or through a connected tool that indexes them | A native Find talent feature, or an ATS connected to an overlay search or matching product |
| Candidate re-engagement | Re-contacting a rediscovered candidate and getting a reply | A shortlist, a consent check, and a message that references the history |
| Redeployment | The staffing case: placing a contractor whose assignment is ending | Recorded end dates, reconfirmed with the candidate and the client |
How ATS candidate rediscovery works
Native ATS features work over the fields your team filled in. Greenhouse documents Talent Rediscovery as filtering and searching prospects and past applicants for a current job, drawing on application data such as scorecards and rejection reasons plus keyword search across resumes and notes. Bullhorn’s Amplify Match identifies candidate matches for open jobs and notifies recruiters; Bullhorn’s own guidance recommends starting with a small, high-quality pool and prioritizing recently engaged candidates and silver medalists.
Connected tools index the ATS and search it from outside, often adding cross-role matching and outreach. Gem documents ATS application filters for job, tag, rejection reason, interview stage, and scorecard rating, excludes candidates with active applications by default, and lets a recruiter add results to a project or sequence. Alex describes Talent Match as matching ATS candidates to open roles on skills, experience, location, and past interview data without exporting the records. SquarePeg describes sourcing for open roles from ATS applicant history and deep-linking back to the ATS profile for outreach.
Manual searches with boolean strings and available filters are another option. Their usefulness depends on the fields your ATS indexes, your plan, and the time spent refining the query.
Related: Candidate rediscovery tools compared by use caseBoolean search in recruitment
A rediscovery workflow to run on one req
Before buying anything, run rediscovery by hand on one live req. The result tells you whether your data can support it.
- Pick a req with a clear spec and a hiring manager who gives feedback.
- Apply the hard filters first: location or shift, credentials the client will not waive, work authorization.
- Pull segments separately, because each gets a different message: runners-up on similar roles, contractors with assignments ending soon, applicants never reviewed, and imported records with no history.
- Check consent and retention on each record before contact. A do-not-contact request or a record past your stated retention period is not a lead.
- Reconfirm before relying on history. An assignment end date recorded at placement may have moved; availability from an old profile is a hypothesis, not a fact.
- Send a re-engagement message that names the earlier interaction and asks one question. Log every outcome, including silence, and record a rejection reason for anyone who does not progress.
A worked example: a light industrial team opens a second-shift forklift req in a suburb it already serves. Shift, certification, and commute radius cut a database of tens of thousands to a few hundred. The finishing-assignment segment gives a dozen people the team has placed before, pending a call to confirm end dates. The runner-up segment gives a dozen more who interviewed for a similar role. That is a shortlist to test before a job board is opened, and the exercise fits in an afternoon.
Re-engagement messages that respect the history
A re-engagement message has one advantage over a cold one: shared history. Use it in the first sentence, be specific about the new role, ask for a yes or no, and never imply the candidate applied for this role.
Hi Dana, we spoke last spring about the quality inspector role in Elk Grove; you were a close second and the client went with an internal transfer. A similar role just opened with a different manufacturer nearby, second shift, same certification. Open to a quick conversation this week, or should I leave you be?
Names the earlier interaction honestly, explains the outcome without blame, and offers an easy no.
Hi Marcus, our records show your Northside assignment wraps up around the 28th; tell me if that has changed. We have a maintenance tech opening at a food plant twenty minutes from you, day shift, starting the first week of the month. Want the details, or is your next thing already lined up?
Treats the recorded end date as something to confirm, not assume.
Related: Candidate outreach: tools, automation, and templates
Data habits and metrics that make it work
Rediscovery tools rank whatever they are given. Bullhorn’s Amplify guidance says matching performance improves when candidate and job data is standardized and up to date, and recommends normalizing titles and skills and standardizing employment history. The habits that matter most: record a rejection reason on every non-progression, normalize titles and skills against one list, record and reconfirm assignment end dates, verify contact details before a batch, and apply a written retention policy. Ask counsel how consent and retention apply in your markets.
Measure the share of the pipeline that came from the database, not the size of the database.
| Metric | How to compute it | What a weak number points to |
|---|---|---|
| Rediscovery shortlist rate | Reqs where the database produced at least three qualified candidates, over all reqs | Database coverage or filter quality |
| Re-engagement reply rate | Replies over re-engagement messages sent, by segment | Message quality, expired contact data, or the wrong segment |
| Database share of submittals and placements | Submittals or placements from existing records, over all | Recruiters skipping the database, or shortlists that do not survive the client interview |
| Time to first submittal | Hours from req open to first candidate sent, rediscovered versus newly sourced | Whether rediscovery is actually faster for your team |
Track these for your own team. Vendor case-study percentages describe other firms under other conditions.
Discuss this workflow with dreach
dreach is a managed service for staffing firms, run by hand in the pilot. It watches the employers your firm knows and the ones it can reach through a warm path, such as a current or past client, a person your firm placed who now works at the hiring company, or a contact your team authorizes. It flags new openings with the source and date, confirms the hiring manager to contact, and shows the warmest way in. For a live role, it ranks people your firm already knows from its own ATS, past placements, and network your firm authorizes, and shows why. Your team makes every contact; dreach contacts no one. Scope, data access, integration requirements, and availability are confirmed before starting.
Curious how this fits your workflow? Bring a real req and we can talk through which ATS records and intro paths are worth checking first.
Discuss your candidate workflowRelated: How staffing agencies get job orders
Candidate rediscovery is a habit backed by clean data: for every new req, pull the runners-up, finishing contractors, and unreviewed applicants, reconfirm what the records claim, re-engage with a message that names the history, and record the outcome so the next search is better. The tools speed it up; rejection reasons and normalized titles decide whether it works.