Sudden Departure Without Notice

They resigned with immediate effect, or walked out, or were dismissed on the spot. There is no notice period and nothing was prepared.

The principles in “Sudden Departure Without Notice” become easier to maintain when ownership and time spent are visible. Teams evaluating the complete guide 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

Secure access: revoke what you can, change shared credentials, check recovery addresses.

Preserve records before anything is tidied.

Establish what is happening today and tomorrow from their calendar.

And decide who is covering, explicitly.

What to get from the person, if anything

Where the relationship allows, ask for one conversation: what is in flight, what is promised, what only you can access.

Fifteen minutes, and some people will give it even in a difficult departure.

Where it does not, do not pursue it. The cost of a contested exchange exceeds the value of the information.

Reconstructing current state

Calendar for commitments.

Sent mail for recent promises.

Any tracker, however partial.

Clients and suppliers, asked directly what is outstanding.

Colleagues, asked systematically rather than in passing.

This produces most of what a handover would have, more slowly.

What gets missed

Verbal commitments nobody else heard.

Informal supplier arrangements.

Half-finished work nobody knew existed.

And renewal dates carried in somebody's head, which surface later as a lapsed policy or an auto-renewed contract nobody wanted.

Expect these and check the obvious categories deliberately.

Telling people

Clients: brief, neutral, with a named replacement contact.

Team: what is known, who covers, what is deferred.

Same day, before rumour.

And no detail about the circumstances, which is both appropriate and safer.

The contract question

General orientation, not legal advice.

Immediate resignation may breach a notice obligation, and pursuing that is rarely worth it.

Focus on what you need: access, current state, and any property or data held.

Take advice where confidential information or clients may be at risk.

Afterwards

Write down everything that had to be reconstructed and how long it took.

This is the most persuasive document your organisation will ever have about why the preventive work matters.

Use it within a month, while people remember.

What to check

Could you revoke all access today?

Do you know where the current state of each person's work would be visible?

Who would ask clients what is outstanding?

And is there a preservation step before anybody tidies up?

The point

Write down everything that had to be reconstructed and how long it took.

It is the most persuasive argument your organisation will ever have for the preventive work.

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.