Executive search client update template: progress, evidence and next decisions

A useful executive search client update explains what changed, what the evidence means for the mandate, and what needs to happen next. Candidate counts belong in it, but counts alone cannot tell a client whether the search is moving toward the agreed leadership requirement.

For a specialist boutique, the report must survive researcher, consultant and partner handoffs. Connect each important statement to a current record.

Adapt this retained-search progress report to the engagement, audience and stage, as an email or short meeting document. The worked example is entirely fictional, not a performance benchmark.

TL;DR

• Label every count as period activity, a cumulative milestone or a current-stage snapshot; do not add those views together.
• Connect candidate movement to the agreed brief, with the evidence and unresolved assessment question beside each judgment.
• Turn a blocker into a specific decision with an owner, requested date and consequence.
• Share the information needed for that decision through the agreed channel; coded profiles still need a confidentiality review.

What the update should help the client decide

Start with three questions: Are we searching the agreed market? Are the people we are engaging plausible against the brief? What decision would move the mandate forward?

Those questions prevent an activity report from becoming a substitute for advisory judgment. A longlist can grow while a crucial qualification remains untested. A smaller pipeline can be appropriate when the team has ruled out a poorly matched market segment and concentrated effort elsewhere. Explain the change rather than expecting the client to infer it.

The AESC Client Bill of Rights expects ongoing communication from member firms about market response, developing candidates and challenges, alongside written engagement clarity. It does not prescribe this template or establish a universally appropriate reporting cadence.

Agree the reporting audience and cadence at kickoff. Identify who can approve a change to the brief, who coordinates interviews and who receives candidate information. If these foundations are unclear, use an executive search mandate kickoff checklist before refining the report layout. A polished update cannot resolve conflicting instructions from different client stakeholders.

A reusable client progress report structure

Keep the opening readable without its attachments. A reader should see the current position and requested decisions before opening individual candidate profiles.

Keep headings stable, but vary emphasis: coverage during mapping, fit evidence during assessment, and dependencies and timing at offer stage.

Copyable reporting prompts

Mandate: [Client / role / assignment reference]. Period: [Start–end]. Information current to: [Date and time]. Brief: [Version or approval date]. Prepared by: [Consultant].

Current position: [Where the search stands against the next agreed milestone]. [What supports that judgment]. [The main condition or uncertainty].

What changed: [Two or three material changes since the previous report]. [State explicitly if a previous assumption changed].

Research and pipeline: [Coverage against agreed target segments]. [Counts with definitions and period]. [Candidate movements that matter, with shareable fit evidence and next steps].

Market evidence: [Observation]. [How many relevant conversations or records support it, and when]. [What remains unknown]. [Recommended test or implication].

Risk or blocker: [Issue]. [Effect on the milestone]. [Response]. [Owner]. [Date for review].

Client decisions: [Specific decision and options]. [Consultant recommendation and reason]. [Requested decision date]. [Consequence if unresolved].

Next period: [Search-team actions with owners and dates]. Next update: [Agreed date or event].

Remove empty fields and bracketed placeholders before sending. State “no decision required” when useful; do not invent answers to complete the scaffold.

Make the counts intelligible

Choose whether each number describes activity during the reporting period, cumulative milestones reached, or people currently in a stage. Label it. These are different views and should not be added together.

For example, “six discussions completed this week” is activity. “Four candidates currently in assessment” is a snapshot. “Twelve candidates have entered assessment since kickoff” is cumulative progress. A person can appear in all three views without representing three people.

Keep a small internal definition sheet. “Identified” might mean a distinct person with an initial reason to investigate. “Approached” should specify whether an introduction or message counts and whether repeat attempts are excluded. “Interested” should mean an actual indication of interest in this mandate, rather than a reply, a historic relationship or willingness to recommend someone else.

State how withdrawals and disqualifications are recorded. If you use mutually exclusive current stages, each person has one stage at the snapshot cutoff. If you use cumulative milestones, someone who withdrew may still belong in the historical approached count. Neither convention is inherently wrong; unexplained switching is the problem.

Clockwork's own status report documentation illustrates grouping candidates by status, including research, interviewing, finalist and timing off. This is evidence of one product's reporting structure, not a universal stage taxonomy. Choose terms your team and client understand, and retain their meanings throughout the assignment.

Coverage also needs context. “Twenty companies researched” tells little if most are from one easy-to-map segment. Show where research is complete, where relevant people remain unverified and which target areas are constrained by agreed off-limits. Avoid treating a researched company as an exhausted talent pool.

Translate observations into qualified advice

Market feedback should show the path from evidence to interpretation. Write an observation first, explain its scope, then offer a recommendation. This lets the client challenge your reasoning without disputing the underlying record.

Compare “the market will not relocate” with “three of the five relevant executives spoken to this period declined relocation; two would consider regular travel, and location preferences remain untested for the others approached.” The second statement is more useful because it exposes the limits of the sample. It could justify testing the travel model. It cannot establish a market-wide relocation rate.

Treat compensation comments similarly. An executive's stated expectation, a published pay range and a consultant's estimate are different kinds of evidence. Specify which one supports the advice. Do not turn a few conversations into a salary survey or describe an indicative discussion as a negotiated package.

For candidate fit, connect the assessment to the mandate criterion. “Strong operator” is difficult to evaluate. “Described leading a multi-site integration; direct responsibility for the relevant commercial outcome remains to be tested” tells the client what is known and what the next assessment should establish.

Clockwork's research reporting guidance, published in 2020, distinguishes company coverage and initial candidate research from interest and availability established later. That distinction is useful when a client mistakes a promising researched profile for an engaged candidate.

Maintain the supporting records behind the report. A practical approach to executive search candidate research notes helps preserve source dates, conversation context and unresolved questions. The client summary should compress those records without increasing the certainty of their claims.

Worked example: a fictional week-three update

The following example concerns an invented industrial business and an invented chief operating officer search. All people are represented by codes. Every count, date, observation and assessment is illustrative.

Mandate and current position

Client: Harbour Components. Role: Chief Operating Officer. Period: 1–7 October 2026. Information cutoff: 7 October, 12:00 client local time. Brief: Approved 16 September. Lead consultant: Assignment lead.

The search is progressing toward an initial candidate discussion on 16 October. Two executives are in consultant assessment; neither is yet presented as a confirmed shortlist candidate. The principal dependency is agreement on whether substantial travel can meet the role's location requirement. We recommend testing this option while continuing the local search.

What changed this period

The team completed initial mapping of the remaining domestic target companies and began checking the agreed adjacent-sector segment. Six first substantive conversations took place. Two people progressed to assessment, two declined because of location, one did not meet the required operating scope, and one asked to revisit the conversation after receiving more role context.

One executive identified in an earlier mandate was re-evaluated against the current brief and approached. Prior interest was not assumed to carry over. Their current responsibilities and willingness to discuss this opportunity were checked before assigning a present status.

Research and pipeline

The agreed target list contains 24 companies: initial mapping is complete for 18, and six remain in research. Completion means that the first mapping pass has been reviewed; it does not mean every possible executive has been identified.

The following are mutually exclusive current stages for 38 distinct people identified since kickoff. The counts sum to 38. They are not weekly activity totals.

This week's six first substantive conversations are reported separately above. They are already reflected in these current stages and must not be added to the total.

Candidate movement and evidence

Candidate A — consultant assessment. Described responsibility for integrating two manufacturing sites and improving delivery planning. The next interview will test direct accountability for the operating budget and the scale of change. Interested in the mandate; availability for client discussion not yet confirmed.

Candidate B — consultant assessment. Relevant adjacent-sector operating experience. Has expressed interest subject to the location arrangement. The next conversation will examine the transferability of their operating model to Harbour's environment. No conclusion on that transferability is recorded yet.

Candidate identities and detailed profiles will be shared through the agreed channel when appropriate. These coded summaries are sufficient for the location decision requested in this update.

Market feedback, risk and decision

Of the six people spoken to this week, two declined on location grounds and Candidate B raised it as a condition. This is a small, selected set of conversations, not evidence that the wider market rejects relocation. It does identify a question worth resolving before additional approaches describe the requirement.

Decision requested: Can a COO based elsewhere, with substantial agreed site attendance, remain within scope? The consultant recommends allowing this arrangement to be tested while maintaining the local search. The client sponsor is asked to decide by 9 October.

Risk: If location remains unresolved, Candidate B's assessment and the relevant adjacent-sector approaches may pause. The 16 October discussion could still proceed with available evidence, but may cover fewer assessed options. The consultant will confirm the implication once the client responds.

Next actions

The researcher will complete the six remaining company maps by 13 October. The consultant will conduct Candidate A's scope assessment by 12 October and confirm Candidate B's next discussion after the location decision. The client coordinator will reserve interview windows for the following week. The next written update is scheduled for 14 October, with earlier contact if a material candidate or mandate change occurs.

Handle blockers without hiding responsibility

A blocker needs an owner and a consequence. “Awaiting client feedback” can be accurate but still leave the reader unsure what to do. Identify the feedback needed, who can provide it and which action depends on it.

Use neutral, specific language: “The panel's assessment of Candidate A against the integration criterion is required before deciding whether to schedule the final discussion.” If the feedback is overdue, state the requested date and current effect. Avoid implying that the client alone controls the outcome when your team also has outstanding work.

When stakeholders disagree, report the disagreement as an unresolved mandate decision. For example, the sponsor may prioritize immediate sector experience while another panel member prioritizes transformation scope. Show how the difference changes candidate evaluation and ask the authorized sponsor to settle it. Do not quietly adjust the brief to whichever preference was expressed most recently.

If research is returning few plausible profiles, separate possible explanations: narrow criteria, incomplete coverage, off-limits constraints, limited responses or an untested adjacent market. Recommend the next diagnostic step. A low count is a reason to investigate; it is not automatically proof that the specification is impossible.

Earlier relationships can inform that investigation. Explain any deliberate return to previous candidate conversations as part of the current strategy. The workflow for executive search candidate rediscovery should include checking current relevance and circumstances, rather than treating an old shortlist as an immediately available pipeline.

Check what is appropriate to share

A report may be forwarded beyond its initial recipients. Select information for the decision and the agreed audience. A broad progress update rarely needs private contact details, raw reference comments or unrelated personal circumstances.

The AESC Candidate Bill of Rights describes confidentiality commitments for its member firms, including protecting candidate interest and agreeing the assignment's confidentiality level. A coded candidate can still be identifiable from a rare employer and role combination, so review the whole description rather than assuming a removed name settles confidentiality.

For processing subject to UK GDPR, the ICO's data minimisation guidance explains that personal information should be adequate, relevant and limited to what is necessary for the purpose. Apply your firm's sharing rules and applicable legal requirements to the report's audience and purpose. This is an operational boundary, not a complete legal checklist or a claim that consent is always the appropriate lawful basis.

The ICO's accuracy guidance also distinguishes historical records from current facts and calls for clarity about information sources and opinions. Date a candidate statement and label consultant interpretation. Correct a misleading client summary when new evidence changes it; keeping an accurate internal note does not fix an inaccurate report already sent.

Prepare the next update from maintained records

Before writing, reconcile candidate stages, review the latest conversations and compare outstanding actions with the previous update. Draft the decision requests first, then the supporting evidence, and write the opening judgment last. Have the mandate lead review conclusions and the recipient list before sending.

After the client discussion, record decisions, owners and any approved brief changes in the assignment records. Keep the sent report as a dated snapshot. The next update should explain movement from that snapshot, not silently overwrite the history.

Frequently asked questions

How often should an executive search client receive an update?

Agree the cadence at kickoff around the engagement, search stage and client decision process. The fictional example uses weekly reporting, but it is not an optimal-frequency benchmark. Arrange earlier contact when a material candidate change, mandate question or blocker needs action before the next scheduled update.

What should we report before any candidates are ready for a shortlist?

Show coverage against the agreed target market, what has been checked, which gaps remain and what the team will investigate next. Keep researched relevance separate from candidate interest and assessed fit. If a milestone depends on an unresolved client decision, state that dependency rather than implying that an early profile is shortlist-ready.

Should pipeline totals include people who declined or withdrew?

That depends on the count's definition. A mutually exclusive current-stage snapshot can include a clearly labeled closed category, as the example does. A cumulative approached count can retain people who later withdrew. Explain the convention, apply it consistently and avoid combining cumulative milestones with current-stage totals.

How do we ask for overdue client feedback without making the update accusatory?

Name the decision or criterion requiring feedback, the person who can resolve it, the requested date and the next action affected. Include your team's outstanding work where relevant. A precise consequence helps the client prioritize; a general statement that the search is waiting gives them little to act on.

If assembling that context is the recurring difficulty, you can describe your client-update task for personally supported early access. Laisy's direction is an executive-search workspace bringing candidate context, mandate progress and client updates together. Early access works alongside existing tools with firm-approved data.

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