Handover Before an Employee Leaves: How to Test the Successor’s Readiness Before the Last Day

Why is a handover note not enough?

Every manager knows the traditional handover note: a list of files, a line on work in progress and a signature in the final week. It proves that something was handed over, but not that the successor can do the job, especially when an unusual case arrives.

The expertise a successor needs is often not in the files at all. Why is a particular type of request rejected? What is the early sign that a transaction will stall? Who can you call when another department is slow to reply? What is needed here is a handover plan for the weeks before a particular employee leaves, not a full organisational knowledge management system.

When does the handover plan start, and who leads it?

Start on the day the departure date is known, not in the final week. Retirements are usually known months ahead, resignations come with a notice period set by the contract and each country’s labour law, and internal transfers are agreed in advance. In every case, the practical stages, such as demonstration and supervised practice, need time that writing cannot shorten.

The line manager leads the plan, not the leaver and not HR alone. The manager names the successor, the priority tasks and the testing dates; the leaver explains and supervises; the successor does the work and asks questions. HR co-ordinates the leaving or transfer procedures and links the handover to them, so that final clearance is not completed before the handover is signed off and equipment returned. The manager also needs to tell the leaver plainly that handover is part of their job in their final weeks, not extra work on top of their usual duties, and to lighten their current workload accordingly.

What should be passed on first?

The succession planning services of the U.S. Office of Personnel Management (OPM) describe the aim as reducing the impact of institutional knowledge loss when employees retire or leave, starting with an assessment of key positions, their risks and the readiness of potential successors. ^[1] The same approach works at the level of a single employee.

Start with four questions for the leaver and their manager:

• Which tasks stop the work when they are missing? Even infrequent ones, such as an annual close or a licence renewal.
• Which decisions depend on their judgement? Ask them to explain why they choose one route over another, not just the steps.
• Which exceptions does the guide not cover? And which cases they already know will be returned, and why.
• What commitments are open? Deadlines, replies awaited from other parties or promises made to customers, and who the other party is in each case.

Do not start with what is already well documented. A procedure written in an approved guide can be read by the successor later; the reasons behind decisions and the exceptions leave with their owner unless they are passed on now.

How do you combine documentation, demonstration and practice?

Writing alone passes on the steps but rarely passes on judgement. Effective handover therefore moves through stages that end with the successor doing the work themselves.

Keep each document short and tied to a single task, and write the decision points explicitly: “if this, do that; otherwise escalate to [job title]”. If you record a video explanation, split it by task rather than making one long recording.

What goes into a single-task guide?

• Purpose: why the task exists and who is affected if it is late.
• Inputs: what must arrive before starting, and where it comes from.
• Steps: in order, noting the system or form used.
• Decision points: when the person doing the task chooses between two routes, and on what basis.
• Exceptions and escalation: cases that do not follow the steps, and to whom they go, by job title.
• Sign of completion: what proves the task was finished correctly.
• Access needed: the systems required and how to request access to them.
• Review: who owns the guide and when it is reviewed.

These elements do not need many pages; one or two pages per task are usually enough if the decision points and exceptions are clearly written.

Hypothetical example: the procurement expert

Hypothetical example: in a procurement team at a Gulf organisation, one long-serving employee could spot the transactions that finance would send back before they reached finance. When he announced he was leaving, his manager selected a number of past transactions and removed the sensitive data from them.

The expert sat with his successor and together they recorded the reasons for returns and what proves each transaction is complete. The successor then processed a full practice transaction, which revealed that one exception depended on an approval the guide did not mention, because the expert had always obtained it by phone. The approval route was documented and signed off by the process owner before his last working day. Had the team relied on a traditional handover note, the gap would have surfaced for the first time on a live transaction, after the only person who knew the answer had gone.

What stays out of the handover file?

Log-in details and secrets. The leaver does not hand over passwords or accounts to the successor. The successor receives their own access through the approved provisioning route, and the leaver’s access is removed as soon as employment ends. The UK Information Commissioner’s Office (ICO) audit toolkit recommends documenting the leavers process, keeping a record of access removals, having managers confirm removal, and keeping a list of staff with privileged access, removing it promptly once it is no longer needed. ^[2]

Official records. These remain in the organisation’s custody and do not leave with the employee. The U.S. Department of Commerce guidance for outgoing employees requires all organisational property and equipment to be returned before departure, with the property custodian confirming receipt and reassigning it, and refers any question about keeping or copying records to the records officer. ^[3] The same principle applies in Gulf organisations under each organisation’s policies and the data protection legislation of its country.

Contacts. Record them by job title and official channel, not by the leaver’s personal numbers or acquaintances.

How do you check the successor is ready?

Success is not measured by the number of documents, but by what the successor can do and explain without going back to the leaver.

Ask the successor to carry out a routine procedure from the guide alone and to answer a hypothetical case involving an exception: when do they escalate, and to whom? Then confirm they can reach every system they need with their own access. Wherever they stumble reveals what the guide is missing, not only what the successor is missing.

What if the handover period is short?

Prioritise: the tasks that stop the work when missing, then the exceptions only the leaver knows, then open commitments and their deadlines. Anything there is no time for is written down as a gap with an owner and a date for resolving it, not left unspoken. Set a date to review the guide once the successor has used it in real work for a month or more.

If the employee leaves before testing is complete, agree with them, where possible and as the organisation’s policy allows, a limited official channel for questions during the first weeks, routed through the manager rather than personal messages, with the answers recorded in the guide itself.

Conclusion

A good handover tests the successor, not the document: selected critical tasks, the reasons behind decisions written down, and supervised practice before the last day. Keep access and records within the organisation’s formal routes; they are part of the handover, not a separate procedure.