A missed leaver costs more

The asymmetry

Every onboarding step has an owner who is present and motivated: the joiner. Missing access gets reported within hours, because it blocks their work.

Offboarding steps have owners who are busy and unprompted. The leaver has gone. The manager is covering the gap. IT has a queue. Nothing in the day points at the unticked line.

So onboarding is self-correcting and offboarding is not. Two lists that look symmetrical need completely different designs.

What actually goes wrong

Accounts stay live. Not the main login, usually. That gets revoked. The shared tool nobody catalogued, the vendor portal, the account created for one project two years ago.

Hardware disappears slowly. A laptop goes home for the last week and never comes back, and by the time anyone checks, the person is unreachable and the serial number was never recorded anyway.

Knowledge leaves undocumented. Handover was scheduled for the last two days and the last two days went on goodbyes.

And ownership stays behind. Files in a personal drive, a repository owned by a leaver's account, a recurring subscription on their card.

Designing for absence

Three changes do most of the work.

Split the process in two. The last day is one list with a hard deadline: access, hardware, the exit conversation. The fortnight after is a separate list with different owners. Running them as one means the tail gets abandoned when the deadline passes.

Give every line an owner who is still employed. A line owned by the leaver needs a deadline before the last day, or it needs reassigning.

Make the open items visible to someone whose job it is to look. An unticked line in a tracked process with a resolved count is a question. An unticked line in a document is invisible.

• Two processes: the last day, and the weeks after it.
• No line owned by someone who has already left.
• Hardware chased against a serial number, not a description.
• Shared and forgotten accounts listed explicitly, every time.
• A named person who reviews open leaver processes weekly.

How this looks in the product

PeopleMuster runs both as SOP templates, instantiated against the person leaving. The live instance keeps Off-boarding and Post-Offboarding as two separate templates, which is exactly the split above, arrived at by getting it wrong first.

Each running process carries an assignee, an initiator, an age and a resolved count such as four of eleven. That count is the thing a document cannot give you.

Hardware is chased against the asset list, where each device holds a code, a serial number and a verified state rather than a description in a sheet.

The sudden exit, which is a different sequence

A planned leaver gives you weeks. A dismissal or a walkout gives you an afternoon, and the order changes completely.

Access usually goes first, which is the opposite of the normal rule. Then hardware, then whatever handover can be salvaged from what was written down.

That last part is why the routine matters more than the list. A team that documents as it goes loses a week when somebody leaves suddenly. A team that does not loses a month.

Write the fast version down before you need it. Deciding the sequence during the afternoon it happens is how steps get missed.

The number nobody measures

Most teams cannot say how long their last five leaver processes stayed open. That figure is worth having, because it is the one that shows the problem.

An open process a month after the last day is not an oversight. It is the normal outcome of a list with no one watching it.

So pick a person, give them a fortnightly look at open leaver processes, and let the age of each one be the prompt. Age is the signal here, not the ticked count.

It is a ten-minute habit, and it closes the gap that costs the most.

The exit conversation, and why it slips

One step gets dropped more than any other, and it is the one with no deadline attached to it.

Held on the last morning, an exit conversation is candid and specific. The person is still close enough to the work to remember it, and far enough out to say what they think.

Held a week later it does not get held. There is no meeting, no prompt, and nobody feels the absence.

Put it on the last-day list, give it an owner who is not the line manager, and treat a skipped one as a missed step rather than a scheduling problem.

People say more to someone from HR or a skip-level, particularly when the manager is part of why they are leaving. That is not cynicism. It is just the reason the step is worth designing rather than hoping for.