Executive search
From opportunity to assignment: hand over what was actually agreed
Reconcile executive-search sales commitments with accepted delivery scope using a promise ledger, source references, dependencies and an explicit receiving-team review.
An opportunity becomes an assignment, and the delivery team inherits a proposal, meeting notes and a CRM record marked won. Somewhere in those materials are the commitments the client believes the firm has made. They may not all appear in the same place or use the same language.
A sales-to-delivery handover reconciles those commitments before work begins. It establishes what was actually agreed, what remains conditional, what was discussed but excluded, and which assumptions need confirmation. The receiving team should leave with an executable instruction and a route for resolving anything it cannot accept.
This is not another sales qualification checklist. It addresses the boundary between a commercial opportunity and an operational assignment. It also does not interpret a contract: where terms conflict or need professional interpretation, the firm must use its appropriate commercial and legal route.
Copyable opportunity-to-assignment handover
| Field | Working record |
|---|---|
| Opportunity and assignment | Stable references linking the commercial record and delivery work |
| Current agreement | Relevant agreed version and authorized source |
| Business problem | Why the client is commissioning this search |
| Promised output | Specific deliverable or activity and its source |
| Conditions | Inputs, approvals or other dependencies attached to the promise |
| Timing basis | Agreed dates or sequencing, including unresolved assumptions |
| Exclusions | Discussed items explicitly outside the accepted scope |
| Delivery owner | Person accepting responsibility for the next operational action |
| Open issue | Gap, conflict or missing evidence and who resolves it |
| Acceptance record | What the receiving team has reviewed and what remains pending |
A compact promise ledger can sit alongside this brief. It should link back to the authoritative commercial record rather than become a competing agreement. Give the ledger a date and an owner who can explain how the handover was assembled.
The mandate kickoff checklist then turns the accepted assignment context into an initial working discussion. That meeting should refine a shared instruction, not reveal a different sale to each participant.
Start with the sources of commitment
Collect the current agreed documents and the relevant discussions that shaped the client's expectations. Keep their status visible: a proposal draft, an accepted engagement and a consultant's meeting note are not equivalent sources.
Where a conversation contains an additional promise, record the statement accurately and ask the appropriate owner how it relates to the agreed terms. Do not discard it because it is inconvenient, and do not treat an unverified recollection as a binding instruction.
A CRM can organize the evidence. HubSpot's current record-creation guidance describes properties, associations and the transfer of existing activities during creation. Those functions can link relevant context, but they do not establish which commitment was accepted by a client or delivery team.
A status transition is therefore a useful trigger to review the record, not proof that the operational brief is complete. Decide what evidence the receiving team needs rather than assuming every required fact exists in the sales pipeline.
Separate outcomes, outputs and activities
A client may describe the business outcome it wants: a leader capable of addressing a defined operating challenge. The firm may agree to deliver a search process and specified outputs. The team then plans activities to produce those outputs.
Mixing these levels creates avoidable ambiguity. A research presentation is an output; reviewing a defined source set is an activity. Neither, by itself, guarantees a successful appointment or a business result after hiring.
Government Project Delivery's planning chapter distinguishes outputs, outcomes, responsibilities and dependencies in its project context. The practical adaptation is to label what the search team is promising to do and what depends on other decisions, rather than promising control of the entire outcome.
The handover should preserve the client's purpose while keeping delivery language accurate. If the proposal overstates what can be controlled, escalate that conflict through the proper route before the team repeats the claim in a kickoff document.
Build a promise ledger with source and status
Use one row for each material commitment. Include its source, current interpretation, conditions and delivery owner. Keep the original wording available to authorized reviewers, especially when a summary could change its meaning.
A useful status describes the commitment's state: confirmed, conditional, excluded, disputed or awaiting clarification. Avoid a general “covered” label. It does not tell a consultant whether an item is included, merely discussed or dependent on a client input.
Atlassian's project-scope guidance provides a way to think about inclusions, exclusions and constraints. Applying those distinctions to a search is an original working method, not evidence that a generic project template defines the firm's commercial obligations.
Keep explanations concise enough to use. The point is not to copy the entire sales history into a table. It is to let a delivery owner find the source and understand the next operational decision without reconstructing the opportunity from scattered materials.
Test dependencies with the people doing the work
Ask the delivery team which inputs, approvals and access conditions are needed for the promised next task. A timeline that assumes client feedback tomorrow is different from a timeline whose next stage starts after feedback is received.
Record the distinction without turning an internal estimate into a new client commitment. If an estimate requires revision after the source material is reviewed, establish who communicates that and what the client has agreed. Do not quietly replace the date in a shared plan.
The receiving team may identify an output it cannot yet produce responsibly because a material input is missing. That should become an explicit issue with an owner and an affected task. It should not become an invented client fact used to keep the plan looking complete.
Use the candidate research-note structure where early factual work is part of delivery. It helps preserve the source and uncertainty of the information, rather than letting sales shorthand become evidence about a market or candidate.
Worked example: eight items with different meanings
In this fictional Cedar handover, a delivery lead compares engagement revision E3 with the accepted scope note S2 and the sales discussion record. The eight rows illustrate different commitment states; they do not describe a real contract or a standard search package.
| Item | Fictional controlling source / state | Receiving team's next action |
|---|---|---|
| Revised role brief | E3: included | Assignment lead prepares the revision for the agreed client review |
| Target-company criteria note | E3: included | Research lead documents the stated boundaries before selection |
| Research coverage update | S2: included | Research lead reports checked scope and gaps, not a claim of whole-market completeness |
| Shortlist discussion pack | E3: included | Consultant prepares the source-backed pack for the authorized audience |
| Assignment closeout note | E3: included | Assignment lead records final decisions and agreed handback |
| Research presentation date | S2: conditional on client confirming the business-unit boundary | Sales owner obtains the decision; delivery does not convert a provisional slot into a deadline |
| Additional regional mapping | Sales note: conditional on scope and access approval | Commercial owner resolves whether it is commissioned before delivery schedules it |
| Compensation benchmarking report | E3: explicitly excluded | Keep excluded; do not turn a sales conversation into included work |
Five included, two conditional and one excluded item total eight. Calling this “five-eighths ready” would confuse the categories: the conditional items may be legitimate parts of the agreement, and the excluded report is not missing work.
The lead can accept preparation of the included criteria note while holding the conditional regional mapping. That bounded acceptance must not rewrite the client agreement. If E3 and S2 conflict, record the conflicting wording and route it to the firm's authorized commercial owner; this example does not resolve contractual priority or interpretation.
Make receiving-team acceptance explicit
A handover has been sent when a message or document is delivered. It has been understood when the receiving people can explain the assignment and act within its boundaries. Those are different events.
Ask the delivery owner to confirm the accepted next actions and identify anything still unresolved. They should be able to distinguish acknowledgement of receipt from acceptance of responsibility. Where the sales owner and delivery owner disagree about a commitment, preserve both accounts and use the designated resolution route.
The assignment handover guide helps structure that receiving conversation. It is particularly useful when the consultant who sold the work will not be responsible for its daily delivery.
Do not demand a ceremonial sign-off that conceals a material gap. If only part of the assignment can proceed, record the bounded acceptance and the work that remains dependent on clarification.
Keep version changes visible after kickoff
The handover is a baseline, not a frozen substitute for the assignment's later decision history. When the client agrees a change, connect it to the affected commitment and preserve what applied before.
Google Docs version history supports named versions. A meaningful version label can help people find the brief discussed at handover, but the tool does not determine whether a change was authorized.
If a new request changes scope, timing or required inputs, record it through the normal assignment process. Avoid editing the old promise ledger so that it appears the new request was always part of the original sale. The distinction matters when explaining rework or comparing planned and actual activities.
Commercial source material should remain accessible only to appropriate readers. A delivery summary can reference the controlling record without copying pricing, negotiation details or unrelated correspondence into broadly shared working notes.
Choose a small handover improvement to test
An initial workflow experiment can focus on one assignment's promise ledger. Use selected permitted proposal and handover materials, keep existing systems, and have a responsible reviewer check every summarized commitment against its source.
Define success before comparing outputs. For example, can the receiving consultant identify the next deliverable, its condition, the relevant source and the person who resolves an open question? Record the review effort and any substantive corrections, rather than counting a polished table as a successful handover.
The pilot success criteria provide a structure for agreeing that bounded task and an exit point. A useful result can justify further testing; it does not prove that a firm should migrate its CRM or automate its commercial decisions.