Executive search
When a search pauses: prepare the client delay discussion with evidence
Prepare a search-delay discussion with a dated blocker, affected work, conditional recovery choices and accepted owners. Includes an issue brief and fictional dependency example.
A search can miss an agreed milestone without every part of the mandate being late. Before sending an update, establish what the client expected, what is blocked, and which decision could change the plan. A revised date by itself does not explain any of those things.
The UK Government Teal Book's issue-management guidance distinguishes cause, event and impact. This brief adapts that distinction for a search firm. It is a discussion tool, not a prescribed reporting process.
Build a one-page delay brief
| Field | What the search lead writes |
|---|---|
| Agreed baseline | Milestone, date, and the client-approved plan or message supporting it |
| Blocker | What is missing or changed, and when the team first verified it |
| Dependency | Which task actually waits on the blocker; which work can continue |
| Working range | An estimate only if assumptions are stated; otherwise a decision checkpoint |
| Choices | What each option changes, including tradeoffs for quality or scope |
| Decision request | Who needs to choose what, by when, and when the team will update again |
Check the underlying record before drafting. For example, Clockwork's status-report documentation describes candidate and note views. Such a report can help find the activity. It does not establish that a missing approval was given or that all work depends on it.
Worked example: a fictional shortlist with a missing decision
The client expected an eight-person shortlist on Friday. On Wednesday the team has five profiles that meet the original brief and three that depend on whether a second city is acceptable. The client has not confirmed the geography.
- Known: The client asked for eight; five meet the original geography. The other three cannot count as agreed-scope profiles.
- Still moving: The team can review references and fill evidence gaps on the five. No sourcing work in the proposed second city is treated as approved.
- Choice: Review five on Friday and decide whether to expand geography, or wait for a full list against the original geography. Do not promise a completion date for the second option without a usable estimate.
- Next checkpoint: Client sponsor decides by Thursday at noon whether to expand. Search lead shares the Friday review plan by Thursday afternoon. If no decision arrives, use the original scope and give a fresh status update, not an invented completion date.
A usable client line: “We can review five profiles against the original brief on Friday. To include the other three, we need your decision on geography by Thursday noon. If the scope stays as agreed, we'll use Friday to review the five and share the next checkpoint.”
Confirm what changed
After the discussion, record the accepted option, explicit scope changes, owner, and next check-in in the working record. Keep the original expectation distinguishable from the revision. A reviewer should be able to answer three questions without calling the search lead: what the client expected, what still depends on their decision, and what the team has actually committed to next.