An employee offboarding process should do more than disable an account. Use this reusable IT offboarding checklist to remove cloud access, preserve business data, recover assets, transfer ownership, and document the handoff without interrupting the team.
Overview
Offboarding is the controlled transition from active employment or contract work to no access, no unresolved ownership, and a clear record of what happened. It applies to permanent departures, contractor end dates, role changes, internal transfers, and situations where access must be removed immediately.
The exact sequence depends on your identity provider, device-management system, SaaS tools, employment process, and security requirements. Treat this checklist as an operating framework rather than a substitute for your organization’s legal, HR, or incident-response procedures. Coordinate the timing of access changes with the authorized HR or management contact, especially when the departure is sensitive.
Before starting, create a ticket or offboarding record with the person’s name, role, manager, departure type, effective time, approved owner, and required completion date. Record each action as it is completed. A simple audit trail makes it easier to confirm that access was removed and that business-critical work was not abandoned.
Core offboarding checklist
- Confirm the departure date, effective time, and authorized request.
- Identify the employee’s identity-provider account, groups, roles, aliases, and authentication methods.
- List SaaS applications, administrative consoles, shared workspaces, repositories, and automation accounts the person could access.
- Transfer ownership of files, folders, projects, calendars, forms, dashboards, workflows, and integrations.
- Revoke sessions, tokens, API keys, personal access tokens, app passwords, and other non-password credentials where applicable.
- Recover company devices, security keys, badges, removable media, and other assigned equipment.
- Preserve required business records according to your retention and legal guidance.
- Reclaim or reassign licenses and paid seats after confirming that access and data transitions are complete.
- Update documentation, escalation contacts, team rosters, and the offboarding record.
- Run a final access review after the changes have propagated across connected systems.
Checklist by scenario
Standard planned departure
For a planned departure, use the notice period to map dependencies without granting unnecessary additional access. Ask the manager to identify active projects, recurring meetings, customer or vendor relationships, approval responsibilities, scheduled jobs, and documents that only the departing person can maintain.
- Export or transfer ownership of work in the approved systems.
- Assign a named owner for open requests, tickets, approvals, and scheduled tasks.
- Review mailbox, calendar, and collaboration-space handling with HR and the manager.
- Schedule account suspension or access removal for the approved effective time.
- Arrange device return, inspection, and secure data handling.
Immediate or sensitive departure
When access must be removed immediately, prioritize containment and preserve evidence. Limit the action plan to authorized administrators and the designated HR, legal, or security contacts. Do not rely on a later manual cleanup if the person can still reach sensitive systems.
- Disable or suspend the central identity account at the approved time.
- Revoke active sessions and authentication factors where the platform supports it.
- Remove privileged roles and access to financial, production, customer, code, and administrative systems.
- Rotate shared credentials, secrets, tokens, and keys that may have been known or accessible.
- Secure company devices and preserve relevant records according to internal procedure.
- Check for unusual forwarding rules, newly created tokens, external sharing, or automation changes.
Contractor or temporary worker end date
Contractors often use a smaller set of systems, but their access may include project workspaces, client environments, repositories, or shared credentials. Compare the end date against the original access request rather than assuming that a standard employee workflow covers every account.
- Confirm the contract scope, sponsor, end date, and any approved extension.
- Remove direct and group-based access to client, project, and internal systems.
- Transfer deliverables, documentation, credentials, and unfinished work to the sponsor.
- Recover or securely delete local copies of company data according to policy.
- Review guest accounts, external sharing links, and collaboration invitations.
Internal transfer or role change
An internal move is not a complete termination, but it still requires an access review. Remove permissions that belonged only to the previous role and grant new access through the current role or group structure.
- Compare old and new role permissions.
- Remove former team groups, project memberships, and approval rights.
- Transfer ownership of the previous team’s files, workflows, and recurring tasks.
- Confirm that required access for the new role is approved and documented.
Role-based handoff matrix
| Owner | Primary responsibilities | Evidence to record |
|---|---|---|
| HR or authorized manager | Confirms departure type, timing, communication, and approved exceptions. | Approved request, effective time, and named contacts. |
| IT or identity administrator | Disables identity access, removes groups, revokes sessions, and reviews authentication methods. | Timestamped access changes and exception notes. |
| SaaS or application owners | Transfers ownership, removes app access, reclaims licenses, and checks integrations. | Application checklist and new owners. |
| Manager or project owner | Identifies business dependencies and accepts work, files, and open responsibilities. | Handoff confirmation and unresolved items. |
| Security or compliance contact | Guides sensitive departures, retention, investigations, and credential rotation. | Review decision and required follow-up. |
What to double-check
Central login removal is important, but it does not always cover every path into a cloud environment. Review access by category so that overlooked accounts do not remain active.
Identity and authentication
- Check the primary account, aliases, directory groups, delegated access, administrator roles, and recovery methods.
- Review multifactor authentication devices, backup codes, passkeys, security keys, and remembered sessions.
- Revoke OAuth grants, personal access tokens, command-line credentials, and API keys where relevant.
SaaS accounts and collaboration spaces
- Search the organization’s application inventory and billing records for assigned accounts.
- Review document ownership, shared drives, project boards, repositories, forms, dashboards, and knowledge bases.
- Check guest invitations and external sharing created by the departing person.
- Confirm that automated workflows, scheduled reports, webhooks, and integrations have a new owner.
If your inventory is incomplete, use this process as a prompt for a broader SaaS stack audit. A reliable application register reduces the chance that an offboarding request depends on personal memory.
Email, files, and data ownership
- Decide whether the mailbox is suspended, retained, delegated, archived, or handled through another approved method.
- Review forwarding rules, filters, delegates, shared inbox membership, and calendar delegation.
- Transfer business-critical files and confirm that permissions remain appropriate after the transfer.
- Do not delete data simply to close the account; follow the organization’s retention and preservation instructions.
Devices and physical assets
- Record the device serial number, condition, return status, and assigned accessories.
- Revoke device certificates or management enrollment when appropriate.
- Confirm that remote-lock, wipe, or recovery actions are authorized before using them.
- Track badges, keys, security tokens, storage media, and other physical assets separately from SaaS access.
For repeatable handoffs, document the process in a shared format. The workflow documentation template can help teams record owners, triggers, steps, exceptions, and completion evidence.
Common mistakes
- Disabling only the email account. Direct logins, local credentials, tokens, and guest access may remain elsewhere.
- Deleting before transferring ownership. Removal can make files, workflows, or project history harder to recover.
- Ignoring shared credentials. Rotate credentials that were shared or stored in places the departing person could access.
- Leaving forwarding rules unchecked. Mail routing and delegates should be reviewed as deliberately as access permissions.
- Using one checklist for every scenario. A planned departure, emergency removal, contractor end date, and internal transfer have different timing and evidence needs.
- Failing to assign the next owner. A transferred file is not a completed handoff if nobody is responsible for its next action.
- Closing the ticket without verification. Ask application owners or run a post-change review to confirm that access, ownership, and licenses match the intended result.
When to revisit
Review this employee offboarding checklist before seasonal planning cycles, after major changes to your identity provider or device-management process, and whenever the team adopts or retires a SaaS application. Revisit it after an internal audit, a security incident, a change in retention requirements, or a recurring handoff failure.
At least periodically, test the checklist with a sample user account or a tabletop exercise. Confirm that the application inventory is current, each critical system has an owner, and administrators know how to revoke sessions, transfer data, and rotate credentials. Update screenshots, platform-specific steps, and escalation contacts when workflows change; keep the core control objectives stable.
For a practical next departure, copy the core checklist into your ticketing or workflow system, add the systems unique to your organization, assign one owner per task, and require a final verification before closure. Pair it with a documented request-and-approval process such as the remote team workflow toolkit so offboarding remains a controlled team workflow rather than an informal series of messages.