Covering for a Teammate on Leave

Covering for a teammate on leave means doing your own job and part of theirs, with full context on only one of them. To make it workable, get a written handover, clear limits on what you may decide alone, and a list of what can wait until they are back, all before they leave.

This guide is written for the person doing the covering, and for the manager who wants to stop leaning on the same backup every time. It covers what covering costs, what to ask for, how to plan coverage for a team, and what to do when someone leaves for good. Each section links to a fuller guide, and the templates are at the end.

What covering costs you

On paper, covering sounds light: keep an eye on their inbox, answer the easy things, pass on the rest. In practice it is heavier. You are making calls in an area you only half know, so each one takes longer and carries more risk. You switch between your work and theirs all day. And you are missing the one thing that would make it easy: the reasons in the absent person's head.

You open their handover doc, and it tells you what they decided but not why, so the first real question leaves you stuck. You can wait for a reply from someone who is meant to be offline, or you can make your best call and hope. Both are stressful, and both happen on top of your own job, which does not pause.

Little of this shows up anywhere. Your own work slips a bit. You get more tired and more scattered. When your colleague comes back rested, the natural thing is to say "thanks for covering" and move on. The cost was real, it was mostly yours, and it left no record.

How to protect yourself when it is your turn

You cannot always say no to covering, but you can say no to covering badly. Before your colleague leaves, ask for the things that keep the load manageable:

• A real handover, not a hallway summary. You need where each piece of work stands and, where it matters, why. If it is not written down, it will reach you later as a live question.
• Clear decision limits. Agree what you may decide alone and what must wait. Vague authority means you carry the worry of every call.
• Permission to let things wait. Ask which items can sit until they return. This is the single biggest relief, and people forget to give it.
• Coverage split by topic. One backup per area, not one backup for everything.

These are fair requests. Making them is not being difficult. It is refusing to absorb a cost that nobody else is counting.

When the backup ends up doing two jobs

The most common failure is a manager naming one backup for everything and calling it a plan. That person now has two full jobs and no extra hours. If you are the manager, a fair split is part of approving the leave. If you are the backup and the split did not happen, raise it before the leave starts, not halfway through.

When the absence is unplanned

Some absences give no warning: an illness, a family emergency, a day someone simply does not log on. There is no handover to read. In that case, start with three questions. What is due in the next few days? Who is waiting on this person? Which decisions can wait a week? Answer those first and leave the rest. A team that keeps its work written down as it goes copes far better with an unplanned day, because most of the handover already exists.

Plan coverage for the whole team

A coverage plan is the team-level version of a handover. It lists each area of work, who covers it, what they may decide, and who to call if something is urgent. Written once and reused, it turns every holiday from a scramble into a routine.

The vacation coverage plan template shows how to build one for a small team and for an engineering team, including how to rotate backups so the same person is not always the one covering. Longer absences need more care. For parental leave, see the parental leave handover plan, which covers the last weeks before leave and the first weeks back.

Write a handover document before you leave

If you are the one going on leave, the most useful thing you can do for your backup is a short handover document. It should list your open work, where each item stands, the decisions you have already made and why, what can wait, and who decides what while you are away.

Lead with the open questions, not the finished work. Your backup can find what is done. What they cannot find is what you were about to decide. Our guide to the handover document before leave includes a template and a checklist for the last day.

Leave a decision list behind

One part of the handover deserves its own list: the decisions that might come up while you are away. For each one, write who may decide it in your absence and what you would decide if asked. That single page saves your backup more stress than anything else you leave behind.

For managers: make covering fair

If you manage the team, coverage is your job to design, not the backup's job to absorb. Three habits make it fair.

First, approve the plan with the leave. A leave request is not complete until the coverage plan is written and the backups have agreed to it. That takes ten minutes when the request comes in and saves days of confusion later.

Second, take work off the backup's plate. If someone is covering a second area for two weeks, something in their own area has to move or wait. Say what, out loud, so they do not try to do both at full speed.

Third, rotate. On most teams the same reliable person ends up covering for everyone, because they never say no. Over a year that adds up to weeks of extra work that nobody sees. Keep a simple list of who covered last time, and spread it around.

None of this needs a new tool. It needs the manager to treat coverage as real work, because it is.

The first day back

Coverage does not end when your colleague walks back in. The handover runs in reverse: what happened while they were away, what the backup decided, and what is still open. Skip it, and the returning person spends a week finding out the hard way.

A good return handover takes half an hour. The backup lists the decisions they made, the questions they parked, and anything that changed. The returning person reads it before opening their inbox. For a step-by-step version, see this order of operations for catching up after time away.

When someone leaves for good

A holiday ends. A resignation does not. When a person leaves the company, their knowledge goes with them unless the team got it written down in time. That includes the reasons behind past decisions, the history of a system, and the names of the people outside the team who helped.

The guide to knowledge loss when someone leaves explains what walks out the door, how to plan a knowledge transfer in the last two weeks, and why transfer that starts at the notice period is usually too late. To put a rough cost on it for your team, try the knowledge loss calculator. A related risk is the one person everyone depends on; see how to spot key person dependency before it turns into an outage.

Hand off engineering work

Engineering handoffs have their own needs. The next person needs the state of each branch, the open pull requests, the failing tests, the deploys in flight and the things that look odd but are fine. A template keeps that consistent from one handoff to the next.

The engineering handoff template is a copy-and-paste format for end of day, end of sprint, and mid-project handoffs.

Hand off across time zones

On a distributed team, a handoff happens every day, not just at holiday time. When one office logs off and another logs on, the work changes hands without a conversation. A weak handoff costs the next team a morning of rebuilding context.

Our guide to async handoffs across time zones covers the four fields every handoff needs, a simple handoff protocol, and how to tell whether your handoffs are working. If you are choosing software for this, see the comparison of tools for async handoffs.

What AI can and cannot do in a handoff

AI tools can draft a summary of a week's work, pull open items from tickets, and answer simple questions while someone is away. They cannot know what a person meant to do next unless that person wrote it down, and they should not guess. A summary built from activity tells you what happened, not what was decided.

The guide on what AI can do in a handoff explains where AI helps, where it gets things wrong, and how to keep a person in charge of the handoff.

A coverage plan and handover template you can copy

Use the first table for the team. Use the second for each person going on leave. Copy both into a shared doc.

Coverage plan

Area of work	Backup	May decide alone	Must wait or escalate	Urgent contact
Customer escalations	Jordan	Refunds under the usual limit	Contract changes	Team lead
Payments service	Aisha	Rollbacks, config fixes	Schema changes	On-call engineer
Hiring loop	Chen	Scheduling, reference calls	Offers	Hiring manager
Weekly report	Jordan	Everything	Nothing	None

Handover document

Item	What to write
Dates	First and last day away, and the day you are back
Open questions	What you were about to decide, and what you would choose
Open work	Each item, where it stands, and the next step
Recent decisions	What you decided in the last month, and why
Can wait	Items your backup may leave until you return
Decision limits	What your backup may decide, and what goes to whom
People	Who is waiting on you, and who you were waiting on
Links	Tickets, docs, threads and dashboards your backup will need
Urgent contact	Who to call if something cannot wait, and how

Where StandIn fits

StandIn is a personal knowledge base, built on the work that you already do, that answers your teammates when you're away, in chat and email. While someone is on leave, their StandIn answers routine questions from what they wrote down, in their words, with a source under every answer. When the answer is not there, it never guesses: it says so and points to the person who knows. So the backup handles only the calls that need a person, and coverage holds while someone is out.

That is also what lets the backup take their own leave later without dreading who has to cover for them. See how StandIn works for employees.