QUICK ANSWER
What should an employee offboarding checklist include?
An employee offboarding checklist should include an authorized trigger, stable record ID, role owners, last-working and effective dates, scope, access and vendor inventory, knowledge and organizational-data handoffs, asset custody, payroll, benefits, legal-records and communication routing, sanitized evidence, bounded exceptions, and closure criteria. It should distinguish scheduled work from observed outcomes and keep local employment, pay, benefits, retention, privacy, and security decisions with qualified owners.
An employee offboarding checklist coordinates what happens after an authorized separation trigger. It gives each operational task a role owner and date, inventories system and vendor access, tracks organizational data and knowledge handoffs, retrieves assets, routes payroll, benefits, and records questions to qualified owners, and closes only from recorded outcomes.
This downloadable pack includes an editable worksheet, a valid JSON starter, a completed fictional example, a closed JSON Schema, and a dependency-free validator with deterministic mutation tests. It is not a termination policy, employment decision, exit-interview script, legal or HR advice, identity platform, payroll calculator, benefits determination, retention schedule, or proof that every account, asset, record, payment, notice, or dispute was resolved.
Coordinate separation from trigger to evidence-based closure
Start from approved authority, preserve sensitive source records outside the checklist, and make every operational owner, date, dependency, outcome, exception, and limitation explicit.
Open the record from an authorized trigger
Assign a stable offboarding ID, revision, separation category, confidentiality level, last-working and effective dates, initiating role, local policy reference, jurisdiction owner, scope, and explicit exclusions. The checklist coordinates an already authorized action; it does not decide whether employment should end or record sensitive allegations.
Sources: [offboarding-pack], [nist-800-53]
Inventory identity, system, physical, shared, and vendor access
List organizational accounts, authenticators, privileged roles, shared access, temporary accounts, work identities used with outside services, vendor portals, physical access, and relevant service relationships. Assign an owner, planned cutoff, expected terminal state, and evidence requirement. Organization policy and risk owners determine timing.
Sources: [nist-800-53], [ncsc-iam], [ncsc-saas]
Plan knowledge, work, data, vendor, and asset handoffs
Give each bounded handoff a from-role, to-role, scope, due date, completion state, and sanitized evidence. Transfer only approved organizational information. Track devices, badges, keys, and documents through custody references rather than copying serial numbers, addresses, secrets, or raw case data into a broad checklist.
Sources: [offboarding-pack], [nist-800-53]
Route pay, benefits, tax, and records questions to qualified owners
Create tasks for payroll, plan administration, employment counsel, tax, privacy, and records owners to apply the relevant jurisdiction, employer coverage, plan terms, contracts, open claims, and legal holds. Record routing and evidence without hardcoding a universal final-pay date, COBRA result, or retention period.
Sources: [dol-last-paycheck], [dol-cobra], [eeoc-recordkeeping], [irs-recordkeeping]
Execute elsewhere and verify the actual outcome
Authorized systems and owners perform access, transfer, custody, payroll, benefits, and communication actions. The checklist records actual cutoff or completion timestamps plus sanitized evidence. A request, ticket, scheduled job, or successful API response is not automatically proof that the intended outcome occurred across every system.
Sources: [offboarding-pack], [nist-800-53], [ncsc-iam], [ncsc-saas]
Bound exceptions and close only when the graph is terminal
Link each exception to affected records, an approver role, approval and expiry times, compensating controls, evidence, and resolution state. Close only when tasks and handoffs are terminal, access is revoked or transferred, assets are returned, exceptions are resolved, and the unresolved list is empty. Keep all legal, security, accuracy, completeness, and consent boundaries false.
Sources: [offboarding-pack], [nist-800-53]
The employee offboarding checklist boundary
Use this owner for evidence-linked operational separation coordination. Reference adjacent policies and systems without absorbing their authority or sensitive data.
Included
- Record ID, revision, separation category, operational status, dates, initiating role, confidentiality, policy reference, jurisdiction owner, scope, and exclusions
- Standard, privileged, shared, temporary, physical, third-party, vendor, and organizational-identity access inventory with planned and actual outcomes
- Knowledge, work, organizational-data, customer, and vendor handoffs with role owners, dates, states, sanitized evidence, and limitations
- Devices, badges, keys, documents, and other property represented by safe custody references and return evidence
- Payroll, benefits, tax, employment, records, privacy, communication, and vendor tasks routed to qualified owners
- Approved exceptions with related records, expiry, compensating controls, evidence, resolution, unresolved IDs, and closure review
Not included
- Employee onboarding, candidate or contractor intake, the underlying employment decision, performance management, disciplinary findings, or a general termination policy
- A universal termination script, severance agreement, exit-interview-only form, legal opinion, final-pay calculation, benefits eligibility decision, tax filing, or retention schedule
- Live identity orchestration, account discovery, credential revocation, data migration, asset retrieval, payroll execution, notice delivery, or vendor-contract action
- Personal email addresses, home addresses, health information, sensitive allegations, credentials, secrets, raw logs, payroll detail, or unrestricted evidence copies
- Proof of legal compliance, fairness, payroll accuracy, benefits-notice compliance, complete revocation, complete transfer, custody, retention, consent, dispute resolution, or absence of a security incident
DOWNLOADABLE RESOURCE
Download the employee offboarding checklist pack
Use the Markdown worksheet for a coordinated review or the JSON starter for a bounded workflow. Inspect the fictional example, closed schema, validator, and mutation tests before adapting the record.
Employee offboarding checklist and evidence pack
A fictional voluntary separation connecting three access outcomes, two asset returns, three handoffs, ten cross-functional tasks, fourteen sanitized evidence records, one resolved exception, and bounded closure.
Format: Markdown, JSON, JSON Schema, and dependency-free Node.js validator/tests in one ZIP
Locally reproduced August 1, 2026. SHA-256: 1721866d7094fde8a077b6e314b7ccf8d2c1ca3abd907862a57cbe3d4d116e72
Included
- Editable Markdown worksheet and a valid JSON draft starter
- Completed fictional JSON example using role-safe IDs and HTTPS `.test` evidence references
- Closed Draft 2020-12 JSON Schema covering every root and nested object shape
- Dependency-free semantic validator for exact keys, IDs, references, UTC chronology, terminal evidence, exceptions, closure, safe URLs, and all-false boundaries
- Thirty-two deterministic tests covering valid records and rejected unsafe or contradictory mutations
- README, package commands, fixed timestamps, exact file allowlist, and reproducible ZIP bytes
Verification boundary
Validated the starter and completed example, passed 32 valid-record and mutation tests, checked closed object shapes and references, rebuilt across three time zones, copied an exact nine-file allowlist, stripped ZIP metadata, and reproduced the same archive hash.
Three employee offboarding patterns
The evidence graph stays stable while timing, applicable rules, risk, handoff scope, and responsible owners change. Qualified local owners still control every real case.
Planned voluntary departure
Use when: An authorized resignation provides time to plan knowledge transfer, organizational-data ownership, asset return, access cutoff, pay review, benefits routing, and approved communication.
Open the record from the accepted trigger, inventory access and property early, stage bounded handoffs, let qualified owners determine applicable pay and benefits work, then capture actual outcomes before closure.
Structure
- Last-working and effective dates remain distinct when local policy requires it
- Scheduled actions stay separate from actual cutoff, return, transfer, and notice evidence
- No personal case detail is copied into the shared operational graph
Watch for: Notice, pay, benefits, confidentiality, retention, and communication requirements vary. A longer planning window does not prove that discovery or handoffs are complete.
Sources: [offboarding-pack], [nist-800-53], [dol-last-paycheck], [dol-cobra]
Employer-initiated separation with restricted timing
Use when: Qualified employment and security owners have authorized a separation whose notification, access, evidence, safety, privacy, and communication timing requires tighter coordination.
Restrict the record, separate decision authority from operational execution, use role owners and need-to-know handoffs, inventory privileged and shared access, and preserve verifiable outcomes without exposing allegations or legal analysis.
Structure
- Employment, legal, safety, and security owners define timing outside the template
- Access actions cover credentials, authenticators, property, shared access, and organizational continuity
- Personnel-record retention and open matters receive qualified applicability review
Watch for: This pack does not recommend pre-notification disablement, establish cause, direct an exit meeting, resolve a dispute, or replace counsel, policy, safety, or incident response.
Sources: [nist-800-53], [ncsc-iam], [eeoc-recordkeeping]
Internal role change or extended transfer
Use when: A person remains employed but old logical, physical, shared, or vendor access and work ownership must be reviewed because operational need changed.
Use the same inventory and evidence structure, set separationType to role_change, remove or modify access that is no longer required, transfer ownership, and keep the record open until the defined changes are verified.
Structure
- Ongoing access is reviewed against the new role rather than automatically retained
- Old privileges, physical access, vendor identities, and temporary accounts remain in scope
- The record does not present an internal transfer as termination of employment
Watch for: Role-change timing and authorization are organization-defined. The checklist does not discover every identity, alter permissions, or prove least privilege.
Sources: [nist-800-53], [ncsc-iam], [ncsc-saas]
Decide whether the offboarding record can close
The validator can reject broken references and contradictory states. Qualified owners still decide applicability, authorization, timing, evidence sufficiency, exception acceptance, and real-world closure.
The employment decision, separation authority, effective date, jurisdiction owner, or need-to-know scope is unclear or disputed.
Choose: Keep the checklist in draft and return those decisions to the authorized people, employment, legal, safety, or security process.
Tradeoff: Operational work waits, but the checklist does not become an unofficial termination decision or leak sensitive case detail.
An account, authenticator, shared secret, vendor portal, temporary identity, privileged role, or physical-access path may exist but has no owner or planned outcome.
Choose: Keep discovery and access work open, assign the relevant system owner, and define evidence for the actual outcome.
Tradeoff: Closure takes longer, but a directory-only list is not mistaken for a complete access inventory.
A payroll, benefits, tax, retention, notice, privacy, contract, or legal-hold question is being answered from a generic checklist.
Choose: Route the question to the qualified owner who can apply the jurisdiction, employer coverage, plan, contract, record type, and facts.
Tradeoff: The record avoids a quick universal answer, but it does not manufacture a deadline or compliance result.
A ticket exists, but the actual access, handoff, asset, communication, payroll, benefits, or records outcome is unobserved.
Choose: Record the request separately and keep the item nonterminal until sanitized evidence supports the intended outcome.
Tradeoff: Completion waits, but activity is not mislabeled as verification.
Access is temporarily retained, an asset is unresolved, a handoff is blocked, or another deviation is necessary.
Choose: Create a linked exception with an approver role, expiry, compensating control, monitoring evidence, and resolution requirement.
Tradeoff: The exception remains visible and prevents clean closure until its defined risk treatment ends.
Every listed item is terminal and evidenced, but completeness across shadow IT, personal devices, outside services, records, or legal duties is unknown.
Choose: Close only the bounded checklist graph and preserve every claim boundary as false.
Tradeoff: The record can finish operationally without overclaiming universal discovery, legality, security, or completeness.
START WITH THE BOUNDED RECORD
Download and validate the offboarding checklist graph
Open the worksheet or JSON starter, inspect the fictional completed example, and run the dependency-free mutation tests before adapting the record.
Download the offboarding checklist packThe ZIP is reproduced locally. Public availability, local requirements, data handling, evidence sufficiency, access outcomes, notice delivery, and real closure require separate verification.
Keep joining and early role enablement in the onboarding checklistUse this page for separation and old-role access closure. Use the onboarding owner for preboarding, provisioned access, first-day readiness, enablement, and early follow-up.
What an employee offboarding checklist cannot prove
A structured checklist improves ownership and traceability. Its conclusions remain limited by discovery coverage, source-system accuracy, timing, evidence quality, access to records, local policy, jurisdiction, plan terms, vendor capabilities, and reviewer judgment.
- An authorized trigger in the checklist does not establish that an employment decision was lawful, fair, final, or communicated correctly.
- An access inventory can miss shadow IT, shared credentials, personal devices, outside services, dormant accounts, integrations, service identities, physical paths, and copied data.
- A completed request or automation response does not independently prove that access was revoked everywhere or remained disabled afterward.
- A recorded handoff does not prove that every organizational record was discovered, transferred lawfully, understood, or usable by the next owner.
- A custody receipt does not prove that every asset was listed, undamaged, sanitized, shipped safely, or handled under every applicable requirement.
- Federal examples for pay, benefits, tax, and employment records are not universal deadlines. Applicability and longer state, local, contractual, plan, claim, or legal-hold duties require qualified review.
- Checklist closure does not prove legal compliance, payroll accuracy, benefits-notice compliance, security, retention, consent, dispute resolution, or absence of an incident.
- This ordinary informational article does not grant AI signup credits. The linked product page follows its own current eligibility rules.
Sources and verification record
The same-release artifact supports the fictional record and validator claims. Current first-party government guidance supports the operational model without certifying this pack or making one jurisdiction, employer, plan, or security catalog universal.
[offboarding-pack] Playcode:Fictional employee offboarding example
Checked August 1, 2026. Supports: The locally reviewed fictional record, role and evidence graph, mutation tests, and reproducible archive. Public availability remains unverified until deployment.
[nist-800-53] National Institute of Standards and Technology:NIST SP 800-53 Rev. 5, Security and Privacy Controls
Checked August 1, 2026. Supports: PS-4 personnel termination, PS-5 personnel transfer, and aligned account-management concepts for organization-defined timing, credential revocation, property retrieval, organizational continuity, access review, and notification. This flexible security-control catalog is not employment law or proof of implementation.
[ncsc-iam] UK National Cyber Security Centre:Identity and access management
Checked August 1, 2026. Supports: Joiner, mover, and leaver access processes plus organizational identities on outside services, temporary accounts, third-party access, privileged review, audit records, and revocation. This is UK security guidance, not employment or privacy law.
[ncsc-saas] UK National Cyber Security Centre:Using Software as a Service securely
Checked August 1, 2026. Supports: Lifecycle coverage for internal and external SaaS users, service identities, integrations, automation where supported, periodic review, and revocation. It does not prove that this pack performs identity automation.
[dol-last-paycheck] U.S. Department of Labor:Last Paycheck
Checked August 1, 2026. Supports: The federal-level statement that immediate final pay is not universally required by federal law while state rules can differ. It supports qualified local payroll routing, not a universal deadline or payment calculation.
[dol-cobra] U.S. Department of Labor Employee Benefits Security Administration:An Employer's Guide to Group Health Continuation Coverage Under COBRA
Checked August 1, 2026. Supports: Applicability, qualifying-event, plan-administrator, employer-notice, and timing concepts for covered U.S. group health plans. Plan terms, employer coverage, facts, administrator roles, and state rules still require qualified review.
[eeoc-recordkeeping] U.S. Equal Employment Opportunity Commission:Recordkeeping Requirements
Checked August 1, 2026. Supports: Selected personnel, involuntary-termination, payroll, benefit-plan, compensation-basis, and charge-related retention duties for employers covered by the cited federal laws. It is not a complete or universal retention schedule.
[irs-recordkeeping] Internal Revenue Service:Employment Tax Recordkeeping
Checked August 1, 2026. Supports: Federal employment-tax record categories and retention guidance. It supports routing to payroll and tax owners, not treating the tax rule as a complete personnel-record schedule.
Employee offboarding checklist questions
What is an employee offboarding checklist?
It is an operational coordination record used after an authorized separation trigger. It connects dates and role owners to access, handoffs, assets, administrative routing, evidence, exceptions, and closure. It is not the underlying employment decision or a general termination policy.
What should an employee offboarding checklist include?
Include a stable record ID, last-working and effective dates, scope, role owners, access and vendor inventory, knowledge and organizational-data handoffs, asset custody, payroll, benefits, records and communication tasks, sanitized evidence, exception controls, unresolved items, and bounded closure criteria.
When should access be revoked during employee offboarding?
The approved organization policy and qualified employment, security, and system owners should define timing from the facts and risk. NIST deliberately uses an organization-defined period. This template records the planned cutoff and actual evidenced outcome; it does not prescribe or execute a universal cutoff.
Is an offboarding checklist the same as a termination policy?
No. A termination or separation policy establishes authority, rules, decision rights, and required processes. This checklist coordinates bounded operational work after an authorized trigger. It also covers voluntary departures and internal role changes without deciding employment status.
How should final pay, benefits, and records be handled?
Route each question to qualified payroll, benefits or plan, tax, employment, privacy, and records owners. Applicable deadlines and duties can depend on jurisdiction, employer coverage, plan terms, contracts, record type, open claims, and legal holds. Do not copy a generic deadline into every case.
How should an offboarding exception be recorded?
Link the exception to affected access, asset, handoff, or task IDs. Record a reason, approver role, approval time, expiry, compensating control, evidence, and state. Keep the checklist open until the exception is resolved and the final outcome is evidenced.
Can Playcode build an employee offboarding workflow?
Playcode can help build a bounded internal workflow from a reviewed schema, roles, states, evidence rules, and integration boundaries. Before operational use, verify authentication, authorization, restricted-data handling, audit, notifications, integrations, failure recovery, retention, monitoring, backup, and release control. The article does not perform identity or HR actions.
BUILD THE REVIEWED OFFBOARDING WORKFLOW
Turn the approved checklist into a bounded internal tool
Give Playcode the reviewed roles, states, evidence contract, exception rules, access boundaries, handoff model, and closure criteria. Verify restricted access, audit, integrations, notification delivery, failure handling, retention, monitoring, backup, recovery, and release control before operational use.
Build and verify the internal workflowThis informational article does not grant AI signup credits. No employment decision, legal sufficiency, payroll accuracy, benefits outcome, notice compliance, revocation, transfer, custody, retention, security, privacy, consent, dispute resolution, or complete offboarding outcome is guaranteed.