Executive search
Executive search brief change log: keep revisions attached to decisions
A working change record for a live search: requested revision, decision owner, evidence, affected work and the point when researchers can use the new brief.
A client asks for a different kind of leader halfway through the research. The conversation sounds clear. Later, one researcher works from the original criteria, another follows the latest call notes, and the consultant has already described a third version to a candidate.
A brief change log gives that revision a place to become a decision. It records what changed, who confirmed it, which work is affected and when the revised instruction starts to apply. The useful output is a shared working boundary, with enough history to explain why earlier work looks different.
Start with the agreed mandate and kickoff record. The process below handles changes after that baseline exists. It is an original working template for a search team, usable in a permitted document or the system you already use.
TL;DR
- Record the requested change before editing the active criteria. Give a proposal a visible status while approval is unresolved.
- Confirm the decision owner, evidence and effect on research, candidate conversations and client expectations.
- Release the revised brief with a clear version and effective point. Tell affected colleagues what to stop, revisit or continue.
- Keep earlier decisions available with appropriate access. A file edit alone does not explain why an instruction changed.
Copyable brief change record
Use one record for a decision that can be accepted, declined or deferred on its own. Separate unrelated requests so a clear decision on one does not silently approve another.
| Field | What to write |
|---|---|
| Assignment and baseline | Stable assignment reference and the currently approved brief |
| Change reference | A short identifier that stays stable during discussion |
| Requested by | The person raising the request and when it was received |
| Proposed revision | The current instruction and the exact proposed replacement |
| Reason and evidence | What prompted the request, with a permitted source pointer |
| Decision question | The specific choice that needs confirmation |
| Decision authority | Who can confirm it under the client's agreed arrangements |
| Affected work | Research, records, conversations and deliverables needing review |
| Interim instruction | What may continue while the question is open |
| Decision | Approved, declined, deferred or superseded, with rationale |
| Effective point | When the instruction applies and the new brief version |
| Owners and confirmation | Who updates each affected artifact and who checks completion |
Use the decision statuses for the change request. They do not describe candidate suitability.
Keep the record short enough to read beside the brief. Link detailed supporting material rather than copying whole conversations into every row. Confirm that those links open for the people who need them and do not expose information to a broader group.
Establish what the current brief actually says
Before comparing versions, find the last agreed instruction. Identify the artifact, its owner and the evidence of agreement. A recent file timestamp does not establish that its contents were approved.
For member engagements, the AESC Client Bill of Rights calls for written clarity about scope and engagement terms. That is a member standard; this change-log format is our suggested operational adaptation, not an AESC form or a legal interpretation.
Read the relevant wording aloud during the clarification. “Broader commercial experience” could mean a different market, responsibility for a larger operation or a preference that should not exclude anyone. Those interpretations lead to different research decisions. Ask the client to describe the work the incoming leader needs to do and the evidence that would make the revised criterion meaningful.
If the team cannot establish an agreed baseline, record that gap. Restore clarity with the client before presenting the latest document as a settled instruction. Keep a named owner for the follow-up so uncertainty does not become the permanent working arrangement.
Separate the request from the approval
Capture the request in the language used, then write a proposed operational instruction. Show both during review. This lets the client correct a translation that has made a preference too narrow or turned a question into a requirement.
Clarify who gathers the information and who can confirm the decision. Atlassian's DACI guide distinguishes driving, approving, contributing to and being informed about a decision. Use that distinction as a conversation aid. The client's actual governance determines authority; a collaboration model does not replace it.
An open request needs an interim instruction. For example: continue checking already agreed experience, hold outreach based on the proposed new sector boundary, and prepare the evidence needed for a decision. Give that instruction an owner and a review point.
Record silence as an outstanding response. If the client has an established approval procedure, follow it. Do not infer permission to change the brief because a proposed document was circulated or someone attended the discussion.
Translate the revision into reviewable research work
Ask what the proposed criterion changes in the actual task. The US OPM job-analysis guidance connects job tasks with required competencies in federal assessment. That organizing principle can help clarify a search discussion; this worksheet is not a validated selection instrument.
For each changed criterion, identify the question a researcher can investigate, the source that might answer it and the uncertainty that will remain. A company label or job title may offer a starting point without establishing the required experience. Keep that distinction visible in the candidate research notes.
Then review affected work by type. An unchanged fact can remain useful while its relevance to the mandate changes. A previous exclusion might need reconsideration. A planned conversation may require a revised question. Avoid rewriting the historical record to make it appear that the new criterion governed the earlier decision.
The owner should be able to explain the effect without saying only “update everything.” List the records or batches requiring attention, who will review them and what evidence will count as complete.
Synthetic example: a sector requirement becomes a question
The following assignment, records and counts are fictional. They illustrate the method and are not customer results or a recommended longlist size.
A search team is working from brief v2. The client initially asked for direct sector experience. During a progress call, the sponsor says experience in a neighboring sector may also be relevant if the person has handled a comparable operating challenge.
The consultant records the request as change C-04. The proposed instruction explains the operating challenge and asks for evidence of that experience. The decision owner confirms the wording and approves brief v3. The researcher is asked to reconsider the affected records rather than treat every adjacent-sector title as suitable.
| Review of the example's 10 existing records | Working action |
|---|---|
| 6 still fit the unchanged research boundary | Continue, preserving original evidence |
| 3 need further evidence under the revised criterion | Assign a research question and reviewer |
| 1 depends on an unresolved interpretation | Hold the affected action and seek clarification |
Those categories total 10. They describe review work, not candidate quality or a prediction of suitability. The unresolved record stays visible; it is not moved into an approved group to make the list look complete.
The consultant also checks two planned conversations for questions based on the older sector requirement. The record shows who will revise those questions and confirm the appropriate message before the conversations take place.
Release the decision into the working tools
Once approved, update the active brief and label its effective point. Preserve a clear reference to the earlier approved version. Keep proposed and superseded copies visibly distinct so a colleague opening an older link can understand its status.
If the team uses Google Docs, its version-history help currently lists up to 40 named versions per document. Use meaningful names for approved baselines. That product limit is not a limit of 40 ordinary edits, and version names still need an accompanying decision rationale.
Update the places where colleagues obtain their instructions. That might include a research brief, an assignment record, a shared working document and the next meeting agenda. The goal is to keep the active instruction discoverable, with a pointer to the change record. Avoid creating unnecessary duplicate copies of sensitive material.
Ask affected owners to acknowledge the action they will take. “Received” can be useful, but a short readback is stronger evidence of shared understanding: which criterion changed, which records require review and what must remain on hold.
Explain the effect to the client and the next colleague
The next client update should make a consequential revision understandable. State the agreed change, what the team is reviewing and which question still needs a client decision. Describe any timing implications as a current assessment, with its assumptions, rather than inventing a revised completion promise.
If research coverage changes, explain the boundary. Earlier work may remain valid within its original scope. A changed brief does not mean all prior work was wasted, and it does not establish that the revised market has already been covered.
Include the current brief, open changes and affected actions in any consultant handover. The receiving colleague should be able to distinguish a pending request from an approved revision without reconstructing the entire conversation history.
Recover when versions have already diverged
Pause the actions that depend on the disputed instruction. Identify the versions in use and ask each owner which decision evidence they relied on. Keep that review factual; its purpose is to restore a shared instruction and understand the affected work.
Confirm the baseline with the authorized client contact, then reconcile the necessary artifacts. Preserve significant differences and their resolution in the change record. If the wrong instruction reached an external conversation, give the consultant responsibility for agreeing an appropriate correction before further contact.
Do not call the issue closed merely because a document has been renamed. Closure needs a confirmed instruction, completed artifact updates, acknowledged owners and an explicit disposition for any remaining uncertainty.
Try the record on one real revision
Choose one suitable change in a live assignment, with permitted inputs and a named reviewer. Agree what useful evidence would look like: an understandable decision, an accurate affected-work list and a handoff the next colleague can follow.
A discussion with Laisy can start around that task alongside your existing tools. Agree the selected data, reviewed output and point to continue or stop. No full migration is required to discuss a bounded test, and no particular result or access is promised.
Frequently asked questions
Does every wording correction need a change decision?
A correction that preserves the agreed meaning can follow the team's ordinary editing process. Escalate a revision that changes who is considered, what evidence is required, what work proceeds or what the client expects. Record the reason for that distinction.
What if the client wants the change immediately?
Capture the instruction, confirm authority and define the minimum affected work before acting. Use a short record if necessary. Urgency does not make an uncertain request or an unresolved contact restriction disappear.
Should old candidate conclusions be rewritten?
Keep the earlier conclusion attached to its original criterion and date. Add the new review and its evidence. Correct factual errors through the appropriate process, while preserving enough context to explain a changed assessment.
How do we know the change is fully handed over?
Check that the active brief is identifiable, affected owners can state their actions, pending questions have owners and the next consultant can locate the decision evidence. A clean folder alone does not demonstrate that understanding.