Skip to content

Blog

Employee offboarding checklist: every step, in order

An employee offboarding checklist for small businesses, in order: accounts, devices, data, shared passwords and the tools nobody remembers to check.

· 10 min read

An employee offboarding checklist has three parts: what to do before the last day (list everything they have access to, plan the handover), what to do on the last day (remove access everywhere, collect devices, change shared passwords), and what to do after (move their data, cancel their seats, check nothing was missed). Every step is below, in order, one paragraph each, so you can work down it.

The hard part is not any single step. It is knowing every tool the person had access to. Get that list right and the rest is routine.

Why offboarding goes wrong in small companies

Large companies have an IT team and a ticket. Small companies have whoever set the tools up, a Google Workspace admin console and a vague memory of who was invited to what.

So the usual failures are not dramatic. Someone is suspended in Google Workspace and everyone assumes that is the end of it. Nobody remembers the analytics tool they were added to for one project. The contractor they invited to the design tool is still there. The shared password for the social media account never changes. None of it is malicious, and all of it is avoidable with a list.

There's a second failure, and it's about ownership rather than memory. The manager assumes ops knows, ops assumes whoever runs the tools knows, and the person who runs the tools finds out on the last day. If that sounds familiar, read the offboarding process alongside this checklist: it assigns each step below to one named person.

Before the last day

Start as soon as you know someone is leaving. For a normal resignation that gives you days or weeks; for a dismissal, see the section further down.

List every tool and account they have. Go through every tool your company uses, not just the ones you think they used, and note what they have in each: a member account, an admin role, a guest invite, an API token. Start with their Google Workspace or Microsoft 365 account, then chat, email lists and shared inboxes. Then go through code, design, docs, CRM, support, finance and analytics tools, and cloud consoles such as AWS, Google Cloud or Azure, along with anything else with production access. Don't skip social media and marketing accounts, especially shared ones. Finally, look for accounts under personal email addresses in your tools; contractors often have these.

If you do not have a current list of who has access to what, this step takes the longest. It is also the step that pays off forever, because next time the list already exists.

Find what only they can do. Look for admin roles, ownership of shared files, billing contacts, domain registrations, and the integration someone connected with their personal API key. Transfer each of these to someone who is staying before you remove the person, or you may lock yourself out of your own tool. Some tools make this a hard stop: Slack, for example, won't let anyone deactivate its Primary Owner until the role is transferred. In Google Workspace, if the leaver is your only super admin, make someone else a super admin first.

Plan the handover. Documents, open work, customer relationships, recurring meetings. The manager decides who gets each piece; whoever runs the tools carries it out. Ask the leaver to write down what only they know, in a shared document rather than their own drive.

Schedule the access removal. Pick the time: normally the end of their last working day. Put it in a calendar, with the name of the person who will do it. Offboarding that depends on someone remembering on a busy Friday is offboarding that happens on Tuesday.

On the last day

Accounts

Suspend their main account first. In Google Workspace, suspend the user rather than deleting them; you will want their data. Per Google's suspension page, as we read it on 27 October 2026, suspending keeps their email, documents and calendars, blocks new email and calendar invitations, and leaves people they shared documents with able to keep working on them. Suspension also resets their sign-in cookies, which signs them out of Google on browsers and phones. In Microsoft 365, block sign-in and revoke sessions.

Close the side doors in Google. Google's own list for when an employee leaves goes further than suspension: remove their recovery email and phone, change the password, revoke OAuth tokens and authorized apps, and revoke security keys and app passwords. Google notes that resetting sign-in cookies does not sign someone out of desktop apps such as Google Drive for desktop, which is one more reason to get the laptop back. Google Workspace offboarding has every click.

Remember what suspension doesn't do. It stops them signing in to Google, and to any tool they reach through "Sign in with Google". It does not remove them from tools that have their own login, and it does not end sessions they already have open in those tools.

Remove them from every other tool. Work through the list you made before the last day. In each tool, deactivate or remove the member. Where a tool offers "deactivate" rather than "delete", deactivation usually keeps their history and frees the seat, which is what you want. Slack is a good example: deactivating removes the person from all channels and signs them out, and their messages stay (how to remove someone from Slack has the steps for each plan). Removing someone from each tool's member list has a name, deprovisioning, and it is the step most small companies do from memory.

Revoke their keys and tokens. Personal API tokens, SSH keys and cloud access keys keep working after a login is gone. Revoke the ones they created, and replace any that production depends on with one owned by someone who is staying. The IT offboarding checklist goes through where these hide.

Devices and passwords

Collect devices and revoke device access. Laptop, phone, security keys, door badges. If you use device management, lock or wipe company devices once data is safe; Google's checklist offers wiping the whole device or only company data. If they used a personal device, remove company accounts from it.

Change shared passwords. Every shared login they knew needs a new password: social accounts, the router, the shared tool account you know you should not have. A password manager makes this a list rather than a hunt, and our post on shared accounts explains how to have fewer of them next time.

After they leave

Move their data. Transfer Google Drive and Calendar ownership to their manager or a successor, set up email forwarding or an auto-reply, and export anything you are required to keep. Google's Drive transfer page has three conditions worth knowing before you start: the new owner must be active, not suspended; items in the leaver's trash are not transferred; and a transfer that runs longer than 36 hours stops and has to be started again.

Cancel their seats. Removing a member does not always reduce your bill. Google says suspended accounts are charged at the same rate as active ones, and on an Annual plan, deleting an account doesn't reduce your number of licenses; you reassign the license to the next hire. Slack, by contrast, credits a deactivated member's unused time under its Fair Billing Policy. Check each paid tool and lower the seat count where it does not happen automatically.

Check for stragglers. A week later, look again: search each tool's member list for their name and email, and check for accounts under personal email addresses. Anything still there is an orphaned account: a login nobody owns, which nobody will notice until it matters.

Delete or archive the main account. Once nothing else needs moving, delete or archive the Google account. Google keeps a deleted account restorable for 20 days, then "a deleted user's data is unrecoverable", per its deletion page. Don't rush it.

Record what you did. Write down what was removed, when and by whom. If you ever face a security questionnaire or an audit, this record is the evidence that offboarding happens.

Contractors, guests and shared accounts

Contractors leave without a last day. A contract just stops being renewed, so nobody triggers the checklist. Give every contractor an end date when you invite them, and run the same steps on that date. Contractor access management covers the rest, including contractors who use their own email address.

Guests don't show up in your directory. Guest invites in Slack, Asana, Linear and similar tools are often under outside addresses, so searching for an employee's company email won't find them. When someone leaves, ask who they invited as guests, and decide who now owns each one.

Shared accounts outlive everyone. A login used by three people can't be suspended for one of them. Change the password, move its second factor off the leaver's phone, and note who still knows it.

Dismissals: what changes

When someone is let go rather than resigning, the order changes. Prepare the access list in advance, quietly. Remove access at the time of the conversation, not after it: suspend the main account and remove admin roles first, then everything else the same day. Transfer ownership of anything critical beforehand. Everything else on the checklist still applies; it just happens faster. The employee termination checklist has the dismissal version, ordered by the damage each account could do.

How long offboarding takes

The account removals are minutes per tool. At 5 people, with one admin who set up every tool and remembers most of them, the last-day section is short if the list exists. At 50 people the tools multiply, admin rights are spread across several people, and nobody remembers who was invited to what, so the same leaver takes far longer, nearly all of it spent finding out what they had. The time goes into the inventory, not the clicks.

Remote leavers add one wait: the laptop comes back by courier, so the device steps stretch over a week or two. Offboarding employees remotely covers the courier, the remote lock and the video-call handover.

Making the next one faster

Every step above gets easier with one thing: a current list of who has access to what. Without it, the first step is an investigation. With it, offboarding is working down a page.

That list is what SmashSSO keeps for you. It reads your people from Google Workspace with read-only access and shows, in one access grid, who has an account in each of your tools and with what role, matched by email, with accounts that match nobody flagged. When someone is suspended in Google Workspace, it alerts you and shows where they still have access, and removals run from the same place: through a tool's member API where you have added a token, otherwise through an agent in your own Chrome, in tabs where you are signed in as an admin. It is not single sign-on, it does not touch devices or files, and its agent runs need your browser open and can fail when a tool changes its screens, which the FAQ explains plainly. It costs a flat fee from $199 a month, billed annually (pricing).

Whether you use it or a spreadsheet, keep the list. And if you have been thinking about SSO mainly because of offboarding, read SSO for small business: do you actually need it? first. SSO stops future logins; it does not remove anyone from anything.

More on offboarding

If you're setting up offboarding for the first time, start with the process and its variants. The offboarding process assigns each step to a person and puts it on a timeline from notice to last day. The employee termination checklist is the version for when you let someone go and access has to go in minutes. Offboarding employees remotely deals with laptops in the post and goodbyes on video, and contractor access management covers the people who leave without anyone noticing.

If you're the one with the admin passwords, read the hands-on guides next. The IT offboarding checklist is the technical companion to this page, down to SSH keys and OAuth grants. Google Workspace offboarding walks through suspending, transferring Drive and Calendar, and redirecting email, and how to remove someone from Slack does the same for the tool every leaver has.

If you want to understand why accounts get left behind, the concepts are worth ten minutes. What is deprovisioning? explains the term and the manual, SCIM and agent-driven ways to do it. Orphaned accounts describes the logins nobody owns and how to find them, and revoking access explains what ex-employees can still do with sessions, tokens and shared passwords.

And if you're tired of doing it by hand, two posts weigh the options. How to automate offboarding without an Enterprise plan looks at the routes that don't need every tool's top tier, and offboarding software sets out what to look for, and what to be suspicious of, before you buy.

FAQ

What should be on an employee offboarding checklist?
Before the last day: a list of every tool and account the person has, handover of their work and files, and a planned time for access removal. On the day: suspend their main account, remove them from every other tool, revoke their keys, collect devices and change shared passwords. Afterwards: transfer data, cancel seats, check for stragglers and record what was done.
When should you remove a departing employee's access?
At the end of their last working day for a normal departure, and at the start of the conversation for a dismissal. Schedule it in advance, with a named person, so it does not depend on someone remembering.
Does suspending someone in Google Workspace remove their access to other tools?
Only to tools they sign in to with Google. Anything with its own email and password, and anything where they already have an open session, keeps working until you remove them in that tool.
How long does offboarding take?
The account removals are minutes per tool; finding every tool the person had is what takes the time. Keeping an up-to-date list of who has access to what turns offboarding from an investigation into a checklist.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google