How to Write a Handover Document for Maternity Leave

A handover document for maternity leave is different from a leaving-a-job handover. You're coming back. The person covering you needs to keep things running, not reinvent them. This guide walks through what to include, how to structure it, and how to hand back cleanly when you return.

Why a maternity handover is different

A handover for someone leaving permanently is about knowledge transfer. A maternity handover is about continuity. Your cover needs enough to keep the role running for six to twelve months, but they don't need to inherit every long-term decision or relationship as if it were theirs forever.

The framing matters. If you write it like a leaving-a-job handover, your cover will either take too much ownership (making the return awkward) or too little (making the maternity period painful for everyone). Aim for a document that says: here is the job, here is what has to keep moving, here is what can wait until I'm back.

When to start writing it

Start at least six weeks before your last day, earlier if you can. Pregnancy is unpredictable, and babies do not always arrive on schedule. If you leave the handover until the last two weeks, you're gambling that nothing goes wrong.

A realistic timeline:

• 6-8 weeks out: Draft the document. Identify who your cover will be.
• 4 weeks out: Share the draft with your manager. Agree what your cover will and won't own.
• 2-3 weeks out: Walk your cover through the document. Update it based on gaps.
• Final week: Introduce your cover to key contacts, transfer meetings, finalise access.

What to include

A maternity handover has seven core sections. Each answers a specific question your cover will have in their first month.

1. Role summary and scope during your leave

Two paragraphs. What the role is normally, and what parts of it your cover is expected to hold during your absence. Be explicit about what is out of scope: strategic decisions, hiring, long-term planning you'd rather return to.

2. Active projects and their status

For each active project: what it is, current status, next concrete action, who else is involved, and (crucially) whether it needs to land during your leave or pause until you return. Not everything needs to keep moving. Some things are better left alone.

3. Recurring commitments

Weekly meetings, monthly reports, quarterly reviews. For each, note what it is, who runs it, and whether your cover needs to attend, deliver, or can skip it. Transfer calendar invites explicitly rather than assuming they'll get picked up.

4. Key contacts

Internal stakeholders, external clients, vendors. Name, role, why they matter, and any nuance about how to work with them. If you have relationships that would be damaged by radio silence, flag them so your cover can send a proactive introduction.

5. Tools, systems, and access

Every system your cover will need. Note who to contact for access (usually IT), not the passwords themselves. Include less obvious things: the shared drive folder, the internal wiki, the vendor portal you log into once a month.

6. Decisions your cover can make (and ones they cannot)

This is the section most maternity handovers miss. Be explicit. Your cover needs to know what they have authority to decide and what should wait for you or be escalated to your manager. Vague authority creates either paralysis or overreach.

Can decide independently:
- Approving invoices under £5,000
- Signing off routine client deliverables
- Rescheduling internal meetings

Escalate to [Manager]:
- Anything involving client contract changes
- Hiring or team structure decisions
- Budget requests over £5,000

Wait for my return (unless urgent):
- The Q4 roadmap decisions
- The vendor renewal in October
- Long-term strategy for the enterprise account

7. The unwritten rules

The workarounds, quirks, and context that only you know. The client who prefers WhatsApp. The colleague you always copy on finance requests. The meeting that always runs over. These are the things that would take your cover three months to figure out otherwise.

Keeping in touch (or not)

Decide before you leave how contactable you want to be. There is no right answer, but there is a wrong one: leaving it ambiguous.

The walkthrough

A document alone is not a handover. Block two to three sessions of 60-90 minutes with your cover in the weeks before you leave. Share your screen, go through the document section by section, and update it as gaps surface. What feels obvious to you will not be obvious to them.

If you're handing over to someone who has never done the role, see the guide on handing over to someone new. The context you take for granted is exactly what they need.

Planning the handback before you leave

The return is where maternity handovers most often go wrong. Six to twelve months is long enough for the role to have drifted. Agree with your manager, in writing, how you'll pick it back up:

• A return-to-work meeting with your manager in the first week back
• A handback document from your cover, mirroring the one you wrote
• Which projects and relationships transfer back immediately, and which stay with your cover
• Whether you're returning to the same role, hours, and scope, or with any agreed changes

If you're planning to return part-time or on flexible hours, raise it before you leave, not two weeks before you come back. It affects how the role is set up during your absence.

How to write it faster

The hardest part isn't writing. It's remembering. Pull your raw material together first:

• Your calendar for the past six months, to surface recurring meetings and key relationships
• Your sent folder, to reveal active threads and external contacts
• Your task list, to catch anything mid-flight
• Existing documentation, so you can link rather than rewrite

If you work in Google Workspace, OneLast.Day reads your Gmail, Drive, and Calendar and drafts the handover from your actual work data, so you're not writing from a blank page in the weeks you least want to be at your desk.