Deputy Coverage: Keeping Vacations and Sick Days from Paralyzing the Business

Why does a single absence paralyze the whole company?

In a company with twelve people, there are rarely two people for the same task. That is efficient as long as everyone is there. When one person is absent, it becomes clear how much depended on them: access to the banking software, the knowledge of which customer has which special terms, the order of steps in the monthly close. Vacations can be planned, sickness cannot. And absences are no side issue. For 2025, the German health insurer AOK counted an average of 23.3 sick days per insured employee, based on about 14.9 million employed members.

Add six weeks of vacation, and each person is absent for about nine weeks a year on average. This leads to the guiding question of this article: How does a small company organize deputy coverage so that vacations and sickness do not paralyze its operations, without everyone having to be able to do everything?

To answer it, we first clarify what organized coverage means and measure the risk with the bus factor. Then we present the thinking model of chaining and weigh how much dual competence is worthwhile. At the end there are the coverage matrix, the handover note for vacations, the precautions for unexpected absence, and a step for this week.

Coverage that is arranged only on the first sick day is not coverage but an emergency.

What is organized coverage, and what is the bus factor?

Deputy coverage is organized when three things are settled in advance: who takes over a task, what that person needs to know and be able to do, and how far their authority extends, for example up to what amount they may approve orders. If one of the three is missing, there is only a name on a list.

How large the risk is can be measured with a term from software development: the bus factor, also called the truck factor. It indicates how many people must drop out before a task or project can no longer be continued. The drastic name refers not only to accidents but to any absence: sickness, resignation, parental leave, vacation. A bus factor of one means the task depends on a single person.

The distinction from responsibility is important. A RACI matrix defines who performs and who is accountable in the normal case, and it requires exactly one A per activity, as the guide to clarifying responsibilities with the RACI matrix describes. The coverage rule supplements it for the exception: for the duration of the absence, the role passes to a named person, with limits set in advance. There is still exactly one accountable person, just a different one.

The thinking model: chaining instead of everyone doing everything

The obvious answer to a low bus factor is: everyone should be able to do everything. That is expensive and rarely necessary. A better answer comes from production research. Jordan and Graves (1995) studied how flexible plants producing several products need to be. Their finding is known as chaining. It is enough if each plant can make one product besides its own so that all plants and products form a closed chain. Such a chain achieves almost the performance of full flexibility at considerably lower cost.

Applied to a team, this means: besides her own task, Anna masters Ben’s, Ben masters Clara’s, Clara masters Anna’s. If one person is absent, there is always someone for their task, and nobody had to learn more than one second task. Like a ring of people holding hands, each holding a neighbor: if one lets go, the chain still holds.

Easton (2011) applied this logic to service operations with long opening hours, fluctuating demand, and uncertain attendance. In his calculations, employees with multiple skills were often, but not always, superior to pure specialists. He summarizes earlier studies to the effect that chained partial cross-training delivers most of the benefit of full cross-training at a fraction of the cost.

How much dual competence pays off? Two perspectives

There are two readings. The first says: every dual competence costs time that is missing in daily business. Whoever trains a deputy trains for a case that may occur twice a year. This view has a true core. Easton (2011) shows that broadly trained employees who perform a task less efficiently than the specialist create a trade-off: either more staff is needed or shortages arise. A review of 87 studies names training costs and productivity losses as the most frequent barriers and notes that the benefit of broad training is often reported but rarely measured end to end (García-Manglano et al. 2026).

The second reading says: dual competence is insurance whose premium is small compared to the damage. A week without payroll, without orders, or without a response to a key account costs more than a few hours of training. There is also a side effect: whoever knows a colleague’s task understands the interface better.

I consider both readings justified and chaining the bridge between them. It limits the effort to one second task per person and applies it where the bus factor is one. One finding from Easton’s review, however, calls for an additional rule: the performance of cross-trained employees declines if they do not apply their skills regularly. Cycles of learning, forgetting, and relearning led to losses in quality and productivity in earlier studies. A deputy who has been shown the task only once is hardly faster than a newcomer when it counts.

The coverage matrix: who covers for whom

The tool for implementation is the coverage matrix. The rows list the critical tasks, the columns the people. Each cell contains one of three levels: 2 means the person performs the task regularly and confidently. 1 means they can take over the task as a deputy, with documents and questions. 0 means they cannot. A task is critical if its failure costs money, a customer, or a deadline within a week.

The first four rows show the chain: Ben covers for Anna, Clara for Ben, David for Clara, Anna for David. Each has learned exactly one additional task, and each critical task has a bus factor of two. The matrix is reviewed once a year and after every staff change.

1. Collect critical tasks

   Ask each person: what would be left undone if you were absent for two weeks starting tomorrow, and what would that cost? At most 15 tasks for a small company.

2. Enter the bus factor

   For each task, count who masters it at least at level 1. Mark all tasks with a bus factor of one.

3. Form the chain

   Name a deputy for each marked task so that a closed chain emerges where possible and nobody gets more than one or two additional tasks.

4. Define authority

   Record in writing for each deputy what they may decide: amounts, approvals, commitments to customers.

5. Practice

   The deputy performs the task once under guidance and then once a quarter alone.

How much time the deputy actually has when it counts is decided by capacity planning. Whoever takes on an additional task must be relieved elsewhere, as the guide to capacity planning shows.

Vacation and unexpected absence: two different cases

With vacation, there is time for a handover. A one-page handover note is enough; it is placed in the shared storage location two days before the vacation begins and gone through in a 15-minute conversation. It contains the open cases with status and next step, the appointments during the absence, the customers with something pending, and when the person on vacation can be reached and when explicitly not.

With sickness, there is no handover. Whatever is needed must already be in a known place. Three things matter. First, the workflows: for every critical task there is a process page following the one-page method that someone who rarely does the task can also use. Second, the documents: cases are kept in shared storage and not in a personal inbox, as the filing charter in the article on digital filing provides. Third, the access: the deputy has their own logins to the necessary programs instead of knowing the colleague’s password.

• Every critical task has a named deputy with defined authority.
• For every critical task, there is a current process page in the shared location.
• Open cases are kept in shared storage, not in a personal inbox.
• The deputy has their own access to all necessary programs and accounts.
• A shared mailbox or forwarding ensures that customer inquiries are not left unanswered.
• The out-of-office message names the deputy and how to reach them.

With customer relationships, a handover note is often not enough because trust is tied to the person. How to spread such relationships across several shoulders is described in the essay on succession and sales.

Conclusion: how does a small company organize coverage?

We set out to ask
a small company organizes deputy coverage so that vacations and sickness do not paralyze its operations, without everyone having to be able to do everything. The answer begins with a measurement: the bus factor shows which tasks depend on a single person. These tasks need a named deputy with knowledge and authority settled in advance.

As shown, this does not require everyone to learn everything. Chaining from production research shows that a closed chain in which each person masters one additional task delivers most of the benefit. However, it holds only if the coverage is practiced regularly. The sober observation is: you do not notice a good coverage rule; you only notice where it is missing.

What you can do this week

1. Ask each person on the team what would be left undone if they were absent for two weeks starting tomorrow.
2. Enter the answers in a coverage matrix and mark all tasks with a bus factor of one.
3. Name a deputy for the three most important marked tasks and record their authority in writing.
4. For each of these deputies, schedule the first joint run-through and a practice date in the next quarter.
5. Check your own bus factor: who can act if you cannot be reached tomorrow?