A long absence: who covers that role in the meantime

Nobody plans a long absence. Holidays get planned, the August shutdown gets planned, the December bridge gets planned; an absence that starts with no return date does not. And when it happens, the work does not stop: tickets keep coming in, returns stay open, and month-end still has a date.

This article is not about what you are entitled to or what you have to do: you look at that with your accountant and whoever advises you. It is about the other part, the one almost nobody writes down: what breaks in the operation, in what order, and why the options available tend to arrive late.

The problem is not day one. It is week three

Day one gets solved. The urgent things get shared out, someone on the team takes over the inbox or the close, and the rest gets parked "until they are back". That is the right answer for a week.

What gets parked does not disappear: it piles up. By week three, whoever was covering the gap has spent twenty days doing their own job and someone else's, and it is no longer a temporary situation, it is the new normal. The queue grows slowly, and precisely because it grows slowly nobody raises the alarm.

And there is a second queue that shows up on no dashboard: the one nobody has opened. The claims that were never filed with the supplier, the reconciliation pushed to next week three weeks in a row, the reviews left unanswered. They do not appear as pending work because they never entered the system.

What leaves with the person was never written down

The part of a role that gets documented is the easy part: the procedure, the access, the reply template. The hard part is the part nobody ever noted, because there was no need while that person was there.

Which customer you have to call before sending the invoice. Which supplier actually takes twice as long as they say. At exactly what point the exception agreed last year applies, the one that is in no written policy. Which of the two warehouses answers the phone faster.

That does not transfer in a handover meeting, least of all when there is no handover meeting, which is what happens in an absence that starts on a Tuesday morning. Whoever covers the role discovers it by getting things wrong, and each discovery costs one uncomfortable customer.

The team covers halfway, and that gets paid too

The default option — sharing the work among the people already there — has one virtue: it is immediate and needs no approval. And it has a cost that gets paid in two places at once.

The first is the own work of whoever is covering. Nobody does two roles at a hundred per cent; what happens is that both drop a little, and the one that drops most is the one with nobody watching it.

The second is slower and more expensive: fatigue. Covering someone else's gap for three weeks is a favour; three months is a reason to answer a recruiter. Long absences that are badly covered have a habit of producing the next absence or the next resignation, and that one you do not see coming.

The options you have, and why they arrive late

Absorb it and share it out. Works for a few weeks. The problem is that it has no explicit expiry date, so it stretches until someone breaks.

Hire a temporary replacement. It is the option that looks obvious and the one least used, for a reasonable motive: by the time you have posted, filtered, interviewed and trained someone, the absence may be ending. And while you decide, the work keeps degrading.

A freelancer for the urgent part. It works for tasks with a clear outline — one reconciliation, one migration, one ticket peak — and stops working as soon as the role needs judgement of its own or several tools. They also work alone: if they get stuck, they stay stuck.

Do nothing and wait. It is the option chosen without choosing it, because deciding is costly and the role still belongs to whoever is away.

The common pattern is the same in all four: they all get activated afterwards. The absence starts on day zero and the response gets going in week three, when there is already a queue, fatigue and customers asking. It is not a management failing: it is that none of those options can be kept ready.

What you can decide in advance

There are two things that cost no money and that completely change how the following month feels.

The first is writing the role down while the person is there. Not a manual: one page. What gets done each day and in what order, what gets escalated and to whom, the five exceptions that are in no policy and the four contacts you have to know. Half an hour a month with whoever holds the role and in a quarter it is done.

The second is deciding the threshold in advance. If the absence goes past two weeks, one plan gets activated; if it goes past six, another one. Written down beforehand, when there is no urgency. Most bad decisions during a long absence are not bad for lack of judgement, but because they get taken on the day there was no room left.

That holds for any operation, but it shows most where the work has a date of its own and does not wait: a shop in peak season, an accounting close, a booking calendar. In an ecommerce business, three weeks of queue in customer support are not recovered by working faster afterwards; they get paid in late returns and in reviews.

How it is solved when the role is not yours

Here we describe our own model, which is the only thing we can assert. When the role is covered by a pod, an absence stops being a problem you have to solve.

Planned absences are covered up to 20 days a year, inside the fee and with no paperwork on your side. If the person is not the right fit, we find another one at no recruitment cost to you and present candidates within 15 working days at most, because we never stop qualifying profiles for your role while the pod is active. The time between one person leaving and the next one starting their day 1 is not invoiced.

And whoever comes in does not start from an empty folder: they inherit the documented procedures for the role, which stay current because a system of ours interviews the person holding it periodically to record their duties and what they are learning. That documentation is available to you and you can add to it.

For an absence longer than that, the honest answer is that it gets discussed case by case, and we prefer that to promising cover that is not defined. What is defined, with its deadlines and its conditions, is in absences and replacements and in the guarantees, including the 90-day guarantee, which goes with the service and does not reset when the person changes.

Where to go next

Think of the role in your company that would be hardest to cover tomorrow. Not the most important one: the one that is least written down. If the answer is "she knows all of it", you already have this month's task: half an hour with that person and one page.

And if you would rather that risk did not live on your side, look at what is covered in writing in absences and replacements before you talk to anyone.