Remote Handover Generator. Leave without the loose ends.

Going on leave while working remotely? Build a structured handover in minutes — what's in flight, who's covering what, where things live, and what can wait — with a completeness score that shows what's still missing.

  • Your handover never leaves the device
  • No sign-up, no account, no upload
  • Completeness score out of 100
  • Free, unlimited use

Build your leave handover

1About you and your leave

2What's in flight

Every task needs a next action, a cover owner and a place where it lives — those three are what the completeness score checks.

3Key contacts

The people your covering colleague will actually need — who they are, what they are for, and how to reach them.

4If something goes wrong

Escalation paths for the urgent stuff — who gets the first call, and who is the backup if they cannot be reached.

5What can wait, and where things live

Name the work that should be left alone until you return — and where shared logins and files live. Never type a password; write the location and who can grant access.

6Notes for your cover

Anything your covering colleague needs that fits nowhere else.

Fill in the form, then press Generate my handover.

Fill in the form, then press Generate my handover. Everything stays on this device. Your handover downloads instantly.

Privacy you can verify, not just trust

Your handover never leaves the device — this generator runs entirely in your browser, and the only third-party requests are the site's own analytics, which count page views. There is no account and no upload: the tool never sends what you type anywhere. Don't take our word for it:

External requests during use: 0
  1. Press F12 to open developer tools, then the Network tab.
  2. Generate a handover above. Watch: apart from the site's analytics, nothing new is requested — your handover never leaves the device.
  3. Extra credit: disconnect your internet after this page loads — the generator still works.

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.

Frequently asked questions

Does this tool store or send my handover?

No. Everything you type is processed entirely in your browser — your handover never leaves the device, and the only third-party requests are the site's own analytics, which count page views. There is no account and no upload, so nothing you enter is saved anywhere except on this page. You can verify it yourself with the network-request counter in the privacy section below the generator.

Can I put passwords in the handover?

No — never enter a real password here. This tool has no password field on purpose. Record only where passwords live, for example 'company password manager, Support vault — ask IT for access', and who can grant access to your covering colleague.

What does the completeness score check?

Twelve checks worth 100 points: your name and role, your away and return dates, a named covering colleague, at least one task, a next action, cover owner and location for every task, an escalation contact, where shared logins live, and at least one thing that can wait. The score lists exactly what is still missing, so you can fix it before you send the handover.

What should a good handover include?

The work in flight with its next action and cover owner, the key contacts for each area, an escalation path for urgent problems, what can safely wait until you return, and where shared logins and files live. Dates matter most: a covering colleague needs to know what is due while you are away and what can wait.

Can I edit the handover after it is generated?

Yes. The document is generated from the form, so change anything in the form — add a task, fix a date, name a different cover owner — and the preview, score and downloads update to match. Copy and download always use the form exactly as it stands.

Can I print the handover or save it as a file?

Yes. Copy it as Markdown to paste into email, Docs or Slack, download it as Markdown (.md) or plain text (.txt), or print it straight from the page — the print view shows the handover document only.