Executive search
Client-input readiness: what must be clear before research starts?
A task-level readiness check for executive search: identify essential client inputs, distinguish gaps from assumptions and record a bounded start, hold or clarification decision.
A search can have an agreed kickoff and still lack the client input its next research task depends on. The researcher may understand the broad role while it remains unclear what a criterion means, whether a list the client sent is approved or who on the client side can confirm a proposed boundary.
Client-input readiness is a decision about one task: does the client input available today support the work about to begin, which gaps matter and who resolves them? It should let appropriate work proceed while making the boundary of that work explicit.
The question is never whether the whole client is "ready." Different tasks depend on different inputs. A missing presentation preference may not stop an internal source review, while an undefined criterion can make a candidate-level research table impossible to interpret.
This check sits between two published guides. The mandate kickoff checklist produces the agreed baseline. The research-request handoff commissions a task inside the firm. Readiness asks a narrower question before that task starts: which client dependencies are confirmed, which are assumed and which are missing?
Copyable input-readiness record
Use this after the assignment baseline exists and before a consequential new task begins. It is an original working aid, not a replacement for the engagement or kickoff process.
| Readiness question | What to record |
|---|---|
| Task | The specific research output and the question it should answer |
| Critical instruction | The criterion or definition without which that output would mislead |
| Current evidence | The confirmed input, source pointer and version |
| Missing input | The exact unresolved question, not a broad "waiting on client" label |
| Effect | Which work or interpretation depends on the missing answer |
| Bounded work | What can proceed without assuming that answer |
| Decision owner | Who on the client side can confirm the instruction, and who in the firm obtains it |
| Working decision | Start within a stated boundary, hold the dependent step or seek clarification |
| Review trigger | The response, event or change that reopens this decision |
The person commissioning the work and the person doing it should both be able to state the recorded boundary. Sending the table is not the same as agreeing it.
Identify the input that changes interpretation
Some client information is useful background. Other information decides whether a finding answers the right question. Sort inputs into those two groups before asking the client for more material.
For a role criterion, ask which work it describes. OPM's job-analysis guidance describes examining the tasks performed in a job, the competencies required to perform them and the connection between the two. It is US federal assessment guidance. It does not validate a private search filter or show that a title alone proves experience.
An input might define the scope of a responsibility, the relevant period or the line between a requirement and a preference. Phrase the gap so the decision-maker can answer it. "Does regional responsibility in this brief mean owning the regional P&L, or overseeing operations without budget ownership?" is answerable. "Please send more detail" is not.
Do not collect unrelated information to make a readiness pack look complete. Ask for the inputs this task needs and keep their source and audience boundaries.
Separate a working assumption from an agreed instruction
An assumption can support a bounded exploratory task if the person commissioning it explicitly accepts its use and the limitation stays visible. It must never be presented as something the client confirmed.
Record the assumption, why it is being used and what would change if it proves wrong. Name two people: the one in the firm who authorizes the bounded work, and the one on the client side who must confirm the underlying instruction.
If the assumption could change which companies or people are included, consider whether the task should wait. An internal exploratory note can carry a clearly labelled provisional boundary. A conclusion presented to the client usually needs the confirmed input first.
Keep proposed and confirmed criteria distinguishable in the research notes. A later reader should be able to see which question the evidence addressed, even after the client settles the point.
Describe the dependency without inventing a schedule
State which step depends on the missing answer and what can proceed independently. That gives the consultant and the client choices without predicting the length of the whole assignment.
Atlassian's critical-path explanation describes finding the longest sequence of interdependent tasks in a schedule. A search task can borrow the dependency thinking without pretending that client responses have reliable durations or that a critical-path calculation has been done.
Distinguish an observed hold from a possible future effect. If a research table cannot start under an undefined criterion, say which work is held. Do not turn that into a prediction about the placement date.
Where work can proceed inside a narrower boundary, describe what that output can support and which parts will need review once the answer arrives. "We can start" is not enough if colleagues disagree about what the start includes.
Confirm the version, not just the file's arrival
A document from the client may be an early draft, a proposal another stakeholder has not approved, or a file that changed after someone reviewed it. Check its status through the client's actual decision route.
Some tools record approvals. Google Drive's approval feature is available only on Enterprise and Google Workspace for Education Plus accounts, and whether an edit resets approvals depends on the "Require all approvers to review the same content" setting. An approval in a tool records that someone approved a file version. It does not tell you that the person had authority over the instruction it contains.
Whatever tool is used, record the confirmed version and the source of the confirmation. A filename, upload time or forwarded attachment does not settle an instruction's status.
When two client sources conflict, keep the discrepancy and assign its resolution. A tidy synthesis of two incompatible instructions hides the choice that needs an authorized answer.
Worked example: the Alder readiness record
Everything in this example is fictional: the client, the assignment "Alder", the documents and the dates. It shows a recorded start and hold decision. It is not a customer result, a readiness threshold or an industry timeline.
The Alder team is about to start two tasks: a company-level map of the target market and a candidate-level research table. The lead consultant and researcher review five client inputs on 10 November.
| Input | Status on 10 November | Work it blocks | Working decision | Owner and review trigger |
|---|---|---|---|---|
| Geography and period in brief B2 | Confirmed by client email, 3 November | Nothing | Use as the baseline for both tasks | None |
| Client's off-limits list, draft L1 | Received from the HR contact; client CEO has not approved it | Final target list and any approach | Company map proceeds with L1 marked provisional, authorized by the lead consultant; no approach uses L1 | Lead consultant asks the HR contact who approves L1; reopen when it is approved or changed |
| Meaning of "regional responsibility" | Missing decision: regional P&L ownership or operational oversight | Which people the research table includes | Hold the candidate-level table; the company map does not depend on it | Lead consultant sends the CEO a two-option question; reopen on the answer |
| Presentation format preference | Open | The client-facing version only | Proceed with internal work | Consultant settles it before the first client presentation |
| Compensation range | Proposed by the consultant, not confirmed | Neither task | Not a dependency for these tasks; record it for later | Consultant raises it at the next client update |
The team does not report "one of five inputs confirmed." That count would treat the presentation preference, which affects only the client-facing version, the same as the undefined criterion, which is the only input that stops the research table.
The researcher starts the company map with L1's provisional status noted in the output. The lead consultant owns both client questions. The candidate-level table stays on hold, and nobody treats the limited start as confirmation of the missing definition.
Ask the client a decision they can make
Write a short request stating the current understanding, the open point and the work it affects. Where useful, offer the possible interpretations without steering the client toward the one that is easiest for the team.
The client-update structure can frame the request in assignment context: what is proceeding, what is waiting and who needs to answer.
Check the client's decision route. One contact may coordinate a reply while another stakeholder approves the criterion. Acknowledgement of the question, or an extra document, is not confirmation.
When the answer arrives, compare it with the question asked. If it settles only part of the ambiguity, keep the remainder visible in the record.
Reopen the record when the task changes
An input that was enough for an internal review may not be enough for a client presentation. A new geography, audience or deliverable can create a dependency that did not exist before.
Identify which existing work is affected and whether its assumptions still hold. Keep sound findings within their original scope instead of discarding everything or treating the whole document as current. If responsibility for the task changes, pass on the current readiness decision and the reason for it.
If you want to try this on one assignment alongside existing tools, the pilot success criteria help define a bounded task with selected permitted inputs, a named reviewer and an exit point. No guaranteed client response or start-to-placement timeline is implied.