Go through connections, shares and keys on the day someone leaves or moves teams, while they are still there, so nothing stays connected after they are gone.
On the day a member leaves or changes roles. Do it on their screen, together with them.
Before you start
Time with the person, whoever takes over, and an admin. The list from last time, if you have one.
Steps
Disconnect: remove the connectors (mail, calendar, storage and so on) connected with their account.
Review shares: move folders, share links and co-edited documents they own to whoever takes over.
Rotate keys: replace shared API keys and passwords that they know.
Hand over work: move owners of recurring work and scheduled tasks to the next person, and keep the result as a list.
Ask your AI
Make an offboarding checklist for [name] with four columns: connections, shares, keys, handover. If there is a list from last time, use the same format. We will fill it in together with [name].
✓ Done when
Every connection on their account has been removed.
Where shares, keys and ownership went is kept in the list.
House rules
Do it on the day, on their screen, while they are there. Only they know everything they connected.
Day to day, note every connection (who, what, when) somewhere the team can see.
This playbook publishes steps the CLUBS team actually uses. Under CC BY 4.0, you may adapt and redistribute it with attribution. If you change it, please say so.
This playbook is one example, provided for general information. We do not guarantee that it is accurate or up to date. Please check the content before you use it, and use it at your own risk.See the Terms of Service (Japanese) for details.