Planned Absence: Holiday as a Test

Everything in this collection is theoretical until somebody is actually away. A planned absence is the rehearsal, and most organisations waste it.

For a resilience routine built around “Planned Absence: Holiday as a Test”, improvement depends on seeing whether backup work happens outside an emergency. Teams can use the time-recording overview to organise practice time and compare planned coverage with actual participation, but the record should prompt a handover conversation rather than become an automatic judgement about an employee.

For an independent benchmark, compare the local approach with WHO guidance on mental health at work; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

Wasting it

The person answers messages from the beach.

Everything difficult is deferred until they return.

Nothing is recorded about what came up.

And they come back to a backlog, which reinforces the belief that they cannot be away.

Using it

Agree in advance that they will not be contacted, and mean it.

Name who covers what.

Ask the coverers to note everything they could not answer, rather than saving it up to ask.

And do a short review afterwards, from that list.

The list is the whole value of the exercise.

The preparation

A week before: what is in flight, what is due, what is promised.

Access checked, not assumed.

Clients and suppliers told who to contact.

An out-of-office that names the alternate rather than saying "I will respond on my return", which defeats the point.

During

The coverer's rule: attempt it, and if you cannot, note it and ask a colleague rather than the absent person.

Deferring is legitimate for genuinely non-urgent things and should be recorded as a deferral.

And a genuine emergency can break the rule — but define what counts in advance, because otherwise everything becomes one.

The review afterwards

Half an hour, with the list.

For each item: was it a knowledge gap, an access gap, or an authority gap?

Each category has a different fix, and the categorisation is what turns a list of annoyances into actions.

Then update the map.

What you usually learn

More access problems than expected.

One or two clients who insisted on the absent person.

A thing everybody assumed was documented and was not.

And that the coverage held better than feared, which is the most common outcome and worth noticing because the fear is what prevents the next absence.

Building the habit

Every significant absence becomes a small test.

Nobody has to schedule anything extra: the holidays are already happening.

Over two years this produces more improvement than any deliberate programme, at no additional cost.

What to check

When somebody was last away, were they contacted?

Did anybody write down what could not be answered?

Was there a review afterwards?

And does your out-of-office name an alternate?

The point

Ask the coverers to record everything they could not answer.

That list is the whole value of a planned absence.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.

The recurring pattern

The recurring pattern across every section here is the same: dependence forms through sensible individual decisions, becomes invisible because it feels like reliability, and is addressed only after it has cost something. The work that prevents that is small, continuous and unglamorous, which is exactly why it gets deferred.