Field notes · July 29, 2026 · 5 min read
How to reactivate old candidates (without getting ignored)
> Editorial Note (August 2026): This post was written during an earlier phase of Voco, when our exploration focused heavily on building software for recruiting teams. While the observations about friction in those workflows remain true, Voco now operates more broadly to build custom AI systems for operational teams. You can read more about why we stopped starting with software.
A search closes. The role gets filled, the file gets archived, and the six or eight candidates who didn't get the offer move to wherever "not this time" candidates go in most ATS setups — technically still there, practically invisible. Then a new req opens, close enough in shape to the old one that a name from that closed search crosses a recruiter's mind. Most of the time, that thought passes without anyone acting on it, because reopening an old file and reaching back out feels like more work than it should.
Why reactivation gets skipped
It's not that recruiters don't believe in it. Ask any recruiter with a few years in the seat and they'll tell you a story about placing someone from a search that had nothing to do with the role they got hired for. The skip happens for practical reasons: the old file is buried in a closed requisition, the candidate's status field says something unhelpful like "rejected" with no note on why, and there's no clean way to ask "who from my last twenty searches would actually fit this one" without opening files one at a time.
Sourcing from scratch, by comparison, feels like forward motion. It's the same reason a cluttered desk gets ignored in favor of a fresh page — reactivation requires reconstructing context that already existed once, and starting over doesn't.
Step 1: Figure out who's actually worth reaching back out to
Not every past candidate is a reactivation candidate. Before writing anyone a message, it's worth being specific about what "worth another conversation" means for the role in front of you:
- The core requirement match is close, even if the title or level isn't identical.
- The reason they didn't get the last offer wasn't about the fundamentals — timing, a narrower need on that search, budget, or another finalist who was a marginally closer fit for that specific role.
- Enough time or circumstance has plausibly changed that reaching out isn't redundant.
Here's a hypothetical version of that: a candidate interviews well for a Senior Financial Analyst role and loses out to a finalist with more industry-specific experience. A similar Analyst opening comes up on a different team nine months later — same core skill set, different reporting line. That's a strong reactivation candidate. A candidate who withdrew from the same search because the base salary didn't clear their floor is a weaker one, unless this role's range is meaningfully different.
Step 2: Re-verify before you reach out
Old notes go stale. Before sending anything, a quick pass confirms the basics still hold: is the contact information current, does the candidate's public profile suggest they're still in a similar role or open to one, and is there anything in the notes — a hard requirement, a location constraint, a reason they were cautious about outreach — that should shape how the message gets written. This step is quick, and it's the difference between a message that reads as informed and one that reads as a mail-merge.
Step 3: Write a reactivation message that doesn't sound like a form letter
The message that works references the specific thing connecting the old conversation to the new one: what the role is, why it's different from the last one they saw, and why their name came up again. "I know it's been a while, but a role just opened that reminded me of our conversation about X" reads as attentive. A generic "I have an opening you might be interested in" reads as the same message every recruiter sends to their whole database — because for a lot of recruiters, it is.
Step 4: Log what happens, either way
A "not interested" or "not a fit" response is still useful information for the next search. The recruiters who get the most value out of reactivation over time are the ones who close the loop — a short note on why this attempt didn't land makes the next reactivation decision for this person faster and better-informed, instead of starting the whole evaluation over from nothing.
Judgment still calls the shots
None of this replaces a recruiter's read on a person. A process for surfacing who's worth a second look is only useful because it narrows the list to reconsider — the actual call on whether someone's right for a specific role, and how to approach them, stays exactly where it's always been: with the recruiter who knows the client and the role.
Where this gets faster
The slow part of reactivation isn't the judgment call — it's getting from "twenty closed searches" to "the three or four people actually worth a second look" without opening every file by hand. That's what Voco is built for: give it the role you're working on and the candidates you already know — a CSV export of a closed search works — and it shows you who's worth reaching back out to and why, before you write anyone off or start sourcing new. Ask Voco.
Worth accounting for too: if candidate data has drifted since the last search, a stale record can make a good reactivation candidate look like a dead end. And once you've got a list of names worth revisiting, ranking who to call first is its own separate step.