Offboarding

The arrival side got a name early. Employee onboarding — helping a new hire get productive quickly — has an owner and a checklist at almost every company. The departure side had no name at all. Say goodbye on the last day, clear the desk, done.

The gaps showed up after the person was gone. A reconciliation job that runs once a quarter stops, and nobody left knows how to run it. Customers keep emailing the old account manager's address and nobody is reading that inbox. Accounts are worse. Finding, during a security check, that someone who left four months ago still has working access was not a rare event.

Looking back, the cause was sequence rather than people. Whoever handled a departure started from whatever came to mind first, so a different item fell through every time. Offboarding is the word for turning that handling into a process with a fixed order and named owners. The starting premise is simple: if there are steps for coming in, there should be steps for going out.

From the day the resignation is confirmed through the week after the last working day, this usually runs in six steps.

1. Set the schedule and who hears about it — fix the last working day and decide who is told and when. Many people want to break the news themselves, and without an agreed order the rumor arrives first.
2. List the work — write down everything the person owns. What gets missed is rarely the daily work, which the team already sees; it's the job that runs once a quarter and the outside vendor whose contact only this person has.
3. Name the receivers — assign one person per item. Writing that the team will share it means, in practice, that nobody has it.
4. Move documents and accounts — shift files out of a personal drive into team space, and move any outside service contracts and alert recipients registered under that person's name onto a team account.
5. Revoke access and collect equipment — disable accounts at close of business on the last working day and take back the hardware. If internal tools sit behind single sign-on (SSO), locking one account closes most of them, but anything signed up for individually stays open.
6. Settle up — calculate and pay the final salary, unused leave, and severance.

Step 5 is the one that slips most often. Skip any of the others and someone is inconvenienced today; skip access revocation and nothing happens for a while. That's why many companies don't treat a last-day check as the end of it, and run an access review a week later to confirm.

No single person can run this. The direct manager decides the work list and who receives each item. The people team handles scheduling and the final settlement. Whoever owns security or IT handles access and equipment. The colleagues inheriting the work do the actual receiving. The person leaving is a participant too — writing the list and leaving the documents behind is work only they can do.

The timing hangs off the notice date. At a company with about a month of notice, the intervals look like this.

1. Day of notice — the last working day is fixed and the announcement order is set.
2. Halfway through the remaining time — the work list and the receivers are settled, and handover starts. If the list isn't ready by then, everything piles into the final two weeks and the handover becomes verbal instead of written.
3. Final week — an exit interview captures why the person is leaving, and equipment return gets scheduled.
4. Last working day — accounts are locked at close of business.
5. One week later — confirm that no access remains and that mail and documents have moved to team accounts.

When the company is the one ending the relationship, these intervals collapse. In a layoff, where notice and the last day are only days apart, access is usually revoked the same day the person is told, and the handover becomes something the remaining team reconstructs from documents afterward.

"Friday next week is their last day, can we get offboarding scheduled?"

A request to decide what gets handed over and revoked, and in what order.

"Does the offboarding checklist cover third-party tool accounts too?"

Pointing out that locking internal accounts alone leaves things open.

"Nothing was written down during their offboarding, so nobody can touch that batch job now."

A rushed process came back as a cost several months later.

When Theo left Pagedeck for another company, his list came to more than thirty items. Half of them were things other engineers already knew. The rest were the problem: a data cleanup he ran by hand in the first week of every month, and the relationship with the contact at the payment processor, which existed only with him.

Mia moved those two to the front of the remaining two weeks. Rather than running the monthly job alone one last time, Theo ran it alongside the person taking it over, and the payment processor was emailed in advance about the change of contact. Grace checked separately on the last afternoon that every account had been closed.

Many people read offboarding as paperwork. Settlements and equipment returns are the visible items, so that's the impression. But the part that takes the most time is moving knowledge, and that's also where the cost lands when it doesn't happen. Cleaning up accounts takes half a day. A procedure that lives in one person's head takes days to write down, and months of fumbling if it isn't. Judging how long an offboarding needs by the length of the checklist, rather than by how much of the work exists only as something one person remembers, is what produces the two-week plan that turns out to need four.

The other frequent assumption is that the last day is enough to do it all in. That day is the company's reference point, so the mistake is natural. The trouble is that by then the person is already looking at the next job. A two-hour meeting on the final day rarely sticks, and when a question surfaces a week later there is nobody to ask. Starting the handover at the halfway point is what buys room to ask twice, and the second question is usually the one that matters, because the first pass tends to cover what the job does rather than what goes wrong with it.