Operations
An offboarding checklist that actually removes access
Disabling someone's email does not remove their paid seats or every login. A checklist for the leaver's last day, built from the software register rather than a manager's memory.
- Published
- 3 Nov 2026
- Read time
- 7 min
- Topic
- Operations
Most offboarding checklists are written by HR and IT together, and most of them say the same thing: collect the laptop, disable the email, remove from groups. That handles the tools behind single sign-on. It does not handle the tools people signed up for with a password, the seats that stay paid after the account is disabled, or the workspaces the leaver owns.
Why disabling email is not enough
- A disabled account can still hold a paid seat. Many tools keep billing for a suspended user until the seat itself is removed or the licence is unassigned.
- Password logins survive. Tools signed up for directly, outside SSO, keep working with the leaver's password until someone removes them.
- Ownership blocks removal. If the leaver owns a workspace, a project or the billing account, removing them may be blocked, or may take company files with them.
- Shared logins. A team password the leaver knew should be changed.
Start from the register, not from memory
The weak point in most offboarding is the question "what did this person use?" Asking their manager produces a partial list. The better source is the software register, crossed with each tool's user list. Every tool where the leaver holds a seat goes on their offboarding list.
The checklist
Before the last day
- Pull the leaver's tool list: every tool in the register where they hold a seat, are an admin, or own billing.
- Transfer ownership of workspaces, projects, shared files and billing to a named colleague.
- Decide, per seat: remove, or reassign to a named person who needs it.
- Note any client-facing tools where the leaver is the contact, and tell the client who replaces them.
On the last day
- Suspend the account in Google Workspace or Microsoft 365, and in Okta if you use it.
- Remove or reassign every seat on the list, in each tool's admin panel.
- Remove the leaver from tools outside SSO and change any shared passwords they knew.
- Remove the leaver as an approver on any purchase, payment or card workflow.
- Log who removed each seat, and when.
Thirty days later
- Check the next statement: did each removed seat actually drop off the bill?
- Delete or archive the suspended account according to your retention policy.
Worked example
A designer at Neelgiri Labs, a fictional company, left on 31 October. The register showed seats in seven tools. Names and prices are invented.
| Tool (fictional) | Behind SSO | Role | Action | Annual seat cost |
|---|---|---|---|---|
| Framewell | Yes | Editor | Reassigned to new hire | ₹15,000 |
| Canvasly | No | Member | Removed | ₹9,600 |
| Clipnote | No | Member | Removed | ₹6,000 |
| Pagenest | Yes | Workspace owner | Ownership moved, then removed | ₹4,800 |
| Trackwise | Yes | Member | Removed | ₹7,200 |
| Huddlecast | Yes | Host licence | Removed | ₹12,000 |
| Promptly | No | Member, own billing | Moved to company billing, then cancelled | ₹19,200 |
Three of the seven tools were outside single sign-on, so suspending the Google account would not have touched them. Without the sweep, the six removed seats, ₹58,800 a year at these prices, would have kept renewing for someone who had left.
Employee data, kept small
Building a leaver's tool list needs only the seat assignment and last sign-in date per tool. Under the DPDP Act, 2023, the employer is the data fiduciary for this data, and employment purposes are a listed legitimate use under Section 7. This is general information, not legal advice; your counsel can confirm how it applies.
Make it routine
The offboarding access checklist template has this list ready to copy. Ayush Agro Foods' Offboarding sweep builds the leaver's tool list from the register and sign-in data, sends each tool's owner the seat to remove or reassign, logs the confirmation, and checks the next statement. For companies with frequent exits, the IT services and agencies page shows how it runs at volume.
Next post
Who should own a tool? A simple model for 100-person companies
Every software tool needs one named person who decides whether it renews. A short model for assigning owners in a growing company, with what the owner does and does not do.
Read nextOwners, offboarding and the forex line, handled.
Every tool with a named owner, every leaver's seats swept, and the INR debited shown next to the vendor price.
- Read-only access
- Data hosted in India
- Priced in rupees
- 14-day trial on your data