How to Prepare a Work Handover Before Leaving a Job

A useful handover is not a history of everything you did. It is a working record that lets the next owner see each live item, its current state, the next action and date, who can decide, and where approved material lives. Start by agreeing the boundary with your manager, then build the record, walk through the priority items once, and update it with the decisions made.

Your employer's required format, confidentiality rules, records policy, notice process, and IT procedures take priority over this template. The document does not guarantee continuity, complete a legal clearance process, or make you responsible for future questions after your last day.

Agree the handover boundary before you write

Confirm five points with your manager: the recipient, the last working date or coverage period, the required format, the approved storage location, and the information that must not enter the document. Also state whether this is a permanent departure, an internal transfer, or temporary leave. The same table can serve all three, but the owner and timing decisions will differ.

Keep the output bounded. University Hospitals Birmingham advises departing employees to cover day-to-day tasks, ongoing projects, deadlines, meetings, contacts, documents, and shared access, then talk the handover through before the last day. Treat those categories as prompts, not as proof that every workplace uses the same process.

Boundary note: This handover covers active work and recurring responsibilities through [date]. It follows [employer format or policy]. Questions about records, access, or confidential information go to [approved role or team].

Build an inventory from evidence, not memory alone

Gather active projects, recurring responsibilities, near-term deadlines, standing meetings, key relationships, tools, records, and pending decisions. The University of Iowa HR knowledge-transfer guidance similarly groups responsibilities, processes, projects, tools, records, and contacts. Your final structure can be shorter and role-specific.

A personal log can help you reconstruct the facts. If you have one, gather accurate source material from your work log, but do not paste the private log into the shared record. Select only what the team still needs. Remove completed history unless it explains a live decision, dependency, or risk.

Sort the inventory into four groups: work that must continue, work that needs a decision, work that can be archived, and work that should stop. Ask your manager to confirm the groups. Do not silently assign a colleague or promise their capacity.

Write each live item as an action record

Use the table fields in the same order so another person can scan them quickly. Label each statement as a confirmed fact, a recommendation, or an unresolved question. “The review is booked for 14 October” is a fact. “Move the review to the interim owner” is a recommendation until the manager agrees. “Who approves the final pack?” is an unresolved question that needs a named decision.

A useful row does not say “Continue supplier work.” It says what is ready, what must happen next, when it matters, who currently owns the step, who can decide, what may block it, and where the approved material sits.

A handover becomes usable when a live item moves from status to action, date, ownership, and an approved location.

Three fictional examples

The examples below are deliberately generic. Do not copy names, customer data, confidential metrics, unreleased work, or links that grant access.

Operations task

Item: monthly facilities check. Fact: September checklist is complete. Next action: open the October checklist from the approved shared folder and confirm any repairs with the facilities contact. Next date: first working day of October. Owner: manager to confirm interim owner. Decision-maker: office manager. Risk: one repair request is awaiting an approved vendor response.

Project dependency

Item: launch-readiness review. Fact: the draft checklist is complete. Recommendation: keep the current review sequence. Unresolved question: whether the legal review moves before or after the technical sign-off. Next action: project lead records the decision at the next checkpoint. File location: approved project workspace.

Recurring stakeholder responsibility

Item: weekly partner update. Fact: the next agenda is drafted. Next action: confirmed owner reviews the agenda and sends it through the normal channel. Next date: Tuesday morning. Owner: named only after the manager confirms. Relationship note: use the team contact record, not a private phone number.

Transfer access without transferring credentials

Name the system, approved folder, record owner, and access-request route. Do not paste passwords, one-time codes, personal-account credentials, real customer or employee data, confidential metrics, or a link that itself grants access. The UK National Cyber Security Centre's end-user guidance is explicit that a password should never be disclosed to a manager, colleague, or support staff. If access must change, use the employer's approved IT route.

Separate file ownership from account access. A manager may need work files transferred before an account closes. UMKC's manager exit resources, for example, pair project status and pending work with transferring ownership of work-related files and coordinating access. Its timing and systems are local policy, not universal rules. Your employer decides the correct sequence.

Triage the record with your manager

If time is short, do not try to document every exception. Ask which items need a walkthrough, which can be archived, which need interim ownership, and which should stop. Use Tadween's guide to agree what must finish, move, or stop when the remaining work exceeds the time available.

Send a short note that asks for review rather than implying the handover is complete:

Subject: Work handover review for [role or coverage period]

Hi [Manager], I have drafted the handover for active work through [date]. It records the current state, next action and date, proposed or confirmed owner, open decisions, dependencies, and approved file locations. Could we use [meeting time] to confirm priorities, owners, access requests, and any items that should be archived or removed? I will update the final record with the decisions and save it in [approved location].

Run one walkthrough and close the record

During the walkthrough, start with the nearest deadline and highest operational consequence. For each unresolved row, capture one of three outcomes: a named decision, a named follow-up owner and date, or a clear decision to archive or stop. If nobody has accepted ownership, write “manager to assign” rather than presenting a suggestion as agreement.

After the meeting, update the owners, decisions, unanswered questions, and final storage location. Ask the manager to acknowledge that the record was reviewed. Acknowledgement is not a promise that every future problem has been prevented, and it does not create an open-ended obligation to stay available after departure.

Final handover checklist

• The scope, recipient, end date, format, and approved storage location are confirmed.
• Every live item has a current state, next action, next date, owner status, decision-maker, dependency or risk, and approved file location.
• Facts, recommendations, and unresolved questions are visibly different.
• No password, one-time code, personal account, real sensitive data, confidential metric, or access-granting link appears.
• Colleagues are named as owners only after confirmation.
• Priority items were walked through and the decisions were written back into the record.
• The final copy follows employer policy and has a clear access-request route.

A personal work log helps you remember; the handover turns only the work the team still needs into a controlled shared record. Once the transition is complete, Tadween can help you prepare for the first months of your next role with a realistic plan you refine with your new manager.