Covering for a Teammate on Leave

Covering for a teammate on leave costs you the ability to do your own job well, because you are now doing two jobs at once and you only have full context on one of them. The load is real, it is mostly invisible to whoever assigned it, and it recurs every time a colleague takes time off.

This one is written for you, the person covering, not for the manager who arranged it. Because there is a quiet unfairness in how coverage usually works. The person on leave gets to be unavailable. You do not. Their absence becomes your extra shift, and nobody quite counts it. Worth naming before it is your turn again.

What covering actually costs you

On paper, covering sounds light: keep an eye on their inbox, answer the easy stuff, escalate the rest. In practice it is heavier and stranger than that. You are making decisions in an area you only half know, so each one takes longer and carries more risk. You are context-switching between your work and theirs all day, which is its own tax. And you are doing it without the one thing that would make it easy, which is the reasoning in the absent person's head.

You read their handover doc and it tells you what they decided, not why, so the first real question leaves you stuck. We wrote about that gap in what a handover never manages to carry. You either wait for a reply from someone who is meant to be offline, or you guess and hope. Both are stressful, and both are happening on top of your actual job, which does not pause to make room.

The worst part is how little of this shows up anywhere. Your own work slips a bit, which you notice and they do not. You are more tired, more scattered, a little resentful, and when the person comes back rested, the natural thing is to say "thanks for covering" and move on. The cost was paid entirely by you, and it left no record.

How to protect yourself when it is your turn

You cannot always refuse to cover, but you can refuse to cover badly. Before the person leaves, ask for the things that keep the load survivable.

• A real handover, not a hallway summary: Insist on where each thread stands and, where it matters, why. If it is not written, it will land on you as a live question later.
• Narrow decision limits: Get clear on what you are allowed to decide alone and what genuinely waits. Vague authority means you carry the anxiety of every call.
• Explicit permission to let things wait: Ask which items are fine to leave until they return. This is the single biggest relief, and people forget to grant it.
• Coverage split by topic: Push for the load to be divided, not dumped. A coverage plan by area spreads it so you are not the only backup.

These are reasonable asks, and making them is not being difficult. It is refusing to silently absorb a cost nobody else is counting.

Who gets to be unavailable

Here is the turn, and it is about fairness more than tooling. The reason covering falls so hard on you is that the absent person's knowledge left with them. It was all in their head, so their being unavailable forced you to be extra available. If that knowledge had stayed answerable, their leave would not have become your second job.

That is the real idea underneath. When someone is off, their work should keep answering, in their words, without guessing, so that being unavailable does not quietly transfer the whole load to a colleague. The point is not to make people work while on leave. It is the opposite: to make sure one person resting does not depend on another person carrying double.

StandIn does this by answering from what the absent person wrote down before they left, plus the team's record. When a routine question comes in, you do not have to field it, because it is answered from their brief, in their words. When it is a genuine decision the record does not cover, StandIn says so and points to the named owner, so you only handle the calls that truly need a human. Coverage stops meaning "you become them for two weeks" and starts meaning "you handle the few things only a person can". That is a fairer trade, and it is the one that lets you take your own leave later without dreading who has to become you. The bigger version of this problem shows up hardest on small teams, which we cover in why small teams take less leave.

Common Questions

Is it fair to be asked to cover for a colleague?

Covering is normal, but doing it without a handover, clear limits, and permission to let things wait is not. You can accept the role and still insist on the conditions that keep it from wrecking your own week.

How do I say no to covering when I am already stretched?

You rarely have to refuse outright. Ask for the load to be split by topic and for a record that answers routine questions, so what lands on you is small enough to say yes to honestly.

Why is covering so exhausting even when the tasks are simple?

Because you are context-switching all day and deciding without the absent person's reasoning. The tasks look simple; carrying two jobs with half the context on one is not.

Can questions be answered without the person or me replying?

Yes, when the answer already exists in writing. StandIn answers from what the absent person wrote down, and when something is not there it says so and routes it on, so the routine load never reaches you at all.

The next time you are asked to cover, remember that the cost is real, it is mostly yours, and it repeats. The fix is not to work harder while your colleague rests. It is to make sure their knowledge keeps answering so their time off does not become your second job. See how that works for the whole team at StandIn for employees.