Executive search

Executive search closeout: agree the handback before archiving the work

A search-assignment closeout checklist for reviewed handback, residual commitments, record ownership and retention instructions, with a fictional example and practical evidence fields.

By LaisyPublished

An assignment can stop being active while its obligations remain open. The client may expect a final explanation, a candidate may be waiting for an agreed update and the firm's records may still contain unresolved instructions about future use.

Executive search closeout is the work of making that position explicit. It establishes what has finished, what has been handed back and who owns the remaining commitments. Clicking “archive” may be part of the process, but it does not by itself establish any of those facts.

The closeout record should be usable by someone who did not attend the final conversation. They need to understand the outcome, the residual work and which instructions govern the records. They should not have to reopen the whole assignment to discover that an important promise was left behind.

TL;DR

  • Confirm the assignment's actual state and the authority for closing it.
  • Separate accepted deliverables, residual actions and unresolved questions.
  • Record handback, access and retention instructions as distinct decisions.
  • Archive only through the appropriate process, with an owner for anything that remains open.

Copyable assignment-closeout checklist

Use this as a coordination record. It does not determine contractual, legal or professional obligations for a particular engagement.

Closeout areaEvidence or decision to retain
Closure instructionWho confirmed the assignment state, when and through which agreed route
OutcomeA factual description using the client's and firm's agreed terminology
DeliverablesWhat was accepted, what remains a draft and where the final record sits
External commitmentsOutstanding client, candidate or other agreed communications with responsible owners
Residual workEach continuing task, its owner, dependency and review point
HandbackRecipient, material, intended use and acceptance evidence
Record instructionsApplicable retention, restriction and future-use decisions, or the owner resolving them
Access and archiveThe authorized operational steps and evidence that they were checked
Next reviewThe event that will revisit an exception or confirm remaining closure work

Not every assignment ends with a placement. It may be paused, withdrawn or concluded another way. Preserve the real outcome rather than forcing different states into a convenient “completed” label.

Establish what is actually closing

Start with the latest confirmed instruction and the engagement's applicable terms. Identify whether the client is ending the assignment, pausing activity, changing scope or accepting a particular deliverable.

Compare that instruction with the mandate baseline. Resolve material discrepancies through the agreed route. A consultant's assumption about the client's next step should not become the recorded authority to close the engagement.

Write the outcome in language that distinguishes observation from interpretation. “The client confirmed that active research should stop” is different from “the market was exhausted.” The latter requires a separate basis and should not be inferred from an administrative end date.

If closure authority is unresolved, record that state and assign the clarification. You can prepare the handback without pretending the final instruction has arrived. Keep any restrictions on further activity visible while the question is settled.

Reconcile the promises before collecting the files

Review the commitments made during the assignment. Identify which were discharged, which changed and which still require an action. Look beyond the last formal update: a relevant promise may sit in a reviewed email or meeting record.

Distinguish a final communication from the evidence it references. A summary may be ready while an agreed supporting item remains under review. Do not mark both complete simply because the summary was sent.

Use the client-update structure to explain the final position where appropriate. Keep the account factual, make open questions visible and state what response is needed. Avoid turning a final update into a claim that every possible obligation has been settled.

For candidate communication, check what was actually agreed and who should deliver it. Do not use a closeout exercise as a reason to send generic messages to everyone associated with the search without reviewing context and recipients.

Keep confidentiality attached to the handback

A final folder can contain material prepared for different audiences. Internal working notes, reviewed client material and source-restricted accounts should not become one undifferentiated package.

For member firms, the AESC Candidate Bill of Rights addresses confidentiality around candidate interest and the search process. That member standard supports a careful audience check; it does not provide a universal retention schedule or establish Laisy's membership or certification.

For each item being handed back, identify the recipient, purpose and relevant restriction. Review linked records as well as attachments. A concise summary can still expose inappropriate material through a link whose access was never checked.

Where the intended use is unclear, ask before expanding distribution. Preserve the useful fact that a question remains open without copying the underlying confidential detail into a broadly accessible closure checklist.

Separate retention instructions from archive convenience

An archive location is a storage choice. It does not decide why information should be kept, how long it is needed or whether a different restriction applies.

The UK ICO's storage-limitation guidance explains that UK GDPR does not prescribe universal retention periods; the appropriate period depends on the purpose. This is UK-specific guidance, not a determination of your firm's obligations. Refer an unclear instruction to the appropriate responsible person rather than inventing a duration.

Record the actual approved instruction and its source. If a decision is pending, give it an owner and review point. Do not label “keep everything” as a policy because the archive has spare capacity, or delete records simply because the assignment no longer appears in an active view.

Future use needs its own context check. The candidate-rediscovery guide addresses reviewing earlier information for a new search question. Closure should preserve the applicable boundaries, not imply that every old record is automatically suitable for every later assignment.

Fictional example: close the assignment, keep the exception visible

The following example is synthetic. Its item counts and review arrangement are original illustrations, not evidence of a customer outcome or a prescribed closeout timetable.

A fictional search firm receives a confirmed instruction to stop an assignment. The consultant identifies five closeout items. Three have accepted evidence: the final client summary, the agreed deliverable handback and the assignment-state confirmation. Two still require work.

One outstanding item is a previously agreed candidate communication. The other is a question about the applicable record instruction, referred to the responsible person. Neither should disappear because the assignment is removed from the active board.

ItemRecorded positionResponsible next step
Final summaryReviewed and received through the agreed channelRetain the accepted record pointer
Deliverable handbackRecipient and acceptance recordedKeep the audience boundary with the material
Closure instructionConfirmed and linkedUse the actual state in the assignment record
Candidate communicationOpen; intended recipient and purpose identifiedNamed consultant prepares and reviews the agreed message
Record instructionUnresolved; no duration inventedResponsible owner resolves the question and records the approved instruction

The consultant records the assignment as closed with identified residual actions, if that state is supported by the firm's process. The residual actions remain visible to their owners. The closeout note does not claim that archival processing, communication or record decisions are already complete.

Make ownership and access changes explicit

Handing someone a link does not necessarily transfer file ownership or change access. Those are operational actions with their own conditions and consequences.

Google Drive's ownership-transfer guidance describes different conditions for personal and work or school accounts. For example, work or school transfers are restricted to the same organization. That is a Google product rule, not a Laisy integration or permission to transfer files during closeout.

Ask the appropriate owner to confirm the intended operational change through the normal process. Check that the recipient can use the necessary final material and that unwanted access has been addressed where required. Record the verification without copying credentials into the checklist. Preparing the closeout document does not itself authorize a transfer or access change.

If the colleague responsible for the assignment is leaving, use the consultant handover for continuing work. The closure record should point to that handover, while preserving the difference between ending an assignment and transferring responsibility for its remaining obligations.

Preserve the context needed to interpret archived records

An archived spreadsheet can look complete while lacking definitions, source dates or explanations of unresolved cases. Keep the context needed for an authorized future user to understand what the records mean.

The Government Data Quality Framework includes an archive-or-destroy stage and emphasizes retaining useful quality context. It is non-prescriptive public-sector guidance, not a private firm's retention policy. Its distinction between completeness and accuracy is also relevant: a filled field can still be wrong.

Record the scope and status of important artifacts. A market snapshot reflects a particular question and period. A working assessment is not necessarily a final client-approved position. A missing source should remain a limitation, even if a tidy archive format makes the record look finished.

Prioritize the context needed to interpret consequential material and assign continuing owners to exceptions. Make substantive corrections traceable.

The AESC Client Bill of Rights describes ongoing communication for member engagements. Check which client commitments still need a reviewed explanation at closeout; the reference does not establish Laisy membership.

For a handback document maintained in Google Docs, its version-history guidance explains how to inspect earlier changes. Identify the accepted version explicitly so an older working copy is not mistaken for the final record.

Review the closeout as a handback

Have an appropriate colleague read the closure record without a spoken explanation. Can they identify the confirmed outcome, locate the accepted deliverables and explain who owns each remaining action?

Then check the operational evidence separately. A document that says “access reviewed” is weaker than a record identifying who checked the relevant state and when. Do not mark an operational step complete merely because it was included on the checklist.

Frequently asked questions

Is archiving the assignment enough to close it?

Check the actual engagement and remaining commitments. Archiving can change visibility or storage without settling handback, communication, record instructions or responsibility for open work.

How long should search records be retained?

Use the applicable approved policy and instructions for the information and purpose. This checklist supplies no universal duration. Refer uncertainty to the responsible person and preserve the question until it is resolved.

Can an assignment close with actions still open?

Follow the firm's actual process and engagement requirements. Where a closed-with-residual-actions state is appropriate, keep those actions visible, accepted and reviewable rather than treating them as completed.

Should AI decide what to delete at closeout?

Keep deletion and retention decisions with authorized people and established processes. A draft checklist can expose missing instructions; it cannot create authority or determine the correct treatment of every record.