
When an employee leaves, your business needs to remove their access while keeping the files, messages, and customer records that others still need. This employee offboarding checklist separates those jobs so an account shutdown does not become an accidental data deletion.
We recommend one authorized coordinator, an agreed cutoff time, and a record of what was disabled, preserved, and checked. Plan these steps during the notice period when possible, with a separate route for departures that require immediate action.
What an employee offboarding checklist must cover
An employee offboarding checklist is a documented process for ending access, preserving business information, recovering equipment, and verifying completion when employment ends.
An employee exit checklist may cover broader employment matters. Here, we focus on accounts, devices, business data, and operational handoffs through three phases: before departure, at departure, and after departure. Use the same structure for contractors, temporary staff, and vendors when their access is no longer authorized.
The personnel-termination and account-management controls in National Institute of Standards and Technology guidance address disabling access, revoking credentials, recovering company property, and retaining organizational access to information. Use that guidance as a reference, not as evidence that this general checklist establishes compliance.
Keep access suspension separate from permanent deletion. Disabling sign-in restricts use of an account, but existing sessions may need separate action. Deleting an account can affect records, ownership, and recovery options. Confirm what each platform does before removing accounts or licenses.
Returning a laptop does not close cloud accounts, stop every personal-device synchronization connection, or terminate independent application sessions. Treat equipment recovery, access removal, and data preservation as separate tasks, and verify each one.
An exit interview may reveal overlooked tools or responsibilities, but it must never become a prerequisite for access removal.
Set the departure trigger, authorized owner, and cutoff time
Assign one owner with authority to coordinate the work
We recommend an office manager or designated operations lead as the authorized owner accountable for closing the checklist. Human resources (HR) or authorized management confirms the departure, the manager identifies business priorities, and information technology (IT) executes technical actions. The records or legal owner approves preservation requirements.
The departure notice should trigger a restricted-access record containing the employee identifier, approved cutoff time and time zone, affected locations, assigned roles, and escalation contact. Sensitive departure details belong only with authorized participants.
Use the checklists below to assign tasks and deadlines. Keep a separate restricted record of each task’s status, completion time, evidence, and any unresolved issue. Assign an owner and follow-up deadline to every blocked item; a request submitted is not proof of completion.
Match the timing to the departure circumstances
The departure circumstances determine the sequence, not the scope of access removal.
- Planned resignation: Begin discovery and the approved handoff during the notice period. Cut access at the authorized departure time.
- Involuntary termination: Limit planning information to authorized staff and coordinate the access cutoff with the approved notification plan.
- Immediate or unexpected departure: Initiate the approved access block promptly. Preserve records administratively and assign successors without waiting for employee participation.
Urgent access removal must not wait for a complete handoff or equipment return. Administrative preservation can continue after employee sign-in is disabled.
If the cutoff falls outside business hours, we recommend agreeing on after-hours support arrangements in advance. An escalation contact without an agreed execution arrangement is not a complete cutoff plan.
Before departure: inventory every account, device, and access route
Identify central accounts and independent applications
IT should start with the central identity provider, the service that manages user identities and sign-ins, then compare its account list with manager records and application-owner information. Single sign-on (SSO) lets an employee access connected applications through a central authentication process. Applications outside SSO require separate action, and connected applications may still maintain independent sessions.
- Send approved departure notice. Owner: HR or management. Timing: on approval.
- Inventory identity, email, storage, collaboration, and business applications. Owner: IT. Timing: before cutoff.
- Identify standalone business applications. Owner: IT and manager. Timing: before cutoff.
- List remote and privileged access. Owner: IT. Timing: before cutoff.
Software as a service (SaaS) accounts can include billing, customer records, booking systems, accounting, and project tools. For Palm Desert and Coachella Valley businesses, reservation systems, property-management platforms, and seasonal-worker accounts deserve explicit review rather than an assumption that central sign-in covers everything.
The remote-access inventory should include virtual private network (VPN) accounts, remote-control tools, administrative accounts, certificates, and application programming interface (API) credentials associated with the role.
Find shared access, recovery methods, and third-party permissions
Shared access requires more than removing a name from an account list. We distinguish employee-specific credentials from shared secrets or integrations that require rotation or reassignment.
- Identify shared credentials, vaults, and recovery methods. Owner: IT and application owners. Timing: before cutoff.
- Record delegated, shared-link, and connected-app permissions. Owner: IT. Timing: before cutoff.
- Identify externally administered access. Owner: Manager and IT. Timing: before cutoff.
Multifactor authentication (MFA) adds verification beyond a password. The inventory should include registered authentication devices, security keys, recovery codes, and recovery contacts.
Mailbox delegates, calendar permissions, forwarding rules, application connections, and external guest access also need review. Customer-owned systems and vendor portals may require action by an external administrator, so we identify that dependency before cutoff.
Record equipment and business data outside company systems
The office manager and IT should record asset identifiers, accessories, access badges, device locations, and return arrangements. Physical possession and account access remain separate findings.
We also ask the manager and IT to identify authorized business information held in personal email, personal devices, local storage, removable media, and artificial intelligence (AI) tool histories. The purpose is to establish an approved preservation or removal process, not to authorize unrestricted inspection of personal content.
Unavailable inventories and device-management limitations must remain recorded exceptions. An unknown location is not a verified absence of business data.
Before departure: preserve records and assign business ownership

Transfer files, mailboxes, and recurring responsibilities
Preserve required records and assign successors before account deletion or license changes can affect access to business information. Check whether existing backup and recovery arrangements cover the required data; a backup is not a substitute for a usable business handoff.
- Assign successors for active work. Owner: Manager. Timing: before cutoff where feasible.
- Transfer approved data and workflow ownership. Owner: IT and application owners. Timing: before destructive changes.
- Confirm retention requirements and legal holds. Owner: Records or legal owner. Timing: before content changes.
- Review deletion and licensing consequences. Owner: IT. Timing: before account or license removal.
Ownership review should cover files, shared drives, mailboxes, calendars, project boards, and automations. Successors must use individual authorized access, never the departing employee’s password.
Retaining a mailbox does not require keeping employee sign-in active. Confirm the platform supports the chosen preservation method while former-employee sign-in remains blocked.
Show a handoff that works without employee participation
The following hypothetical example shows a property-services business transferring work without relying on employee participation.
- Open project: The project manager finds the contractor schedule in the shared project workspace, confirms it, and records the review.
- Customer contact: The account manager opens the customer record and confirms the pending appointment.
- Recurring responsibility: The operations coordinator checks the shared calendar and procedure library before resuming weekly reconciliation.
- Outstanding decision: The business owner reviews the approved proposal folder and records a decision on the revised scope.
When normal participation is impossible, HR coordinates the authorized process while the manager reconstructs priorities from approved records. The absence of a handoff meeting must not leave customer commitments without an owner.
A listed folder is insufficient evidence. We recommend confirming that the successor can locate, open, and use the transferred information, including any dependencies needed to continue the work.
At departure: disable sign-in and close the remaining access paths
Block account use and revoke active sessions
At the approved cutoff, IT should execute the access block while preserving required records. Security-focused offboarding requires both account restrictions and session controls.
- Disable central and separate privileged sign-in. Owner: IT. Timing: authorized cutoff.
- Revoke active sessions and refresh tokens. Owner: IT. Timing: authorized cutoff.
- Disable remote access and revoke relevant credentials. Owner: IT. Timing: authorized cutoff.
- Remove employee authentication and recovery methods. Owner: IT. Timing: authorized cutoff.
A password reset alone must not be treated as proof that all sessions have ended. Refresh tokens, which applications can use to obtain renewed access, require attention through supported platform controls.
Cached access, offline copies, and application-specific sessions need separate consideration. We record the controls applied and any remaining limitations rather than describing a central account block as universal revocation.
Remove delegated, standalone, and connected-app access
IT and application owners should disable standalone accounts and terminate application sessions through supported controls. One identity-provider action does not guarantee that every third-party session has ended.
Remove the departing person’s group memberships, administrative roles, and access to other mailboxes or calendars. Review sharing links and forwarding rules, restricting anything that would preserve unauthorized access. Keep approved successor access to retained records intact.
Revoke relevant third-party application grants and employee-specific tokens without unnecessarily disabling approved organization-wide services. Confirm that the business has an authorized administrative recovery route before removing the employee’s authentication and recovery methods.
The manager or application owner should obtain removal confirmation from externally administered customer and vendor systems. Facilities or the office manager should disable physical access credentials where applicable.
An unanswered external request remains an open exception. We record the responsible owner, interim restriction, follow-up deadline, and business exposure until confirmation arrives.
Rotate shared secrets without breaking business services
IT should rotate shared passwords, recovery credentials, and other secrets the departing employee knew or could retrieve. Removing password-vault membership stops future retrieval through that vault, but it does not erase previously exposed credentials.
Before replacing shared API keys, service credentials, or automation connections, the application owner must identify dependent services and approve the replacement sequence. Otherwise, a security change can interrupt reservations, accounting transfers, or customer notifications.
After approved changes, IT and the manager should verify that business integrations still work. Rotation is not complete merely because a new secret exists; dependent services must use it successfully, and the old secret must no longer provide access where revocation is supported.
At and after departure: recover equipment and control remote wiping
Arrange, track, and confirm equipment returns
The office manager should provide written return instructions listing expected assets and an approved local handover or tracked shipping method. For remote returns, we recommend packaging instructions appropriate to the equipment and a recorded carrier tracking reference.
Delivery tracking alone does not verify the contents. IT or receiving staff should confirm physical receipt, asset identifiers, accessories, and visible condition, then record discrepancies.
Returned devices should be secured pending preservation review. We preserve approved business records before reimaging or reassignment, particularly when local files may be the only available business copy.
Missing equipment should be escalated through the approved management or HR process. The device-return exception remains open independently of account-access closure: successful sign-in removal does not establish that company property has been recovered.
Authorize a wipe only after checking ownership and preservation
Before issuing a remote wipe, IT and the authorized owner should confirm device ownership, management capability, written authorization, and preservation requirements. The available control may erase the whole device or only managed business data; that difference must be understood before execution.
For personal devices, use approved company-data removal controls where available and authorized. Do not assume permission to erase personal content.
An offline device may not receive a command immediately. A command sent is not proof of completion, so pending wipes remain exceptions with follow-up ownership and recorded results.
Business information in personal accounts requires an approved return, preservation, or deletion process. We must also acknowledge the verification limit: an organization may not independently confirm every previously copied file. Remote wiping therefore cannot establish that all data-exposure concerns have been resolved.
After departure: verify access removal before deleting accounts or licenses
Verify both closed access and working business handoffs
We treat verification as a separate task, not an automatic result of submitting requests. IT should inspect account states, session-revocation results, application-administrator confirmations, and available access logs.
Verification must use authorized administrative methods. Staff should not sign in as the former employee to test access.
The manager and successors should confirm access to required documents, customer records, calendars, and recurring workflows. Business continuity requires usable records, not simply a completed transfer command.
For each action, the record should show who performed it, the completion timestamp, systems checked, evidence location, and where business information now resides. The authorized owner should review every blocked item, assign a due date, and require closure evidence.
Keep requests, approvals, and completion evidence together in the support workflow. Our guide to help desks and service desks explains why the responsibilities and scope matter more than the label. A closed support ticket should not conceal an unresolved external account or unavailable device.
Revoking future access does not prove that previously downloaded information was removed. That distinction belongs in the final exception review.
Approve permanent deletion separately
The records or legal owner must confirm that applicable retention requirements and legal holds permit deletion. We do not recommend one universal retention period across all records, platforms, and organizations.
Before deleting accounts or removing licenses that could affect retained data, IT should verify preservation results, ownership transfers, and platform-specific consequences. A disabled account may remain necessary while records are retained under approved controls.
Organizations subject to privacy, contractual, or industry-specific requirements should have the responsible legal or compliance adviser review the process. Completing a general checklist does not establish regulatory compliance.
Plan your next employee departure
We recommend maintaining one controlled master checklist with a named owner and an approved restricted storage location. The structure can serve as an offboarding template in Word or Excel, with a PDF export retained as a completion record. Sensitive credentials should remain in approved credential storage, not inside the checklist.
Before operational use, conduct a tabletop review based on a hypothetical immediate departure. Confirm authorized contacts, application ownership, preservation approval, and unresolved-access escalation. The test should expose missing decision authority before an actual cutoff depends on it.
Palm Desert and Coachella Valley businesses should coordinate planned departures with available support coverage, particularly across multiple locations or seasonal staffing changes. Our help desk and remote support team can help coordinate the technical work within an agreed scope.
Standard help-desk hours are business hours. Continuous, 24/7 monitoring is distinct from separately scoped extended-hours or after-hours live support, so departure timing and execution coverage must be agreed explicitly.
Need help managing access when an employee joins or leaves? We can help you plan account changes and data handoffs around your business’s needs.
