Candidate rediscovery for executive search: a mandate-first workflow

A new mandate arrives, and someone remembers an executive who nearly fitted a previous assignment. The researcher finds a profile, the consultant recalls a promising conversation, and an old note says “not quite right.” Before the team can act, it needs to reconstruct what that decision meant.

Was the concern about capability, the client's ownership structure, relocation, timing or a requirement that no longer applies? Has the executive's experience changed? Did they invite future contact? The name is familiar, but the decision is new.

Candidate rediscovery means finding relevant people in your existing records and re-evaluating them for a current search. For a specialist executive-search boutique, its useful output is a small set of defensible next actions: research further, discuss internally, re-engage appropriately or exclude from this mandate with a reason. An old shortlist alone cannot provide those answers.

Try this proposed workflow on one assignment using your existing CRM, approved notes and mandate records.

TL;DR

• Start with the current mandate’s outcomes and constraints; familiar names should not define the role.
• Recover why the earlier process ended, with the original source, author and date.
• Separate historical evidence from current facts and identify what fresh research or conversation must establish.
• Give each reviewed record a reasoned next action and owner; check relationship preferences and firm rules before reuse or contact.

Start with the new mandate's questions

Write the questions the current search must answer before looking for familiar names. Otherwise, the people the team remembers can quietly become the definition of the role.

A title such as “chief operating officer” is too broad. The client may need someone to integrate acquisitions, rebuild regional accountability or professionalise a founder-led business. Those demands imply different evidence, even when the title is identical.

Use three groups of criteria:

• Required outcomes: what the executive needs to deliver, and under what operating conditions.
• Relevant experience: the situations that would make those outcomes credible, including scale, geography and decision authority.
• Practical conditions: location, travel, compensation framework, reporting relationships and any agreed restrictions.

Distinguish a real requirement from a preference. “Has operated in a sponsor-backed business” might be necessary for one client and simply familiar to another. If it is a preference, let adjacent evidence remain visible instead of excluding it at retrieval.

The mandate kickoff checklist provides a place to establish these criteria and record later changes. Rediscovery should use the current agreed version, with its date. If the client changes the brief, identify which earlier exclusions need another look.

Frame a retrieval question: “Who has led integration across multiple operating businesses, and what evidence do we have?”

Search for experience and context, as well as titles

Use several routes into the existing records. Search relevant past mandates, target companies, experience terms, conversation notes and relationship owners. A person may have discussed the right work without holding the title your new client expects.

Build a small vocabulary around the actual problem. Acquisition integration might appear as post-merger integration, operating model redesign, shared services, consolidation or bringing regional businesses together. Record which terms you used so another researcher can see how the pool was assembled.

Software can support this retrieval, but the search mechanism matters. Greenhouse's Talent Rediscovery documentation describes an older workflow with stage, rejection-reason and scorecard filters, plus exact keyword matching in resumes and notes. Before interpreting an empty result, check how your own system retrieves records.

A missing keyword is weak evidence that a person lacks the experience. Equally, a keyword appearing in a note does not demonstrate that they personally led the work. Search terms help locate material for review; they do not complete the assessment.

Include people whose previous process ended for contextual reasons: a search was cancelled, the role changed, the candidate could not relocate or the timing was wrong. Review other records where substantive experience is relevant too. A finalist label is useful history, but it should not be the only gateway into consideration.

Keep fresh market mapping active alongside this work. Your records reflect the sectors, clients and people your firm encountered before. A new mandate may require a different pool, and an apparently rich database can still have substantial gaps.

Reconstruct the earlier decision

For each promising record, recover the reason the earlier process ended. “Rejected” is a status. It becomes decision evidence only when the underlying explanation is available and relevant.

Find the original note, its author, its date and the mandate criteria at that time. Separate the candidate's account, the consultant's assessment and the client's feedback. These may disagree, and collapsing them into one sentence removes information the next consultant needs.

Use the following review table as a working structure. It is a proposed template, not an assessment standard.

An earlier concern may remain decisive. If the current mandate requires a capability that was previously explored and found wanting, retrieve that evidence rather than dismissing the concern as old. But test whether the concern was actually about the person, or about the previous role's demands.

Avoid converting a client's shorthand into a permanent trait. “Too corporate” may have meant experience in larger organisations, a perceived communication style or uncertainty about working with a founder. Those are different propositions. Where the original reasoning is missing, mark it as missing and seek clarification if appropriate.

This is where well-structured candidate research and conversation notes make a handoff useful. The next consultant should be able to follow the evidence without needing the original researcher to remember every detail.

Separate historical evidence from current facts

An accurate historical note can still be unsuitable as a statement about today. “Would not relocate in March 2024” records a conversation at that time. It cannot support “will not relocate” indefinitely.

Keep the old statement with its date and add a separate current status: unconfirmed, updated or contradicted. Do this for role scope, location preferences, compensation expectations and interest in a move. Avoid overwriting the history so completely that the earlier decision becomes impossible to understand.

The ICO's UK GDPR accuracy guidance distinguishes historical records from misleading current statements and requires clarity about sources and opinions. It is under review following legislative changes. In your working record, make each material statement's date and status visible.

Fresh public research can establish that someone changed employer or took on a different title. It may not establish their actual remit, willingness to move or reasons for the change. Capture the source and access date, then state what it leaves unresolved.

A company announcement, for example, may describe an appointment across a region without specifying budget ownership. Treat it as a reason to investigate regional scope. Do not silently turn it into evidence of full regional profit-and-loss responsibility.

Some systems refresh profiles automatically. Ashby's May 2026 rediscovery release describes refreshed work history, location and education where available, alongside previous application and feedback context. Treat this as a feature description; it does not establish outcomes for boutique executive search. Even with refreshed information, a consultant still needs to judge which facts answer the mandate's questions.

Use a review decision that shows the next step

Create a compact review queue with an explicit rationale for each entry. A useful classification is:

1. Research further: the earlier evidence suggests relevance, but a material current fact is missing.
2. Review with the consultant: evidence is available, but its significance or a restriction needs judgment.
3. Consider re-engagement: the rationale is clear and the appropriate relationship owner has reviewed the approach.
4. Exclude from this mandate: a specific requirement or restriction prevents progression.

These are working decisions, not a ranking of a person's general quality. A candidate excluded from one mandate might be relevant to another. Keep the reason attached to the assignment.

For every positive entry, write two short sentences: why this person deserves attention, and what might invalidate that view. “Led integration following two acquisitions; responsibility for commercial integration remains unverified” is more useful than “strong candidate.” It gives the researcher a task and the consultant a question.

Ask a colleague to challenge familiar names and inspect adjacent records excluded by the first query. Check for narrow language or requirements the client never agreed.

Do not add a precise-looking score simply because the queue needs ordering. If a score is used, explain its inputs and uncertainty. An incomplete record should remain visibly incomplete rather than receiving a low score that appears to describe capability.

A fictional example: reopening a useful conversation

The following example is fictional. The people, firms, mandates and dates illustrate the process; they are not customer evidence.

A twelve-person boutique, Alder Search, receives a mandate for an operating leader at a European industrial services group. The agreed priorities are integrating acquired businesses and strengthening regional accountability. The client is open to adjacent sector experience. Relocation is not required, although regular travel is expected.

A researcher recalls Maya Chen, previously considered for a manufacturing COO assignment. Her record carries the outcome “candidate withdrew.” The researcher opens the underlying conversation note rather than excluding her through that status.

The June 2024 note says Maya described leading the operational integration of two service businesses. It also records that she declined a requirement to relocate. The previous consultant had identified a gap in manufacturing plant experience, which mattered to that client. Neither point automatically settles the new search.

The researcher checks current public information and finds a September 2026 company announcement naming Maya as a regional operating director. The announcement supports the appointment date and title. It does not confirm the scale of her integration work or current interest in another role.

The rediscovery entry now reads:

• Reason to review: earlier integration experience appears relevant to the new mandate; mandatory relocation and manufacturing plant experience are absent from the current brief.
• Historical evidence: Maya's account of two integrations, recorded by the consultant in June 2024; detail and outcomes need renewed exploration.
• Fresh evidence: September 2026 employer announcement confirms a regional operating director appointment.
• Open questions: current authority, integration responsibilities, travel preferences and appetite for discussion after a recent appointment.
• Decision: consultant review before any approach; no client presentation at this stage.
• Owner: the consultant who holds the relationship, with the researcher responsible for preparing the evidence.

The consultant may decide the recent appointment makes an immediate approach poorly timed. Alternatively, an appropriate conversation may establish that the new remit is materially different from what the public title suggests. Either outcome improves the record without assuming that rediscovery must produce a candidate for presentation.

The old note identified a connection; fresh research introduced a question that could change the approach.

Re-engage with a specific reason

Before contacting someone, check the relationship owner, contact preferences, relevant restrictions and the firm's approved outreach process. Familiarity should make the approach more considered.

The AESC professional standards commit its members to confidentiality and independent, objective judgment. Those principles matter when deciding which parts of an earlier conversation belong in a new approach and which should stay within the appropriate restricted record.

Explain why this opportunity may warrant a conversation, acknowledge the earlier context accurately and make room for circumstances to have changed. Avoid describing the person as available before they have said so. Where the mandate is confidential, use the level of detail the client has approved.

A fictional outreach opening could read:

We spoke in June 2024 about an operating role that required relocation. I am now working on an assignment where acquisition integration is central and relocation is not required. Your description of bringing two service businesses together came to mind. Would you be open to a brief discussion to establish whether the scope and timing could be relevant?

Adapt this to the actual relationship and approved communication channel. It makes a proposition to explore; it does not imply that the candidate has passed an assessment or agreed to be introduced.

After the conversation, record what changed. If the executive declines, capture the relevant reason and any contact preferences they choose to express. Do not infer a permanent lack of interest from silence or reuse an earlier explanation for a new response.

Keep reuse within the firm's data rules

Rediscovery should begin within records the firm is authorised to hold and use. Access to a note does not by itself settle whether its contents can be reused for another assignment or shared with another client.

In the UK, the ICO's purpose limitation guidance, updated in March 2026, explains that new purposes require compatible reuse and an appropriate lawful basis. Consent is not automatically the basis for every activity. Have the firm's responsible person resolve uncertain reuse under its policies and applicable jurisdiction before proceeding.

Retention also needs an existing rationale. The ICO's storage limitation guidance says retention should be justified by purpose and reviewed; it does not prescribe one universal period. That guidance is also under review. A rediscovery project should work within the firm's retention rules, rather than revive records that should have been removed.

Carry the decision into the mandate

When a person progresses, attach the current rationale, unresolved questions and next action to the new assignment. Keep the earlier mandate as context, with an accessible source trail for authorised colleagues. Do not copy an entire old dossier into a new client-facing document.

Use the client update template to communicate relevant progress and decisions at the appropriate level. Internally, distinguish a record reviewed from a person contacted, an interested executive and a candidate ready for presentation. These represent different amounts of evidence.

At the end of the first review, inspect the work itself: which prior decisions were understandable, which records required reconstruction, and what fresh mapping still needs to cover. These observations can guide better notes and handoffs. They do not establish that rediscovery improved placement quality or shortened a search.

Keep the review small enough for the named consultant and researcher to assess thoughtfully, leaving a decision and usable source trail.

Frequently asked questions

Should a previous rejection exclude someone from a new mandate?

Only if the underlying reason remains relevant. Recover the earlier criteria and distinguish a capability concern from timing, relocation or a changed role. Where the reason is missing, mark that gap. A status such as “rejected” or “withdrew” cannot explain suitability for a different assignment by itself.

What should be refreshed before re-engaging an executive?

Check current public role information and review the relationship owner, contact preferences and relevant restrictions. Identify which facts still require a conversation, such as actual remit, travel expectations or interest in moving. An updated title can establish a research lead without confirming availability or readiness for client presentation.

How can researchers search beyond previous finalists?

Search experience terms, past mandates, target companies and conversation notes as well as titles and process stages. Include contextual endings such as cancelled searches or relocation constraints. Record the retrieval terms and check the system’s matching behavior; an empty result may reflect search limitations rather than absence of relevant people.

What should appear in the new mandate’s record?

Attach the current reason for consideration, dated supporting evidence, unresolved questions and a named next action. Keep earlier decisions available to authorized colleagues without copying the entire old dossier into client materials. Distinguish reviewed, contacted, interested and ready for presentation: each status requires different evidence and communicates different progress.

If that work is difficult to keep connected, describe your candidate rediscovery task for Laisy early access. Laisy is your executive-search workspace: bringing candidate context, mandate progress and client updates together, from the first conversation to the next decision. Early access is personally supported alongside existing tools, using firm-approved data.

Editorial note: Prepared by Laisy with AI assistance from the cited sources. Worked examples are fictional.