Free Offboarding Checklist Template 2026 (6 Sections)

A good offboarding checklist turns 30 days of moving parts into a deterministic process where nothing gets dropped, no piece of knowledge walks out the door undocumented, and the security perimeter never has an orphan account. A bad one is a Word doc nobody opens, owned by nobody, and updated never.

The difference between the two is structural: the working offboarding checklist template is split by owner (HR, manager, IT, successor, departing employee, compliance), sequenced by week, and integrated with the actual systems where the work happens (HRIS, IdP, ticketing, knowledge base). This guide gives you the complete employee offboarding checklist in that working format, plus the integration patterns that make the checklist actually run instead of sitting on a shared drive.

For the broader process context behind every item on this checklist, see our complete employee offboarding guide. For the exit interview component, see our exit interview guide and our 30+ exit interview questions.

The 6-Section Structure of a Working Offboarding Checklist

Most offboarding checklists fail because they are owned by HR alone. A real workflow has six different owners, each with non-overlapping responsibilities. Splitting the checklist by owner is the single design decision that determines whether items get done.

Section 1: HR-ops checklist

Logistics, paperwork, payroll, benefits transition, exit documentation. The administrative spine of offboarding. Owned by HR-ops with cross-functional dependencies on payroll, benefits providers, and legal.

Section 2: Manager checklist

Knowledge transfer scope, successor coordination, team communication, exit interview preparation, goodbye message, LinkedIn endorsement. The pillar most often skipped because there's no compliance-officer chasing it. The single highest-leverage section for retention insight downstream.

Section 3: IT / security checklist

Equipment return, access deprovisioning, account suspension timing, data ownership transfer, SCIM 2.0 sync verification, security audit log. The pillar with the lowest tolerance for missed items: an orphan admin account is a security incident waiting to happen.

Section 4: Successor checklist

Knowledge package review, shadow period commitments, 30/60/90 day check-ins, escalation contacts. Often missed entirely because successors are not yet hired or onboarded when the checklist is built. The fix: a parallel track that activates when the successor is named.

Section 5: Departing employee checklist

What the employee themselves owns: knowledge interview participation, customer/vendor handoff emails, goodbye message, alumni network opt-in, equipment return logistics. Often forgotten because most checklists are written from the company's perspective only.

Section 6: Compliance & legal checklist

GDPR data subject rights handling, retention policy compliance, NDA/non-compete reminders, post-employment obligations, regulatory notifications where applicable. Owned by HR-legal partnership; required for any role where regulatory or fiduciary responsibilities apply.

Week 1: Resignation Accepted (Days 1-7)

The single highest-leverage week. The employee is most cooperative, has clearest context on every active project, and has not yet started mentally checking out. Knowledge work that gets pushed to later weeks loses 30-50% of quality.

HR-ops actions

• Acknowledge resignation in writing within 24 hours
• Open offboarding ticket in HRIS with departure date and 30-day plan
• Notify payroll, benefits provider, and IT of pending termination
• Schedule exit interview for week 4
• Generate offboarding documentation pack for the employee

Manager actions

• 1:1 with departing employee within 48 hours: confirm 30-day plan, knowledge transfer scope, communication strategy
• Inventory active projects, named relationships, edge-case knowledge held by the employee
• Identify successor (internal candidate, interim coverage, or trigger external hire process)
• Schedule structured AI-assisted knowledge extraction interview within 5 working days
• Communicate departure to the immediate team and to key cross-functional stakeholders

IT actions

• Receive offboarding ticket from HRIS
• Schedule access deprovisioning for end of last working day (not earlier)
• Verify SCIM 2.0 sync configuration covers all employee's connected systems
• Schedule equipment return logistics (in-office: pickup; remote: prepaid shipping label)

Departing employee actions

• Confirm last working day in writing
• Participate in structured knowledge interview within first 5 working days
• Begin drafting customer/vendor handoff communications

Week 2: Documentation and Handoffs (Days 8-14)

Convert the knowledge extracted in week 1 into reusable documentation. Begin systematic relationship handoffs.

HR-ops actions

• Update org chart to reflect pending departure
• Trigger benefits transition workflow (COBRA equivalent in applicable jurisdictions, pension/401k transfer instructions, stock vesting communications)
• Confirm final payroll calculation including unused vacation

Manager actions

• AI-synthesized knowledge package finalized: project briefs, decision logs, vendor map, stakeholder profiles
• Departing employee reviews and corrects synthesized documents
• Customer/vendor introduction emails sent (departing employee → successor → external party)
• Internal stakeholder introductions scheduled (1:1 between departing employee, successor, key collaborators)
• Calendar transferred or scheduled meetings reassigned

IT actions

• Identify shared/owned files in personal cloud storage requiring transfer to team drive
• Configure email forwarding rules for active customer/vendor conversations
• Audit any shared admin credentials the employee held

Departing employee actions

• Personal data cleanup in work systems
• Customer/vendor handoff emails sent with successor introduction
• Documentation of pending decisions with recommendation + rationale

Week 3: Successor Onboarding and Parallel Work (Days 15-21)

Departing employee shifts from primary owner to consultant. Successor begins running operational tasks under guidance.

Manager actions

• Successor takes over routine operational work; departing employee shadows
• Hand-off review: verify the successor can complete each major workflow independently
• Document edge-case escalation protocol: who the successor calls when something unexpected happens after departure

Successor actions

• Review knowledge package thoroughly; flag gaps to departing employee for week 4 follow-up
• Begin running operational tasks with departing employee shadowing
• Schedule introductions with named relationships from the stakeholder map

IT actions

• Equipment return logistics confirmed (date, method, condition acknowledgment)
• Access deprovisioning checklist validated against full inventory of systems

Compliance actions

• NDA and non-compete reminders prepared (where applicable)
• GDPR Article 17 (right to erasure) handling reviewed for personal data
• Regulatory notifications drafted (where the role requires regulatory disclosure)

Week 4: Exit Interview and Last Day (Days 22-30)

Operational work largely complete. Final week focused on exit feedback, employer brand, and clean closure.

HR-ops actions

• Run structured exit interview (AI-driven preferred for honesty; see our guide on AI-powered exit interviews)
• Final payroll processed
• Benefits transition documentation delivered
• Tax form delivery scheduled per regulatory calendar
• HRIS termination flag set effective last day

Manager actions

• Goodbye message published to team
• LinkedIn recommendation written for departing employee
• Reference letter provided (or LinkedIn recommendation in lieu)
• Alumni network invitation sent
• 30-day post-departure check scheduled with successor

IT actions

• Equipment received and itemized acknowledgment signed
• Access revoked at end of last working day across all systems (SCIM 2.0 cascade verified)
• Email forwarding rules activated
• Personal cloud storage data transferred to team drive
• Security audit log entry created for compliance archive

Departing employee actions

• Goodbye message customized and sent
• Equipment returned with documented condition
• LinkedIn endorsement of manager reciprocated
• Alumni network opt-in confirmed
• Personal acknowledgment of receipt of final payroll, benefits documentation, NDA reminders

Compliance actions

• NDA acknowledgment signed
• Documentation pack archived per retention policy
• Regulatory notifications submitted where applicable

Post-Departure: 30, 60, 90 Day Audits

Offboarding does not end on the last working day. The first 90 days post-departure produce diagnostic information you cannot get any other way.

Day 30: documentation gap audit

• 60-minute review with successor: which sections of knowledge package have been used, which gaps surfaced, which questions could not be answered from documentation
• Update the knowledge package with the gaps
• Tighten extraction protocol for future departures

Day 60: pattern check

• Has the team shown signs of ongoing disruption (stalled projects, missed deadlines, repeated escalations)?
• If yes, diagnose: was the issue in knowledge transfer, successor onboarding, or workload allocation post-departure?

Day 90: post-mortem

• Internal review with manager, successor, HR-ops
• What worked? What would you do differently next time?
• Combined with quarterly aggregation across multiple departures, drives iterative improvement

Common Checklist Mistakes

1. Single-owner ownership

A checklist owned only by HR fails because HR has no visibility into IT, manager, or successor work. Six owners, six sub-checklists, weekly cross-checking by HR.

2. No pre-departure activation

Many checklists activate only after resignation. The pre-departure prep (clear successor pipeline, named knowledge categories per role, generic communication templates) saves 3-5 days of week 1 time.

3. Treating the checklist as paperwork

A checklist that lives in a Word doc and gets manually checked is a paperwork exercise. A checklist integrated with HRIS, IdP, ticketing, and knowledge base is a workflow. Integration is the difference between a process that runs and a process that gets skipped under pressure.

4. No 30/60/90 audit

Without the post-departure audit, the checklist never improves. Each departure becomes an opportunity to learn what worked and what didn't, and the checklist gets sharper over 12-18 months.

5. One checklist for all role types

Senior engineer offboarding ≠ entry-level customer success rep offboarding. The framework is the same; the depth scales. Top 20% of roles by tacit knowledge value get the full checklist; lighter roles get a streamlined version.

KS-Agents Torch: Pay-Per-Use Knowledge Extraction

KS-Agents Torch runs the AI-driven knowledge extraction interview when an employee leaves, produces structured records ready for the successor, and ships with EU data residency, GDPR Article 22 compliance, and EU AI Act alignment built in. Every AI-assisted output is confirmable and reversible by a human reviewer. Torch is pay-per-use, with no subscription required: EUR 45 for one extraction interview, EUR 175 for a 5-interview pack. See Torch pricing →

Offboarding Checklist FAQ

What should an offboarding checklist include?

Six sections by owner (HR, manager, IT, successor, departing employee, compliance) sequenced across a 30-day timeline (resignation acceptance, knowledge transfer, successor onboarding, exit and last day). Plus a 30/60/90 day post-departure audit to verify the knowledge transfer actually worked.

How long is a typical offboarding process?

Standard mid-market practice: 30 days from resignation acceptance to last working day. Senior roles requiring deeper knowledge transfer often justify 45-60 days. Below 14 days produces measurable knowledge loss and successor productivity gap.

Who owns the offboarding checklist?

Joint ownership by section. HR-ops owns logistics. Manager owns knowledge transfer. IT owns access deprovisioning. The departing employee owns their own sub-checklist. Compliance owns regulatory items. HR-ops cross-checks weekly to ensure nothing falls through the gaps.

Is an offboarding checklist required for involuntary terminations?

Yes, with adaptations. The HR/IT/compliance sections are nearly identical. The manager section reduces (no goodbye message planning, modified exit interview format). The departing employee section largely doesn't apply. Add a section on how the termination was communicated and handled, since this affects employer brand.

What's the difference between an offboarding checklist and a termination checklist?

Offboarding is the broader workflow covering all departures (voluntary, involuntary, retirement, layoff). Termination is one specific scenario within offboarding. They share most checklist items but the termination scenario adds legal documentation (severance acknowledgment, COBRA notification, final paycheck delivery within statutory deadlines) that voluntary resignations may not require.

How do I track checklist completion across many active departures?

Three mechanisms scale: (1) workflow tool integration (HRIS-triggered tickets per owner with due dates), (2) weekly cross-functional standup to review active offboardings (15 minutes covers up to 8-10 simultaneous), (3) automated reminder cadence per role to escalate stalled items. Spreadsheet tracking breaks down past 5 simultaneous departures.

Does the checklist apply to remote employees?

Yes. Most items are identical. Differences: equipment return uses prepaid shipping label sent in week 3 with deadline; access deprovisioning is identical; goodbye communication may be video farewell or async written message instead of in-person; knowledge transfer interviews via video conference with identical structure. Alumni network maintenance is more important than for in-office because the lack of physical proximity makes ongoing relationship maintenance harder.

What GDPR considerations should the checklist address?

Three categories: (1) personal data of departing employee (right to erasure subject to legal retention obligations), (2) data they accessed in their role (lawful basis review for ongoing retention), (3) data the company collects during offboarding itself (lawful basis, retention policy, data subject rights). The checklist should reference the company's data retention policy and GDPR documentation pack.

Should AI conduct the exit interview as part of the checklist?

AI-driven exit interviews extract more honest data than HR-led interviews because the departing employee perceives less interpersonal risk. They are also more consistent across interviews, scale better at higher departure volumes, and feed pattern aggregation more cleanly. See our analysis of AI exit interviews. The exit interview is best scheduled as part of week 4 of the checklist.

How does this checklist integrate with HR analytics?

Quarterly aggregation of completed checklists feeds: retention strategy (exit interview themes), succession planning (knowledge transfer outcomes), recruiting (alumni network growth, boomerang pipeline), compliance reporting (audit trail), and process improvement (which checklist items consistently fall through and why).

From Checklist to Capability

The companies that handle offboarding well don't have better checklists than competitors; they have checklists that actually run consistently because they're integrated into the systems where work already happens. The 6-section structure and 30-day timeline above are the framework; the multiplier is the discipline of running them every time, learning from the post-departure audit, and refining the checklist quarter by quarter.

For deeper exploration, see our complete offboarding process guide, our exit interview complete guide, our library of 30+ exit interview questions and examples, our analysis of AI-powered exit interviews, our research on the strategic cost of knowledge loss, and our guide to retaining knowledge through structured extraction.