FirstHR

IT Offboarding Checklist: A Small Business Guide

IT offboarding checklist for small businesses where HR handles IT. Covers access revocation, hardware, shared passwords, BYOD, and compliance.

Nick Anisimov

Nick Anisimov

FirstHR Founder

Onboarding•
•
16 min

IT Offboarding Checklist for Small Businesses

When you don't have an IT department, this guide walks you through every step

When an employee leaves, most small business owners think about the same things: final paycheck, returning keys, maybe an exit conversation. IT access is an afterthought - something you remember two weeks later when you notice the former employee is still in your Slack or still showing up in your Google Drive shared files. Your employee offboarding checklist should include IT steps, but most small businesses treat them separately or skip them entirely.

That is a security problem waiting to become an expensive incident. At companies without a dedicated IT department, nobody owns the IT offboarding process by default. HR handles it, the office manager handles it, or nobody handles it until something goes wrong.

This guide is written for that person at a small business who is not an IT professional but needs to handle IT offboarding correctly. Plain language, specific steps, and guidance for the tools you actually use. At FirstHR, we have helped hundreds of small businesses build offboarding processes that protect them without requiring a technical background.

TL;DR
IT offboarding is the process of revoking a departing employee's access to company systems and recovering hardware. At small businesses, HR handles this. The most critical steps - disabling email, changing shared passwords, revoking SaaS access - must happen on the day of departure. This checklist covers every step with specific instructions for common SMB tools like Google Workspace, Slack, and Dropbox.

Why IT Offboarding Matters

Nobody publishes a trustworthy count of how many former employees still hold a live login, and the percentages that circulate online trace back to vendor surveys a decade old. What is documented is how often people leave and what the rules ask of the account they leave behind.

3.1MUS workers quit in a single month, July 2026 (BLS JOLTS). Every one of them is somebody's offboarding
5 yearsMaximum federal prison term for accessing a computer without authorization for private financial gain (18 U.S.C. 1030)
60 daysHIPAA deadline to notify individuals after discovering a breach of unsecured health information (45 CFR 164.404)
1 yearEEOC retention for personnel records at employers with 15 or more employees, from the termination date (29 CFR 1602.14)

According to the Bureau of Labor Statistics Job Openings and Labor Turnover Survey, 3.1 million US workers quit in July 2026 alone. Every one of those departures landed on somebody who had to remember which systems the person could reach.

For a small business, the math is more personal. A former employee with active access to your accounting software can see your financial data. Access to your CRM means access to every customer relationship you have built. Access to your email means access to ongoing client conversations, contracts, and internal communications.

The Zombie Account Problem
A zombie account is an active login that belongs to someone who no longer works for you. CISA counts anyone who has or had authorized access to an organization as an insider, which is the whole point: the account you forgot to close is still your exposure, not the former employee's. At a small company without SSO tools, zombie accounts accumulate fast, each one an open door into your business.

The exposure is not only financial. A login left open costs you the time to work out what was touched, any regulatory notice you owe, the customer trust you spend explaining it, and your legal position if a former employee uses access you never revoked.

That last part is not theoretical. Under the federal Computer Fraud and Abuse Act, accessing a computer without authorization carries up to a year in prison, and up to five years where it is done for private financial gain. The statute turns on authorization, and revoking the account is what removes it.

Who Handles IT Offboarding at Small Businesses

At enterprise companies, IT offboarding is handled by an IT department with tools like Okta or Microsoft Entra ID (the identity service formerly called Azure Active Directory) that let them disable access to dozens of applications simultaneously with a single click. At a small business, none of that infrastructure exists.

The reality is that at most small businesses, HR or the office manager handles IT offboarding alongside all other exit tasks. That arrangement works fine. The difference between doing it well and doing it poorly is not technical expertise: it is having a system.

TaskWho Handles ItWhen
Notify payroll to stop direct depositHR / OwnerBefore final paycheck
Disable email accountHR (via Google/M365 Admin)Day of departure
Set email forwardingHR (via Google/M365 Admin)Day of departure
Revoke individual SaaS accessHR working from access listDay of departure
Change shared passwordsHR / Office managerDay of departure
Collect hardwareHR / Office managerDay of or before departure
Transfer file ownershipHR (via Admin Console)Day of departure
Remove building/office accessHR / Office managerDay of departure
Final security reviewHR (checklist verification)Within 1 week
Archive offboarding recordHRWithin 1 week
From the field
The single biggest change we made to our offboarding process was building an access log during onboarding. Every time we gave a new hire access to a tool, we recorded it: tool name, account email, access level, date. When someone left, offboarding became working through a known list instead of trying to remember every system they might have touched. That list alone cut our offboarding time in half and eliminated zombie accounts entirely.

If you track access during onboarding, offboarding becomes a checklist exercise. If you do not, offboarding becomes an audit - which takes much longer and misses things. Consider using an onboarding checklist that includes a column for tools and access levels granted to each new hire.

Here is that log as a workbook you can start today. The first tab is one row per person per system, filled in the day access is granted. The second is the inventory of shared logins, which is the part no per-departure checklist can reconstruct after the fact.

Employee Access Log and Shared Credential Inventory
ABCDEFGH
1EmployeeTool or systemAccount or usernameAccess levelGranted onGranted byRevoked onRevoked by
2[Employee name]Email and calendar[name@company.com]Standard user[MM/DD/YYYY][Name]
3[Employee name]Team messaging[name@company.com]Member[MM/DD/YYYY][Name]
4[Employee name]File storage[name@company.com]Editor on [folder][MM/DD/YYYY][Name]
5[Employee name]Project management[name@company.com]Member[MM/DD/YYYY][Name]
6[Employee name]Accounting software[name@company.com]View only[MM/DD/YYYY][Name]
7[Employee name]CRM and customer data[name@company.com]Full user[MM/DD/YYYY][Name]
8[Employee name]Password manager[name@company.com]Shared vault: [name][MM/DD/YYYY][Name]
9[Employee name]VPN and remote access[username]Enabled[MM/DD/YYYY][Name]
10[Employee name]Developer tools and API keys[username][Scope][MM/DD/YYYY][Name]
11[Employee name]Building accessBadge [number][Location][MM/DD/YYYY][Name]
12
13NoteAdd the row the day access is granted, not the day someone leaves. The two right-hand columns are what turn this into the offboarding worklist.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

IT Offboarding Timeline

IT offboarding has a clear priority order. Not everything needs to happen immediately, but the highest-risk items - access to live systems - must happen on the day of departure. Here is the timeline structured around actual risk level.

Day of departureImmediate actions
Disable email account (keep forwarding active)
Revoke SSO / Google Workspace / Microsoft 365 access
Change all shared passwords the employee knew
Remove from Slack and internal messaging tools
Disable VPN and remote access credentials
Within 24 hoursAccess revocation
Revoke access to every SaaS tool individually
Transfer file ownership in Google Drive or Dropbox
Remove from project management tools (Asana, Notion, Jira)
Disable access to accounting software (QuickBooks, Xero)
Remove from CRM and customer data systems
Within 48 hoursHardware and data
Collect company laptop, phone, and peripherals
Wipe company data from personal devices (BYOD)
Back up all email and files before account deletion
Retrieve physical items: keys, badges, access cards
Run a security review of recent account activity
Within 1 weekCleanup and documentation
Reclaim and reassign software licenses
Cancel subscriptions tied to departing employee
Update building and office access systems
Document all steps completed with timestamps
Archive offboarding record for compliance
Voluntary vs. Involuntary Departures
The timeline above assumes a standard planned departure. For involuntary terminations, the day-of-departure steps become the first-hour steps. Disable access before or immediately when the conversation happens, not after. Waiting even a few hours after a termination creates real risk of data exfiltration.

Step-by-Step IT Offboarding Checklist

This checklist is organized by priority. Work through it in order - the most critical security steps come first.

Step 1: Notify your team and prepare

Before the employee's last day, confirm the departure date internally and identify who will take over their responsibilities. Build or pull up your access log. The goal is to start the last day with a complete picture of what needs to be done, not to figure it out on the fly.

If you are running a structured offboarding process, this preparation should begin as soon as the departure is confirmed - whether that is two weeks out for a resignation or the morning of for a termination. Use this time to schedule a exit interview and document knowledge transfer before access is revoked.

Step 2: Disable email and set up forwarding

Email is typically the master key to other accounts - password reset emails go there, client communications come in there, and it contains a record of most business activity. Handle it first.

Set up email forwarding before you suspend the account. In Google Workspace, go to Admin Console, select the user, and set a forwarding address before suspending. In Microsoft 365, create a shared mailbox or forwarding rule first, then disable the sign-in. Do not give the departing employee's password to a colleague - use the admin console.

Step 3: Revoke SSO or identity provider access

If your company uses Google Workspace or Microsoft 365 as your primary identity, suspending the user account in the admin console automatically blocks access to Google or Microsoft services. It does not automatically block access to SaaS tools that have their own login - those need to be revoked individually in step 4.

If you use a dedicated SSO tool that sits in front of your applications, disabling the account there can revoke access to all connected apps simultaneously. This is the fastest path if you have it set up.

Step 4: Revoke access to every SaaS tool

This is the most time-consuming step because it must be done tool by tool at most small businesses. Work through your access log methodically. The next section of this guide covers specific instructions for the most common SMB tools.

Do not assume that removing someone from Google Workspace removes them from Slack, Asana, HubSpot, or any other tool that has its own user management. Each requires its own revocation.

Step 5: Change all shared passwords

This step is more dangerous to skip at a small business than at an enterprise company, because small businesses have more shared credentials. See the dedicated section on shared passwords below for a complete process.

Step 6: Transfer files and data ownership

Before suspending the email account or removing the user from cloud storage, transfer ownership of their files. In Google Drive, use the Admin Console to transfer all of a user's Drive files to their manager in one action. In Dropbox Business, you can move files to another team member before removing the user.

If you skip this step and delete the account first, you may permanently lose files the employee created - especially in tools where deleting a user also deletes their content.

Step 7: Collect hardware

Laptops, phones, monitors, peripherals, keys, and access badges all need to come back. For in-person employees, collect on the last day. For remote employees, send a prepaid shipping label in advance and confirm receipt in writing. Do not hold the final paycheck as leverage for a laptop. The Department of Labor notes that federal law sets no immediate deadline but some states require immediate payment, and in those states an unreturned device changes nothing about when you owe the money.

Document the condition of returned hardware. Take photos if there is any damage. This protects both parties.

Step 8: Handle BYOD (personal devices)

If the employee used personal devices for work, you cannot wipe them without MDM tools. See the BYOD section below for what you can and cannot do without technical infrastructure.

Step 9: Reclaim licenses and subscriptions

SaaS licenses cost money. After access is revoked, check each tool to confirm the seat has been freed. Some tools automatically free the seat when a user is deactivated; others require you to manually downgrade your subscription. Also cancel any tool subscriptions or credit cards tied specifically to the departing employee. For a full list of financial and administrative steps, see our employee offboarding checklist.

Step 10: Run a security review and document everything

After completing the checklist, do a final pass. Review recent account activity for anything unusual in the days leading up to departure. Confirm every item on your access log has been addressed. Document the date and time each step was completed - this is your compliance record if questions arise later. Store this alongside your other HR documentation for the employee.

Keeping that record is also a legal minimum once you are large enough. EEOC recordkeeping rules, which reach employers covered by Title VII at 15 or more employees, require personnel records to be held for one year from the date of the personnel action, and for anyone involuntarily terminated, one year from the termination date.

SMB Tools: Access Revocation Guide

The following table covers the tools most commonly used by small businesses and where to revoke access for each. All paths assume you are an admin on the account.

Tool CategoryCommon SMB ToolsWhere to Revoke AccessTime Required
EmailGoogle Workspace, Microsoft 365Admin Console > Users > Suspend2 min
MessagingSlack, Teams, DiscordWorkspace Settings > Members > Deactivate1 min
File StorageGoogle Drive, Dropbox, BoxAdmin Console > Transfer ownership first5-10 min
Project MgmtAsana, Notion, Trello, MondayWorkspace Settings > Members > Remove1-2 min each
AccountingQuickBooks, Xero, FreshBooksSettings > Users > Remove or downgrade2-3 min
CRMHubSpot, Salesforce, PipedriveSettings > Users > Deactivate2 min
DesignFigma, Canva, AdobeAdmin > Members > Remove1-2 min each
Password Mgr1Password, LastPass, BitwardenAdmin > People > Suspend + rotate shared vaults5-10 min
Video ConfZoom, Loom, RiversideAccount Management > Users > Deactivate2 min
Payroll/HRYour payroll providerTerminate in system, cancel direct deposit5 min
Start With Your Admin Consoles
Google Workspace and Microsoft 365 admin consoles are your primary control panels. Suspending a user there immediately blocks their access to all Google or Microsoft products. Make this your first step - it handles email, Drive, Calendar, and Meet simultaneously. Everything else on the list above must be done separately.

Shared Passwords and Credentials

Shared passwords are the most underestimated IT offboarding risk at small businesses. Enterprise companies solve this with SSO - one identity system that controls access to everything. Small businesses typically have dozens of shared logins that were passed around by email, Slack DM, or sticky note.

When an employee leaves, every shared credential they knew becomes a security risk. This includes team email inboxes, social media accounts, billing and subscription accounts, shipping accounts, vendor portals, and any other shared login that was not managed through a password manager with individual access controls.

The Federal Trade Commission keeps describing the same failure in its security guidance for businesses. In one enforcement matter, a company shared a single cloud administrator credential across employees and outside contractors and never changed it when a contractor left. The agency also tells businesses to limit administrative access to the people whose job actually requires it.

1
Audit all shared credentialsList every shared account the employee had access to: team email inboxes, social media, billing accounts, vendor portals, shipping accounts.
2
Change passwords immediately on departure dayDo not wait. Do all shared passwords on the day of departure, before the person actually leaves if possible.
3
Use a password manager for shared credentialsTools like 1Password or Bitwarden allow you to share credentials with team members and revoke individual access without changing the password for everyone else.
4
Update saved passwords in browsersAny browser-saved credentials tied to a company account should be updated. This includes Chrome profiles signed in with a company Google account.
5
Rotate API keys and tokensIf the employee had access to developer tools, API keys, or webhooks, rotate or revoke those credentials even if you are unsure they were used.
From the field
We started using a team password manager after a departure where we realized we genuinely did not know which shared passwords the employee had seen. The difference is significant: instead of changing every shared password when someone leaves, you just remove their access to the shared vault. They lose access to all shared credentials instantly without forcing everyone else to update saved passwords. Once more than a couple of people share a login, this pays for itself the first time someone leaves.

BYOD: What To Do About Personal Devices

BYOD (Bring Your Own Device) is common at small businesses because it saves money on hardware. The tradeoff is that you have less control over company data on personal devices, especially at offboarding. Here is what you can and cannot do without dedicated MDM tools.

Risk ScenarioWhat To Do
Company email cached on personal phoneRemote wipe company account via Google Workspace or Microsoft 365 MDM
Company files in personal Dropbox or Google DriveTransfer ownership before access is revoked; cannot retrieve after
Company Slack on personal deviceDeactivating account removes access; no further action needed
Company apps with offline dataRequest employee deletes apps; no enforcement without MDM tool
Password manager on personal deviceRemove from shared vaults; personal vault remains theirs
The BYOD Offboarding Limit
Without a Mobile Device Management (MDM) tool like Jamf or Kandji, you cannot remotely wipe a personal device, enforce app deletion, or verify that company data has been removed. You can only request that the employee takes these actions and accept their confirmation. This is a real limitation - if you handle sensitive customer or financial data, consider whether BYOD is worth this risk, or invest in a basic MDM tool.

For remote employees on BYOD, send written instructions for what needs to be removed and request written confirmation on or before the last day. Ask for it on its own timeline rather than tying it to the final paycheck, which state wage law schedules for you. This creates a record even if you cannot verify enforcement.

Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Compliance Requirements

Depending on your industry and the type of data you handle, IT offboarding may have specific legal requirements. You do not need to be a compliance expert, but you should know which frameworks apply to your business and what they require at minimum.

Two federal sources are worth bookmarking. NIST publishes the Cybersecurity Framework, now in version 2.0, and its Small Business Cybersecurity Corner curates the same material for companies with no security staff.

HIPAAHealthcare businesses
45 CFR 164.308(a)(3)(ii)(C) asks for procedures that end access to electronic health information when employment ends. It is addressable, so document the procedure you chose
SOC 2Software and SaaS companies
Auditors test access removal against evidence, so the dated revocation log is the control they sample
PCI DSSBusinesses that process cards
Requirement 8.2.5: access for terminated users is immediately revoked. Requirement 8.2.2 keeps shared or generic logins to documented, approved exceptions
CCPA and GDPRCompanies holding customer personal data
Both require reasonable security over personal data, which a live account belonging to a former employee defeats

The HIPAA rule people most often misquote is the one on termination. 45 CFR 164.308(a)(3)(ii)(C) asks a covered entity to implement procedures for ending access to electronic protected health information when employment ends. It is an addressable specification rather than a stopwatch, so there is no federal 24-hour deadline, but you do have to be able to show what your procedure is.

The deadline in HIPAA sits on the other side of the incident. 45 CFR 164.404 gives a covered entity 60 calendar days from discovering a breach of unsecured protected health information to notify the individuals affected.

Even if none of these specific frameworks apply to your business, maintaining a documented record of your offboarding process protects you legally. The U.S. Small Business Administration tells owners to run access audits on a regular basis so that former employees are removed from their systems. If a former employee later claims they never had access to something, or if a breach occurs, your timestamped offboarding checklist is evidence of due diligence.

For businesses subject to HIPAA or SOC 2, consider involving your legal or compliance advisor to confirm that your offboarding process meets the specific documentation and timing requirements. The cost of a 30-minute consultation is far less than the cost of a compliance violation.

Key Takeaways
Revoke access on the day someone leaves, because the federal computer fraud statute turns on whether authorization was actually removed.
At small businesses HR handles IT offboarding, so build the access log during onboarding and offboarding becomes a checklist rather than an audit.
Shared passwords are the biggest small business offboarding risk, so change every shared credential on departure day and move the team onto a password manager with per-person access.
Set email forwarding before you suspend the account, because deleting the account first can take the messages and files with it.
Document every step with a timestamp, which is what HIPAA, PCI DSS, and the EEOC retention rule all expect you to be able to produce.

Frequently Asked Questions

What is IT offboarding?

IT offboarding is the process of revoking a departing employee's access to company systems, tools, and data. It includes disabling email accounts, removing access to SaaS applications, collecting company hardware, rotating shared passwords, and wiping company data from personal devices. IT offboarding is distinct from HR offboarding, which covers final pay, benefits termination, and exit interviews. Both must happen when an employee leaves, but IT offboarding focuses specifically on data security and system access.

Who is responsible for IT offboarding - HR or IT?

At most small businesses, there is no dedicated IT department. That means HR, the office manager, or the business owner handles IT offboarding tasks. This is normal and manageable as long as you have a checklist and work systematically through each system the employee had access to. The key is to build and maintain an access log during onboarding, so offboarding is a matter of working through a known list rather than trying to remember every tool.

How long should IT offboarding take?

The most critical steps - disabling email, revoking SSO access, and changing shared passwords - should happen on the day of departure, ideally within the first hour. Secondary steps like transferring file ownership and removing from individual SaaS tools should be completed within 24 hours. Hardware collection, BYOD cleanup, license reclamation, and documentation can be completed within one week. The total time investment at a small business is typically 2 to 4 hours, depending on how many tools the employee had access to.

What is the biggest IT offboarding risk for small businesses?

The biggest risk for small businesses is shared passwords. Enterprise companies use SSO tools like Okta that let you disable access to dozens of apps simultaneously. Small businesses typically have dozens of shared logins - team email inboxes, social media accounts, billing accounts, vendor portals - that must be changed manually. If you miss even one, a departing employee retains access indefinitely. Building a shared credential inventory and using a password manager with team access features significantly reduces this risk.

What should I do with a departing employee's email?

First, set up email forwarding to a manager or the employee's replacement before suspending the account - this ensures no incoming messages are lost. Then suspend the account rather than deleting it immediately. A suspended mailbox keeps its contents while you back up the messages and contacts that matter, whereas deleting the account starts a short recovery window that differs by platform and can take attached files with it. Check your own admin console for the exact window before you delete anything. Do not give the departing employee's email password to a colleague - use the admin console to access or forward the account directly.

How do I handle offboarding for a remote employee?

Remote employee IT offboarding follows the same steps but has additional considerations. You cannot physically collect hardware on the last day, so arrange shipping in advance with a prepaid label. For access revocation, everything is handled digitally - disable accounts remotely through admin consoles the same day. For BYOD situations, request the employee wipe company apps and data before their last day, and verify via your admin console where possible. Document everything in writing and get written confirmation from the employee that hardware has been shipped.

What is a zombie account and why is it dangerous?

A zombie account is an active user account that belongs to someone who no longer works at your company. It typically exists because IT offboarding was incomplete or not performed at all. Zombie accounts are a serious security risk because former employees can use them to access company data, customer information, or financial systems long after their employment ended. CISA counts anyone who has or had authorized access as an insider, which is why an account nobody closed stays on your side of the ledger rather than the former employee's. For small businesses, a zombie account in your accounting software or CRM represents direct access to sensitive business and customer data.

Do I need to track IT offboarding for compliance?

Yes, for most businesses. If you handle health information, the HIPAA Security Rule asks you to implement procedures that end access to electronic protected health information when employment ends, and to be able to show what those procedures are. If you process credit card payments, PCI DSS Requirement 8.2.5 says access for terminated users is revoked immediately. If you hold personal data about EU or California residents, both regimes require reasonable security over it, and an account belonging to someone who left is the opposite of that. Even where no specific regulation applies, a dated record of what you revoked and when protects you if a departed employee later disputes what they could reach.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial