A Checklist for the Whole Thing

This afternoon

Check who owns your domain and hosting, and whose card renews it.

Once the minimum record described in “A Checklist for the Whole Thing” is defined, the practical challenge is keeping it current as work changes. A coordinator can use the reporting guide to plan review time, compare the effort attached to recurring processes and identify work that still depends on one person, without confusing activity visibility with proof that the underlying knowledge has actually been transferred.

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.

List accounts registered to personal email addresses.

Find out whose phone holds two-factor for anything critical.

Write down your key suppliers: contact, account number, what is normally ordered, what has been agreed informally.

This week

Write the map: activities down the side, who does it, who else could, where the knowledge lives.

Do the day-one exercise for your most depended-upon person, and for yourself.

Score the list by consequence and effort.

Do the high-consequence, low-effort items.

This month

Set up a password manager with a shared vault.

Start the process for a second bank signatory, which will take longer than you expect.

Write a page for each of your three most critical activities: what it is for, where things are, what is unusual, who to ask.

Assemble the folder: bank, insurance, accountant, registrations.

This quarter

Use the next planned absence as a rehearsal: no contact, coverers record what they could not answer, half-hour review afterwards.

Name a second person for each critical activity and have them do it once.

Check which permissions depend on a named individual, and what the replacement process involves.

This year

Introduce a second person to each significant client, gradually.

Pair on the things that cannot be documented.

Record decisions as they are made, a dozen a year.

And if you own the business, take two weeks without contact.

At each event

Someone joins: they write their own role's documentation in the first eight weeks.

Someone goes on holiday: rehearsal, review, update the map.

Someone resigns: named receiver, access first, four handover conversations, document started on day two.

A vacancy: redistribute before writing the job description.

Someone is unexpectedly absent: triage, name a coverer, record what has to be discovered.

Twice a year

Update the map.

Count the three numbers: single-person activities, uninterrupted days off, single-person access.

Delete what is obsolete from the shared folder.

And review what you have accepted, against the organisation's current size.

The whole thing in one line

Know where the dependence is, do the cheap fixes, use the absences that are already happening, and decide deliberately about the rest.

The point

Know where the dependence is, do the cheap fixes, use the absences that are already happening, and decide deliberately about the rest..

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.