Tools and Operations

What to Do When an Employee Leaves: An IT Offboarding Checklist

/

6 min read

IT offboarding checklist

When companies onboard new employees, there’s usually a clear checklist of tasks to complete within those first few days. The new employee’s accounts get created, devices are issued, and access is granted to dozens of tools.

Offboarding rarely gets the same attention as employee onboarding. When someone leaves a company, their digital footprint often remains scattered across apps, devices, and login credentials. It’s actually surprisingly easy for former employees to retain access long after their departure if you don’t have a structured IT offboarding checklist, creating both security and operational risk for growing companies.

This guide explains what to do when an employee leaves, from revoking system access to securing company data. The goal is simple: make offboarding predictable, secure, and repeatable so every departure is handled the same way.

Key Takeaways

  • An IT offboarding checklist ensures departing employees lose access to systems, devices, and company data quickly and consistently
  • Weak offboarding processes can leave active accounts, shared credentials, and security gaps that expose businesses to breaches
  • Core steps include revoking access, recovering devices, securing files, and reviewing SaaS licences
  • A well-documented onboarding process makes offboarding far easier because it shows exactly what access the employee had

Why Your IT Offboarding Checklist Matters More Than You Think

Offboarding mistakes are more common than many businesses realize.

Weak employee offboarding is a real security risk. A survey shows, 83% of former employees said they were still able to access accounts from a previous employer after leaving the company. The reason is simple: employees leave, but their access often remains active.

Small businesses are especially vulnerable because IT responsibilities are frequently shared across HR, operations, or whoever “handles tech.” Without a clear process, access removal can easily fall through the cracks.

An IT offboarding checklist ensures that every departure triggers the same security steps. Instead of relying on memory or informal coordination, teams follow a documented process that protects systems and data.

What happens when IT offboarding goes wrong?

Lingering access points are often called zombie accounts. They quietly increase the risk of unauthorized access, data theft, or accidental data exposure.

In some cases, the consequences extend beyond security. Businesses operating under GDPR or other data protection frameworks must demonstrate control over who has access to company data. Poor offboarding practices can create compliance issues that surface during audits or client security reviews.

Over time, these small gaps accumulate and without a consistent offboarding process, businesses lose visibility into who still has access to what.

The IT Offboarding Checklist: What to Do When an Employee Leaves

A strong offboarding process doesn’t have to be complicated, it simply needs to be consistent and clearly documented. Below is a practical IT employee offboarding checklist that most businesses can adapt to their environment.

Step 1 — Revoke access immediately

The first step in any offboarding IT checklist is disabling system access, so accounts connected to company systems should be deactivated as soon as the employee leaves, and in some cases, before the departure is announced internally.

This typically includes:

  • Email accounts
  • Single sign-on systems
  • Cloud applications
  • VPN access
  • Collaboration tools
  • Internal databases

Speed matters here. The longer access remains active, the greater the potential risk. Termination scenarios make this step especially important. Access should be revoked at the moment the employee departs to prevent unauthorized activity.

Step 2 — Recover company devices and equipment

Next, recover any company-issued hardware, which includes laptops, phones, security badges, tablets, external drives, and authentication devices. 

Remote employees require a slightly different approach. Shipping labels, return deadlines, and asset tracking should be part of the offboarding process so equipment does not disappear into someone’s home office.

Device recovery is not only about cost. Hardware often contains company data or stored credentials that could allow future access if not properly secured.

Step 3 — Change shared passwords and credentials

Team inboxes, marketing platforms, analytics tools, and social media accounts are often accessed by multiple employees using the same credentials. If a departing employee had access to those accounts, passwords should be updated immediately.

Failing to update shared credentials is one of the most common employee offboarding security gaps. Over time, businesses can reduce this risk by implementing password managers and role-based access controls, which make access management more structured.

Step 4 — Transfer or archive data and files

Departing employees often leave behind valuable information such as emails, documents, and project files. Before deleting accounts, businesses should ensure that important data is preserved.

Typical actions include:

  • Transferring file ownership
  • Archiving email accounts
  • Exporting project files
  • Documenting key client relationships

The goal is to retain business knowledge while avoiding unnecessary retention of personal information.

Step 5 — Review and cancel SaaS licences

Software licences are frequently overlooked during offboarding. Departing employees may still have active subscriptions across tools such as CRM platforms, project management software, analytics tools, and collaboration apps.

Unused licences create two problems: they increase costs and maintain unnecessary access points. Offboarding is a good time to review licences and clean up your software environment. Businesses dealing with growing tool sprawl often start by taking time to audit their tech stack and understand where access and spending have accumulated.

Step 6 — Conduct an exit security review

The final step in the offboarding checklist is verification. Before closing the process, confirm that:

  • All accounts are disabled
  • Shared credentials are updated
  • Licences are reassigned or cancelled
  • Devices are recovered
  • Data ownership is transferred

Some organizations also review access logs to confirm there was no unusual activity before departure. Documenting these steps creates a clear record that the offboarding process was completed correctly.

IT Offboarding Checklist and GDPR — What You Need to Know

Employee departures also have data protection implications.

Under GDPR, businesses must ensure that access to personal data is limited to authorized individuals. When an employee leaves, any access they had to customer or employee data must be removed promptly. 

Organizations should also review data retention policies. Some records may need to be retained for legal or HR reasons, while other personal data should be deleted once it is no longer required. A structured offboarding process helps demonstrate that appropriate access controls and data management practices are in place. 

IT Onboarding and Offboarding Checklist — How the Two Connect

Strong offboarding begins with strong onboarding. If access rights, devices, and accounts were documented when employees joined, removing them later becomes much easier. Without that record, teams often end up guessing which systems someone may still have access to. That’s why onboarding processes matter operationally. Onboarding sets the structure that offboarding eventually depends on. 

IT Offboarding Checklist Template — A Quick Reference

For teams that want a simple reference, here is a condensed offboarding checklist template:

Access

  • Disable user accounts
  • Remove SSO and VPN access
  • Deactivate email login

Devices

  • Collect laptops, phones, and hardware
  • Disable device management access

Credentials

  • Change shared passwords
  • Update team accounts

Data

  • Transfer file ownership
  • Archive emails and documents

Software

  • Review and cancel SaaS licences

Security review

  • Confirm access removal
  • Document offboarding actions

Saving a checklist like this ensures offboarding happens the same way every time.

How a Managed IT Partner Makes Employee Offboarding Easier

For businesses without dedicated IT teams, offboarding can easily become inconsistent. A managed IT partner helps standardize the process and instead of relying on memory, offboarding becomes a documented workflow tied to user accounts, device management systems, and access controls. Accounts are disabled quickly, licences are reviewed, and the process is recorded, resulting in a more secure and predictable IT environment.

If your team is reviewing how employee access, devices, and data are managed across the full employee lifecycle, it can help to speak with an IT partner who handles these processes every day. If you’d like to explore what that could look like, you can book a consultation.

Connect with us

Get Industry-Best Support, Starting at Only $99/user.

Set up a short consultation call today. Our team will help you create a clear IT plan, giving you the right blend of ongoing and project-based support.

prmt newsletter

Every week, get the latest AI and IT news in your inbox.

read next
Not sure if managed IT services are right for your growing business? Here are the signs that partnering with an MSP makes sense — and...

/

4 min read

When an employee leaves, your IT checklist matters more than you think. Here's what to do — from revoking access to recovering devices — to...

/

6 min read

Should you hire an in-house IT person or outsource to a managed service provider? Here's a practical framework to help you make the right call...

/

5 min read

Dark Web Scan Terms and Conditions

1. Public Report – Important Legal Notice (Read Before Use)

This Dark Web Exposure Report (“Report”) is generated automatically by Promethean IT, LTD, a New York State corporation (“PRMT,” “we,” “us”), using third-party and open sources. The Report may be incomplete, outdated, contain errors, or include information that is misattributed to the domain searched. The presence of information associated with a domain does not prove that the domain owner, any organization, or any person has been compromised, acted wrongfully, or experienced a current security incident.

This Report is provided for informational and defensive security purposes only and is not a security audit, penetration test, incident response service, breach notification, legal opinion, compliance determination, or a guarantee of security. Do not rely on this Report as the sole basis for decisions, and do not use it to target, harass, investigate individuals, or attempt unauthorized access.

Public availability & indexing. This Report is provided on a public website and may be accessible to anyone. It may be indexed, cached, archived, screen-captured, or copied by third parties beyond PRMT’s control.

By accessing or using this Report, you agree to the Dark Web Exposure Report Terms applicable to PRMT’s dark web monitoring pages and subpages (the “Site”).

2. How to Interpret This Report

  • The Report surfaces signals that may indicate exposure of credentials, identifiers, or domain-associated artifacts in third-party datasets (including, without limitation, breach corpuses, malware logs, paste sites, and other sources).

  • Results may reflect historical events and may include false positives, duplicates, synthetic/test data, “look-alike” domains, recycled addresses, forwarding aliases, data entry errors, or data unrelated to the current domain operator.

  • “Exposure” does not necessarily mean an active compromise or current vulnerability, and absence of findings does not mean no exposure exists.

  • The Report is not an attribution statement and should not be interpreted as alleging fault, negligence, or wrongdoing by any organization or individual.

3. Submission Form Language

Authorization & Proper Use Certification

I certify and agree that:

  1. I control the email address I provided and am authorized to request cybersecurity exposure information for the domain derived from that email address (the portion after “@”) (the “Domain”), either as (i) the Domain owner/operator, (ii) an employee/contractor acting within the scope of my duties, or (iii) an agent with written permission;

  2. I will use the Report solely for lawful, defensive security and risk-management purposes relating to the Domain;

  3. I will not use the Report to target, harass, stalk, defame, phish, spam, extort, or attempt unauthorized access to systems, accounts, or data;

  4. I understand and accept that the Report may be publicly accessible and may be indexed/cached/archived by third parties beyond PRMT’s control; and

  5. I have read and agree to the Dark Web Exposure Report Terms and acknowledge PRMT’s disclaimers and limitations of liability.

Email Delivery Consent

I request and consent to receive the Report and related service communications at the email address provided. I understand the message is service-related/transactional and may contain security information.

The Report will be generated only for the Domain derived from the email address provided, as determined by PRMT’s normalization and validation logic. PRMT may refuse, restrict, or suppress outputs in its discretion to mitigate abuse or risk.

4. Dark Web Exposure Report Terms

Effective: January 1, 2026

These Dark Web Exposure Report Terms (“Terms”) govern access to and use of the dark web exposure reporting features made available by Promethean IT, LTD, a New York State corporation (“PRMT,” “we,” “us”), on PRMT’s dark web monitoring pages and subpages (the “Site”). By searching a domain, requesting a Report, accessing a Report, or receiving a Report by email, you (“you,” “Requester”) agree to these Terms.

1. Definitions

  • “Report” means any output, score, summary, finding, alert, visual, or display generated by the Site in connection with a Domain search or request.

  • “Domain” means the internet domain derived from the email address submitted (generally, the portion after “@”), as determined by PRMT in its discretion, including normalization (e.g., handling of subdomains, internationalized domain names, aliases, and domain equivalents).

  • “Service” means the Site features that generate, display, or email Reports.

2. Eligibility; Authority to Request

You represent and warrant that you: (a) are at least the age of majority in your jurisdiction; and (b) are authorized to request and use the Service with respect to the Domain (e.g., you own/control the Domain, are acting within the scope of your employment/engagement, or have express permission from the Domain owner/operator).

No obligation to verify. PRMT may use technical measures to reduce unauthorized requests (including Domain-based email delivery), but PRMT does not guarantee that any Requester is authorized. You acknowledge that identity and authority verification may be limited and that PRMT is not responsible for misrepresentations by Requesters.

3. Public Nature of Reports; No Confidentiality

Reports are made available on a public website. You acknowledge and agree that:

  • Reports may be indexed by search engines and stored via caching, archiving, or mirroring services;

  • Copies may persist even if PRMT later updates, suppresses, or removes a Report; and

  • You will not treat Reports as confidential and you assume all risk of public exposure, republication, and downstream dissemination.

4. Permitted Use

Subject to these Terms, you may use the Service and Reports only for lawful, defensive security, risk management, and internal assessment purposes relating to the Domain.

5. Prohibited Use

You agree not to, and not to permit any third party to:

(a) use the Service or Reports to compromise, attempt to compromise, or gain unauthorized access to any system, account, or data;

(b) use the Service or Reports for phishing, credential stuffing, doxxing, harassment, extortion, fraud, spamming, social engineering, or any unlawful purpose;

(c) use the Service or Reports to investigate, evaluate, or make determinations about individuals (including employment, housing, credit, insurance, eligibility, or similar decisions), or otherwise use Reports as a “consumer report” or similar regulated report;

(d) scrape, crawl, bulk download, or systematically extract data from the Service (including via bots, automation, or any non-public interface), except as expressly permitted in writing by PRMT;

(e) reverse engineer, bypass, or interfere with Service security, rate limits, access controls, or anti-abuse measures;

(f) misrepresent your identity, authorization, or affiliation with any Domain;

(g) introduce malware or malicious code, or use the Service to distribute or facilitate malicious activity; or

(h) use the Service in a manner that could reasonably be expected to create liability, reputational injury, or harm to PRMT or others.

PRMT may investigate suspected violations and may suspend, block, limit, suppress, remove, or refuse Service access at any time.

6. Nature of the Data; No Statement of Fact; No Endorsement

The Service aggregates, analyzes, and summarizes information from third-party and open sources. Reports are indicators and signals, not verified facts. PRMT does not independently verify the completeness, accuracy, timeliness, source provenance, legality of upstream collection, or attribution of underlying data.

No implication of wrongdoing. Reports do not allege, and must not be interpreted as alleging, wrongdoing, negligence, breach, or fault by any Domain owner/operator, employee, contractor, or user. Any labels, severity indicators, or summaries are for informational triage only.

7. No Security Audit; No Incident Response; No Duty to Update

The Service is not a penetration test, vulnerability assessment, audit, certification, compliance determination, managed detection and response (MDR), or incident response service. PRMT does not guarantee that:

  • the Service will identify all exposures, threats, incidents, compromised credentials, or affected individuals;

  • any finding reflects a current risk; or

  • the Service will continuously monitor or update any Report.

PRMT may change the Service, sources, scoring, display logic, or reporting format at any time without notice.

8. Your Responsibilities

You are solely responsible for:

(a) determining whether you are authorized to request and use a Report for a Domain;

(b) verifying results through your own security processes and qualified advisors;

(c) using the information lawfully and responsibly; and

(d) complying with all applicable laws and policies (including privacy, cybersecurity, employment, and communications laws) relating to your access and use of Reports.

9. Email Delivery; Consent; Misdelivery and Compromised Mailbox Risk

By submitting an email address, you request that PRMT send the Report and related service communications to that address. You acknowledge that:

  • PRMT cannot guarantee deliverability or confidentiality of email in transit or at rest outside PRMT’s systems;

  • email may be forwarded, archived, accessed by administrators, or viewed by unintended recipients; and

  • if the mailbox is compromised or shared, a Report may be accessed by unauthorized parties.

PRMT is not responsible for unauthorized access to emails outside PRMT’s control.

10. Privacy; Personal Data; Redaction; Sensitive Information Handling

Reports may reference datasets that include identifiers (including email addresses) associated with a Domain. PRMT may redact, mask, hash, summarize, aggregate, or otherwise transform data to reduce sensitivity, and may change presentation at any time in its discretion.

You agree not to publish, share, reidentify, or misuse sensitive data obtained from the Service, and to handle any personal data in compliance with applicable law.

Your use of the Service is also governed by PRMT’s Privacy Notice.

11. Takedown / Dispute / Correction Process

If you believe a Report is inaccurate, unlawfully published, defamatory, infringes rights, or was requested without authorization, you may contact PRMT at [email protected] with: (i) the Domain, (ii) the specific Report URL or identifying details, (iii) the basis for your request, and (iv) evidence of authority to act for the Domain (which may include DNS-based verification or other reasonable proof requested by PRMT).

PRMT may, but is not obligated to, correct, suppress, or remove Reports, and may require verification before acting. PRMT may retain records necessary for security, audit, or legal compliance.

12. Intellectual Property; License

The Service and its underlying software, design, compilation, and presentation are owned by PRMT and its licensors and are protected by applicable laws. Subject to these Terms, PRMT grants you a limited, non-exclusive, non-transferable, revocable license to access and use the Service solely for the permitted purposes. No other rights are granted.

13. Disclaimer of Warranties

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE AND REPORTS ARE PROVIDED “AS IS” AND “AS AVAILABLE,” WITH ALL FAULTS AND WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, COMPLETENESS, TIMELINESS, OR THAT THE SERVICE WILL BE UNINTERRUPTED OR ERROR-FREE.

14. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW:

(a) PRMT WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, DATA, GOODWILL, BUSINESS INTERRUPTION, REPUTATIONAL HARM, OR THIRD-PARTY CLAIMS, ARISING OUT OF OR RELATED TO THE SERVICE OR REPORTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES; and

(b) PRMT’S TOTAL LIABILITY FOR ALL CLAIMS ARISING OUT OF OR RELATED TO THE SERVICE OR REPORTS WILL NOT EXCEED THE GREATER OF US$100 OR THE AMOUNT YOU PAID TO PRMT FOR THE SERVICE IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM (IF ANY).

Some jurisdictions do not allow certain limitations; in those jurisdictions, liability is limited to the minimum extent permitted by law.

15. Indemnification

You agree to defend, indemnify, and hold harmless PRMT and its officers, directors, employees, contractors, agents, and affiliates from and against any claims, demands, damages, losses, liabilities, costs, and expenses (including reasonable attorneys’ fees) arising out of or related to: (a) your submission of a request for a Domain; (b) your access to or use of any Report; (c) your violation of these Terms; (d) your violation of any law or the rights of any third party; or (e) any allegation that your request or use was unauthorized, deceptive, abusive, defamatory, or otherwise improper.

16. Suspension; Termination; Removal

PRMT may suspend, restrict, or terminate access to the Service and may remove, suppress, modify, or reissue any Report at any time, with or without notice, including to prevent abuse, comply with law, mitigate risk, correct errors, or improve the Service.

17. Changes

PRMT may update these Terms at any time by posting an updated version on the Site. Continued use after the effective date of updated Terms constitutes acceptance.

18. Governing Law; Dispute Resolution; Venue

These Terms are governed by the laws of the State of New York, excluding conflict of laws principles. Any dispute arising out of or relating to the Service, Reports, or these Terms must be brought exclusively in the state or federal courts located in New York County, New York, and you consent to personal jurisdiction and venue there.

19. Contact

Questions or notices: [email protected]

Mailing address: Promethean IT, LTD, 426 West Broadway, 6D, New York, NY 10012

5. Dispute or Request Suppression of a Domain Report

If you are the owner/operator (or an authorized agent) of a domain and you believe a Report is inaccurate, unlawfully published, or was requested without authorization, you may submit a dispute or suppression request to [email protected].

Please include:

  1. Domain name

  2. The Report URL or identifying details (e.g., screenshot + timestamp)

  3. Your role and proof of authority (PRMT may request DNS TXT verification, an email from an administrative mailbox at the domain, or other reasonable evidence)

  4. The specific correction/suppression requested and the basis for the request

PRMT may request additional verification before acting. PRMT may retain limited records for security, audit, abuse prevention, and legal compliance.