Employee offboarding: the process that protects both sides
TL;DR
- Offboarding gets a fraction of the attention onboarding gets, and it carries more risk: unrevoked access, lost knowledge and public reviews.
- Access revocation happens on the last day, not the following week. Manual checklists routinely miss two or three accounts.
- The knowledge transfer window is the two weeks before departure, not the exit interview. After that, nobody is motivated to document anything.
- An exit interview is worth running only if somebody reads the aggregate. A single conversation changes nothing; a pattern across ten does.
Every company invests in onboarding and almost none invests in its mirror image, which is odd given where the risk actually sits. A badly run departure leaves accounts open, knowledge undocumented and a former colleague writing a public review of your management. Here is a seven-step process that takes an afternoon to set up, the access checklist that matters most, and an honest view of what an exit interview can and cannot do.
Why offboarding carries more risk than onboarding
A slow onboarding costs productivity. A sloppy offboarding costs something harder to recover.
- Security. An account left open after a departure is not a loose end, it is an exposure. Manual checklists miss accounts routinely, especially the tools adopted by one team without IT involvement.
- Knowledge. The undocumented process, the client relationship, the reason a workaround exists: all of it walks out with the person unless it is captured before the last week.
- Reputation. Public employer reviews are overwhelmingly written by people who left, and mostly in the weeks that follow. How you handle a departure is being published either way.
The asymmetry to keep in mind
You control onboarding entirely and you control offboarding only partially, because the person is already leaving. That is exactly why it has to be a process rather than a set of good intentions.
The seven steps, in order
Acknowledge the departure formally
Confirm dates, notice period and final day in writing on the day it is agreed. Everything downstream keys off those dates.
Build the transition plan
Who takes which responsibility, and from when. Do this in week one of the notice period, not week three, because it determines what needs documenting.
Capture the knowledge
Two weeks before the last day, while there is still motivation. Written handover of live work, key contacts and anything only this person knows.
Announce internally
Before the rumour does. A short, factual message from the manager beats speculation, and it lets colleagues plan handovers themselves.
Run the exit interview
Ideally a few days before the last day, conducted by someone other than the direct manager.
Revoke access on the last day
Every account, every device, every physical key. Same day, not the following week.
Close the administrative file
Final pay, documents, equipment returned, and whatever your jurisdiction requires. Missing paperwork is the most common reason a clean departure turns sour.
The access checklist nobody completes
This is the step most often botched, because access has spread far beyond what IT formally issued. Work through five categories rather than trying to remember tool by tool.
| Category | What to check | Common miss |
|---|---|---|
| Identity | Email, single sign-on, directory account | Shared mailboxes and aliases that survive the main account |
| Business tools | CRM, help desk, HRIS, finance, code repositories | Tools adopted by one team without IT knowing |
| Credentials | Shared passwords, API keys, service accounts | Anything the person knew rather than held |
| Devices | Laptop, phone, security keys, badges | Personal devices with company data still synced |
| External | Client portals, supplier accounts, social media | Accounts registered under a personal email address |
The category people forget
Shared credentials. Revoking someone’s account does nothing if they knew a password used by the whole team. Any shared secret the person had access to should be rotated on departure, not just their individual login.
This is precisely the problem platforms with IT provisioning are built to solve: when the employee record drives account creation, it can also drive account removal in one action. It is worth weighing when you compare Gusto and Rippling.
Capturing what only they know
The mistake is treating this as documentation, which nobody wants to write on their way out. Frame it as three questions instead, answered in a shared document during a working session.
- What is in flight right now, and what happens if nobody touches it? This surfaces the urgent handovers.
- What do you do that is not written anywhere? Recurring tasks, informal approvals, the vendor contact who only replies to them.
- What would you warn your replacement about? This one produces the most useful answers and the ones nobody else can give.
Quick quiz
When should knowledge capture happen?
What an exit interview can and cannot do
It cannot save the departure, and treating it as a retention conversation makes it worse. What it can do is surface patterns, and only if two conditions hold.
- Someone other than the direct manager runs it. People do not describe a management problem to the manager causing it.
- Somebody reads the aggregate. A single interview changes nothing. Ten interviews reviewed together tell you whether departures share a cause, and that is the only actionable output.
If you cannot commit to the second condition, be honest and skip the exercise. A ritual interview whose notes nobody opens costs everyone time and produces a quiet cynicism that outlives the departure.
What happens after the last day
The relationship does not end at the door, and the companies that understand this get two concrete returns.
- Rehiring. Former employees who return are cheaper to hire, faster to ramp and already understand the business. That only happens if the departure was handled well.
- Referrals and reputation. A well-treated leaver refers candidates and clients. A badly treated one writes a review that costs you both.
None of this requires a formal alumni programme. It requires that the last two weeks are handled with the same care as the first two, which is the whole argument for treating offboarding as a process rather than an afterthought.
Automate the access checklist?
Our comparison ranks the HR platforms of 2026, including those that provision and revoke access automatically.
What to do next
To automate onboarding and offboarding, see our best HR software 2026 comparison, or our guide to employee onboarding.
Frequently asked questions
What is employee offboarding?
It is the structured process that runs from the moment a departure is confirmed to the closing of the administrative file: transition planning, knowledge capture, internal announcement, exit interview, access revocation and final paperwork. It is the mirror image of onboarding, and it carries more risk because unrevoked access, lost knowledge and public reviews are all decided here.
When should access be revoked?
On the last day, not the following week. The category most often missed is not individual accounts but shared credentials: revoking someone’s login does nothing if they knew a password used by the whole team, so any shared secret they had access to should be rotated at departure. Tools adopted by one team without IT involvement are the other common gap.
When should knowledge transfer happen?
About two weeks before the last day, while there is still motivation to do it. Framing it as documentation rarely works. Three questions in a working session produce far more: what is in flight right now, what do you do that is written nowhere, and what would you warn your replacement about. The last one produces answers nobody else can give.
Are exit interviews worth running?
Only under two conditions. Someone other than the direct manager must run it, because people do not describe a management problem to the manager causing it. And somebody must read the aggregate across many interviews, since a single conversation changes nothing while a pattern across ten tells you whether departures share a cause. If you cannot commit to the second, skip the exercise honestly.
Why does offboarding matter after someone has left?
Because former employees are cheaper to rehire, faster to ramp and already understand the business, and because they write the public employer reviews that shape your hiring. A well-handled departure produces referrals and candidates; a badly handled one produces a review that costs you both. None of this needs a formal alumni programme, only that the last two weeks get the care the first two got.