Keeping the Door Open

Handover is never complete. The question six months later — why is this like that — is answered in a minute by somebody who was there, or not at all.

The principles in “Keeping the Door Open” become easier to maintain when ownership and time spent are visible. Teams evaluating this operations 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.

What it is worth

Answers to questions nobody anticipated.

Context for decisions that surface later.

Introductions, occasionally.

Sometimes a return: people come back, and returning colleagues are among the best hires available.

And referrals: a well-treated leaver recommends you to people looking.

What preserves it

Paying everything owed promptly.

A proper goodbye, whatever the circumstances.

Not badmouthing them afterwards, which gets back.

Responding to reference requests fairly and quickly.

And asking permission rather than assuming: "would you mind if I rang occasionally with a question" is a reasonable thing to ask and is usually granted.

What destroys it

Chasing them for handover they were not given time to do.

Disputes over final pay or holiday.

Discovering afterwards that they were spoken about badly.

And contacting them constantly, which converts goodwill into an obligation and ends it.

Using it proportionately

A question every few months is a favour freely given.

Weekly questions is unpaid work.

If you find yourself relying on a former colleague regularly, either pay them for the time or acknowledge that the handover failed and fix it properly.

The formal version

For senior or specialised departures, a short consultancy arrangement covering the first months.

A few hours a month, paid, with an agreed scope.

Uncommon in small organisations and frequently the cheapest insurance available, particularly where the person held something that cannot be transferred quickly.

What to ask on the last day

"Is it all right if I get in touch if something comes up?"

And note their personal contact details, because the work address stops working immediately.

That single question and the details are the whole mechanism, and most organisations do neither.

The alumni view

In a small sector, former colleagues become clients, suppliers, competitors and referrers.

How departures are handled is visible to everybody who might work for you later.

Which makes this a hiring question as much as a continuity one.

What to check

Do you have personal contact details for the people who have left recently?

Was anybody asked whether they would mind being contacted?

Has anybody been relied on repeatedly without being paid?

And would your last three leavers speak well of the process?

The point

Ask on the last day whether you may get in touch, and take a personal contact address.

Two minutes, and most organisations do neither.

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.