Free template
Free employee offboarding checklist (Excel)
When someone leaves, the risk isn’t the goodbye — it’s the account nobody remembered to disable and the SaaS licence still billing three months later. This checklist gives IT a per-system, per-asset list to work through on someone’s last day, with columns to record who did what and when. It’s a free .xlsx — no email, no sign-up.
Download the checklist
Free · .xlsx · no email required
What’s in the checklist
An instructions tab plus an offboarding tab with a row per action, grouped by category so nothing is missed:
- A Category column — Identity, Application access, Devices & assets, Data & handover — grouping the work.
- A Task / System column so you can add one row per SaaS app or internal system the person had access to.
- Action and Owner columns — what needs to happen (disable, revoke, transfer, collect) and who’s responsible.
- A Status dropdown (Not started / In progress / Done / N/A) and a Completed Date column.
- A Notes column for ticket links, licence-reclaim confirmations, and re-assignment details.
How to use it
When a departure is confirmed, copy the offboarding tab into a sheet named for the person and their last day. Start with identity — disable the primary directory account and revoke SSO — then add a row for every application and internal system they had access to and mark each one revoked. Collect devices and physical assets, reassign any owned data, files, or governance roles, and record the owner and completion date on each line. Keep the finished sheet as your record that access was removed.
Where a spreadsheet falls short
A checklist is only as good as the list of systems you remembered to add — if you don’t already know every place the person had access, a blank spreadsheet won’t tell you. It also can’t prove a revocation actually happened, won’t escalate a step left half-done past the last day, and won’t route the departed person’s ownership of a system or approval to someone new. Useboards pulls the leaver’s actual access from your catalog, turns each item into a tracked revocation, routes replacement tickets to the right owners, and gates completion until the work is genuinely done.
Frequently asked questions
Is this offboarding checklist really free?
Yes — download the Excel file with no email or sign-up. It’s made by Useboards; if manual offboarding is leaving gaps, our product automates the revocations and hand-offs.
What should be on a security offboarding checklist?
At minimum: disable the identity/directory account and SSO, revoke access to every application and internal system the person used, reclaim or reassign licences, collect devices and physical assets, and hand over owned data and any governance roles. This template covers each of those as its own category.
How is this different from Useboards offboarding?
The checklist relies on you remembering every system and manually confirming each step. Useboards starts from the person’s actual access in your catalog, turns each item into a tracked revocation, routes replacement tickets to the right system owners, and won’t mark the offboarding complete until the last day has passed and every item is done.
Related
Stop offboarding from memory
Pull the leaver’s real access, track every revocation, route the hand-offs — automatically.