Employee Offboarding Checklist: Automate Access Removal
When someone joins a company, everybody moves fast: a laptop is ordered, an email account is created, a CRM seat is assigned, and the new colleague is added to a dozen shared folders. When someone leaves, the energy is gone. The farewell message goes out, the laptop comes back eventually, and the accounts are switched off “when someone has a minute”. That gap between the last working day and the moment every access really disappears is one of the most common and most avoidable security risks in small and mid-sized businesses.
This guide gives you a practical employee offboarding checklist focused on IT access, multi-factor authentication (MFA), data and archives, and shows which steps you can automate so that offboarding stops depending on someone’s memory.
Why offboarding is an IT problem, not only an HR one
HR owns the contract, the final payroll and the exit conversation. But the real exposure sits in systems that HR usually does not manage:
- Identity accounts – Google Workspace or Microsoft 365, plus every app connected through “Sign in with Google/Microsoft”.
- Standalone SaaS logins – tools that were signed up for with a work email and a separate password: design tools, survey tools, file-transfer services, AI assistants.
- Shared credentials – a common password for the router, the PBX admin panel, a supplier portal or the company’s social media accounts.
- MFA factors – an authenticator app on a personal phone, a hardware key, a phone number used for SMS codes or account recovery.
- Data held outside central systems – files in a personal cloud folder, exports on a laptop, contacts in a private phone.
An account that stays active after someone leaves is a door nobody watches. Even when the former employee has no bad intentions, an unused but valid account is an attractive target: nobody will notice a strange login, and nobody will react to a password-reset email.
The employee offboarding checklist
Use the checklist below as a starting point and adapt it to your stack. The order matters: first protect access, then preserve data, then clean up.
Before the last day
- Confirm the exit date and time in one place that IT can see (an HR system, a ticket or a shared form) – not only in an email thread.
- List every system the person uses. If you keep an access register, this takes minutes. If you don’t, start one now (see below).
- Identify owned assets: shared drives, calendars, mailing lists, automation workflows, API keys, domains or ad accounts registered under the person’s name.
- Plan the handover: who takes over open deals, client conversations, recurring tasks and scheduled reports.
On the last day
- Suspend (don’t delete) the main identity account at the agreed time. Suspension immediately blocks sign-in and connected single sign-on apps while keeping the data intact.
- Sign out all active sessions and revoke app passwords, OAuth tokens and mobile device access from the admin console.
- Remove or reset MFA factors linked to the account, and remove the person’s phone number or personal email from any recovery options on company accounts.
- Disable standalone SaaS accounts that are not covered by single sign-on.
- Rotate shared passwords the person knew – Wi-Fi, PBX admin, supplier portals, social media. Update them in your password manager so the rest of the team is not locked out.
- Remove the extension or forward the number on your phone system, so client calls to the former employee go to a colleague or a queue instead of a dead voicemail box.
- Collect hardware – laptop, phone, security keys, access cards – and mark it as returned.
After the last day
- Set up email handling: an auto-reply that names the new contact, mail forwarding to a manager for a limited period, or delegation of the mailbox.
- Transfer file ownership of documents and shared drives to the new owner before deleting anything.
- Archive what you must keep – mailbox and files – according to your retention policy, then release the paid licence.
- Wipe or re-image returned devices before they are reassigned.
- Close the ticket with evidence: who did what and when. This record is valuable if you ever need to show how access was handled.
MFA: the step most companies get wrong
Multi-factor authentication protects accounts while a person works with you. During offboarding it can work against you in two ways.
First, the second factor often lives on a personal device. If a shared account (for example, the admin login to a hosting panel) uses an authenticator app on the departing employee’s own phone, the company can lose access to its own system the day that person leaves. The fix is a policy: shared and admin accounts use factors that belong to the company – a password manager with shared TOTP, or hardware keys registered to at least two people.
Second, recovery options outlive the job. A personal phone number or private email set as a recovery method on a company account means the former employee could, in theory, still reset the password. Review recovery settings during offboarding, not only the password.
Data, archives and GDPR
Offboarding is also a data-protection moment. Under the GDPR, personal data should be kept no longer than necessary for its purpose (the “storage limitation” principle) and protected with appropriate security measures. For offboarding this translates into a few concrete decisions:
- Decide in advance how long you keep a former employee’s mailbox and files, and why. Write it down in a short retention policy rather than deciding case by case.
- Separate business data from personal data. Client correspondence belongs to the company; the employee’s private messages do not, and they should not be reused.
- Keep archives where access is controlled – a restricted archive or backup location, not a shared folder everyone can open. If you automate backups, our guide on automating S3 and database backups with Python shows the building blocks.
- Delete on schedule. When the retention period ends, delete the archive and note that you did it.
This is general information, not legal advice. For specific retention periods (for example accounting or employment records), check local law or ask your legal adviser.
What you can automate
The checklist above is long, but much of it is mechanical. Most modern business tools expose APIs, which means a large part of offboarding can be triggered by a single event: the exit date entered in your HR system or a form.
1. Start from one trigger
Pick one source of truth – an HR tool, a CRM record, or even a simple internal form – where the manager enters the leaving date. An automation listens for that change and creates the offboarding run. If you already automated the opposite direction, the same structure works: see our guide on automating employee onboarding workflows with Python.
2. Suspend accounts through APIs
Google Workspace and Microsoft 365 both offer admin APIs to suspend users, sign out sessions and transfer data ownership. Many SaaS tools offer user-deactivation endpoints or SCIM provisioning. A script or workflow can run these steps at the exact time agreed, instead of “later today”.
3. Create tasks for what can’t be automated
Some steps need a human: collecting a laptop, rotating a router password, checking a supplier portal without an API. The automation should create those tasks with owners and deadlines in your task or ticket system, so nothing is forgotten.
4. Update the phone system and CRM
Reassign the person’s open CRM records and leads to a named colleague, and change call routing for their extension. If missed calls are part of the risk, it is worth combining this with a missed call text back flow that logs every call in the CRM.
5. Produce an audit log
Every automated action – account suspended, tokens revoked, licence released – is written to a log with a timestamp. That log is your proof that offboarding was completed, and it makes the next access review much faster.
Start with an access register
Automation only works when you know what to switch off. If you don’t have one yet, create an access register: a simple table with one row per system, listing who has access, what role they have, how they sign in (SSO or separate password), where MFA is configured and who is the owner on the company side. Specialised firms, such as law offices, often add case-management and e-signature systems to this list; our article on law firm workflow automation covers that context.
Keep the register updated during onboarding – every new account is added there – and offboarding becomes a matter of going down the list.
Common mistakes to avoid
- Deleting the account on day one. Deletion can remove files and mail that the business still needs. Suspend first, transfer, archive, then delete.
- Forgetting shared credentials. Changing the person’s own password does nothing for the shared admin login they also knew.
- Leaving forwarding rules in place. Check the departing user’s mailbox for rules that forward mail to an external address.
- No owner for the process. If HR thinks IT handles it and IT waits for HR, nothing happens. Name one owner.
FAQ
Should we delete or suspend a former employee’s account?
Suspend first. Suspension blocks sign-in immediately while keeping mail and files available for handover. Delete only after data ownership has been transferred and anything you must keep has been archived according to your retention policy.
How quickly should access be removed?
Ideally at the moment employment ends – agreed in advance with HR and the manager. Automating the suspension with a scheduled trigger removes the delay that usually comes from waiting for someone to do it manually.
What about MFA on shared accounts?
Shared and admin accounts should not rely on a factor tied to one person’s private phone. Use company-owned factors, such as a shared password manager or hardware keys registered to at least two people, and review recovery options during every offboarding.
Can a small business automate offboarding without an HR system?
Yes. A simple internal form or a field in your CRM can act as the trigger. From there, scripts or workflow tools can call the admin APIs of your email, file storage and SaaS tools, and create tasks for the manual steps.
Next step
Offboarding touches identity, phone systems, CRM, file storage and data protection at the same time, which is exactly why it is so often left half done. At TOOL1 we build automations and integrations that connect these systems – from a single offboarding trigger to suspended accounts, reassigned leads, updated call routing and a clean audit log. If you want to review your current access setup or automate the process, get in touch with our team.















Leave a Reply
Want to join the discussion?Feel free to contribute!
Join the Discussion
To prevent spam and maintain a high-quality community, please log in or register to post a comment.