Employee Offboarding Checklist
The access revoked on the day, the shared credentials nobody rotates, final pay including untaken holiday, and the handover asked for while they still care.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Employee Offboarding Checklist?
Offboarding is the mirror of onboarding and is done far worse, because nobody owns it. The person leaving has stopped caring, their manager is covering the gap, and IT was told on the last afternoon. The result is former employees with live access and knowledge that walked out of the building undocumented.
This list separates the three things that actually matter: access, which is a security matter with a hard deadline; knowledge, which is only capturable while they are still here; and pay, which has legal requirements. Everything else is courtesy.
- Separates access, knowledge and pay, which have different deadlines and owners
- Treats shared credentials and enrolled authenticators as separate from account revocation
- Covers external ownership of domains and accounts, which fails silently much later
- Includes the one-week access re-audit, because one system is always missed
- Editable and exportable as PDF, CSV, Markdown or a Google Form
Updated
How to use the Employee Offboarding Checklist
- Acknowledge the notice in writing, with the leaving date and notice terms.
- Ask for the handover in week one of the notice period, not the last afternoon.
- Build the full access inventory before the last day, including shared credentials.
- Revoke access at the agreed time, rotate shared credentials, and transfer external ownership.
- Settle final pay including untaken holiday, then re-audit access a week later.
Worked examples
Resignation just received
Input
First section
Output
Written acknowledgement, handover requested, work reassigned
Knowledge capture only works while they still care.
Last day today
Input
Essentials only
Output
Access revoked, credentials rotated, kit returned, final pay calculated
The items with a same-day deadline.
A week later
Input
Final section
Output
Access re-audited, handover tested, exit feedback acted on
There is always one system nobody remembered.
Background and insight
Access is the part with real consequences. Revoking the main account is the easy half; the half that gets missed is shared credentials they knew, personal access tokens, an authenticator still enrolled on their phone, and accounts or domains registered in their name. A shared password is access that disabling an account does not remove, which is why rotation is a separate item from revocation.
The item that bites years later is external ownership. A domain, a cloud account or a social profile registered under a personal email keeps working until a renewal fails on a card that was cancelled, and by then nobody knows how to recover it.
Knowledge capture has a timing problem. Asked in week one of a notice period, people write a genuinely useful handover; asked on the final afternoon, they write a list of folder names. The valuable content is never the documented part: it is which supplier contact actually answers, which scheduled job is load-bearing, and which customer has to be handled personally.
On pay, accrued and untaken holiday is generally payable by law on termination, and deductions usually require a contractual basis or written agreement rather than a manager's decision. Most countries also require a specific leaver document from payroll, often with its own deadline. Benefits need an explicit end date communicated to the person, because health cover and life assurance stopping silently is how a former employee discovers it at the worst moment.
Finally the exit conversation, which is worth more than it is given credit for. Someone leaving has no reason to be diplomatic, which makes it the most honest feedback an organisation will get about itself, and several people leaving for the same reason is the cheapest data available.
Common use cases
Small businesses without HR
The statutory pay items and the security items, in plain terms.
A senior or long-tenured leaver
Where undocumented knowledge and external account ownership are the real risk.
Security and IT teams
A complete access inventory, including the credentials revocation misses.
Writing a repeatable process
A starting point to adapt, so offboarding stops being improvised each time.
Tips and limitations
- Ask for the handover in week one of notice. On the last afternoon you get folder names.
- Rotate shared passwords. Disabling an account does not remove access someone memorised.
- Check for domains and accounts registered in their name before the card is cancelled.
- Have the exit conversation with someone who is not their manager.
- Re-audit access a week later. The distance is what makes you find the missed system.
Sources and further reading
- Notice periods, Acas. Notice, garden leave and leaving employment
- Holiday entitlement, UK Government. Accrued leave and payment on termination
- Termination, US Department of Labor. US final pay and benefit continuation rules
Frequently asked questions
What should be done when an employee leaves?
Acknowledge the notice in writing, get a handover written early in the notice period, build an access inventory, revoke access and rotate shared credentials on the agreed day, settle final pay including untaken holiday, and re-audit access a week later.
When should access be revoked?
At the agreed time on the last day, not days afterwards. Revoking the main account is only half of it: shared credentials they knew must be rotated, personal tokens removed, and their devices unenrolled from any shared two-factor setup.
Does untaken holiday have to be paid out?
Accrued and untaken statutory leave is generally payable on termination, and deductions from final pay usually need a contractual basis or written agreement rather than a manager's decision. Check your own jurisdiction, as the detail varies.
How do I capture what a leaver knew?
Ask in week one of the notice period and sit with them to record the undocumented things: which supplier contact answers, which job is load-bearing, which customer needs personal handling. Then have their successor try the handover and fix what is wrong.
Is an exit interview worth doing?
Yes, with someone who is not their line manager. A leaver has no reason to be diplomatic, which makes it the most honest feedback you will get, and several people citing the same reason is data worth acting on.
Is there an in-depth guide to the Employee Offboarding Checklist?
Yes. “Why Checklists Work, and How to Use One Properly” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.