Published October 12, 2026
Published October 12, 2026
Start with systems and responsibilities
Offboarding is not only an account checklist. It is a transfer of work, information, relationships, and authority. Inventory email, calendars, password vaults, project systems, finance tools, vendor portals, shared drives, automation accounts, devices, and recovery methods alongside the responsibilities they support.
Classify access as individual, shared, delegated, or service-based. Shared credentials and automations need special handling because disabling one identity may not remove the actual path.
Set timing by risk
Coordinate the end of access with the transition plan and applicable policy. Immediate removal may be required for an involuntary separation or security concern. A planned transition may allow staged handoff, but continuing access should have a named purpose and end time.
Do not announce timing broadly before security and people owners agree. The offboarding coordinator should work from an approved schedule rather than improvise based on convenience.
Transfer ownership before deletion
Reassign calendars, files, forms, automations, dashboards, distribution lists, and vendor contacts. Confirm that the successor can open and administer them. Copying a file is not enough if the departing account still owns the workflow or recovery channel.
Identify pending approvals and external commitments. Preserve the context needed to complete them without retaining unrelated personal information.
Rotate shared secrets
Remove vault membership, rotate credentials the assistant knew or could export, and review API keys, backup codes, device sessions, and recovery addresses. Where possible, replace shared passwords with individual roles.
Record who performed each action and the system evidence. Sensitive secrets should never be pasted into the offboarding tracker.
Preserve appropriate records
Follow approved retention, privacy, legal, and contractual requirements. Preserve business records needed for continuity while restricting access to personnel or confidential material. Do not create an uncontrolled archive “just in case.”
If mailbox or file retention is required, document the custodian, scope, duration, and access path. Redirect new work to a monitored owner instead of leaving it in an inactive account.
Communicate the transition
Tell internal teams and relevant external contacts who now owns active work. Keep the message factual and proportionate. The assistant’s departure does not authorize sharing personnel details.
Update contact pages, meeting invitations, routing rules, and automated signatures. A technical account closure can still fail operationally when requests continue to point at the old owner.
Verify after the cutoff
Test that sign-in, sessions, forwarding, delegated access, and recovery paths behave as intended. Confirm that business-critical automations still run under an approved service or owner account.
Review the checklist for gaps exposed by the transition. A good offboarding process protects information and relationships while ensuring that legitimate work does not vanish with one user identity.
This guide was published on October 12, 2026. For adjacent workflows, explore the Delegation Assistant blog or review the deeper evidence in Research.