The placement invoice went out, so everyone called the search finished. Three rejected candidates still showed “client interview.” Two client guests retained portal access. The market map sat in a partner’s spreadsheet. Commercially closed, operationally open.
What belongs in a search-mandate closeout?
A search closeout confirms the commercial outcome, gives every candidate an accurate status, resolves open interviews and tasks, removes unnecessary client access, decides what data is retained or deleted, captures reusable market learning and assigns any post-placement obligations.
Closure is needed whether the result is a placement, cancellation, pause, internal hire or lost mandate. The reason changes the follow-up, but unfinished candidate communication and stale access create the same trust and security problems.
Run the closeout from a named owner and a dated checklist. “The team knows” is unreliable after consultants change desks, the client restructures or a candidate asks what happened six months later.
Classify the real closure outcome
Use a specific outcome code and narrative instead of one generic “closed” status.
Distinguish placed, client-cancelled, candidate-withdrew, role-filled-internally, budget-withdrawn, paused and agency-released. Record the effective date, commercial reason and person who confirmed it. A paused mandate should have a review date; otherwise it becomes a permanent open process without active work.
Separate the client outcome from each candidate outcome. One successful placement leaves shortlisted candidates rejected, withdrawn, held for another role or awaiting final communication. Bulk-changing everyone to “closed” erases useful context and can trigger the wrong future message.
For confidential mandates, note whether the existence of the search remains restricted after closure. A succession project does not become public merely because the selected executive signed.
- Final mandate outcome and effective date.
- Named client confirmation and internal owner.
- Commercial obligations still open.
- Confidentiality conditions that survive closure.
Resolve every candidate journey
No person should remain in an ambiguous active stage after the mandate ends.
List all approached, screened, presented and interviewed candidates. Assign a truthful final status, communication owner, channel and completion time. Candidates who invested in interviews deserve a personal update; early-stage prospects may need a shorter message, but silence is still a decision with consequences.
Do not expose the successful candidate or confidential client reasoning in rejection messages. Give useful process feedback only where it is supported, fair and authorised for sharing. Avoid converting subjective client remarks into permanent labels on the candidate profile.
Record future preferences separately. A candidate can be wrong for this mandate and valuable for another. Confirm whether they want continued contact, note relevant role interests and remove closed-search automation. Reuse should follow the agency’s lawful process and current information, not an assumption that one application lasts forever.
Close client decisions, feedback and approvals
Capture the final decision evidence before stakeholders and context disappear.
Complete outstanding scorecards and clarify which comments informed the decision. Remove duplicate drafts and mark the final shortlist version. If the client rejected a candidate for a vague “fit” reason, don’t polish that into objective evidence. Record the limitation and avoid reusing the phrase as a universal judgement.
Ask the client owner to confirm no direct interviews, reference conversations or informal approaches remain active. A late stakeholder introduction can restart contact after candidates were told the process ended. Close calendar holds, assessment invitations and external-provider tasks.
Where a candidate was hired, hand the relevant facts into the post-placement or guarantee workflow without opening the entire recruitment file to payroll, finance or client-support colleagues. Different work needs different access.
Revoke portal access and account for exports
End access by default, then retain only what a defined continuing purpose requires.
Expire guest users, pending invitations and public links for the closed workspace. Remove support access and API feeds used only for the mandate. If the client needs a final report, publish a deliberate closeout view rather than leaving the live candidate pipeline open indefinitely.
Check downloads and emailed attachments. The agency may not control every client copy, but it should know what was shared and communicate the agreed retention or disposal steps. Candidate withdrawals, restrictions or corrections need their own recipient follow-up.
Test that removed users cannot reopen old sessions and that scheduled reports stop. Access revocation written in a checklist but not enforced technically is paperwork, not closure.
Apply the retention schedule by record category
Closeout should trigger a reasoned decision, not immediate deletion of everything or indefinite storage of everything.
Separate candidate profiles, CV versions, interview notes, vetting material, client feedback, contracts, invoices, conflict records and access logs. Their purposes and legal requirements differ. The GDPR’s storage-limitation principle ties retention to necessity for a purpose; it does not prescribe one universal recruitment period.
The ICO’s recruitment guidance, currently presented as draft, likewise says organisations should set clear periods and carefully assess what remains necessary after recruitment. European agencies must apply the law and limitation periods relevant to their country and role in the processing.
Where records are retained for legal claims or contractual administration, narrow the fields and access. A possible dispute does not make every raw interview note necessary. Put review dates on exceptions and make expired records enter an actual disposal queue.
“Keep for compliance” is not a retention rule. Name the purpose, record category, period, owner and deletion event.
Preserve market intelligence without preserving every profile copy
Useful search learning can often be separated from unnecessary identifiable detail.
Capture target-company coverage, title variants, compensation signals, location constraints, response themes and search channels that worked. Distinguish evidence gathered during the mandate from consultant inference. These lessons improve the next brief and help explain where the market was genuinely tight.
Ask whether the insight needs a person’s identity. An aggregated note such as “most regional CFO prospects required two remote days” may support planning without retaining a deck of identifiable rejected profiles in the client workspace. True anonymisation is demanding, so do not call data anonymous if people remain inferable from niche roles and companies.
Link reusable candidate relationships to the agency CRM only where the purpose, transparency and current contact rules support it. Copying every person into a generic talent pool at closeout creates volume, not relationship intelligence.
Complete commercial and post-placement handover
Fees, guarantees and onboarding checks need owners without keeping the search operationally open.
Confirm invoice milestones, expenses, rebate or replacement terms and any client purchase-order requirement. Assign guarantee-period check-ins and decide what outcome evidence will be recorded. Finance needs contractual facts, not broad access to candidate notes.
Schedule candidate and client check-ins with clear purpose and expected audience. Post-placement support should not become hidden monitoring of an employee. Tell the person what follow-up the agency offers and keep notes proportionate to that relationship.
If the mandate ended without a placement, record any agreed credit, exclusivity release or future restart condition. Settle these details before the team reuses the same brief under a new project name.
Run a short retrospective and certify closure
The final review should produce a few decisions, not a ceremonial meeting nobody can use.
Compare the original brief with the final outcome. Which must-have changed? Where did client feedback stall? Which source produced credible candidates? What caused withdrawal? Use concrete process evidence and avoid blaming individuals for constraints the brief created.
Choose one or two actions with owners: tighten intake evidence, shorten feedback time, change the market-map taxonomy or improve compensation calibration. Store the lesson where the next mandate owner can find it. A retrospective buried in a slide deck does not change the workflow.
Certify candidate communications, access removal, retention decisions, commercial handover and unresolved exceptions. Name the person who accepted any exception and its due date. Only then mark the mandate operationally closed.
Search-mandate closure control record
A useful closeout links each workstream to evidence and a named owner.
| Closeout area | Evidence of completion | Owner question |
|---|---|---|
| Outcome | Specific reason, date and client confirmation | Who authorised closure? |
| Candidates | Final status and completed communication | Has every active person been told? |
| Client workspace | Guests, links, feeds and sessions revoked | Can any stale user still enter? |
| Records | Category-level retention or disposal decision | What purpose supports each exception? |
| Commercial | Invoice, guarantee and future obligations assigned | Who owns the next milestone? |
| Learning | Evidence-based retrospective and action owner | What changes on the next search? |
Closeout limitations
Retention, deletion and client-recipient duties depend on the actual legal roles, national law, contracts and individual requests. This checklist supports the operational review but does not determine those conclusions.
A closed mandate can still have valid post-placement or legal work. Keep those purposes narrowly separated rather than leaving the full recruiting workflow and every user permission active.
Search-mandate closure questions
These answers help agencies close searches without losing relationships or leaving data and access behind.
When should a paused mandate be closed?
Give every pause a dated review and owner. If the client cannot confirm a realistic restart, close active candidate work and access, communicate honestly and create a new controlled restart later.
Should every rejected candidate record be deleted at closure?
Not automatically. Decide by record category, purpose, lawful basis, transparency, national rules and candidate instructions. Remove what is no longer necessary and separate justified retained records from active recruiting.
Can the client keep a final shortlist?
That depends on purpose, roles, agreements and the information given to candidates. Do not leave a live portal open by default; document any final report, audience, retention and later disposal.
What is the most useful closeout metric?
Start with unresolved work: candidates without a final update, active guests, open tasks and records without a disposition. Revenue outcome matters, but it does not prove operational closure.
Official sources for retention and closeout decisions
The GDPR, EDPB and ICO materials explain storage limitation, rights, security and the need for defined recruitment-record periods.
- EUR-Lex: General Data Protection Regulation — principles, rights and security of processing
- European Data Protection Board: Secure personal data and review access authorisations
- UK Information Commissioner’s Office: Recruitment and selection guidance, currently identified as draft
Continue improving agency operations
Review access to the client portal · Manage candidate withdrawal across systems · Plan GDPR candidate-data retention · Explore Yena for recruitment agencies
Close the mandate without losing its useful memory
Yena brings candidate status, client collaboration, search evidence and accountable follow-up into one workflow so a finished search is actually finished.
See Yena for recruitment agencies