Offboarding SOP
A zero-loss handover process for accounts, access, client relationships and sensitive assets when someone leaves.
When a team member leaves Tenten, how to hand over accounts, access, files, client relationships and sensitive assets to the successor — zero loss, zero residue, zero downtime.
Tenten relies on a lot of SaaS, infrastructure, API keys, social accounts and client systems. If any departure isn't handed over properly, at best you lose files or break an automation; at worst, client data leaks, social assets go out of control, or billing goes haywire. This SOP standardizes offboarding. It pairs with the Security & Assets guide: one covers "how to protect while here," the other "how to hand over when leaving."
The Five Handover Roles
Every handover needs the roles below clearly assigned. In a small setup one person may wear several hats, but accountability must be written on the tracking sheet.
Proactively lists their accounts, in-flight work, client relationships and single-points-of-failure.
Confirms knowledge and relationship handover is done, approves access transfer, answers for the outcome.
Revokes accounts, rotates keys, rebinds automation credentials, reclaims delegated access.
Approves transfer of the most sensitive matters — finance (Mercury), social ownership.
The Handover Timeline
Handover doesn't start on the last day. The ideal process spans two weeks before to 30 days after departure, to avoid a last-day scramble and missed access.
The Six Most Error-Prone Areas
The six below are where Tenten is most likely to slip up and most likely to overlook. Double-check them every time.
The final sweep before closing
Even after the full process, the most-missed items: the 2FA authenticator on a personal phone, browser-saved passwords, company files in a personal drive, and recovery paths bound to a personal email. Clear each, then sign off and archive.