The Employee Offboarding Checklist: Every Step and Who Owns It

When someone leaves a company, the work of the departure is split across at least four people. The manager handles the handover of in-flight work, HR runs the paperwork and the exit interview, IT pulls access and collects equipment, and finance closes out payroll. Nobody owns the whole process, and most of the people involved only deal with a departure a few times a year. That combination is what an employee offboarding checklist is for: a written list of every step, with a named owner for each, so the process runs the same way whether it's the third departure this quarter or the first one since last spring.

This post covers what a complete checklist needs to include — knowledge transfer, access revocation, equipment return, final pay, the exit interview, and the long tail of ownership changes — plus a sample checklist you can copy, and a practical way to run it so each step actually gets done by its deadline.

Knowledge transfer and handing over in-flight work

This is the part to start the day notice is given, because it's the only part that needs the departing person's active participation and their time is now finite. Begin with an inventory: open projects, client or vendor relationships they own, and recurring duties like a weekly report or a monthly invoice run. Recurring duties deserve special attention because they don't appear on any project board, and a skipped handover there only shows up when the month ends and the invoices haven't gone out.

For each item on the inventory, name a successor and have the departing employee write down enough for that person to take over: current status, where the files live, who the contacts are, and any deadlines already promised. For complex workflows, a recorded screen walkthrough captures more than a document, and it takes the departing person less time to produce. Then have the successor actually do the task once while the departing employee is still around to answer questions.

If the person owns customer relationships, treat each account as its own handover with an introduction to the new owner before the departure is announced more widely. The structure is the same as any planned ownership change between teams; this guide to running a sales-to-customer-success handoff in Slack covers that pattern in more detail.

Revoking access across your SaaS tools

A mid-sized company typically runs on dozens of SaaS products, and a departing employee has accounts in many of them. If you use single sign-on, deactivating the SSO account covers the connected tools in one step. It doesn't cover tools that were never put behind SSO, shared team logins, API keys the person created, or accounts they signed up for directly and expensed. Those have to be found and revoked one by one, which is why the access step belongs on a checklist rather than in someone's head.

The risk of skipping this is well documented. A Beyond Identity survey of over 1,100 employees and business leaders found that 83% of respondents could still access accounts from a previous employer after leaving, and only 9% remembered IT being involved in their offboarding at all. Most of those people never do anything harmful with the access, but the accounts sit open indefinitely, and every one of them is outside your security controls.

A practical approach: keep a per-person access inventory while people are employed (your SSO admin panel plus expense reports will surface most of it), revoke on a defined schedule rather than "soon," terminate active sessions as well as the account itself, and rotate any shared credentials the person knew. The timing of the cutoff depends on how the person is leaving, which is covered below.

Equipment, final pay, and benefits

Equipment return is easy to overlook, especially for remote employees. List what the person has (laptop, monitor, badge, keys, hardware tokens), and for remote staff, send a prepaid shipping box before the last day rather than after it. Decide in advance what happens if something doesn't come back; most device-management tools can wipe a laptop remotely, which protects the data even if the hardware is gone.

Final pay has legal deadlines, and they vary by jurisdiction. In the US there's no federal deadline — the Department of Labor notes that state law controls, and many states set different deadlines depending on whether the person quit or was let go, in some cases requiring payment on the last day itself. Other countries have their own rules. The checklist step here is for payroll to confirm the applicable deadline as soon as the departure date is known, along with accrued vacation payout, outstanding expense reimbursements, and the paperwork for benefits ending or continuing. Confirm the rules that apply where the employee works rather than relying on a general article, this one included.

The exit interview

The exit interview is HR's step, and the main decisions are who runs it and when. ADP's offboarding guidance recommends having someone other than the direct manager conduct it — people are more candid with someone they didn't report to — and giving the employee a few days' notice so they can collect their thoughts. Scheduling it a couple of days before the last day works better than the last day itself, when the person is distracted and half gone.

Keep the questions open-ended, write down what you hear, and route anything actionable to whoever can act on it. The interview is only worth the half hour if the notes actually go somewhere afterwards.

Announcements and the long tail of ownership

The departing person's own team should hear the news first, directly from the manager, before any wider announcement. For a voluntary departure, agree on the wording with the employee — how much detail to share is partly their call. After the team, notify the people who interact with the person from outside: clients, vendors, and partner teams, each with an introduction to the new contact.

Then there's the quieter category of things the person owns that nobody thinks about until they break. Remove them from the on-call rotation and any approval chains where they're the approver. Transfer ownership of documents and shared folders; in Google Workspace, files owned by a deleted account can become inaccessible to everyone else, so transfer before deactivating. Reassign recurring meetings they organize, set up email forwarding, take them off distribution lists, and reassign their accounts in the CRM. Each of these is a small task, but a skipped one surfaces weeks later as a dead calendar invite or a document nobody can edit.

Voluntary departure vs. termination

Most of the checklist is the same in both cases, but the timing and the order of the steps change.

With a voluntary departure and a notice period, you have two weeks or more for the handover, and access normally stays on until the end of the final shift so the person can keep working. The checklist runs front-loaded: knowledge transfer and successor training fill the notice period, and the access and equipment steps cluster on the last day.

With a termination, the order inverts. Access is cut at or immediately before the notification (the common security guidance for involuntary exits is no grace period), and equipment is collected the same day or by courier. Knowledge transfer compresses to whatever can be reconstructed from documents and the team's memory, which is a good argument for keeping handover documentation current before anyone is leaving. One sequencing detail matters in both cases: transfer ownership of documents and accounts before deactivating, because deactivation can orphan content in ways that are tedious to undo.

A sample employee offboarding checklist

Here's a concrete employee offboarding checklist for a voluntary departure with two weeks' notice, grouped by timeline. Owners in this example: Priya is the manager, Dave is in HR, Maya is in IT, and Sam runs payroll. Adjust the names and the split to your own org; the point is that every step has exactly one owner.

Running the checklist instead of remembering it

The steps above belong to four different functions, none of which talks to the others day to day, and departures arrive irregularly enough that each one gets run partly from memory. The Beyond Identity numbers above are what that looks like in aggregate: a process everyone agrees matters, executed inconsistently because no one person sees the whole list. A reusable checklist with an owner per step is the standard fix for processes like this: cross-functional, repeated, but not frequent enough for anyone to have it memorized.

There are a few places that checklist can live, and the main difference between them is follow-up. An HR platform with offboarding workflows works well if you already have one, though IT and the manager may not live in it. A shared doc or spreadsheet holds the list but reminds nobody. Slack Lists can hold it where the team already is; this guide to Slack Lists and checklists covers what they do well and where they stop. You can also set a Slack reminder per step, but reminders are personal: nobody else can see which steps are done, and nothing follows up if a reminder is dismissed.

Chaser handles this case directly: you build the offboarding checklist once as a reusable template in Slack, with an owner and a deadline on every step, and trigger it with one command when someone hands in their notice. Each step becomes a tracked task, so Maya gets hers and Dave gets his, and Chaser follows up with each owner automatically until their step is done, with the status of every step visible without leaving Slack. This guide to Chaser templates shows the setup. The same pattern covers any process that's cross-functional and recurring but irregular; planning a conference has the same shape.

Final thoughts

Offboarding runs well when it's treated as routine: a written checklist, one owner per step, deadlines pinned to the departure date, and a final audit after the person is gone. The manager, HR, and IT usually coordinate the departure in Slack anyway, which makes it a sensible place for the checklist to live. It also makes Slack the last account a departing employee keeps, since the coordination itself happens there, so the closing item on the list can literally be deactivating their Slack account, checked off by IT once everything above it is done.

You can try Chaser for free and see how it fits the way your team already works in Slack. Get started and add Chaser to Slack, for free.