Candidate Rediscovery: A Practical Agency Workflow

Candidate rediscovery: start with the people your agency already knows

Candidate rediscovery means searching existing recruitment records for people who may fit a new opportunity, then checking whether their circumstances and interest are still current. It works best as a repeatable step at the beginning of a search, with a clear brief and a human review before outreach.

An old conversation can be a useful starting point. It might tell you why someone declined an earlier role, which work they enjoyed or when they expected to reconsider a move.

It cannot tell you that the same conditions still apply today.

The purpose of rediscovery is to identify a relevant conversation to reopen. Finding a record is the beginning of that work.

Define the search before opening the database

Write down three categories: required evidence, flexible preferences and facts that need reconfirming.

For an illustrative customer success leadership search, those might be:

• Required evidence: Has led a team responsible for enterprise renewals.
• Flexible preference: Experience with a similar product category.
• Reconfirm: Location, compensation expectations and interest in management.

This distinction helps prevent a familiar name from becoming a favourite before anyone checks whether the role is suitable.

If the brief is vague, clarify it with the client. A database search cannot resolve a disagreement about what the business needs.

Search from more than one direction

Start with the work the person must have done. Then try adjacent titles, related responsibilities and previous projects your agency handled.

Use whatever search methods your current system supports. A title search and a review of candidates from a relevant past assignment may reveal different people.

Write down useful search phrasing so the next recruiter does not have to repeat the same exploration. Also record where the search was unhelpful: missing notes, inconsistent fields or overly narrow criteria.

Connekt supports plain-language searches of your candidate database. See its approach to candidate search.

Read the record before writing the message

For each plausible candidate, check the source and age of the important information. A CV from two years ago and a conversation last month carry different kinds of context.

Look for commitments your agency made, recent contact from colleagues and any recorded communication preferences. Repeated messages from the same agency can make a supposedly personal approach feel careless.

Separate what is known from what is inferred. “Previously managed a renewals team” is evidence. “Probably wants another management role” is a question to ask.

Reopen the relationship with a specific reason

Here is an illustrative message:

Hi Morgan, when we last spoke, you were interested in leading a smaller team with more responsibility for customer strategy. I’m working on a role with that scope. Has that preference changed, or would a short overview be useful?

Only use a reference like this when the earlier conversation actually supports it. If your record is incomplete, acknowledge that you are checking rather than pretending to remember more than you do.

Make declining easy. Someone who is unavailable today may still appreciate an accurate, considerate approach.

Run a small rediscovery experiment

Choose one live role. Review a manageable cohort of existing candidates before expanding to new sources. Track how many records you assessed, how many supported relevant outreach and how many conversations confirmed a possible fit.

The cohort size is an operational choice, not a benchmark. Twenty records could be enough to expose a data problem without turning the exercise into a separate project.

Review the reasons for exclusion. If many people were wrongly located or no longer doing the same work, prioritise those data updates. If the records were accurate but unsuitable, revisit the search criteria.

Use the results to improve the next search, not simply to celebrate the size of the database.

Want to test this with your own workflow? Book a Connekt demo.

A common rediscovery question

How old is too old for a candidate record? Age alone is not enough to decide. Assess the information’s relevance and verify changeable facts before using the record to recommend an opportunity.