UK

Handover Plan Generator

A personalised, week-by-week handover plan based on your notice period. Pick how long you have, follow the steps, leave the team in good shape.

A month is enough time to do this properly. Document early, transition steadily, and finish strong.

  1. Week 1Plan and document

    • Write a handover document covering every recurring task, project, and key contact.
    • Identify successors for each area and check their availability.
    • List all external stakeholders who should know you're leaving and when.
    • Confirm the final working day, accrued holiday, and final pay date with HR.
    • Block the rest of the month into themed weeks — what gets handed over when.

  2. Week 2Start transitions

    • Run individual handover sessions with each successor.
    • Begin pairing on the work — let them lead with your support.
    • Send heads-up emails to external stakeholders introducing the successor.
    • Update internal documentation, runbooks, and any team wikis.

  3. Week 3Hand over the work for real

    • Successors take primary ownership; you're now the backstop.
    • Decline any new work that won't be finished by your last day.
    • Tidy up shared drives, archive old projects, remove personal data from work systems.
    • Confirm any non-compete, non-solicit, or confidentiality clauses that apply after you leave.

  4. Final weekTie up and exit

    • Final review with your manager — open items, risks, anything they should know.
    • Return equipment, revoke personal access, hand back passes/keys.
    • Confirm receipt of your P45 and final payslip in writing.
    • Send a brief goodbye note to your team, with a personal contact email if you'd like to stay in touch.
    • Take a moment to write down what you learned — useful for your CV and the next role.

Why a structured handover matters

The way you leave is what your manager and colleagues remember longest. A clean, well-documented handover protects your professional reputation, smooths your reference, and leaves the door open if you ever want to come back. It also makes the last fortnight or month much less stressful — there’s nothing worse than discovering a critical undocumented dependency on your final afternoon.

The plans on this page are templates. Adapt the actions to your role and don’t treat them as a checklist to tick off mechanically. The point is to leave behind the information your successor needs to do the work without paging you on day one.

What every handover should include

Whatever your notice length, the same five things make a handover land well: a written document covering all the work you own, a clear list of contacts and where to find things, time spent pairing with whoever takes over, an introduction to the external stakeholders, and a final review with your manager covering anything they need to know once you’ve gone.

What to skip if you’re short on time

If you only have a week, pick the highest-leverage handover — usually one document covering the most important three projects and a list of who to ask about each. Don’t try to onboard someone fully into a senior role in five days; instead, leave enough breadcrumbs that the team can stitch together what they need.

This page provides general guidance only. Your contract may require specific handover steps — check the relevant clauses before you finalise.