17 items

Employee Offboarding

Offboarding done right protects your data, satisfies legal obligations, and turns departing employees into future allies — this checklist coordinates HR, IT, and management through every critical step from the moment notice is received to 90 days after the final day. For more background and examples, see the guidance below; for built-in tools and options, use the quick tools guide.

Author

Checklistify Editorial Team

Last Updated

Checklist Items

0 done•17 left•5 of 6 sections collapsed

Initiate the offboarding process and assign owners across HR, IT, and the direct manager

Offboarding requires simultaneous coordination across at least three functions: HR (final pay, benefits, legal documents), IT (access planning, device recovery, data preservation), and the direct manager (knowledge transfer, project continuity, team communication). The critical failure mode of uncoordinated offboarding: access revocation happens before knowledge transfer completes, or knowledge transfer proceeds but access isn't revoked promptly on the final day — a security gap. Create a shared tracking document at the outset with owners and due dates assigned per function. For involuntary terminations the process is compressed to same-day and requires all three functions to coordinate in advance, before the termination meeting occurs.

For involuntary terminations: coordinate access revocation to occur simultaneously with the termination meeting

For involuntary separations — layoffs or terminations for cause — the security risk is highest in the window between when the employee learns they are being terminated and when access is revoked. Best practice: IT disables email, systems, and building access at the exact moment the termination meeting begins, coordinated in advance. The employee should have no opportunity to download company data, forward client lists, or delete work files after learning of the termination. This is a systemic precaution, not a presumption of bad intent from every departing employee — the window between notification and access removal is a well-documented vector for data exfiltration. For voluntary resignations this urgency does not apply; the focus shifts fully to knowledge transfer.

Identify the departing employee's critical knowledge — including tacit knowledge, not just documented processes

The common failure mode of knowledge transfer: asking the departing employee to 'document their processes' produces documentation of formal, explicit procedures — not the tacit knowledge that makes them genuinely effective. Tacit knowledge examples: knowing that a key client prefers calls on Friday afternoons, that an internal system has a bug requiring a specific workaround, or that the finance team's pre-close quiet period means the first week of each month is a poor time for cross-functional requests. Methods that elicit tacit knowledge: recorded Q&A sessions where the departing employee walks through their actual work as if explaining to a successor, shadow sessions where the successor observes real work and asks questions in the moment, and scenario walkthroughs — 'What would you do if X happened?' Written documentation captures explicit knowledge; real-time conversation captures the implicit.

Prioritize knowledge transfer by operational criticality and documentation gap — not by what the departing employee values most

A departing employee typically holds more transferable knowledge than two to four weeks allows time to capture. Use a prioritization framework: map responsibilities on a 2×2 of operational criticality versus degree of existing documentation. High criticality combined with low existing documentation is the immediate priority for knowledge capture. Low criticality combined with thorough documentation can be handled by the materials already on file. The most common failure here is spending transfer time on well-documented processes anyone could learn independently, while neglecting undocumented institutional knowledge and relationship context. The manager should own this prioritization — the departing employee will naturally focus on areas they're most invested in, which may not align with what the organization actually needs most.

Schedule structured handover meetings early in the notice period — record them for the successor's ongoing reference

Ad hoc knowledge sharing leaves critical details to chance. Structure the handover as a series of short, topic-focused recorded sessions rather than one long catch-all meeting — recording preserves the nuance of verbal explanations that written documentation loses. Recommended format: 30–45 minutes per session, focused on one major responsibility area, with the departing employee narrating their work live (screen share where applicable) and the successor asking clarifying questions in real time. Schedule these sessions in the first week of the notice period, not the final week — this leaves time to surface follow-up questions and for the successor to attempt tasks independently while the departing employee is still available to course-correct. Store recordings in a shared drive accessible to both the successor and manager after departure.

Prepare the final paycheck — state law governs timing and varies significantly by jurisdiction

Final paycheck timing is governed by state law, not federal law, and the variation is substantial. California requires payment on the last day of work for involuntary terminations and within 72 hours for voluntary resignations with notice. New York requires the next regular payday. Texas requires the next regular payday for voluntary departures and within six calendar days for involuntary. Violations carry penalties, typically ranging from one to three days of wages per day of delay up to statutory caps. The final paycheck must include all hours worked through the final day, accrued and unused vacation or PTO where state law mandates payment (California, Montana, Nebraska, and Illinois require it; many other states defer to company policy), and any bonuses or commissions that have vested. Never withhold the final paycheck pending return of equipment — this is illegal in virtually every state regardless of what the employee handbook states.

Provide COBRA notification within 14 days of the coverage loss event

Under COBRA, employers with 20 or more employees must provide written notice of continuation rights within 14 days of the qualifying event — typically the last day of employment. COBRA allows departing employees to continue group health coverage at their own expense, paying the full premium (both employer and employee share) plus a 2% administrative fee, for 18 to 36 months depending on circumstances. The written notice must include plan descriptions, premium costs, enrollment deadlines (60 days to elect), and coverage duration. State mini-COBRA laws may impose similar requirements on smaller employers. Penalties for failure to provide timely COBRA notice reach $110 per day per qualified beneficiary, plus potential liability for medical expenses the employee incurs due to an undisclosed coverage gap.

Review and confirm NDA, non-solicitation, and IP assignment obligations with the departing employee — in writing

Departing employees often leave unaware of the specific post-employment obligations they agreed to, or aware but unclear on the boundaries. A brief, documented review meeting covering the key provisions of any non-disclosure agreement, non-solicitation clause, and IP assignment agreement creates a clear record that the employee was informed and acknowledged the obligations. Practical approach: prepare a one-page summary of the key restrictions — duration, scope, and prohibited activities — and have the employee sign an acknowledgment confirming receipt. This does not create new obligations; it ensures the employee cannot later claim they were unaware of existing ones. Non-compete enforceability varies significantly by state and has faced increasing scrutiny from the FTC; confirm enforceability in the employee's work state before relying on one as a protective mechanism.

Confirm your company's reference policy and communicate it clearly to the departing employee

Many employees leave without knowing what their former employer will say when a prospective employer calls for a reference. A clearly communicated reference policy reduces uncertainty for the departing employee and protects the company from defamation risk. Standard approaches: title-and-dates-only (confirm employment dates and job title, decline to comment on performance — lowest legal risk), or authorized reference givers (a defined list of managers who can provide fuller references, with HR directing calls to them). Communicate which policy applies and, if applicable, who the departing employee may list as a reference. Document this conversation. For involuntary terminations, a title-and-dates-only policy is especially important — statements about the circumstances of termination carry significant defamation risk even when factually grounded.

Conduct the exit interview — scheduled by HR, not the departing employee's direct manager

The exit interview produces the most candid and actionable data when conducted by someone other than the direct manager, who is the most likely subject of critical feedback. Research supports that employees are substantially more honest when they believe feedback will be used constructively rather than relayed to the person they're assessing. Effective questions: 'What prompted you to start looking?' identifies root cause rather than proximate trigger. 'What could we have done differently to retain you?' produces actionable intelligence. 'What did the best parts of your experience here look like?' reveals what to preserve and replicate. 'Is there anything else that would help us improve?' surfaces issues that don't fit the standard questions. Aggregate data across multiple exit interviews before drawing conclusions — a single departure's feedback reflects one relationship; a consistent pattern across five departures is organizational signal.

#10

Arrange equipment return for remote employees — with a prepaid shipping label and explicit deadline

For remote employees, provide a prepaid, trackable shipping label and appropriate packaging before the final week — ideally a purpose-built laptop return box available from UPS and FedEx. Set a specific return deadline, typically within five business days of the last day, and state the consequences of non-return clearly in writing. Options for non-compliance: deduction from final wages where legally permissible (varies by state — confirm with legal counsel before pursuing this), or recovery through small claims court for the fair market value of the equipment. High-volume companies often use dedicated remote equipment recovery services that handle logistics, packaging, and tracking at scale. Before the device ships back, IT must confirm all company data has been backed up and that a remote wipe has been completed or is staged to execute on receipt.

#11

Retrieve all physical access items — key cards, fobs, parking passes, and company credit cards

Maintain a physical items checklist from the start of employment and use it during offboarding. Items commonly overlooked: parking passes registered to the employee (which may generate ongoing charges), company-issued credit or procurement cards (deactivate with the card issuer on the last day — do not rely solely on returning the physical card, as the account remains open until issuer notification), client-provided building keys or access credentials for external sites, and company-owned peripherals taken home for remote work such as monitors, keyboards, and docking stations. For building access: confirm with facilities management that the key card or fob has been deactivated in the access control system — physical return of the card alone does not revoke access if the card number remains active in the system.

#12

Revoke all access on the last day — coordinated across email, SaaS tools, cloud infrastructure, and physical systems

The access revocation list must be comprehensive. Disable email and calendar accounts, then configure an auto-reply informing contacts and an auto-forward to the manager for time-sensitive items. Deactivate communication platforms such as Slack or Microsoft Teams and remove the employee from all channels and groups. Remove access to cloud storage platforms, confirming that no company documents reside exclusively in the employee's personal storage folders. Deprovision every SaaS application the employee held credentials for — this list is frequently longer than IT's records reflect. Remove code repository access and confirm no active SSH keys or personal access tokens remain. Revoke cloud infrastructure roles in AWS, GCP, or Azure and deactivate any API keys. A persistent gap in most offboardings: tools provisioned informally without IT visibility remain active indefinitely — a shadow IT audit during offboarding routinely surfaces five to fifteen applications never recorded in the official system inventory.

#13

Preserve and transfer company data before wiping returned devices

Before executing any device wipe, IT should confirm that all company data has been transferred to company-controlled storage. Data at risk: documents saved locally rather than to cloud storage, browser-saved passwords for company tools, application data stored in local directories, and for legacy setups, email stored in local mail client archives rather than synced to the server. For roles where significant work was stored locally, image the device before wiping it and retain the image for at least 90 days before permanent deletion. Use the manufacturer's certified erase process or an MDM-driven remote wipe. Document the wipe with a timestamped record identifying the device, the method used, the person who performed it, and the date — this record serves compliance purposes in regulated industries.

#14

Communicate the departure to the team — with timing and messaging agreed between HR and the manager before it's delivered

How a departure is communicated to the team shapes morale and how the departing employee is remembered within the organization. Agree on the message in advance: what the employee is moving on to (if they have consented to share), what the transition plan looks like, and where the team should direct questions in the interim. For voluntary departures, the departing employee should have a role in shaping the announcement — being blindsided by a message they didn't agree to is a poor final experience. For involuntary departures, the communication should be prompt (same day where possible), factual, and free of any explanation of the reason for termination. Delayed team communication creates a rumor vacuum that is harder to manage than the original announcement. Confirm with legal counsel whether any WARN Act notification obligations apply if the departure is part of a larger reduction.

#15

Ensure the final experience is positive — departing employees are future references, clients, and candidates

Research on boomerang employees — former staff who return to a previous employer — finds that roughly 15% of new hires at organizations with structured alumni engagement are returnees, and they typically ramp faster and perform better than first-time hires because they already understand the culture and systems. Beyond boomerangs, departing employees shape employer brand through public reviews, informal industry references, and word-of-mouth in their next roles. The practical investment in a positive departure experience is minimal: a genuine team acknowledgment, a personal note from the manager, accurate final pay and paperwork completed without delays, and a direct conversation signaling that the door remains open. Organizations that treat offboarding primarily as a compliance-and-security exercise — rather than a relationship transition — create alumni who describe the experience negatively, with lasting effects on hiring, client development, and referrals.

#16

Schedule a 90-day post-departure check-in with the successor to surface knowledge gaps that emerged after the transition

The gaps in a knowledge transfer rarely surface during the transfer itself — they emerge when the successor encounters a situation the departing employee handled routinely but never thought to document. A structured 90-day check-in between the manager and successor surfaces these gaps while there is still an opportunity to address them: through additional documentation, targeted training, or in some cases a brief outreach to the former employee where the relationship permits. This check-in also reveals whether the handover period was sufficient — a consistent pattern of material knowledge gaps at 90 days across multiple departures signals that notice periods are too short or knowledge transfer processes are too superficial. Log the findings and use them to improve the offboarding template for future departures.

#17

📖 The 11-minute window

In a case studied by the Ponemon Institute, a departing sales manager downloaded the company's full customer database 11 minutes after a resignation conversation with HR. The company's access revocation process required a ticket to IT — which typically took four to six hours to execute. The data surfaced at a competitor within 30 days. Total estimated damage: $2.1 million in lost contracts. The policy that would have prevented it cost nothing to implement: a direct line from HR notification to an IT access-hold trigger, executed the moment notice was received.

🧮 Counting the full cost

IBM's annual Cost of a Data Breach Report consistently places insider threats — including departing employees — among the costliest breach sources, averaging higher remediation costs than external attacks. Stack the legal exposure on top: COBRA non-notification penalties, state final pay violations, and the measurable productivity loss from knowledge gaps at 90 days post-departure, and a single poorly executed offboarding can cost between $15,000 and $50,000 before any litigation enters the picture. The checklist items above address each of these vectors individually. This section is about understanding why they compound.

⚖️ What NDAs actually protect — and where they fall short

A well-drafted NDA protects legitimate trade secrets: client lists built using company resources, proprietary pricing structures, internal formulas and processes. What it cannot protect — and what courts consistently reject — is the employee's general professional skills, accumulated industry expertise, and personal relationships that predated or developed independently of employment. This distinction matters more than most employers realize when they're relying on an NDA as their primary post-departure protection.

The enforcement economics are sobering. NDA violations are civil matters requiring the company to discover the violation, document demonstrable harm, and bring a case — a process that typically costs $50,000 to $200,000 in legal fees before any judgment is entered. This is precisely why the prevention side of offboarding — data preservation, access revocation, and the documented acknowledgment conversation — generates a far better return than enforcement after the fact.

On non-competes specifically: the FTC's 2024 rule banning most non-compete agreements was blocked in federal court and remains in active litigation, but California, North Dakota, Minnesota, and Oklahoma already prohibit them by state law. If your offboarding strategy relies on a non-compete to prevent competitive harm in any of these states, you may have meaningfully weaker protection than assumed. Customer non-solicitation clauses — narrower in scope and more consistently enforced — are generally the more defensible instrument.

💬 What to actually say to the team

Most departure announcements fail in one of two ways: they are so brief they invite speculation, or so effusive they feel hollow. The announcement that lands well is factual, forward-looking, and visibly respects the departing employee's privacy. A working template for voluntary departures:

"[Name] has decided to pursue a new opportunity and their last day with us will be [date]. We are grateful for [one specific, concrete contribution]. [Name or role] will be handling [key responsibilities] during the transition. Please join me in wishing [Name] well."

What this omits on purpose: the destination company (let the employee share that on their own terms), the reason for leaving (not yours to explain), and any editorial judgment on whether the departure is good or bad for the team. Both are visible to perceptive readers and both undermine the tone you want.

For involuntary departures: replace the contribution line with "[Name] is no longer with the company as of [date]" and redirect questions to HR. Do not explain the circumstances — even when you believe the team deserves transparency. Employment decisions are private, and partial explanations create more questions than silence. If the departure is part of a larger restructuring with WARN Act implications, confirm notification obligations with legal counsel before any team communication goes out.

📞 The reference call: what actually happens

Most HR professionals have absorbed the idea that employers can "only confirm title and dates" — but this is a policy choice, not a legal requirement in most states. The legal risk in providing a fuller reference is defamation: a false statement of fact that damages the employee's reputation. Truthful, accurate statements — even negative ones — are generally not defamatory. The practical implication: the legal risk of honest, accurate feedback is considerably lower than widely believed; the risk of providing it inaccurately — exaggerating, generalizing, or framing opinion as established fact — is real and avoidable.

For departing employees navigating their own reference list: the most useful references are former managers who observed their work directly and can speak to specific outcomes. Experienced interviewers discount vague positives immediately. References that say "rebuilt the client onboarding process, cutting time-to-value by 40%" carry far more weight than "great team player, highly recommend." Coaching departing employees on what their references might say — not to coordinate stories, but to surface accurate specifics — is a professional courtesy that most managers never think to offer and that costs nothing to extend.

✅ Organizations that treat alumni as assets

McKinsey, Microsoft, and Deloitte maintain active alumni networks that generate substantial and measurable business value — former employees as clients, as senior recruits, and as referral sources. McKinsey's alumni network of over 30,000 people is widely credited as one of its most durable competitive advantages, not despite the high rate of departures, but because of how consistently those departures are handled. The common thread across all three: a departure experience that is treated as a professional transition, not an administrative termination.

🔧 The minimum viable alumni touchpoint

You don't need a dedicated alumni portal or a dedicated headcount to run one. The minimum viable version: a LinkedIn group, an optional quarterly email to former employees, and a clear behavioral signal from the organization that the door remains open for future collaboration. The signal that matters most is not the infrastructure — it is the departure experience itself. No alumni newsletter repairs a departure where the employee was walked out without warning and never received a personal word from their manager.

🔍 Auditing your own offboarding process

Most organizations discover offboarding gaps reactively — after a security incident, a legal notice, or a boomerang candidate who reports a poor departure experience. A proactive audit takes two hours and requires three inputs: your last five offboarding records, your IT system access log, and your HR case files for those same departures.

→Access log gap: For each departure, compare the last-day timestamp on the employee record against the access disable timestamp in IT's system. A gap of more than four hours on the last working day is a process failure — and a gap that crosses into the next calendar day is an active exposure.
→COBRA timing: Pull the date the COBRA notice was mailed against the last day of employment for each case. A gap exceeding 14 days represents potential penalty exposure — multiplied by every qualified beneficiary on the employee's plan.
→Knowledge transfer evidence: Is there a documented handover plan, a recorded session, or a successor sign-off for each departure in the sample? If not, the transfer existed only in conversation — and the institutional knowledge left with the employee.
→Exit interview completion rate: What percentage of departures in the last 12 months produced a completed exit interview? Anything below 80% means your organizational intelligence on departures is systematically incomplete — and the patterns that would tell you why people are leaving are invisible to you.

Master This Checklist Quickly

Every important button and option for this pre-made checklist, shown in a glance-friendly format.

Start Here

1
Click any item row to mark it complete.
2
Use the note row under each item for quick notes.
3
Use the tool row for undo, redo, reset, and check all.
4
Use Save Progress when you want to continue later.

Checklist Row Tools

UndoRedoResetCheck allCollapse/Expand sectionsShow/Hide detailsInline notes

Top Action Buttons

Open all sharing and export options in one menu.

Email DraftContinue on another devicePrint or Save as PDFPlain Text (.txt)Word (.docx)Excel (.xlsx)

Add & Ask

Open one menu for apps and AI guidance.

NotionTodoist CSVChatGPTClaude

Copy and customize

Create a new editable checklist pre-filled with your chosen content.

Save Progress

Adds this checklist to My Checklists and keeps your progress in this browser.

Most Natural Usage

Track over time

Check items -> Add notes where needed -> Save Progress

Send or export

Open Share -> Choose format -> Continue

Make your own version

Copy and customize -> Open create page -> Edit freely