Executive search candidate research notes: a template for useful handoffs

A useful candidate note lets another consultant continue the work without guessing what happened. They can see why the person entered the search, what the evidence supports, what the candidate actually said, and which question needs answering next.

A career history may leave transformation responsibility unclear; a short summary may conceal an inference from a job title.

This suggested template supports continuity within your existing candidate system and firm-approved records: context to act, evidence to challenge and clearly marked limits.

TL;DR

• State the next decision the note supports, then connect evidence to the current mandate criteria.
• Separate public facts, candidate statements and dated consultant judgment; keep uncertainty beside the claim.
• Preserve source references, contradictions and promised follow-ups so the next colleague can continue the work.
• Prepare client-facing material for its audience rather than exporting the full internal note.

Start with the decision the note should support

Research notes, conversation notes and client candidate reports serve related purposes, but they should not be interchangeable.

An initial research note might support a decision to approach someone. A first conversation note might support a decision to involve the lead consultant. A later assessment note might support a decision to present the candidate to the client. Each stage asks for different evidence, and each should make its limits visible.

The AESC guide to choosing an executive search firm describes longlist reports that include interaction notes and later shortlist reports that include assessments and analysis against role competencies. This distinction matters: an early note is an input to further evaluation, rather than a substitute for it.

Write the immediate decision near the top. For example: “Decide whether to arrange a consultant conversation about multi-site operational integration.” This focuses both research and reading. It also gives the next person a reason to examine the relevant gap instead of repeating the candidate’s whole career story.

Before designing the note, identify the current mandate criteria. If the brief is unclear about what successful integration means, a better note cannot resolve that ambiguity. Use the mandate kickoff checklist to connect candidate evidence to agreed outcomes, scope and priorities.

Keep facts, statements and judgment visibly separate

Three kinds of information often become one sentence: public information, an account given by the candidate, and the consultant’s interpretation. Separating them does not mean distrusting the candidate. It means preserving how the team knows something.

Compare “Built the European operation” with a more useful sequence:

• Public source: company announcement identifies the candidate as regional operations director during the expansion period.
• Candidate statement: candidate says they integrated three acquired businesses and managed the regional operating team.
• Consultant judgment: experience may be relevant to the client’s integration challenge; personal authority over the integration budget is not yet established.

The second version gives the reader a way to test the interpretation. It also prevents a company’s growth story from becoming proof that one executive caused the growth.

For UK operations, the ICO’s guidance on accuracy calls for opinions to be identified and historical records to be recognizable as historical. This guidance is under review; check the current position for your firm.

As a working practice, label a judgment with its author and date. “Consultant assessment, 7 October” is more informative than an unattributed tag such as “strong leader.” Keep uncertainty beside the claim it qualifies. A disclaimer at the bottom does little if the first paragraph already presents an untested assumption as fact.

A compact candidate research note template

Use a small shared core rather than a form that tries to anticipate every search. The fields below are intended to support a handoff. Add detail when the mandate needs it, and allow “not yet established” as a legitimate answer.

Do not make every field mandatory at every stage. Before contact, motivation may be unknown. After an exploratory call, notice period may still be unconfirmed. Recording those gaps is more useful than completing the form with guesses.

Keep the narrative easy to scan, with supporting material retrievable through the approved record. Each sentence should answer a specific working question.

Record sources so a colleague can inspect the claim

For public research, capture the source title, publisher, publication date where available, access date, and the specific fact used. In your working system, keep the original link or an approved source reference. A bare link gives the next reader extra work and may later lead to a changed page.

A company biography may support a current title. An annual report may explain the scale and structure of a business. A conference profile may describe the executive’s remit at the time of the event. None automatically establishes the executive’s personal contribution to a particular result.

Match the source to the claim. If the claim is that someone held a role, an employer announcement may be useful. If the claim is that they personally redesigned a distribution network, seek a specific account of their responsibilities and decisions. Record whether that account comes from the candidate, another source, or a later verification step.

Do not count repeated versions of the same announcement as independent corroboration. Two biographies that copy the same company description still share one underlying account. Similarly, a referral is evidence that someone recommended the executive, rather than proof of every capability attributed to them.

When sources disagree, preserve the disagreement and identify the next check. “Company page lists regional responsibility; candidate describes global project responsibility” can be a useful question. Silently choosing the broader interpretation changes the evidence before a consultant has examined it.

Take conversation notes against the mandate

A conversation should leave a record of relevant evidence and the candidate’s position, rather than a transcript of everything discussed. Start with the business problem behind the criterion, then record the example offered, the candidate’s role, the context, and what remains unclear.

For an integration mandate, that might mean distinguishing participation from accountability. Who set the operating model? What decisions did the candidate own? Which functions reported to them? What changed, and what evidence describes the result? What would they do differently in the client’s circumstances?

The US Office of Personnel Management’s structured interview guidance describes using predetermined questions and consistent rating standards across candidates. It is general selection guidance, rather than a bespoke executive-search framework, but the principle is useful: a common evidentiary core helps readers compare relevant answers.

Executive conversations can still follow unexpected lines. Consistency does not require every exploratory call to become a rigid assessment. It means that a polished communicator and a reserved communicator should both be asked for evidence against the important mandate criteria.

Avoid turning conversational style into unsupported competence judgments. “Explained the integration sequence clearly and identified two tradeoffs” describes an observation. “Board-level presence” needs a defined meaning and a reason it matters for this role. Otherwise, the phrase is difficult for a colleague to examine or use fairly.

Preserve motivation and candidate care

Keep capability and interest in separate fields. An executive can look relevant on paper and have little reason to pursue the opportunity. Another may be interested but need more information before deciding whether a further conversation is worthwhile.

Record the candidate’s actual position: willing to hear more, interested subject to learning about the board, unavailable for this mandate, or awaiting clarification. Do not convert willingness to speak into willingness to join. Date the statement, because circumstances can change.

The AESC Candidate Bill of Rights places confidentiality and open communication among the expectations candidates can have of AESC members. A working note should therefore help the next colleague maintain the relationship: what has been shared, what remains confidential, what was promised, and what the candidate expects next.

Record practical constraints only to the extent relevant and appropriate. If travel is a concern, note the working arrangement the candidate can consider. A detailed account of their family circumstances is rarely necessary to explain that constraint. Keep sensitive disclosures within the firm’s approved handling process.

Finish the conversation record with commitments. If the researcher promised to clarify the reporting line, the next consultant should know that before making another approach. Candidate care becomes harder when promises live only in someone’s memory.

Worked example: a fictional COO research handoff

The following example is entirely fictional. The people, companies, dates and circumstances illustrate the method; they are not customer evidence or a recommended assessment outcome.

Mandate: COO for Harbour Components, a manufacturer integrating recently acquired sites. Brief version 3 prioritizes operational integration, local leadership development and a workable travel pattern.

Candidate: Morgan Lee, regional operations director at fictional Northbridge Manufacturing. Researcher: Priya Shah. Exploratory conversation: 5 October 2026. Note prepared: 6 October 2026.

Immediate decision: Should the lead consultant arrange a deeper conversation about integration responsibility and operating-model design?

Reason for inclusion: Morgan’s described remit includes several manufacturing sites during an acquisition period. This suggests a potentially relevant background; it does not yet establish responsibility comparable to Harbour’s COO position.

Evidence against integration criterion: A fictional employer announcement dated March 2024 lists Morgan as regional operations director. In the exploratory conversation, Morgan stated that they coordinated integration planning for three acquired sites, including a common maintenance approach. Morgan described proposing the sequence of implementation, while investment decisions remained with the group COO. This is a candidate account; independent verification has not been completed.

Evidence against leadership criterion: Morgan described appointing two site leaders and introducing a monthly review of operating issues. The example covered selection and coordination, but did not establish how underperforming leaders were developed. Ask for a specific case involving coaching, changed accountability and the resulting operating behavior.

Candidate perspective: Morgan is willing to discuss a wider role if the COO has meaningful authority over site priorities. They asked how the chief executive and board would resolve disagreements about investment. Morgan said a predictable travel pattern matters and requested detail before considering the mandate further.

Researcher interpretation: Priya considers the integration experience relevant enough for further exploration. The key gap is breadth of accountability: the current evidence describes regional coordination, while the client needs an executive who owns the group operating model. This is a preliminary interpretation, not a shortlist recommendation.

Sharing boundary: Internal search-team note. Follow the firm’s agreed candidate-sharing process before preparing a client-facing profile. The candidate’s questions can inform the consultant conversation; they do not establish permission for broader circulation.

Next action: Lead consultant Alex to clarify decision authority with the client, then offer a conversation to Morgan by the agreed follow-up date. Ask Morgan for an integration example that distinguishes their decisions from those of the group COO.

The lead consultant may discover broader responsibility or decide the gap is material. The record gives that next conversation a purpose.

Review the handoff before someone relies on it

Give the receiving colleague a brief reading task: identify the proposed next decision, name the strongest relevant evidence, and locate the most important unresolved question. If they cannot do this, revise the summary before adding more detail.

Check for conclusions that have outgrown their evidence. “Led integration” may have started as a research hypothesis, become a researcher’s shorthand, and then appear as an established capability in the client report. The review should return to the source rather than simply approving cleaner prose.

Useful review questions include:

• Does each material claim have a source or an attributed account?
• Are the mandate criteria current and clearly identified?
• Is the candidate’s stated interest distinct from the team’s view of suitability?
• Are gaps visible without requiring the reader to reconstruct the call?
• Does the next action have an owner and a reason?

If a colleague disagrees with an interpretation, record the reasoning rather than averaging the views into a vague statement. “Researcher sees relevant integration exposure; consultant needs evidence of group authority” explains the issue. “Mixed feedback” conceals it.

Handle corrections, access and tools deliberately

Corrections should travel with the claim they change. If a candidate clarifies that they advised on a project rather than led it, update the working summary and the downstream material that relied on the earlier description. Where a historical record is retained appropriately, mark the correction so the old statement is not mistaken for the current position.

For UK operations, the ICO’s recruitment and selection guidance covers head-hunters and recruitment records. It remains draft guidance and is under review. Use current jurisdiction-specific advice and firm policy to settle lawful basis, transparency, retention, access and other obligations; this article does not prescribe a universal retention period or consent model.

Set the intended audience before sharing the note. Internal researchers, lead consultants and client stakeholders may need different information. A client candidate report should be deliberately prepared for its purpose, rather than generated by exporting every internal comment.

If tools help structure or summarize notes, a person should check attribution, dates, omissions and whether uncertainty survived the rewrite. The AESC Professional Practice Standards say AI may support professional work but should not replace professional judgment. A fluent summary still needs someone accountable for its meaning.

Put the note to work across the search

Candidate notes become useful when they support the next piece of work. For a client discussion, extract the relevant evidence, unresolved assessment questions and decisions required. The client update template shows how to connect those findings to mandate progress without forwarding the whole internal record.

For a later mandate, keep historical evidence recognizable as historical. An old preference or assessment may help frame a question, but it should not silently become a current conclusion. The candidate rediscovery guide covers re-evaluating earlier conversations against a new brief.

Trial the structure on one mandate and review handoffs together. Remove fields that do not help decisions; watch for repeated questions, unattributed claims and missed commitments.

Frequently asked questions

What is the minimum useful candidate research note before first contact?

Record the candidate and mandate references, current brief, reason for inclusion, relevant sourced evidence and the question that contact should resolve. Include the research author and dates. Motivation and interest can remain unknown; filling those fields from an old relationship or a public profile would imply evidence you do not have.

How should we record a candidate's claim that they led a transformation?

Attribute the account to the candidate and date the conversation. Record their described decisions, authority and scope separately from public information about the company. Then state the consultant's interpretation and what remains unverified. Ask a follow-up that distinguishes personal accountability from participation in a wider leadership team.

Can a client candidate report use the internal handoff note unchanged?

Prepare the report deliberately for the client decision and agreed audience. Extract relevant evidence, assessment gaps and questions while respecting the firm's sharing boundaries. Internal comments, private constraints and preliminary interpretations may need different handling. A candidate's willingness to discuss the role does not establish permission for broader circulation of the note.

What should happen when a candidate corrects an earlier conversation note?

Update the working summary and identify downstream material that relied on the earlier claim. If a historical record is appropriately retained, mark the correction so readers can distinguish the original account from the current position. Reconsider any assessment based on the disputed detail rather than correcting the wording alone.

Laisy’s direction is an executive-search workspace that brings candidate context, mandate progress and client updates together. If continuity between research and consultant conversations is a task your firm wants to explore, describe your candidate-note workflow for personally supported early access, alongside existing tools and using firm-approved data. The practical starting point is the next handoff: evidence someone can inspect, judgment someone can challenge, and an action someone can own.

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