Vacation Coverage Plan: How to Set Up Deputies Who Keep Work Moving

Every company has vacation cover. It sits in the out-of-office message, on the leave request form and sometimes in the org chart, and how well it holds becomes clear once a colleague is genuinely away for three weeks and the deputy takes over her work.

This guide shows how to build a vacation coverage plan so that work keeps moving while someone is on holiday. You will find a copyable template for the deputy arrangement, a 20-minute format for the handover conversation, a dry run before the real thing, and a worked example from a 25-person tax firm. Vacation cover is often the first tangible step in implementing knowledge management, because twice a year it shows where knowledge rests with a single person.

What makes vacation cover hold

Vacation cover holds when the deputy has three things: knowledge of the process, access to the systems and a clear scope for decisions. The name in the out-of-office message is the starting point, and with these three things it becomes someone who actually carries the work forward.

Cover is therefore just as much a question of knowledge as of responsibility. Handle it as an organizational matter and you have a name; handle it as a knowledge matter as well and you have someone who can do the work. Your colleague then comes back from three weeks off, finds her cases handled and plans her next vacation with the same ease.

Knowledge. The deputy finds a description of the process that is accurate, with the order of steps and the special cases. Often the preparation is the moment it turns out the process has not been written down yet, and that is a good occasion to capture it together.

Access. The deputy has a login for the banking portal, a personal certificate for the regulatory filing and the ERP permission to approve. This part is the easiest to arrange, and because IT roles take lead time, it is worth checking early.

Scope for decisions. The deputy knows whether they may grant the discount, release the order or send the reminder, and whom to ask when unsure. With that clarity they also handle the cases they would otherwise set aside for their colleague's return.

A vacation coverage plan template: the deputy table

A deputy arrangement that brings knowledge, access and decision scope together fits into a single table. It is kept per task or process, which sets it apart from the usual "Ms. A covers for Mr. B" assignment: Mr. B has twelve tasks, and each of them may call for a different deputy.

Each of the seven columns has its own purpose, and the arrangement needs all seven:

Task / process. Specific enough that you can tell what has to be done and when. "Accounting" is still too broad, while "client payroll runs, monthly by the 10th" is a task. Recurring deadlines belong in the label, because they show whether the deputy has to act during the absence at all.

Primary owner. A name rather than a department. For tasks that several people handle equally well, the cover question is already solved and the row can be dropped.

Deputy 1 and deputy 2. Two names, because the first deputy often happens to be away at the same time during the summer holidays. The second deputy may know the topic less deeply, but should be able to find the instructions and get the process through in the normal case. A skills matrix shows quickly who can step in for which task.

Where the instructions live. A path rather than a hint like "on the shared drive." If this column stays empty, you have found a knowledge gap, and the deputy arrangement has just given you your documentation priority list. What a process description looks like that a deputy can work with comfortably is covered in the guide to documenting processes: short, with the special cases, written from the perspective of the person doing the work. So that the path points to one single place, a fixed home helps, such as a knowledge base that is maintained regularly.

Access / authority. Which systems, which roles, which limits. You check this column before the vacation: does the deputy actually have access today to everything listed here?

Last checked. The date of the last review. A deputy arrangement last touched eighteen months ago quite often contains a name that has left the company.

The table is best kept where the process documentation lives, and reviewed twice a year, once before the summer holidays and once before Christmas. Those are the two periods when most people are away at the same time and cover chains are put to the test.

The legal side, briefly

This section is not legal advice. Three points are best settled with your management or your adviser before a deputy steps in.

Authority to sign and to approve. Anyone who signs contracts on behalf of the company, releases payments or deals with authorities needs the authority to do so, and an internal deputy arrangement does not create that authority by itself. Check whether the deputy needs written authorization with a clear monetary limit, whether the banking portal provides its own approval role, and whether the government portals you use rely on personal certificates. Passing on a personal certificate usually breaches the terms of use, so the deputy is best given one of their own.

Data protection and inbox access. The deputy needs access to incoming requests, and for that a shared functional inbox (payroll@, dispatch@, purchasing@) that several people are authorized for is usually enough, together with an out-of-office message pointing to it. For access to a personal work mailbox, it matters whether private use is allowed. Under the German authorities' guidance, if private use is prohibited, access to work emails during an absence is generally possible to the extent necessary; if it is allowed or tolerated, employees' consent is usually required. A written arrangement agreed in advance is the cleanest route, in companies with a works council usually as a works agreement. Settle this calmly before the vacation starts and, in an individual case, with whoever is responsible for data protection.

Working hours and extra load. Someone covering two areas of work for three weeks needs room to do so, not least because in Germany, for instance, the working day is capped at eight hours, and ten hours are only allowed with compensation later (Section 3 ArbZG). Agree together in advance which of the deputy's own tasks may wait during that period, so that the cover fits into regular working hours.

The handover: 20 minutes before the vacation

The handover conversation assumes the deputy already knows the process in principle, and concentrates on what is concretely coming up in the next three weeks. Twenty minutes are enough if they have a fixed structure:

Minutes 1 to 5: what is coming up? The knowledge holder walks through the dates and deadlines that fall into the absence. Which runs, filings, submissions and deliveries land in that window? What is prepared, and what does the deputy have to trigger themselves?

Minutes 6 to 12: where is it burning right now? The open cases that need special handling, such as the client who always follows up, the complaint that could escalate or the supplier who wants to change prices. This kind of information appears in no process description, because in four weeks it will look different again.

Minutes 13 to 17: what may the deputy decide? Monetary limits, room for goodwill, who to ask when unsure, and who the next escalation level is. This part clarifies the scope for decisions, and in everyday work it deserves the most attention.

Minutes 18 to 20: test the access. The deputy logs into every system from the table once, while the knowledge holder is still sitting next to them and can help straight away if a permission is missing.

The result fits on one page and gets attached to the deputy arrangement. Make this handover a fixed part of every leave request and you gain more time per vacation than the conversation takes.

The dry run: rehearse the cover before it matters

A name in the table, instructions in the wiki and a handover conversation are good preconditions. How well the cover holds becomes clear once the deputy has run the process once themselves.

The dry run needs little preparation and gives the most certainty: the deputy takes over the process on a normal working day, while the knowledge holder is in the building and holds back. They run the month-end payroll, create the delivery route or release the payment, with real data, in the real system and following the instructions listed in the table. The knowledge holder sits beside them, lets the deputy work and notes down where they get stuck.

That log tells you three things. First, whether the instructions hold up, since every point where the deputy had to ask is a gap in the documentation. Then, whether the access rights are complete. And finally, whether the deputy would be able to act in an emergency or would benefit from a second round. After a dry run that passes, the name in the table belongs to someone who has already done the work once.

Incidentally, the dry run is a very simple form of knowledge transfer, because the knowledge is applied while the knowledge holder looks on. Which other formats suit which kind of knowledge is compared in the guide to knowledge transfer methods.

Example: a payroll specialist takes three weeks off

A composite example; names and figures are made up. A tax firm with 25 employees. Ms. Nowak has been running payroll for 38 client companies for nine years, around 600 payslips a month in total. She is away from 27 July to 16 August, and the entire July payroll run falls into that window: payslips by the 5th, wage tax returns by the 10th, plus the usual client questions about joiners and leavers.

The year before, Mr. Pahl, a financial accountant, was listed as the deputy. He had no permission in the payroll system to execute the run, did not know the specifics of the three construction clients with their sector-specific pay rules, and did not know that for one client the payslips are only ever sent out after their managing director signs off, because of a works council agreement. As a result, two wage tax returns went out late, one client called the practice management, and Ms. Nowak processed the construction payroll from her laptop on the evening of her third vacation day.

This year it runs according to the deputy arrangement. Six weeks before the vacation, Mr. Pahl gets the payroll system role for executing the run, and Ms. Ricci, as second deputy, is authorized for the payroll@ inbox. Four weeks out, Mr. Pahl runs the June payroll for ten clients himself, with Ms. Nowak sitting beside him. Along the way they notice that the wiki instructions do not mention the construction clients at all and that so far only Ms. Nowak knows the sign-off rule. The two of them add both points together in half an hour. On her last working day comes the handover: which clients have joiners or leavers in July, where extensions are running, and up to what amount may Mr. Pahl release corrected payslips without asking?

After the three weeks, every filing has gone out on time, twelve client queries have been answered through the shared inbox, and there was a single phone call to Ms. Nowak about a back payment that genuinely nobody else knew about. Preparation took Mr. Pahl roughly five hours and Ms. Nowak three, and in return she had three quiet weeks of holiday this year.

Vacation cover, bus factor and knowledge silos

A vacation is the harmless version of a question that in its hard form is called the bus factor: how many people can drop out before a process stops? If the cover exists only on paper, the answer for that process is "one", and the bus factor is 1. A vacation ends after three weeks, whereas a resignation does not.

That makes vacation cover a very good early warning system. Every process where work piles up during a holiday is a knowledge silo, and the deputy arrangement makes it visible long before anyone leaves the company. Every deputy who passes the dry run dissolves one such silo. How to get from that single measure to a system that spreads all critical processes across at least two heads is covered in the guide on breaking up knowledge silos.

Often the first step is the hardest: finding out which processes have no working cover at all. Management rarely has the full picture, and the people affected do not always raise it on their own. At wissa.ai, that inventory runs through AI-led interviews with your employees, around 15 to 20 minutes per conversation, in a chat and whenever it suits them. wissa.ai does not rate people: no scores, no ranking. If someone names a colleague as a knowledge holder, wissa.ai suggests inviting that colleague next. The conversations produce process documentation with a source reference for every statement, an overview of all areas and processes, and an org chart. Because the system records who carries which step of a core process, the analysis shows which steps so far depend on exactly one person, and in the conversation the AI asks who covers for that person. That makes the cover gaps visible. That fills in the first column of your deputy arrangement, from the statements of the people doing the work.

If you would like to find out which of your processes will need cover next summer, you can start with wissa.ai right away, with hosting in Germany, AI processing in the EU and a data processing agreement under Art. 28 GDPR. As with any new software, involve your works council early. A free trial package to start with (10 credits, once per company, terms) usually covers a first interview, and interviewees need neither an account nor a license of their own. Try one interview for free

Conclusion

A vacation cover plan that holds consists of four parts: a deputy arrangement per task, instructions the deputy can find and understand, access rights and authority checked before the holiday, and a dry run before it matters. The handover conversation adds what changes too quickly to document. With a few hours of preparation per process, everyone gets through the summer at ease.

FAQ

What belongs in a deputy arrangement?

Per task or process: the primary owner, two deputies, where the instructions live, the required system access and authority, and the date of the last review. The arrangement is kept per task, because one person has many tasks and a single deputy is rarely the right fit for all of them.

How far in advance should the deputy be prepared?

Request access rights and permissions about six weeks ahead, because IT roles and banking authorizations take time. Schedule the dry run three to four weeks out, so there is time to close gaps in the instructions. Hold the handover on the last working day, because it deals with the cases currently open.

May the deputy access a colleague's email inbox?

That needs an arrangement. The simplest route is shared functional inboxes that several people are authorized for, together with an out-of-office message. For a personal work mailbox, it matters whether private use is allowed: if it is prohibited, access to work emails during an absence is generally possible to the extent necessary; if it is allowed or tolerated, employees' consent is usually required. A written rule agreed in advance creates clarity. When in doubt, ask whoever is responsible for data protection.

What if nobody but the knowledge holder knows the task?

Then you have found a knowledge silo, and the vacation is a good occasion to break it up. Name a deputy, document the process together and have them run through it once. If there is not enough time before the holiday, at least sort out access rights and an emergency contact, and put the dry run firmly in the calendar for the next one.

Should the deputy be allowed to call the knowledge holder during the vacation?

As an emergency option yes, as a way of working preferably not. If the deputy has to call regularly, something is still missing from the preparation, and the holiday stops being restful. Agree on a single channel for genuine emergencies and take every call as a pointer to what can still be added to the instructions.

Sources

• Datenschutzkonferenz (DSK, the German data protection authorities): guidance on the data-protection-compliant use of email and other internet services in the workplace (Orientierungshilfe, January 2016, predating the GDPR) - on accessing work mailboxes during an absence, depending on whether private use is prohibited or permitted.
• Section 3 of the German Working Hours Act (ArbZG): eight-hour working day, extendable to ten hours only with compensation.