Employee Offboarding Checklist (2026): Every Task by Owner and Timing, Including the Ones That Leak

TL;DR

An employee offboarding checklist assigns every exit task to an owner and a moment: during notice, on the last day and after exit. HR and the manager confirm the date and hand over work, IT revokes access and recovers equipment, finance and payroll stop payments and reclaim paid software seats, and legal handles contract terms and contractors. The tasks that leak are the ones no record triggers, such as a project-end date mentioned in an email that never reached accounts payable. This guide is published by Sentra, which understands how a company really runs, and acts on it before anyone asks. Sentra joins those conversations with HRIS, payroll, invoice and access records and flags mismatches for review.

Why offboarding checklists still leak

A written checklist gives each task an owner, but it cannot close access that IT does not know exists. Disabling a directory account blocks the main sign-in while other credentials keep working. Personal access tokens, SSH keys and cloud access keys can operate independently of single sign-on. OAuth grants and SaaS apps with their own logins need separate review, including tools a team bought without IT, the pattern described in our guide to shadow AI.

Security frameworks treat this as a defined control. NIST SP 800-53 control PS-4 on personnel termination asks organizations to disable system access within a defined period, revoke authenticators and credentials, conduct exit interviews and retrieve organizational property. ISO/IEC 27001:2022 covers the same ground in its Annex A controls on return of assets, access rights and responsibilities after termination or change of employment. Set your own deadlines from the framework you are audited against.

The process must also branch on how the person leaves. With notice, IT can reduce privileges in stages while work transfers, then revoke the rest on the last day. For an involuntary termination, HR and IT coordinate revocation with the termination meeting, because leaving access open for days after the conversation is the riskiest window of all. Access that outlives a role is also a segregation of duties problem when the old and new permissions together let one person approve and record the same transaction.

The offboarding checklist by owner and timing

Copy the table into a shared record. For each task, add the assigned person, the due date, the completion time and the evidence or link the next owner needs to verify the handoff.

IT offboarding steps in order

• Before the last day. Build the access inventory from the identity provider, SaaS admin consoles, cloud accounts, code hosts and device management. Include tools paid for on expense cards.
• At departure. Disable the directory account and SSO, revoke active sessions and refresh tokens, and revoke personal API keys, SSH keys and OAuth grants in the same step. Disabling SSO alone does not invalidate every machine credential.
• Immediately after. Rotate shared secrets the person knew. Transfer ownership of service accounts, scheduled jobs and integrations without breaking them.
• Verification. Within a set window, confirm that no credential or session is still active, record who revoked what and when, and keep the evidence for audit.

Payroll and benefits notes

Final pay deadlines vary by state and country, so payroll should check the applicable law for each departure. In the United States, group health plans covered by COBRA must offer eligible employees continuation coverage after employment ends, and the US Department of Labor's COBRA guidance sets out the notice duties for employers and plan administrators.

Contractor offboarding

Contractor offboarding needs a trigger outside the HRIS, because a contractor may have no HR record at all. The project owner should tell legal and finance when the work ends, even if the contract's stated end date has not arrived. Finance then checks upcoming invoices against the documented end date and stops recurring payments that no longer match active work.

Worked example: a departure that looks clean but is not

This example is illustrative. A project lead gives notice and HR records a last day at the end of June. The manager completes the handoff checklist. IT reduces access during the notice period, disables the account on the last day and audits keys and tokens afterwards. Every owner signs off.

The project lead also managed an outside contractor. In early June, the lead emails the manager: “We wrapped up last month. The contractor won't be doing any more work.” The manager closes the project tickets, but nobody forwards the message to finance. Accounts payable keeps processing the contractor's monthly invoice because the vendor record is still active and nobody told it the work had ended.

Each owner completed their checklist against the dates and records they received. The missed handoff sat in an email that none of those records saw. A checklist line that asks the manager to confirm which contractors the leaver managed would have caught it, and so would a check of invoices against project-end dates. The same pattern is a common source of revenue leakage and overpayment, where work is billed after it ended or never billed at all.

What a checklist cannot capture

Some of what leaves with a person is not access or equipment. It is knowledge of why accounts, vendors and projects are set up the way they are. The handoff document captures the status of open work, but the reasoning behind past decisions usually lives in that person's threads and meetings. Our guide to institutional knowledge covers how to keep it when people leave.

Where Sentra fits

Sentra understands how a company really runs, and acts on it before anyone asks. It reads email, chat, meetings and documents alongside ERP, CRM, HRIS and BI data, and works out what is true now and why. When a manager's email says a project ended, Sentra notes when that became true and checks later invoices, payroll runs and access records against it. If a contractor invoice arrives after the work was confirmed finished, Sentra raises the mismatch to the person who can stop the payment, before the next payment run.

A named person approves each finding before it reaches anyone else. Every claim cites its source, and permissions follow the source, so HR conversations stay visible only to the people who could already read them. Sentra replaces none of the company's systems. The HRIS, payroll and identity provider stay the record. Sentra holds SOC 2 Type II and ISO 27001 certifications.

FAQ