trio.so
Templates

IT Offboarding Checklist (Free Excel, PDF + Word Template)

Free IT offboarding checklist with an Excel tracker: access removal, device return and wipe, admin and BYOD steps, plus sample offboarding emails.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

An IT offboarding checklist is the list of steps IT follows when someone leaves: remove their access to every system, collect and wipe their devices, hand their data to a new owner and record that each step was done. It turns "we think their access is gone" into dates you can show.

This free template gives you a checklist in PDF and Word with steps for before the last day, the last day itself and the weeks after, plus extra steps for involuntary terminations, admins and personal devices, three sample offboarding emails and a sign-off page. An Excel tracker follows every leaver, system and device, and flags access still on after the deadline, devices that have not come back and leavers with no data owner.

In short

  • Start the day HR confirms the departure: list accounts and devices, name a data owner and set the access deadline.
  • On the last day, disable the directory account first, then end sessions, remove SSO apps and MFA, and change shared passwords.
  • Collect company devices and wipe them before reuse. On personal devices, remove work apps and accounts; never erase the device.
  • Admins and involuntary exits get a same-day deadline, and every step gets a date in the tracker so the offboarding can be signed off.

What IT Offboarding Covers, and What HR Owns

Offboarding is shared work. HR owns the employment side: notice, final pay, benefits and the exit interview. IT owns accounts, devices, data and the evidence that all of it was closed. The handoff happens when HR tells IT the name, the last day and the type of departure, and everything in this template starts from that message.

The IT side has four parts, and each one is a security control as much as an admin task:

  • Access removal: the directory account, single sign-on apps, MFA methods, VPN, admin consoles, vendor portals and any shared password the person knew.
  • Devices: laptops, phones, tablets, security keys, badges and keys come back, and company devices are wiped before anyone else uses them.
  • Data: files, the mailbox, projects and recurring tasks move to a named owner before the account closes.
  • Records: each step has a date, so you can show when access ended for any person who left.

Our overview of onboarding and offboarding covers the whole employee lifecycle, and the guide to employee offboarding automation looks at connecting HR and identity systems so fewer steps depend on memory. This post is the IT team's checklist. Its twin for new starters is the IT onboarding checklist, so what you hand out on day one is what you take back at the end.

The IT Offboarding Process in Three Stages

A departure is a short project with a fixed end date. The template splits it into three stages, each with an owner for every step:

The three stages of the offboarding process in the template, with the main steps in each
The three stages of the offboarding process in the template, with the main steps in each
StageWhenMain steps
Before the last dayFrom the moment the departure is confirmedInventory accounts and devices, agree the data owner, start the handover, send the leaver email
On the last dayBy the access deadlineDisable the directory account, end sessions, remove SSO and MFA, change shared passwords, collect devices
After the last dayDays to weeks afterWipe or reassign devices, chase late returns, transfer licenses, check sign-in logs, sign off

The access deadline matters most. The workbook sets it from the leave type: in the example values, the day after the last day for voluntary departures and contract ends, and the same day for involuntary exits and admins. NIST SP 800-53 control PS-4 asks organizations to disable access within a time period they define, so write your number down.

Before the Last Day

Most offboarding mistakes are planning mistakes: an account nobody knew about, a laptop nobody asked for. Use the days before the last day to build the list:

  • HR tells IT the leaver's name, role, last day and leave type as soon as the departure is confirmed.
  • Open an offboarding ticket and a row in the leaver tracker; set the access deadline from the leave type.
  • List every account, system and shared credential the person uses (directory, SSO apps, admin consoles, vendor portals).
  • List the devices, security keys, badges and keys assigned to the person, with serial numbers.
  • Agree with the manager who owns the person's files, mailbox, projects and recurring tasks after they leave.
  • Start the knowledge handover: documents, passwords held in the vault, scheduled jobs and open tickets.
  • Remote workers: send a prepaid return kit and agree the return date.

The workbook's systems checklist helps with the third step: each system a leaver may use, how to remove access, its owner, whether it signs in through SSO and what evidence to keep. Fill it once, and every offboarding starts from the same list. Take the device list from your inventory with serial numbers; our guide to device inventory management covers keeping it current.

On the Last Day: Remove Access in the Right Order

Most access hangs off one account. Disable the directory account first, and every app that signs in through single sign-on closes with it. Then deal with the rest:

The order the template uses to remove access on the last day, from the directory account to devices
The order the template uses to remove access on the last day, from the directory account to devices
  • Directory account: disable the user in Microsoft Entra ID, Google Workspace, Okta or your directory, by the access deadline.
  • Sessions, SSO and MFA: sign the person out everywhere, remove their SSO app assignments and remove their MFA methods, so a recovery flow cannot bring the access back.
  • Access outside SSO: VPN and remote access, apps with their own logins, vendor portals, shared mailboxes, groups and distribution lists.
  • Shared secrets: change shared passwords, door codes and API keys the person knew, and move password vault items to their new owner.
  • Mailbox: set an out-of-office reply or forwarding agreed with the manager, for a period agreed with HR, and hide it from the address book.
  • Devices and badges: collect laptops, phones, chargers, security keys, badges and keys, and check serials against the inventory.

This is the offboarding security checklist auditors care about. The tracker stores the date and time each leaver's accounts were disabled and compares it with their deadline. A row shows Access still on once the deadline has passed with no date recorded, and Disabled late if the date came after it. If you use SCIM, check that deprovisioning reached each connected app (deprovisioning in cybersecurity covers the gaps). For mail and Drive ownership, see our Google Workspace offboarding guide.

Device Return, Wipe and Reassignment

Every company device a leaver had should come back, be backed up if needed, and be wiped before it goes to someone else. The workbook's device return log has one row per device, with the serial number, ownership, the date it came back and what happened to it: wiped, reassigned after a wipe, retired or kept by agreement. Pick the leaver's name and the log fills in their last day and the return date, then flags devices that are not back in time and returned devices still waiting for a wipe.

A wipe is the step that protects the data on a device you can't recover, and the step that makes a returned device safe to hand on. For phones and laptops under device management, a remote wipe resets the device to factory settings; our guide to remote wiping a mobile device explains how it works per platform. NIST SP 800-88 Rev. 2 counts a factory reset as a clear technique for many devices, and drives that leave your control need a method that fits the data, which our asset disposal policy template covers. Record each device's status in your inventory too, as your IT asset management policy describes.

Before you wipe, back up what must be kept, including anything legal or HR asked you to hold. Ask HR and legal how long to keep a leaver's data; it depends on your contracts and local law, so the template leaves it as a value to fill in.

Personal Devices (BYOD)

A personal phone or laptop goes home with its owner, so the goal is to remove company access and work apps without touching anything personal. What that looks like depends on how the device was enrolled:

DeviceWhat unenrolling doesWhat IT can't do
Android with a work profileRemoves the work profile with its apps and data. The personal side of the phone stays.See or erase the personal side.
iPhone, iPad or Mac enrolled as personalRemoves the work apps your device management tool installed and ends management.Erase, lock or locate the device.
Windows PC enrolled as personalEnds management of the work apps and updates; remove the work apps you deployed before you unenroll.Erase the device.

Disabling the person's accounts and ending their sessions also closes email, chat and file-sync apps on the device. Ask the leaver to confirm that company files they saved outside managed apps are deleted, as your BYOD policy should say, and end any phone stipend. Our guide to the Android work profile explains how the work profile keeps work apps and data separate from the personal side of an Android phone. Write these steps into the policy before anyone leaves, so the leaver knows what to expect.

Involuntary and Immediate Terminations

When someone is dismissed, or leaves on bad terms, the timing changes. Access goes during the termination meeting, not after it. HR gives IT the date and time of the meeting in advance, and only the people who need it know. The template's steps for this case:

  • HR gives IT the date and time of the termination meeting, and only the people who need it know.
  • Disable the directory account and admin rights during the meeting, not after it.
  • Sign the person out of every session and block new sign-ins, including on mobile apps.
  • Collect devices, badges and keys in the meeting; for remote staff, arrange a courier the same day.
  • Change shared passwords and keys the person knew the same day.
  • Disable email forwarding rules and remove delegated mailbox access the person set up.
  • If a company device is not coming back, wipe it remotely and record why.
  • Keep a dated record of every step, in case it is needed later.

In the workbook, an involuntary leave type sets a same-day deadline, so any delay shows up at once. Keep the record factual and dated in case the departure is disputed later.

Admin and Privileged User Termination

An administrator can change systems, create accounts and read most data, so their offboarding is the one to get right. A checklist for IT administrator termination adds these steps to the standard ones:

  • Remove admin roles first: directory, cloud consoles, device management console, firewall, backup and finance tools.
  • Disable the person's separate admin accounts as well as their normal account.
  • Rotate credentials for service accounts, API keys and break-glass accounts they knew or managed.
  • Transfer ownership of scheduled jobs, scripts, domains, DNS records and vendor accounts held in their name.
  • Check for accounts or keys they created that are not in your inventory; disable or reassign them.
  • Review admin activity logs for the last [30] days before the departure.
  • Export the console member list after the change as evidence that the admin access is gone.

The step people miss is access the admin created rather than was given: a service account, an API key or a mail rule in their name. In the tracker, marking a leaver as privileged sets the privileged deadline from Settings (the same day in the example values) whatever their leave type. Our access control policy template sets the rules for privileged accounts in the first place.

After the Last Day: Confirm and Close

The last day is not the end. The steps after it close the loose ends and produce the record:

  • Back up what must be kept, then wipe returned company devices or reassign them after a wipe.
  • Chase devices not returned by the return date; escalate to HR after [7] days.
  • Transfer or close licenses and seats in each SaaS tool.
  • Tell vendors and partners who hold accounts for the person (portals, support contracts, banks).
  • Check sign-in logs for the disabled accounts for [30] days after the last day.
  • Delete or archive the account after the retention period agreed with HR and legal.
  • Confirm access removal system by system and record the dates in the tracker.
  • Sign off the offboarding: IT, the manager and HR.

The tracker counts the closing steps still open for each leaver after the last day (MFA and SSO removed, shared passwords rotated, data handed over, access removal confirmed). A row turns to Ready for sign-off when no flag and no open step is left, and to Closed once you enter the sign-off date. Periodic access reviews catch anything the offboarding missed; our user access review template runs them system by system.

Offboarding Email Templates

Three emails cover most departures. Replace the bracketed parts, and agree anything about pay, notice or personal data with HR first. The same text is in the PDF, the Word file and the workbook.

Email to the leaver

Send it once the departure is confirmed: what to return, when access ends and what happens to their files.

Subject: Your last day on [date]: returning equipment and accounts

Hi [First name],

Thank you for your work at [Organization]. Before your last day on [date], here is what happens with your equipment and accounts.

Please return your [laptop, phone, charger, security key and badge] to [person or desk] by [date and time]. If you work remotely, a prepaid return kit will reach you by [date]; please send it back within [7] days.

Your company accounts, including email and [apps], will be switched off at [time] on [date]. Please move any personal files off company devices and accounts before then, and hand over work files to [manager] as agreed.

If you use a personal phone or computer for work, we will remove the work apps and company accounts from it. We will not erase your device.

If you have questions, reply to this email or contact [IT contact].

[Name], IT

Email to the manager

It asks for the data owner, unlisted accounts and the mailbox decision in one go.

Subject: Offboarding [Name]: what we need from you by [date]

Hi [Manager name],

[Name]'s last day is [date] ([voluntary / involuntary / contract end]). To close their IT offboarding on time, please confirm the following by [date]:

1. Who takes over their files, mailbox, projects and recurring tasks.

2. Any systems, vendor portals or shared accounts they use that are not on the attached list.

3. Whether their mailbox should forward to someone, and for how long (we will confirm the period with HR).

4. That the knowledge handover is complete, on or before the last day.

Access will be removed at [time] on [date]. Devices are due back by [date].

Thanks,

[Name], IT

Email to system owners and vendors

For systems outside single sign-on and accounts held by vendors, ask for removal and a confirmed date.

Subject: Remove access for [Name], effective [date and time]

Hello,

[Name] ([email address], [role]) leaves [Organization] on [date]. Please remove their access to [system or service] effective [date and time], including any API keys, shared logins or support contacts in their name.

Please transfer anything they own in [system] to [new owner, email].

Reply to confirm when the access has been removed, so we can record the date. Ticket: [ID].

Thank you,

[Name], IT, [Organization]

For the rules on a leaver's mailbox after they go, see our terminated employee email policy.

Offboarding and Audits: ISO 27001, NIST and SOC 2

Auditors test offboarding by sampling: they take the HR list of leavers and ask, for a few names, when each account was disabled and whether the devices came back. The checklist lines up with these references:

FrameworkWhat it asks for at offboarding
ISO/IEC 27001:2022 Annex A5.11 Return of assets, 5.18 Access rights, 6.5 Responsibilities after termination or change of employment, 8.10 Information deletion.
NIST SP 800-53 Rev. 5PS-4 Personnel Termination: disable access within a set time, revoke credentials, hold an exit interview, retrieve property and keep access to the person's information. PS-5 covers transfers.
SOC 2CC6.2 and CC6.3: remove credentials and access when they are no longer authorized.
NIST SP 800-88 Rev. 2Clear, purge or destroy data on devices before reuse or disposal.

A tracker with a dated row per leaver answers that sample quickly. The mapping in the PDF and Word file is a general guide: your audit scope and your auditor decide what counts.

What's in the Download

The checklist PDF: cover, the last-day steps and the personal device steps
The checklist PDF: cover, the last-day steps and the personal device steps
  • Excel IT Offboarding Tracker (IT-Offboarding-Checklist-trio.so.xlsx): a leaver tracker that sets each access deadline from the leave type and flags late access removal, missing devices, missing data owners and open steps; a systems checklist; a device return log with serial numbers; the email templates; a filled-in example; a dashboard; and sources. Formulas only, no macros.
  • PDF checklist (IT-Offboarding-Checklist-trio.so.pdf): leaver details, the three stages, involuntary, admin and personal device steps, three sample emails, a sign-off page and framework references, ready to print.
  • Word version (IT-Offboarding-Checklist-trio.so.docx): the same checklist to edit, with fillable fields, tick boxes and date pickers on every step.
The workbook's Example tab: a made-up company's leavers and devices with their flags
The workbook's Example tab: a made-up company's leavers and devices with their flags

The example shows a made-up company with 9 leavers and 14 devices, including a contractor whose access is still on and whose laptop is missing, an admin disabled a day late, a phone waiting for a wipe and a personal iPhone still to unenroll.

Where trio.so Fits

trio.so does not run an offboarding workflow or approval chain: the checklist and the workbook carry the steps and the sign-offs. It covers the identity and device steps of the checklist. For those steps, trio.so gives you:

  • User sync from Microsoft Entra ID, Google Workspace, Okta and OneLogin, and SCIM 2.0 deprovisioning from Entra ID, Okta and OneLogin, so a person you disable or delete in your directory is deactivated or removed in trio.so too.
  • Single sign-on with SAML 2.0 or OpenID Connect (OIDC) and multi-factor authentication at user sign-in, in the Zero Trust plan, so the apps you connect through trio.so sit behind one account to close.
  • Console roles, so you can remove a leaving IT admin's rights in the trio.so console.
  • A CSV export of console members with their roles, status and last-active dates, as evidence that a leaving admin's access is gone.
  • A device inventory with each device's owner, serial number and installed apps, to check what a leaver must hand back.
  • Remote wipe of company-owned devices, before a returned device is reassigned or when one is not coming back.
  • Unenrolling personal devices: on Android the work profile and its apps and data are removed and the personal side stays; on a personal iPhone, iPad or Mac, IT can't erase, lock or locate the device, and unenrolling removes the work apps trio.so installed; on a personal Windows PC, trio.so manages work apps and updates only, and unenrolling ends that management.
  • Per-device policy status that shows whether each policy applied, failed or is still pending, so a reassigned device is checked before it goes to the next person.

It covers Windows, macOS, Linux, iOS/iPadOS and Android from one console. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates

Sources. Last reviewed November 2026. Framework names, control numbers and titles are used as references only; the checklist wording, formulas and example are ours. trio.so is not affiliated with or endorsed by ISO, NIST or the AICPA.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Close a leaver's accounts and devices from one console

trio.so syncs users from your directory with SCIM 2.0 deprovisioning, shows each device's owner and serial number, wipes company-owned devices and unenrolls personal ones without erasing them.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Four groups of steps. Access: the directory account, SSO apps, MFA methods, VPN, admin consoles, vendor portals and shared passwords. Devices: return of laptops, phones, security keys and badges, and a wipe before reuse. Data: a named owner for files, the mailbox and projects. Records: the date of each step and a sign-off. Add steps for involuntary departures, admins and personal devices.

By the end of the last working day for most departures, and during the termination meeting for involuntary exits and anyone with admin rights. NIST SP 800-53 PS-4 leaves the exact time period to each organization, so write your number into the policy and record the date and time accounts were disabled.

Three stages. Before the last day, list the person's accounts and devices, agree a data owner and send the leaver email. On the last day, disable the directory account, end sessions, remove SSO and MFA, change shared passwords and collect devices. After it, wipe or reassign devices, chase late returns, transfer licenses, check sign-in logs and sign off.

Their last day, what to return and by when, the time their accounts will be switched off, what to do with personal files on company devices, what happens to work apps on personal devices, and who to contact with questions. Keep pay and benefits out of it unless HR wrote that part. The download includes the full text, plus emails to the manager and to vendors.

IT removes company accounts and work apps and leaves the device with its owner. On Android, unenrolling removes the work profile and the personal side stays. On a personal iPhone, iPad or Mac, IT can't erase, lock or locate the device, and unenrolling removes the work apps that were installed. Personal devices are never erased.

Remove admin roles first, disable their separate admin accounts, rotate credentials for service accounts, API keys and break-glass accounts they knew, transfer ownership of scheduled jobs, domains and vendor accounts, look for accounts or keys they created, review their recent admin activity, and export the admin list after the change as evidence.

In ISO/IEC 27001:2022 Annex A, 5.11 Return of assets, 5.18 Access rights, 6.5 Responsibilities after termination or change of employment and 8.10 Information deletion. NIST SP 800-53 covers it in PS-4 Personnel Termination and SOC 2 in CC6.2 and CC6.3. The download maps each checklist step to these references.

Related

From the blog

The related industry news, interviews, technologies, and resources.