Notice Periods and What They Are For

General orientation, not legal advice; notice requirements differ by jurisdiction and contract.

The principles in “Notice Periods and What They Are For” become easier to maintain when ownership and time spent are visible. Teams evaluating the practical checklist 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.

Notice exists so that work can be transferred. In practice it is frequently spent finishing projects, which is the least valuable use of it.

What notice is usually spent on

Completing whatever the person was working on.

A flurry of documentation in the final week.

Exit formalities.

And awkwardness, which consumes more of the period than anybody admits.

What it should be spent on

Transferring the things only they know, in order of consequence.

Introducing successors to clients and suppliers.

Writing down reasons and exceptions, not procedures.

And answering questions from whoever is taking over, which is the highest-value activity and requires that somebody is taking over.

The first conversation

Within a day of the resignation, agree what the notice period is for.

Ask them: what do you know that nobody else does?

People are usually candid at this point — they have nothing to lose and most want to leave things in order.

That conversation produces a better dependence map than any exercise you could run while they were staying.

Ordering the transfer

Consequence first, as in the spreading note.

Access and credentials immediately, because they are quick and because delay creates security problems.

Client introductions early, so there is time for more than one contact.

And the writing last, because it can be done alone and the interactive things cannot.

Who receives it

Name somebody, even if they are not the permanent successor.

Transfer to nobody in particular does not happen: the documents get written and nobody reads them.

A named receiver asks questions, which is what makes the transfer real.

When notice is short

A week, or a day where the departure is immediate.

Then triage ruthlessly: access, client contacts, current state of in-flight work. Nothing else.

Thirty minutes of the right questions beats three days of documentation, and the question list is in the note on handover conversations.

Garden leave and immediate exits

Sometimes required for competitive or security reasons.

It costs you the handover entirely, which is a real price and should be weighed rather than assumed.

Where it is necessary, a structured written handover before the exit is announced is sometimes possible, and worth arranging with advice.

What to check

When somebody last resigned, what did the notice period actually produce?

Was there a named receiver?

Did anybody ask what only they knew?

And was access transferred in the first days or the last?

The point

Notice exists so work can be transferred, not so projects can be finished.

Ask on day one what they know that nobody else does.

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.