Employee Offboarding Checklist Template (2026)

Onboarding gets the binders, the buddy systems, the branded welcome kits. Offboarding gets a forwarded email and a hopeful assumption that everything will be fine. The asymmetry is strange, because departure is where businesses leak the most: unrevoked system access, unpaid final wages turning into labor-board complaints, client relationships walking out the door undocumented, and equipment that quietly never comes back.

An offboarding checklist fixes this the way any checklist fixes anything — by converting a stressful, multi-department scramble into an ordered sequence someone can actually execute. This guide gives you that sequence: what happens at notice, in the final week, on the last day, and after. Adapt it to your size; skip nothing.

Why Offboarding Deserves the Same Rigor as Onboarding

Four failure categories account for nearly every offboarding disaster:

Security. A departing employee's credentials remain live until someone manually revokes them — and "someone" is exactly the kind of word that means nobody. Industry breach surveys have reported for years that a meaningful share of ex-employees retain access to at least one company system after leaving. Every one of those accounts is either a breach vector or, at minimum, an audit finding.

Legal and financial. Final-pay timing rules vary by jurisdiction — some require payment on the last day worked, others within days — and getting it wrong converts a routine departure into a wage claim. Add COBRA-equivalent notices, benefits termination, references, and (in some roles) post-employment restriction reminders, and there's real paperwork with real deadlines.

Relationships. Clients, vendors, and internal partners all had a person, not a process. Without a documented handover, the successor starts from zero and the counterparties feel the drop in service before anyone explains why.

Knowledge. The processes that lived in one person's head leave with them unless deliberately captured. The work-handover document covers this — offboarding is the frame that makes sure it happens.

The connecting thread: none of these failures announce themselves on departure day. They surface weeks later as a security incident, a statutory notice letter, or a confused client — which is precisely why they need a checklist rather than good intentions.

The Master Checklist

Here is the complete sequence. The sections below explain the non-obvious items; the condensed copy-paste version is at the end.

Phase 1 — The Moment Notice Lands (Day 0)

Manager acknowledges resignation in writing and confirms last working day.

• Notify HR/payroll with dates and reason category.
• Decide access posture now, not on the last day: standard (access until final day) or restricted (immediate removal of sensitive systems) — based on role sensitivity and departure circumstances.
• If involuntary: coordinate legal review first, plan same-day execution, and never tip off the employee before the meeting.
• Open the offboarding record — one document tracking every step below with owners and completion dates.
• Trigger the work-handover process with a deadline of the second-to-last day.

The access-posture decision is the one most companies get wrong in both directions. Defaulting to "keep everything until Friday" risks data exfiltration during notice periods, which are statistically the highest-risk window; over-locking a trusted resigner's accounts creates resentment and disrupts their handover work. Decide per case, document the decision.

Phase 2 — The Final Week

Knowledge transfer (the highest-value phase).

• Work handover document drafted by the departing employee: open tasks, deadlines, contacts, file locations, credential inventory.
• Joint walkthrough with the incoming owner and manager — questions answered live, gaps filled on the spot.
• Client/vendor notification list agreed: who tells which counterparty, and what they say about continuity.
• Introduce the successor to key external contacts while the predecessor can still vouch for them.

Administrative.

• Schedule the exit interview (see below for how to make it useful).
• Confirm final-pay calculation inputs: unused leave accrual per your jurisdiction's rules, outstanding expenses, bonuses proration, deductions.
• Prepare benefits termination and any continuation-of-coverage notices with correct deadlines.
• Collect company property arrangements: laptop, phone, keys, badges, corporate cards — schedule returns, don't improvise them.

Access preparation (IT).

• Inventory all the leaver's accounts: SSO apps, email, VPN, shared drive permissions, third-party tools purchased by their team, social/media account admin rights, domain registrar access. The inventory matters because the accounts everyone remembers (email, Slack) are rarely the ones that bite — the forgotten marketing-tool admin login is.
• Prepare credential transfers via password manager sharing, never via the handover document itself.

Phase 3 — The Last Day

• Exit interview held (or scheduled if the employee declined).
• Equipment returned and checked against the inventory; signed receipt issued.
• Final systems sweep: disable SSO, revoke tokens and sessions (not just passwords — active sessions survive password changes), redirect email per policy, remove from distribution lists and org charts.
• Final pay processed per statutory timing; documentation provided.
• Departure announcement sent internally and externally with the successor's contact details.
• Collect signatures closing the loop: handover acknowledgement, property-return receipt, final-pay acknowledgment. E-signature keeps all three timestamped and filed without paper.

Phase 4 — After Departure

• Verify access revocation took effect (test-login spot checks beat assuming).
• Update client records, websites, and procurement portals listing the former employee as a contact.
• Diarize the 30-day check-in: is the successor running the inherited processes independently?
• If the person was client-facing or senior: confirm whether post-employment restrictions apply and who's monitoring them.
• Close the offboarding record and archive it with the signed documents.

The Exit Interview: Making It More Than Ritual

Most exit interviews produce polite nothing, for a structural reason: employees leaving voluntarily have little incentive to be candid with people who may respond badly, and no mechanism exists to do anything with what they say anyway. Two adjustments change the yield:

Ask forward-looking questions instead of autopsy questions. "What would you tell someone joining this team?" and "What should we stop doing?" extract more truth than "Why are you leaving?" — which mostly produces rehearsed answers ("better opportunity") that protect references.

Aggregate before judging. One departure is anecdote; five departures citing the same manager or the same broken process is intelligence. Keep responses structured enough to compare — consistent question sets, recorded themes, reviewed quarterly against your attrition pattern.

For involuntary departures, skip the interview entirely or hold it weeks later; same-day interviews after termination generate neither candor nor goodwill.

Adapting the Checklist to Your Size

Under 20 people: the founder runs phases 1–3 personally from this list; "IT" is whoever set up your Google Workspace. The critical subset if you do nothing else: access inventory and revocation, final-pay compliance, handover walkthrough, property return with signature.

20–200 people: split ownership explicitly — HR owns phases 1–2 administration, IT owns access, finance owns payroll, the line manager owns knowledge transfer. One named coordinator holds the master record; most failures at this scale are handoffs between departments, not missed steps within one.

Larger or regulated: add retention-hold checks before deleting anything (litigation holds override cleanup), formal deprovisioning tickets with SLAs, and documented evidence trails — auditors and enterprise clients increasingly ask to see the process, not just believe in it.

Common Mistakes

• Starting offboarding in the final week. Knowledge transfer needs runway; compressed handovers are decorative.
• Revoking access but not sessions. Password resets don't kill logged-in devices. Terminate tokens and active sessions explicitly.
• Letting the departing employee keep sending "final" emails. Uncontrolled goodbye messages with personal contact details create both compliance and relationship problems. Send the official announcement yourself.
• No signed closure. Handover accepted, property returned, final pay acknowledged — unsigned, every one becomes a dispute waiting for a bad quarter. Signed with timestamps, they're closed files.
• Treating contractors as exempt. Externals hold some of your riskiest access (social accounts, ad platforms, registrar). Their engagements end with the same revocation discipline.

Copy-Paste Master Checklist

• Acknowledge resignation in writing; confirm dates
• Set access posture (standard/restricted) and record reasoning
• Open tracked offboarding record with named owners
• Start work handover document (day 1 of notice)
• Inventory all accounts and prepare credential transfers
• Run joint handover walkthrough with successor and manager
• Agree client/vendor notification plan
• Schedule exit interview with forward-looking questions
• Prepare final-pay inputs and statutory notices
• Arrange equipment returns with inventory check
• Last day: disable SSO, revoke tokens/sessions, redirect email
• Collect e-signatures: handover, property return, final pay
• Send official announcements with successor contacts
• Spot-check revocation; update external listings
• Diarize 30-day successor check-in; archive the record

Wrapping Up

Offboarding is risk management wearing HR clothes: security exposure, statutory deadlines, relationship continuity, and knowledge retention, all converging on a single date. The checklist above sequences all four so nothing depends on memory. Run it as written for your next few departures and you'll notice the quietest benefit first — the last day stops feeling like a scramble, because almost everything important already happened before it arrived.

If coordinating this across documents sounds heavy, AiDocX generates the companion paperwork in one flow — offboarding checklist, work handover document, exit-interview form, final-pay acknowledgment — each e-signable with a full audit trail, so closure is provable rather than assumed.