Silver-Medalist Talent Pool Re-Engagement
Every search that ends in a hire also produces one or more strong runner-up candidates — people who cleared the full loop and would have been hired for a different req — but once the search closes, those candidates disappear into the ATS as 'rejected' and are effectively invisible to future sourcing. When a new, similar req opens months later, recruiters typically start sourcing from zero rather than checking whether someone who already passed the bar for a comparable role is sitting in the database, which wastes both the recruiter's time and the goodwill of a candidate who went through a full interview loop and never heard from the company again.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 3-6 hrs per matched requisition in avoided external sourcing time, plus faster time-to-first-candidate on similar reqs.
How the automation works
We flag runner-up candidates at the close of every search — people who reached final stages and received positive feedback but weren't the selected hire — and keep them in an actively matched pool rather than letting them fall into an undifferentiated 'rejected' bucket. When a new requisition opens, the pool is checked automatically for candidates whose prior interview loop and scorecard closely match the new role's requirements, surfacing genuine matches to the recruiter before they start sourcing externally. Candidates in the pool get a periodic light-touch check-in rather than silence, so someone who's since taken another role or gone off the market gets removed from active consideration instead of getting a stale re-outreach months later.
Process flow
- 01
Search closes with a runner-up trigger
When a search closes, candidates who reached final stages with positive scorecard feedback but weren't selected are flagged as runner-ups rather than filed simply as rejected.
- 02
Enter structured talent pool ai
Runner-up candidates enter an actively maintained pool tagged with their scorecard strengths and the role type they were evaluated against, rather than disappearing into a generic rejected-candidates list.
- 03
Match pool against new requisitions ai
When a new req opens, the pool is checked for candidates whose prior loop and scorecard closely match the new role's requirements, surfacing genuine fits rather than a loose keyword match.
- 04
Light-touch periodic check-in output
Pooled candidates receive an occasional light check-in to confirm continued interest and availability, so the pool stays current rather than accumulating candidates who are actually off the market.
- 05
Surface matches before external sourcing output
Recruiters see pool matches for a new req before starting external sourcing from scratch, giving a warm, already-vetted option first look.
Inputs
- Closed-search candidate scorecards and outcomes
- Runner-up eligibility criteria (stage reached, feedback rating)
- New requisition requirements
- Candidate check-in response/availability status
Outputs
- Structured runner-up talent pool
- New-requisition-to-pool match list
- Candidate availability status log
- Time-to-first-sourcing-action reduction on matched reqs
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Filing a strong runner-up candidate under the same generic 'rejected' status as someone who failed an early screen makes them functionally invisible to future sourcing — the pool only works if runner-ups are distinguished by stage reached and feedback quality, not lumped with every other closed application.
- Matching purely on job title similarity between the old and new requisition misses genuine fits and surfaces bad ones — a candidate evaluated against a very different set of actual requirements under a similar-sounding title isn't necessarily a match, and the comparison needs to work off scorecard content, not title text.
- Re-outreaching a pooled candidate without having checked in on their status first risks contacting someone who's already accepted another role or is no longer interested, which reads as the company having no idea what happened after their last interaction — worse for goodwill than not reaching out at all.
- A talent pool that's never pruned accumulates stale entries faster than it accumulates useful ones — candidates who've gone off-market, taken other roles, or simply lost interest need to be identified and removed via check-ins, or the pool degrades into noise a recruiter learns to ignore.
Frequently asked questions
How is a runner-up different from any other rejected candidate?
A runner-up reached final interview stages and received positive scorecard feedback but wasn't the selected hire, as distinct from candidates who didn't clear earlier stages — that distinction is what makes them worth re-engaging later.
Does the matching just look at job titles?
No — matching compares the candidate's actual prior scorecard and interview loop content against the new role's requirements, since similar titles can mask very different actual requirements.
How do you avoid contacting someone who's already taken another job?
Pooled candidates receive periodic light check-ins to confirm continued interest and availability, so outreach on a new match isn't based on stale status.
Does this replace the recruiter's decision to reach out?
No — it surfaces qualified matches from the pool for the recruiter to review and decide on, rather than auto-contacting candidates without human judgment involved.