All answers

What is an IT offboarding procedure?

March 6, 2026·2 min read·SOPs by Role and Use Case

An IT offboarding procedure is a step-by-step checklist for revoking a departing employee's access to company systems, recovering hardware, and securing data. It covers disabling accounts (email, SSO, SaaS tools), transferring file ownership, revoking VPN and building access, wiping devices, and archiving the employee's data. A missed step can leave the company exposed to unauthorized access.

What does an IT offboarding checklist include?

CategoryActions
Identity & accessDisable SSO account, reset passwords, revoke MFA tokens
EmailDisable account, set up auto-forward or out-of-office, transfer mailbox ownership
SaaS toolsDeactivate accounts in CRM, project management, communication tools
Cloud storageTransfer Google Drive/OneDrive ownership, archive shared files
Code & infrastructureRevoke GitHub/GitLab access, rotate API keys, remove SSH keys
VPN & networkDisable VPN credentials, revoke Wi-Fi certificates
Physical accessDeactivate badge, recover building keys
HardwareCollect laptop, phone, monitors; initiate device wipe
CommunicationRemove from Slack channels, distribution lists, shared calendars

What is the typical timeline?

TimingAction
Last day (immediate)Disable SSO, email, and critical system access
Within 24 hoursDeactivate all SaaS accounts, revoke VPN
Within 1 weekCollect hardware, transfer file ownership, archive data
Within 30 daysDelete account data per retention policy

How do you document this efficiently?

Record each deactivation step in your admin consoles using Glyde. The capture tool creates visual guides showing exactly which buttons to click in Google Admin, Okta, or Azure AD. This ensures any IT team member can execute the offboarding — not just the person who set up the accounts.


This answer is part of our guide to SOPs by role and use case.

Related Questions

You might also ask

SOPs by Role and Use Case

How do you standardize and document client reporting processes for an agency?

Standardize client reporting by creating a reporting SOP that defines the report template, data sources, metrics to include, review process, and delivery schedule. Record the report-building workflow in your analytics and reporting tools using a capture tool. The generated guide ensures every account manager produces consistent, professional reports — regardless of experience level.

SOPs by Role and Use Case

Why does a lack of SOPs kill profit margins for service agencies?

Service agencies without SOPs lose profit to rework, inconsistent deliverable quality, excessive client hand-holding, and slow onboarding of new team members. Every time a senior team member re-explains a process, that is unbillable time. Every time a deliverable needs revision because a junior followed a different process, that is margin erosion. SOPs standardize execution so the work gets done right the first time.

SOPs by Role and Use Case

How do you write a step-by-step procedure for handling angry customers and issuing refunds?

Write the SOP in two parts: de-escalation steps (acknowledge, empathize, clarify the issue, offer a resolution) and refund processing steps (verify eligibility, select refund method, process in the system, confirm with the customer). Include specific language templates for each de-escalation step and screenshot-based instructions for the refund workflow in your ticketing and payment systems.

Get Started Today

Stop explaining.
Start documenting.

Join hundreds of teams building their knowledge base with Glyde.
Free to start. No credit card required.