Resource Center
Practical guides, checklists, and frameworks to help your team run safer, more consistent employee departures.
Click any guide below to read the full content — everything HR and IT teams need for compliant, efficient offboarding.
As soon as a departure is confirmed, create one shared workflow with the employee's final working date, owner, required tasks, and deadlines. HR, IT, the manager, facilities, finance, and security should work from the same process instead of separate email threads.
Confirm the departure details, final day, manager, employment-status requirements, exit interview, benefits or payroll handoff, policy acknowledgements, and any records your organization must retain. Assign each task to a named owner and record completion.
Inventory the employee's accounts before the final day. At the appropriate time, block sign-in, revoke active sessions where supported, remove application access and privileged roles, handle email and file ownership, and document each completed action. Microsoft's current guidance for former employees specifically includes blocking access, preserving needed mailbox/data, handling devices, forwarding or transferring data where appropriate, removing licenses, and deleting accounts when the organization is ready.
List every assigned laptop, phone, badge, key, token, monitor, credit card, and other company asset. Record the expected return method, due date, condition, and final disposition so missing equipment does not disappear into an email thread.
Before the employee leaves, identify open projects, shared credentials that must be rotated, customer or vendor relationships, recurring responsibilities, documents, and data that need a new owner. Avoid retaining access simply because ownership was never transferred.
A strong offboarding process ends with a review: all required tasks completed, exceptions documented, assets reconciled, access-removal evidence retained, and the workflow closed. This creates a usable audit trail if HR, IT, management, or an auditor needs to verify what happened later.
Document the employee, manager, department, final working date, departure type, and the internal teams that need to participate. Use the final working date to drive due dates instead of relying on people to remember them.
Plan the employee communication, exit interview when appropriate, benefits and payroll handoffs, policy reminders, and return instructions. The exact employment and records requirements depend on your organization and jurisdiction, so keep legal or HR-specific requirements in your approved internal process.
HR should not have to perform technical deprovisioning, but it should reliably trigger it. Send IT the confirmed timing, manager, applications or special access known to HR, and any urgency. For sensitive departures, coordinate the timing closely so access does not remain open after it should end.
Make sure company equipment, badges, cards, keys, documents, and other property have an owner and return status. At the same time, make sure projects, approvals, customer relationships, and recurring responsibilities are reassigned.
Do not treat "email sent to IT" as completion. The HR checklist should show whether required offboarding tasks were actually completed, who completed them, when they were completed, and any exceptions that remain open.
Start with identity providers, email, collaboration tools, VPN or remote access, cloud platforms, business applications, developer tools, shared systems, physical access, and privileged accounts. Include SaaS applications that may not be centrally provisioned.
At the approved departure time, block sign-in and revoke sessions where supported. Remove privileged roles, group memberships, application assignments, tokens, keys, and other access paths. Revoke user access and terminate active sessions across identity and application platforms simultaneously when possible.
Before deleting accounts, determine what mailbox, OneDrive, files, calendars, shared resources, or application records need to be retained or reassigned. Preserve mailbox content and give another employee access to needed files and resources where required by policy or legal hold.
Track laptops, phones, security keys, badges, and other assigned equipment. For managed devices, follow your approved process for blocking or wiping organizational data when necessary, then document return, condition, and reissue or disposal.
Once retention, transfer, and policy requirements are satisfied, remove unneeded licenses and complete the account lifecycle according to your organization's retention policy. Record each action so a later review can distinguish completed work from planned work.
Review SSO and identity-provider assignments, Microsoft 365 or Google Workspace, VPN and remote tools, cloud consoles, source control, password vaults, finance and HR systems, CRM, support tools, physical badges, and locally managed SaaS accounts.
Administrative accounts, production access, finance permissions, security tools, shared secrets, API keys, and service credentials deserve special attention. If a departing employee knew a shared secret, rotate it rather than assuming account disablement is sufficient.
Disabling an account is an important step, but active sessions and tokens can have their own lifecycle. Use the controls available in each identity or application platform to revoke access appropriately and verify the result.
Check groups, delegated mailboxes, shared drives, team memberships, distribution lists, application roles, OAuth grants, device registrations, and external sharing. These indirect paths are easy to miss when offboarding is handled application by application.
For every critical system, capture status, owner, completion time, and any exception. The goal is to be able to answer "Was access removed?" with evidence rather than relying on memory.
Create the offboarding record as soon as the departure is approved. Capture the final date, manager, department, departure type, and required participants.
Use a standard template to create HR, IT, manager, facilities, finance, and security tasks. Add conditional tasks for privileged users, remote employees, company equipment, or special applications.
Some tasks happen before the last day, some at a precise departure time, and some after. Define those dependencies so access is not removed too early and does not remain active too long.
Reassign projects and approvals, preserve required business data, transfer files or mailboxes where appropriate, and establish new owners for customer, vendor, and operational responsibilities.
Reconcile company property and execute the approved deprovisioning plan across identity, applications, devices, and physical access.
Confirm required tasks are complete, document exceptions, retain the audit history, and close the workflow. A repeatable process is easier to improve because missed steps can be identified and corrected in the template.
Onboarding coordinates the work required to make a new employee productive: account creation, equipment, training, documents, introductions, application access, and role-specific tasks.
Offboarding reverses parts of that lifecycle, but it is not simply "delete the account." It includes access removal, asset recovery, data and knowledge transfer, documentation, and confirmation that required tasks actually happened.
Both processes cross HR, IT, managers, and other teams. When tasks live in separate inboxes and spreadsheets, ownership and status become difficult to see. Workflow software can centralize assignments, deadlines, reminders, and evidence.
Look for reusable templates, role-based task ownership, due dates, notifications, asset and account tracking, status visibility, reporting, and a durable audit trail. The software should support your process rather than forcing every organization into the same checklist.
Organizations with many applications, distributed teams, recurring departures, security requirements, asset-return challenges, or audit obligations usually gain more from a structured offboarding workflow than from an informal checklist alone.
OffboardSafe automates every step your guides and checklists describe.
