Vacation Cover: How to Set Up Deputies That Actually Work

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 in a lot of companies that is exactly what it is: a name in a field. The moment a colleague is genuinely away for three weeks, you find out whether there is a working deputy behind that name or just the hope that nothing important will come up.

This guide shows how to set up vacation cover so that work keeps moving instead of piling up: 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.

Why vacation cover fails so often in mid-sized companies

The pattern is the same in almost every company between 10 and 500 employees. The deputy is named but has never been trained. They know the process from watching, but have never run it themselves. They have no access to the systems where the work actually happens. And they do not know which decisions they are allowed to make and which they are not.

You know how that ends. The deputy answers the easy questions and puts everything else on a pile. Customers hear "we will sort that out when my colleague is back." And after three weeks off, that colleague spends two weeks working through the backlog, which cuts the recovery value of the holiday roughly in half. So next year she only takes one week at a time and answers email from the holiday house.

The fault rarely lies with the deputy, and rarely with the knowledge holder. It lies in the assumption that cover is a question of responsibility. It is a question of knowledge. Handle cover as an organizational matter and you have a name. Handle it as a knowledge matter and you have someone who can do the work.

Three gaps show up again and again:

The knowledge gap. The process is written down nowhere, or the description is out of date. The deputy would have to guess which steps come in which order and which special cases exist.

The access gap. The deputy has no login for the banking portal, no certificate for the regulatory filing, no permission in the ERP to approve. This is the easiest gap to close and still the one most often missed, because it only becomes visible on day one of the vacation.

The decision gap. The deputy could handle the case but does not dare, because it is unclear whether they may grant the discount, release the order or send the reminder. In doubt, they wait. Waiting is the safest decision for the deputy and the most expensive one for the company.

A template for a deputy arrangement

A deputy arrangement that closes those three gaps fits into a single table. It is kept per task or process, not per person. That is the crucial difference from the usual "Ms. A covers for Mr. B" assignment: Mr. B has twelve tasks, and Ms. A is not automatically the right deputy for a single one of them.

Each of the seven columns has a purpose, and none of them is optional:

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

Primary owner. A name, not 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 has a habit of being away at the same time during the summer holidays. The second deputy may have a lower level of knowledge, but must be able to find the instructions and get the process through at least in the normal case.

Where the instructions live. A path, not a hint like "on the shared drive." If this column stays empty, you have found a knowledge gap - and the deputy arrangement has just handed you your documentation priority list. What a process description that a deputy can actually use looks like is covered in the guide to documenting processes: short, with the special cases, written from the perspective of the person doing the work.

Access / authority. Which systems, which roles, which limits. This column gets checked before the vacation: does the deputy have access today, not in theory, to everything listed here?

Last checked. The date of the last review. A deputy arrangement last touched eighteen months ago will, in our experience, contain at least one 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, once before Christmas. Those are the two periods in which cover chains break.

The legal side, briefly

This section is not legal advice, but there are three points you should have 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. 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 a personal certificate to someone else is usually not a solution but a breach of the terms of use.

Data protection and inbox access. The deputy needs access to incoming requests, not to a colleague's entire personal mailbox. The clean solution is shared functional inboxes (payroll@, dispatch@, purchasing@) that several people are authorized for, plus an out-of-office message pointing to them. If access to a personal work mailbox really is necessary, there should be a written arrangement that employees have agreed to and that rules out private use of the work mailbox. Settle this before the vacation, not during it.

Working hours and extra load. A deputy doing two jobs for three weeks is usually not something that just happens on top. It helps to agree in advance which of the deputy's own tasks are allowed to wait during that period. Without that agreement, cover is effectively built out of overtime.

The handover: 20 minutes before the vacation

The handover conversation is not a workshop and not a training session. It assumes the deputy already knows the process in principle, and limits itself to 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, deliveries land in that window? What is prepared, 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. The client who always follows up. The complaint that could escalate. The supplier who wants to change prices. This is exactly the kind of information that appears in no process description, because in four weeks it will be 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 closes the decision gap and is the one most often skipped.

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. Not tomorrow, now.

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 save more time per vacation than the conversation costs.

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. You still will not know whether the cover works until the deputy has run the process once themselves.

That makes the dry run the most important part of the whole arrangement, and it needs the least preparation: the deputy takes over the process on a normal working day, while the knowledge holder is in the building but does not intervene. They run the month-end payroll, create the delivery route, release the payment. With real data, in the real system, following the instructions listed in the table. The knowledge holder sits beside them, stays quiet, and notes down where the deputy gets stuck.

That log yields three findings. First, whether the instructions are any good: every point where the deputy had to ask is a gap in the documentation. Second, whether the access rights are complete. Third, whether the deputy would be able to act in an emergency or needs a second round. Only after a dry run that passes is the name in the table more than an intention.

Incidentally, the dry run is the simplest form of knowledge transfer there is, because the knowledge is not explained but applied. 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 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 filings and social insurance statements by the 10th, plus the usual client questions about joiners and leavers.

The year before, the cover looked like this. 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 had no idea that for one client the payslips are only ever sent out after their managing director signs off, because of a works council agreement. The result: two social insurance statements 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. That is when it becomes clear that the wiki instructions do not mention the construction clients with a single word and that the sign-off rule exists only in Ms. Nowak's head. Both get added, half an hour of work. On her last working day, the handover: which clients have joiners or leavers in July, where extensions are running, and up to what amount Mr. Pahl may release corrected payslips without asking.

The outcome of the three weeks: every filing on time, twelve client queries answered through the shared inbox, and a single phone call to Ms. Nowak about a back payment that genuinely nobody else knew about. Preparation cost roughly five hours of Mr. Pahl's time and three of Ms. Nowak's. Measured against two late filings and three weeks of half-vacation the year before, that is a good trade.

Vacation cover, bus factor and knowledge silos

A vacation is the harmless version of a problem 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. The only difference between a vacation and a resignation is that the vacation ends after three weeks.

That makes vacation cover the best early warning system you have. Every process where the work piles up during a holiday is a knowledge silo. The deputy arrangement shows it to you without anyone having to resign. And every deputy who passes the dry run is a silo dissolved. 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.

The hardest step is often the first: finding out which processes have no working cover at all. Management usually does not know precisely, and the people affected rarely volunteer it. At wissa.ai, that inventory runs through AI-led interviews with your employees, 15 to 20 minutes per person, by chat or voice, voluntary and with no performance evaluation. If someone names a colleague as a knowledge holder, that colleague is invited next. The conversations produce process documentation with a source reference for every statement, a process map and an org chart. And because the system records for every process step who carries it and who could take it over, the analysis shows the cover gap per step owner: the places where a step has exactly one person and nobody is named as a deputy. That is the first column of your deputy arrangement, filled in from the statements of the people doing the work.

If you want to know which of your processes would grind to a halt next summer: wissa.ai finds out by interview in the open beta, GDPR-compliant with EU hosting and a data processing agreement, and works council friendly. The first three interviews are free; after that, 12 interview credits cost 149 euros net, and interviewed employees stay free. Register for free

Conclusion

Vacation cover that works consists of four parts: a deputy arrangement per task rather than per person, 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 cannot be documented because it changes too fast. None of this takes much effort. What takes effort is what happens when it is missing.

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 rather than per person, 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?

Not without an arrangement. The clean route is shared functional inboxes that several people are authorized for, plus an out-of-office message. Access to a personal work mailbox needs a written company rule that employees have agreed to and that rules out private use. When in doubt, ask whoever is responsible for data protection.

What if nobody but the knowledge holder knows the task?

Then you have a knowledge silo, and the vacation is the best occasion to break it up. Name a deputy, document the process together, 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 working method no. If the deputy has to call regularly, the preparation has failed and the vacation is not one. Agree on a single channel for genuine emergencies and treat every call as a pointer to what is still missing from the instructions.