---
name: offboarding-checklist
description: Use when asked to build or run an employee departure checklist — access revocation, equipment return, knowledge transfer, final pay, and team communication — for a voluntary or involuntary exit, as distinct from the exit-interview conversation itself, which captures feedback rather than executing logistics.
---

# Offboarding Checklist

An offboarding checklist is the operational process that runs when an
employee leaves an organization: it makes sure access is revoked,
equipment comes back, outstanding work gets handed off, and final pay
and benefits are settled — regardless of whether the departure was the
employee's choice or the company's. It's a logistics document, not a
feedback-gathering one; the conversation about why someone is leaving
belongs in [[exit-interview]].

## Key components

- **Access and credential revocation** — disabling accounts, badges,
  VPN, email, and any third-party or customer systems the person could
  reach, timed to the last day (or immediately, for an involuntary
  departure — see below).
- **Equipment and asset return** — laptop, phone, badge, keys, and any
  company property, with a clear owner tracking what's returned and
  what's outstanding.
- **Knowledge transfer** — documenting in-progress work, handing off
  active projects and relationships, and identifying who inherits each
  responsibility, so the departure doesn't leave silent gaps.
- **Final pay and benefits wrap-up** — last paycheck, unused
  PTO payout, benefits continuation (e.g. COBRA in the US), and any
  equity or retirement plan handling, per policy and local law.
- **Team and stakeholder communication** — a clear, timely message to
  the team and any external contacts about who's leaving, when, and who
  to route their work to going forward.
- **Documentation** — the signed record that each step was completed,
  which matters both operationally and, for involuntary departures,
  legally.

## Timing: before, on, and after the last day

- **Before the last day** — plan knowledge transfer, identify what
  needs to be documented, and (for a voluntary departure with notice)
  begin transitioning relationships and access gradually.
- **On the last day** — collect equipment, complete final
  paperwork, and revoke access no later than end of day.
- **After the last day** — process final pay, confirm benefits
  transitions, and follow up on anything still outstanding (a returned
  laptop that didn't arrive, a system access that's still live).

## Voluntary vs. involuntary departures

The checklist's shape is the same, but the sequence isn't: a voluntary
departure with two weeks' notice allows access to stay live and
knowledge transfer to happen gradually and collaboratively. An
involuntary departure (termination, layoff) generally calls for access
revocation *at the moment of notification*, not end of day, and
knowledge transfer has to happen without the departing employee's
ongoing cooperation — often by having a manager or teammate reconstruct
what's needed from existing documentation and systems rather than a
handoff conversation.

## Common pitfalls

- **Access revoked late or not at all** — an ex-employee retaining
  system, email, or building access even a day past their last day is
  a real security risk, not a paperwork loose end.
- **No knowledge transfer plan** — work quietly stalls weeks later when
  someone discovers the departed employee was the only one who knew
  how a process, credential, or relationship worked.
- **One checklist run identically for every departure** — applying the
  voluntary sequence (gradual access wind-down, collaborative handoff)
  to an involuntary departure creates security and legal exposure;
  applying the involuntary sequence (abrupt, minimal-contact) to an
  amicable departure damages the relationship for no reason.
- **Equipment return tracked informally** — "I think they gave it
  back" is not a record; untracked equipment becomes a lost-asset
  problem months later.
- **No named owner for the checklist** — offboarding spans IT, HR,
  facilities, and the manager; without one person accountable for the
  whole list, individual steps get assumed to be someone else's job.
- **Team told too late or too vaguely** — leaves colleagues fielding
  questions from the departing employee's contacts with no idea what
  to say or who owns the work now.

## Learn more

- [[exit-interview]] for the separate feedback conversation that often
  runs alongside offboarding but serves a different purpose.
- [[employee-onboarding]] for the mirror-image process on the way in.
- [[performance-improvement-plan]] for one path that can lead to an
  involuntary departure.
- [[incident-response-plan]] for the same "who's accountable, what's
  the sequence" discipline applied to a security or operational event.