offboarding-checklist

$npx mdskill add Significant-Gravitas/skills-catalog/offboarding-checklist

Use this once the leaving date is confirmed by HR.

SKILL.md

.github/skills/offboarding-checklistView on GitHub ↗
---
name: "offboarding-checklist"
description: "Build an offboarding checklist for access, equipment, knowledge handover, and farewell."
triggers: ["offboarding", "employee leaving", "exit checklist", "last day", "handover"]
version: "1"
---

# Offboarding checklist

Use this once the leaving date is confirmed by HR.

## Confirm the facts

Ask for the last working day, the manager, the systems and tools the person
uses, equipment they hold, work in progress, and whether the leaving is public
yet. Leave the reason for leaving out of the checklist. Ask HR which steps
they own, such as final pay, benefits, and documents.

## Build the checklist

- Knowledge: open work, documents, contacts, and who takes each over.
- Access: every account to remove or transfer, at the separation time approved
  by HR and security. Use the end of the last day only for an ordinary
  departure when they confirm it.
- Equipment: what to return, and how.
- Customers and partners: who needs to know, and who tells them.
- Farewell: how and when the team hears, and any goodbye.
- HR items, listed as owned by HR.

## Owner and date for each item

Put an owner, a date, and a status on every line. Flag anything with no owner.

Never comment on the reason for leaving, pay, notice, or legal terms; send
those to HR. Do not remove access, message staff, or change an HR record
yourself; each owner does their item.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.