The short version
- Naming a backup usually means one person now holds two workloads, and the second one arrives as constant interruption.
- Split the load: the backup handles decisions, and the record handles questions. Those are different jobs and only one needs a human.
- Most of what a backup absorbs is retrieval, which is the part that does not need their judgement at all.
- Reduce the backup's own commitments for the period. Coverage on top of a full workload is how a holiday becomes two bad fortnights.
Coverage plans usually consist of one line: while Ana is away, Marek is covering. Marek's own work does not reduce, nobody defines what covering means, and two weeks later Marek has had a poor fortnight and Ana returns to several things that waited anyway.
"The backup person is now two people."
What a backup actually absorbs
Break it into categories, because they are wildly different in cost and in what they require.
| What arrives | Share of volume | Needs the backup? |
|---|---|---|
| "Where does this stand?" | Most of it | No, this is retrieval |
| "What did she decide about X?" | Substantial | No, if it was recorded |
| "Can we do X?" (a real decision) | Smaller | Yes, this is the job |
| Something has broken | Rare | Yes, or the on-call person |
The top two rows are the majority of the volume and the least valuable use of a colleague's time. The backup is being used as an index for someone else's work, which is both the most interrupting part of the role and the part that does not require them.
Split the load
State the division explicitly when you set up the coverage: the backup handles decisions, and the record handles questions.
That is workable because the person on leave has been confirming a ninety-second brief at the end of each day: current state, open questions, blockers, next actions, decisions made and why. While they are off, their StandIn answers questions from it in their words, with a source under every answer, and never guesses. When the answer is not in the record, it says so and names the backup, which routes the real decisions to the human and nothing else.
The backup's fortnight then looks completely different. Instead of forty interruptions, they get four decisions, which is a manageable addition to an existing workload. And the asker is better off too, because a sourced answer from the person who did the work beats a colleague's best reconstruction of it. See retire your out-of-office.
Giving the backup real authority
Coverage fails as often from too little authority as from too much volume. A backup who cannot decide anything is a message-forwarding service, and work stalls until the person returns.
Write the limits down before the leave starts, in specific terms with numbers where numbers apply. "Refunds up to 500 euros: Marek decides. Above that: it waits, and the customer gets a date." Then tell the team, not just Marek, because a backup with authority nobody knows about will still be bypassed.
And say what happens to the things that wait. A decision that waits with a communicated date is a managed delay. A decision that waits silently is a stalled project, and the person on leave returns to discover it.
The capacity conversation nobody has
If coverage is real work, it needs real capacity. That means reducing the backup's own commitments for the period, and it is almost never done, because the coverage is assumed to be a small favour.
A reasonable default: take one significant deliverable off the backup's plate for the fortnight, and say so publicly. It costs the team one item and buys a coverage arrangement that works rather than one that formally exists. It also makes the role something people will accept again next time, which matters more than any single absence.
Common Questions
How do you cover for someone on leave without overloading the backup?
Separate questions from decisions. Questions about state and past decisions should be answerable from the record without a person. The backup handles only the genuine decisions, which is a small fraction of the volume and the only part that needs their judgement.
Should one person cover everything or should it be split?
Split by area with one name each, rather than one person covering a whole role. Splitting spreads the load and matches decisions to whoever actually has the context, which produces better decisions as well as a lighter fortnight.
How much authority should a backup have?
More than most get. Write specific limits with numbers, and tell the whole team what they are. The most common coverage failure is a backup who technically covers and cannot decide anything, so everything waits.
What if the backup is also on leave?
Name the second fallback in the same document, and check the holiday calendar when you set the coverage. Overlapping absences are predictable and are nearly always discovered on the first morning of the first one.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.