The Manager Who Cannot Take Holiday

They have not taken a full week in two years. Every time it is arranged, something comes up, and everyone agrees it is easier if they are around.

That is not dedication. It is a description of how the venue is built, and it is a risk that grows quietly.

What it actually means

Several jobs are one person. Not their formal role — the accumulated set of things only they do.

Nothing is documented, because they never needed it to be. ⚠️ They are the documentation, and it is only in one place.

Decisions wait for them. Which is efficient while they are present and stops entirely when they are not.

Nobody else has practised. ⚠️ The part that matters. Even a capable deputy who has never actually run a week is not a tested arrangement.

Why it persists

It is easier every single time. Each individual occasion genuinely is easier with them there. The cost is only visible in aggregate, over years.

They may prefer it. Being essential is a real form of standing, and stepping back can feel like being diminished. ⚠️ This has to be handled openly, or every attempt at delegation quietly fails.

Nobody has calculated the risk. The question "what happens if they are ill for a fortnight" has never been asked out loud, and the answer is uncomfortable enough that nobody asks it.

The cheap test

You do not need a crisis. A week, planned, with them genuinely unreachable.

Plan it a month out. Which itself forces the preparation that has never happened.

Genuinely unreachable. ⚠️ The whole value is in this. A manager answering messages from a beach is still running the venue, and the test measures nothing.

Write down what broke. Not to blame anyone — the list of what broke is exactly the list of what needs fixing, and it cannot be produced any other way.

Expect it to be uncomfortable. One uncomfortable planned week is much cheaper than one unplanned one.

What the list will contain

Predictably:

Suppliers who only speak to them. Fixable in an afternoon by making an introduction.

Decisions nobody felt authorised to make. ⚠️ Usually the largest category, and usually solved by stating a limit rather than by training anyone.

Information that only exists in their head. Guest history, precedent, why things are as they are.

Tasks nobody knew existed. The invisible weekly things. These only surface by not being done.

Fixing it afterwards

Authority first. Most of what broke was not capability — it was permission. Say what the next person may decide, in specific terms and in advance.

Then the single-source knowledge. One item at a time, captured where the next person will look.

Then practise again. ⚠️ Two days, three months later. If nothing breaks, it worked. If the same things break, the fix was written down and not adopted.

The part that is about them

Someone who cannot take holiday is on a path to leaving. Not soon, and not loudly — but the accumulation is real and the resignation, when it comes, will be attributed to something else.

⚠️ Removing the dependency is a retention measure, and it is worth saying that to them explicitly, because from the inside it can look like being sidelined.

Three to hold

Days since each key person had a genuine week off. ⚠️ Write it down. The number is usually a surprise.

Items on the broke-while-away list, and how many are fixed. The only real measure of progress here.

Decisions escalated to one person per week. Falling means the authority fix worked.

Where the record has to sit

Everything that broke while they were away broke because it lived only with them. The fix has to sit where the next person on shift will find it, not in a document written once after an uncomfortable week.

tasteck keeps notes, tasks and history on the records staff already open, so what one person knows has somewhere to accumulate.

They are not indispensable by nature. They became indispensable because it was easier every single time, and nobody was counting.