Executive search
Candidate contact continuity: preserve promises when the consultant changes
Keep candidate-facing commitments usable through a consultant change: confirmed preferences, promised updates, scheduled messages, context and an accepted next owner.
A consultant changes responsibility midway through a search. The incoming colleague can find the candidate's profile and recent notes, but cannot tell whether an update was promised, whether a draft was sent or whether the person asked to use a different channel.
Candidate contact continuity means carrying those commitments forward with their context. It gives the next consultant an accurate account of what was agreed and what remains to do. The candidate should not receive a second introduction based on the firm's inability to find its own promise.
Keep this work distinct from candidate assessment. A contact preference, an unanswered message or a request for clarification should not become an inferred judgment about motivation or suitability. The record exists to support appropriate communication and follow-through.
Copyable candidate-contact continuity note
Prepare the note from selected records appropriate to the handoff. Link to the permitted source where necessary instead of reproducing the entire conversation history.
| Field | What the next consultant needs |
|---|---|
| Assignment context | The relevant search and the current confirmed stage |
| Last meaningful exchange | Event date, participants, subject and source pointer |
| Candidate preference | The channel, timing or other request actually expressed, with its context |
| Firm commitment | What the consultant agreed to do and any condition attached |
| Communication state | Proposed, drafted, reviewed, scheduled, sent or acknowledged, as established |
| Open question | What remains unknown or dependent on an appropriate response |
| Next owner | The person accepting responsibility for the outstanding commitment |
| Review trigger | When or after which event the owner will check the position |
| Boundary | Relevant confidentiality or use instruction carried with the account |
This is an original working structure. It should help someone explain the next action, not provide a speculative narrative about the person's intentions.
Reconstruct the promise before writing a new message
Start with what was actually said. Was the commitment to provide an update after a client meeting, to confirm receipt of material or to answer a particular question? Preserve any condition that affects the timing or meaning.
Use the consultant handover guide to connect the commitment with the wider assignment. The incoming colleague needs the current instruction and relevant dependencies as well as the contact record.
Separate a suggestion from a promise. “We could discuss this next week” may not establish an arranged conversation. A note that someone planned to send an update does not establish that the candidate was told to expect it.
If the account is unclear, ask the appropriate colleague or retain the uncertainty. Do not generate a confident “as agreed” opening merely because it makes the new message read smoothly. A factual clarification can be more respectful than pretending the firm's record is complete.
Preserve preferences within their actual context
Record what the person expressed and the situation in which it applied. A preference about arranging one conversation may not describe every future assignment or disclosure.
For AESC member firms, the Candidate Bill of Rights addresses confidentiality in the search process. That member standard is a reason to carry the relevant boundary with the handoff, not a claim that every conversation has identical terms or that Laisy certifies compliance.
Avoid turning a preference into a personality label. “Requested an email before arranging a call” is more precise than “hard to reach.” An unreturned message has several possible explanations; the contact record should not convert the absence of a reply into a suitability judgment.
Where a preference or instruction needs clarification, assign that question through the appropriate route. Do not treat an empty field as permission to choose any channel or circulate the person's interest more broadly.
Distinguish the communication states
A draft exists in a preparation context. A reviewed draft has passed a particular content check. A scheduled message may still be awaiting its send event. A sent message does not prove that the recipient read, understood or accepted it.
Keep those states visible where they affect the next consultant's action. This prevents a colleague from promising an update that has already been scheduled, or assuming a candidate received material that never left a draft folder.
The candidate research-note method helps separate observations from interpretation. Apply the same discipline to communication: a timestamp establishes an event in a system, while the meaning of a reply depends on its actual content.
Do not ask the incoming colleague to infer state from the document's title. “Final update” could still be an unsent draft. Attach the relevant evidence or an explicit unresolved state to the handoff.
Check scheduled work before creating another commitment
Review appropriately accessible scheduled messages and tasks that belong to the transferred work. A colleague may have prepared a communication to send after a planned event that has since changed.
Gmail's scheduling help says scheduled messages use the scheduling time zone and may send a few minutes after the selected time. It also describes cancellation returning a message to draft. Those are Gmail mechanics, not a delivery guarantee or Laisy sending feature.
Identify the responsible person for any required change. A handoff note should not authorize someone to enter another person's account or silently cancel correspondence. Use the firm's proper process and record the resulting state.
Where a message depends on a client decision, verify that the decision occurred before relying on the prepared wording. The outgoing communication should describe the current position, not a forecast embedded in a draft several days earlier.
Make dates and time zones explicit where they matter
“Tomorrow afternoon” becomes ambiguous when a note crosses time zones or is read later. Preserve the actual event date and the relevant zone, with the source of any agreed appointment.
Google Calendar's time-zone guidance explains selected event time zones and UTC conversion with local display. That product behavior helps explain why two colleagues can see different clock times for the same event. It does not establish which time was agreed in a separate message.
Check the actual event and date instead of relying on a remembered seasonal offset. If the intended time cannot be established, record the question and have the appropriate owner confirm it before making another commitment.
Avoid converting every conversation into a rigid service promise. Preserve the timing actually agreed and distinguish a proposed review point from an externally communicated deadline.
Fictional example: a handoff with three different next steps
These names, dates, sources and commitments are invented. Consultant Noor is transferring Cedar to consultant Eli on 6 November. The note separates three candidate-facing items rather than creating three fresh introductions.
| Item and source | Established state | Accepted next action in the exercise |
|---|---|---|
| Person A; Noor's 4 November email: “I will update you after Friday's client discussion” | Promise is conditional on that discussion; no outcome recorded yet | Eli checks the discussion outcome, then prepares the appropriate reviewed update; no invented shortlist decision |
| Person B; approved draft B-v2 and the responsible owner's scheduled-message record | Email is scheduled for 9 November at 10:00 Asia/Hong_Kong; not established as sent | Account owner verifies the live scheduled state and current wording; Eli does not send a duplicate or enter another person's account |
| Person C; 5 November reply asking which region a role covers | Question received; source brief conflicts with a later note | Eli obtains the assignment owner's clarification before coordinating a response |
In the second row, 10:00 Asia/Hong_Kong on 9 November is 02:00 UTC on that date. Retain the source zone and actual date when another colleague views the event locally. The conversion is arithmetic for this invented appointment, not evidence that a real message was scheduled or delivered.
The handoff is accepted when Eli can explain each obligation and the responsible owner has taken the relevant next action. A scheduled state is not a send event; a send event is not evidence of reading, interest or acceptance. Missing source access stays an open question instead of becoming a guessed communication state.
Connect tasks to the commitment they represent
An internal task should identify the relevant person, assignment and source promise. That context helps its owner act without searching unrelated notes.
Clockwork's task-panel documentation describes task links to people, projects and deals, and local-time display. Those are vendor-specific features. A task's presence or assignment does not establish that someone accepted the commitment or that a candidate agreed to the proposed next step.
Ask the incoming owner to read back what they are taking on. Establish the dependency, completion evidence and next review point. If the work needs a different person, keep the responsibility question open until it is resolved.
Avoid closing a task solely because the owner changed. A transfer of responsibility should preserve the original commitment and its current state, with a clear account of who will now act.
Keep the client dependency visible without exposing unnecessary detail
Some candidate updates depend on client information that the consultant cannot yet confirm. Record that dependency factually and identify who is obtaining the answer.
The client-update workflow can help prepare a clear request for the missing decision. Keep the candidate-facing message appropriate to its audience rather than copying an internal explanation of the client discussion.
If a promised timing cannot be met, the appropriate consultant needs to decide the reviewed communication. Do not invent a client decision to give the candidate a more definite answer.
When the assignment ends or changes, check which commitments remain relevant and which need clarification. A change in the firm's internal assignment state does not automatically settle a promise already made to someone outside the firm.
Test the handoff on one suitable assignment
Select a bounded continuity-preparation task and agree the reviewer before changing the firm's wider workflow. Check whether the incoming colleague can identify the accepted promise, current state and appropriate next step from the selected material.
Use pilot success criteria to include the effort of checking and correcting the note. A Laisy discussion can begin with selected permitted inputs and a reviewed output alongside current tools, with a point to continue or stop. No automatic nurturing, inbox access, message sending or guaranteed response is promised.