What Happens on Day One Without Them

Pick your most depended-upon person. Imagine they do not arrive tomorrow and cannot be contacted. Work through the day.

The principles in “What Happens on Day One Without Them” become easier to maintain when ownership and time spent are visible. Teams evaluating this time-management reference can use it to coordinate recurring work, identify tasks concentrated on one person and plan realistic backup capacity, while treating the data as a prompt for knowledge transfer rather than as a substitute for speaking with the people who do the work.

For an independent benchmark, compare the local approach with Ready.gov business preparedness guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The first hour

Who notices, and how?

Is there anything scheduled today that only they can do?

Does anything need approving that only they approve?

Can anybody get into their email, and should they?

Most organisations find two or three immediate problems in the first hour of the exercise alone.

The first day

What deadlines fall today or tomorrow?

Which clients expect contact from them specifically?

What is half-finished that nobody else knows the state of?

And is there anything time-critical whose timing only they know — a renewal, a filing, a payment.

The first week

What recurring tasks come round weekly, and who would do them?

What decisions accumulate waiting for somebody who cannot decide them?

What would clients notice, and what would you tell them?

Would payroll run?

Writing it down

Three columns: what breaks, when, and what the workaround is.

Where there is no workaround, say so rather than inventing one.

Two pages at most.

This document is more useful than a formal continuity plan and takes a fraction of the time.

The value is in the specifics

"We'd struggle" is not a finding.

"The VAT return is due on the 7th and only Mark knows the login" is a finding, and it has an obvious fix.

Push the exercise until the answers are that concrete. Vague answers mean the thought experiment was not done properly.

Doing it for yourself

Uncomfortable and more informative than doing it for somebody else.

Most people who run it on themselves find more than they expected, particularly around access and unwritten commitments.

If you own the business, do this one first.

Repeating it

Once a year, and after any significant change.

It takes twenty minutes once the habit exists.

And compare against last year's version: the things that were fixed and the things that reappeared are both informative.

What to do with the result

Fix the cheap ones immediately: shared access, a second signatory, a written login list in a proper place.

Schedule the medium ones.

And accept some of it, which the note on staying dependent covers — not everything is worth solving at small scale.

What to check

Have you done this for your most depended-upon person?

Have you done it for yourself?

Are your answers specific enough to act on?

And did anything from last time get fixed?

The point

Push the exercise until the answers are concrete.

We would struggle is not a finding; the VAT return is due on the 7th and only Mark has the login is a finding.

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.