A useful employee handover document tells the next person what is happening, what needs attention and where the approved information lives. It should support continuity without becoming a dump of old emails or confidential material. Start with the work the receiving colleague will need to manage first.
This checklist works for a role change, departure or extended transition. Adapt it to your organisation’s approved process. A handover document does not replace formal access changes, employment procedures or specialist instructions.
1. State the scope and effective date
Identify which responsibilities are being handed over, who is receiving them and when ownership changes. Note anything outside the handover so the recipient does not assume it is included. A dated scope helps distinguish a current handover from an old reference file.
For example, separate recurring reporting from a project still owned by another team. Ask the receiving manager to confirm the division of responsibilities. Do not leave ownership implied by whoever happens to be copied on the document.
2. List active work by next action
For each active item, record its current status, next action, owner and relevant deadline. Use a brief factual description rather than a complete history. Distinguish confirmed commitments from proposed dates or unresolved requests.
A useful entry is: “Draft reviewed; waiting for the owner’s decision on the final section; next follow-up with the project lead.” An entry saying “ongoing” does not tell the recipient what to do. Link to the authorised record rather than copying every attachment into the handover.
3. Explain recurring tasks and their triggers
List tasks that happen regularly or in response to a particular event. Include the trigger, expected output and where the current procedure is stored. Clarify who reviews the result and how exceptions are handled.
Avoid relying on phrases such as “do the usual report”. The recipient may not know the usual timing, data source or reviewer. Where a procedure is missing, write a concise outline and identify it as requiring review rather than presenting an untested personal method as official policy.
4. Record important contacts and decision owners
Identify the role or approved contact responsible for decisions, approvals and specialist questions. Explain when to involve them. Prefer maintained directories or team contacts where appropriate so the handover does not become stale immediately.
Do not include unnecessary personal details or informal opinions about colleagues. “Finance confirms the payment status” is useful; commentary about who is difficult to work with is not. Keep the document factual and relevant to the receiving person’s responsibilities.
5. Point to files and arrange access properly
Link to the current authorised folder, system or record. Ask the recipient to check that they can access what they need before the handover ends. Identify requests still awaiting approval.
Never put passwords, recovery codes or another person’s login details in the handover. Access should be granted through the organisation’s approved process. A link that works only for the departing employee is not a completed transfer. Keep sensitive material restricted to the people who need it.
6. Make risks and unresolved decisions visible
Describe known blockers, dependencies and decisions that remain open. State the evidence and next owner without exaggerating or hiding uncertainty. If a deadline depends on another team, identify that dependency.
Separate a confirmed problem from a possible risk. “The supplier has not confirmed the date” is different from “The supplier will be late”. This helps the recipient follow up appropriately. Do not close an issue in the handover simply because responsibility is moving to someone else.
7. Test the handover with the recipient
Walk through one real or permitted example and ask the recipient to find the relevant information. Check whether the next action, source and escalation route are understandable without extensive verbal explanation. Update the document where they are not.
Agree how remaining questions will be handled within the actual transition arrangement. Do not assume the departing employee will remain indefinitely available. Record acceptance of the handover’s scope while keeping unresolved items clearly assigned, rather than treating a signature as proof that every issue is solved.
A compact handover template
Use one row per item: responsibility; current status; next action; owner; due date or trigger; source link; unresolved issue. Add a separate section for recurring tasks and access requests. Keep the current version in an approved location.
Hypothetical example: a monthly report is drafted but not approved. The handover names the reviewer and links to the draft, rather than labelling the report complete. The recipient knows the next action is approval follow-up, not recreating the work.
Final check
Can the recipient find the latest file, explain the next action and identify who can decide an exception? If not, revise that part before adding more background detail.
Should every email be copied into the document?
No. Summarise the relevant state and link to permitted source records. Avoid unnecessary duplication and personal information.
Is a leave handover different?
A temporary absence usually needs a narrower scope and return update. See the leave handover checklist for that situation.
