How to write a remote handover before you go on leave
Remote leave is where handovers fail most: there is no desk to hover over, no corridor chat to catch the thing you forgot, and your covering colleague cannot see what is on your screen. A written handover is the only bridge. This generator builds it for you, in your browser, in minutes — and scores it, so you can see the gaps before you send it.
- Start with the basics. Your name, role and team, the dates you are away and the date you return, and the colleague covering for you with a way to reach them. A handover without a named cover owner is a note to nobody.
- List what's in flight. Every live task or project, with its status, the next action, the date it is due, who covers it, and where it lives — a link, a folder, a ticket. "Where it lives" is the field people skip and the one your cover needs most.
- Name the key contacts. For each area of your work, who your cover should talk to and how to reach them. Include your manager for approvals.
- Write the escalation paths. For each thing that could go wrong — an outage, an angry customer, a missed deadline — name the first call and the backup. Your cover should never have to guess who to phone in a crisis.
- Say what can wait. Explicitly listing the work that should be left alone until you return is as useful as listing the work that cannot. It stops your cover doing low-value work and stops you coming back to half-finished jobs.
- Record where things live. Shared logins, inboxes, drives and dashboards: write where each one is and who can grant access. Never type a real password — there is no password field here on purpose.
- Check the score, then send it. The completeness score lists exactly what is still missing. At 90 or above the handover is ready to send; below that, fill the gaps first. Copy it as Markdown into email, Docs or Slack, download it, or print it.
Honest limitations
It is a planning aid, not a mind reader
This tool cannot read your real systems, calendars or inboxes. The document is only as complete as what you type into it — if a task never makes it into the form, it never makes it into the handover.
Coverage depends on what you enter
The completeness score checks that fields are filled in, not that they are true. A cover owner who has not agreed to cover, or a link that is out of date, still scores full points — confirm both before you go.
There is no password field
On purpose. Never type a real password into this page or into the handover itself. Record where passwords live — the company password manager, the shared vault — and who can grant access.
Dates are as typed
Due dates are copied from the form as written. If a date changes after you generate the handover, update the form and generate again — the downloaded copy does not update itself.
It cannot notify anyone
The handover is a document, not a message. Copy it into email or Slack and tell your covering colleague and your manager it exists — this page cannot send it for you.