Executive search

Executive search client-call brief: prepare the next decision

A private preparation brief for a search partner: current instruction, source-backed progress, open decisions, promises and reviewed questions for the client call.

By LaisyPublished

Before a client call, a search partner needs a clear account of where the assignment stands and what the conversation should resolve. The relevant context may already exist across the mandate, recent notes, research records and the previous update. Preparation makes that context usable for this meeting.

A call brief is a private working document. It helps the consultant distinguish confirmed information, open questions and the decisions that need client input. It should also show the promises already made, so the next conversation does not begin with a different account of the assignment.

Keep it distinct from the client-update template. An update is material you review for sharing. A preparation brief can contain unresolved questions and internal working pointers that require a separate visibility check before anything leaves the firm.

TL;DR

  • Begin with the purpose of the call and the decision or clarification it should support.
  • Bring the current instruction, recent evidence and earlier commitments into a short, traceable brief.
  • Label uncertainty and review source dates. A recent note can still describe an earlier event.
  • After the call, record the confirmed outcome and accepted actions so the next brief starts from the right context.

Copyable client-call brief

Fill the parts that matter to this conversation. Link to permitted source records rather than copying every note into the document.

SectionWhat to prepare
Call purposeThe useful question the meeting should answer
Current mandateA pointer to the agreed brief and any pending changes
Client participantsWho is attending and which decisions need their input
Material developmentsSource-backed changes since the last discussion
Previous commitmentsWhat the firm and client said they would do
Open questionsWhat remains unknown, disputed or dependent on a response
Proposed discussionSpecific questions, relevant evidence and possible next actions
Sharing boundaryWhat is suitable to discuss or send, and what needs further review
Follow-up captureSpace for confirmed outcomes, owners and unresolved points

Keep detailed evidence available through appropriate links. A consultant should be able to read the brief quickly, then investigate a consequential statement without searching through an unrelated archive.

Choose the purpose before collecting the material

Write what would make the call useful. “Discuss the search” leaves too much room for a long status recap. A more useful purpose might be to clarify a revised criterion, agree how to handle a coverage gap or obtain a decision needed before the next research step.

Use the client's actual process to establish which decision can be made in the meeting. If a necessary participant is absent, prepare the evidence and a route to confirmation. Do not frame the agenda as though attendance by one contact settles every question.

For member engagements, the AESC Client Bill of Rights includes ongoing communication about market response and search challenges. This brief is our suggested preparation aid, with that member scope clear. It is not an AESC form or a promise of a search result.

Limit the agenda to questions that need the client's attention now. Keep background material available, but distinguish it from the request you are making. If the call is mainly informational, state which understanding you want to confirm before closing.

Establish the current instruction and recent changes

Open the agreed mandate record. Check the current criteria, relevant restrictions and any pending requests. A proposal should remain identifiable as a proposal until it has been confirmed through the client's agreed route.

Compare the instruction with the material prepared for the call. A research summary may use an older criterion. An action from the previous meeting may no longer be appropriate. Record those mismatches as questions to resolve, with the relevant source pointers.

Read the date and meaning of the evidence. “Updated this morning” could mean someone corrected formatting or added an old account. The consultant needs to know when the underlying event occurred and what the source actually establishes.

If the baseline cannot be established, make that the first preparation issue. Give an owner the task of obtaining the instruction rather than letting a polished summary conceal the uncertainty.

Assemble the evidence that changes the conversation

Use material permitted for this preparation task. Access to an inbox or project folder is not a reason to include its entire history.

Select developments that affect the purpose of this call. For each one, write the finding, source period and implication you want to discuss. Keep a factual observation separate from the interpretation the consultant proposes.

The existing system may already offer a useful view. Clockwork's status-report documentation describes candidate information and recent notes available to firm and client users. That is a feature description of Clockwork, not Laisy. Check the current tool before building another report with the same information.

Review whether a summary preserves the important qualification. A company's activity does not establish a person's responsibility. A previous expression of interest does not establish current availability. An unanswered question does not become a negative finding because the call is approaching.

Use the candidate research-note structure when you need to separate source-backed findings, attributed accounts and consultant judgment. The brief should point to that work rather than compress it into an unsupported conclusion.

Review promises before proposing new actions

Look at the previous discussion and identify commitments that affect this call. Record who accepted each action, what completion was meant to look like and what evidence is now available.

If an action remains open, describe its present state accurately. It may be waiting on a source, a client response, a permission clarification or a colleague's review. Prepare a clear question about the dependency and a proposed next owner.

Check commitments made in different channels. A consultant may have discussed a question in a call while a researcher received a separate instruction in a message. Preserve the source of each account and resolve any conflict before presenting a single version as agreed.

Avoid using the brief to assign blame. Its purpose is to prepare a useful conversation. A factual description of the dependency, the work affected and the choice now needed gives the client something concrete to respond to.

Synthetic example: a brief with a bounded purpose

This example is fictional. The assignment, timing suggestion and counts illustrate the method; they are not measured preparation times, customer results or a prescribed search process.

A consultant is preparing for a progress discussion with a fictional industrial client. The team has three open items: a criterion awaiting clarification, a source account needing review and a client input that affects the next research task.

The consultant chooses the criterion clarification as the main decision request. The other items are prepared as a source limitation and a dependency. That distinction prevents every open point from being presented as though it needs the same kind of client response.

Prepared itemEvidence brought to the callQuestion or action
Criterion clarificationCurrent brief and the client's proposed revisionConfirm the wording through the agreed decision route
Source limitationDated record and the unresolved pointExplain the limit; agree the appropriate follow-up owner
Client inputPrevious request and the dependent research taskConfirm the input owner and next review point

For this exercise, the consultant uses a suggested 12-minute preparation timebox, then asks a colleague to check the consequential statements. The timebox is an original working suggestion. If the evidence is incomplete, preparation needs more work; the number is not a completion guarantee.

The final brief names the open decision and points to the records needed to discuss it. It does not claim that the source question has been resolved or that the client input has arrived.

Check the boundary between private preparation and shared material

Review the intended audience for every item. A record useful to the consultant may include a working interpretation or a source restriction that needs a different treatment in client-facing material.

For example, Clockwork's internal-project-note documentation describes explicit client-visibility and notification behavior. That describes Clockwork only. Check the actual tool settings and the content before changing visibility, tagging someone or sending a message.

Prepare a reviewed client-facing version where one is needed. Retain the useful qualification and avoid copying an internal explanation wholesale simply because it already exists. Check recipients and linked-record access before distribution.

If a colleague provides the brief, ask them to point out which parts remain internal working material. Include that boundary in the handoff. A label on a document is less useful if the consultant cannot tell which statement still needs verification.

Use file history to clarify changes

If a shared document has changed since the previous call, review the relevant edit before relying on the summary. Check whether the change concerns a fact, an interpretation or presentation.

Google Docs' version-history help documents reviewing earlier changes and creating named versions. That describes Google's product, not a Laisy capability. A file's edit history can help locate a revision; the consultant still needs the reason and evidence behind a consequential decision.

Keep the brief's current status identifiable. If several colleagues contribute, assign a person to reconcile the final version before the meeting. Preserve useful source pointers and avoid leaving different copies that appear equally current.

After the call, add the outcome through the team's normal record process. Do not overwrite an unresolved pre-call question in a way that makes it look as though the answer was known earlier.

For decision requests, Atlassian’s DACI play offers a useful distinction between the person driving a decision and the person approving it. Use the client’s actual authority arrangements when preparing the question.

The Government Data Quality Framework guidance also emphasizes communicating limitations to users. Apply that discipline to the brief: make the unresolved point visible beside the finding it qualifies. This is our adaptation, not a search-industry standard.

Close the loop after the conversation

Record the instruction that was actually confirmed, the actions people accepted and the questions that remain open. Distinguish an idea discussed from a commitment made. If a decision needs further confirmation, retain that status and its owner.

Where appropriate, send a reviewed readback through the usual channel. Make clear which response or correction is needed. The next colleague should be able to understand the working state without having attended the call.

Carry those records into any consultant handover. The next preparation cycle should begin with confirmed outcomes and visible gaps, rather than a fresh attempt to reconstruct the same conversation.

Test one preparation task alongside existing tools

Choose a suitable client call in a real assignment, with selected permitted inputs and a named reviewer. Agree what a useful brief would contain and how the reviewer will check it. Include review and correction effort when deciding whether the process helped.

A Laisy discussion can start with that bounded task alongside your existing tools. Agree the reviewed output and the point to continue or stop. No full migration, promised access or guaranteed preparation saving is implied.

Frequently asked questions

How long should preparation take?

Use a working timebox appropriate to the task, while allowing enough time to check the evidence. This guide supplies no measured benchmark. A short brief can require substantial research when the underlying context is unclear.

Is the preparation brief suitable to send to the client?

Review it separately for that audience. Internal questions, interpretations and linked records may need different treatment. Check content, recipients and permissions before sharing a client-facing version.

What if a source cannot be checked before the call?

Label the uncertainty and decide whether the statement is necessary to discuss. Present it as an open question where appropriate. Do not convert an unverified account into a confident conclusion to fill the agenda.

Can AI prepare the brief automatically?

Any draft needs review against the selected sources and the current instruction. Keep a person responsible for the final brief and external communication. This guide does not promise automatic preparation or sending by Laisy.