All templates

Offboarding Checklist

Capture departing employee knowledge, revoke access, and ensure smooth, professional transitions. Try it in Elium.

Example: Fictional content for illustration purposes

Offboarding: Marie Kowalski (Senior Project Engineer, Brussels)


Department
Infrastructure Projects
Status
In Progress
Manager
TLThomas Laurent
Last Working Day
28/02/2026

📚 Knowledge transfer

ItemRecipientStatus
Lyon metro extension: risk register + supplier contactsDavid LefevreDone
Quality inspection procedures: QC-SITE templates + training notesEmma HurteauxIn Progress
Client relationship notes: Métropole de Lyon + SNCF RéseauThomas LaurentNot Started

🔒 Access and equipment

TaskOwnerDeadlineStatus
Deactivate AD account + VPNIT Ops28/02Scheduled
Return laptop + mobile phoneMarie K.28/02Pending
Transfer shared mailbox ownershipIT Ops25/02Done

📝 Administrative tasks

  • Exit interview: Scheduled 26/02 with HR (Sophie Petit)
  • Final payroll: Accrued leave (14 days) included in February pay run
  • Reference policy: Standard company reference letter issued on request
This is an example. Create yours in Elium

The Offboarding Checklist Template ensures nothing gets missed when someone leaves: access revocation, equipment return, knowledge transfer, and exit interviews. It protects your organisation and gives departing employees a clean, professional send-off. It's the process nobody thinks about until something goes wrong.

Category

HR & People

Try this template in Elium

What is it?

An offboarding checklist is a structured document that lists every task required when an employee leaves the organisation, covering knowledge transfer, access revocation, equipment return, and administrative closure. It assigns each task to a responsible person with a deadline so nothing falls through the cracks.

Offboarding is where organisations lose knowledge. When an employee resigns, the focus shifts to finding a replacement, and the departing person’s expertise walks out the door undocumented. A standardised checklist ensures that knowledge transfer happens before the last day, system access is revoked on schedule, and the transition is managed consistently regardless of department or seniority. Without one, each departure is handled ad hoc, and critical gaps only surface weeks later.

Who should use this template?

This template is for teams responsible for managing employee transitions:

  • HR Business Partners: ensure every departure follows the same structured process across departments and locations

  • Line Managers: coordinate knowledge transfer, task reassignment, and team communication before the employee’s last day

  • IT Administrators: revoke system access, recover devices, and transfer digital assets on the correct dates

  • Knowledge Managers: capture institutional knowledge before it leaves the organisation permanently

How to create this template in Elium

  1. Open the Template Builder: Go to your profile menu and select the Template Builder tab, or click “+ Create” and choose “Create a new template”.

  2. Set the scope: Choose an icon, enable the template, and decide whether it applies platform-wide or to specific spaces (e.g. HR only).

  3. Add structured fields: Click “Field” to add metadata: text fields for employee name and department, a date field for last working day, a user field for responsible manager, a tag field for status (pre-populate with “Initiated”, “In Progress”, “Completed”), and a text field for replacement. Mark employee name and last working day as mandatory.

  4. Build the offboarding structure: Use the “+” button to add content blocks: a checklist block for knowledge transfer items, a checklist block for access and equipment tasks, a text block for administrative tasks, a text block for the communication plan, and a text block for sign-off confirmations.

  5. Preview and save: Review the template layout, then save. HR and managers can now select it when initiating an offboarding, and you can apply it to existing content in bulk.

How AI helps

Capture faster. Tell Elium’s AI the departing employee’s role and department. It generates a tailored offboarding checklist pre-populated with relevant systems, typical handover documents, and standard administrative steps for that function, so the manager customises rather than builds from scratch.

Retrieve smarter. An HR partner asks Elium’s AI: “What knowledge transfer steps did we follow for the last senior engineer who left the Brussels office?” The AI returns the specific checklist, handover items, and lessons learned, so best practices from previous departures inform the current one.

Why teams use Elium for this

Every departure is a knowledge risk. The cost is not just replacing the person. It is reconstructing what they knew. When offboarding is managed through scattered emails, undocumented knowledge vanishes and access revocation is delayed. Elium makes offboarding systematic: structured checklists ensure consistency, knowledge transfer is captured in searchable articles, and completed offboardings become reference material for future transitions.

Bouygues Construction, with 53,500 employees across 80 countries, uses Elium to centralise people and operational knowledge. When employees transition between roles or leave the organisation, their knowledge stays accessible to colleagues across the business.

FAQ

Common questions about offboarding checklist templates

An offboarding checklist is a structured list of tasks to complete when an employee leaves, covering knowledge transfer, access revocation, equipment return, and administrative closure. Without one, departures are handled inconsistently, critical knowledge is lost, and security risks arise from delayed access removal.

A complete offboarding checklist includes employee details and departure date, knowledge transfer tasks with named recipients, system access and equipment return items, administrative steps (payroll, benefits, exit interview), a communication plan, and sign-off confirmations from HR, the manager, and IT.

Standardised offboarding reduces knowledge loss because transfer steps are completed before the last day. It improves security because access is revoked on schedule. It creates consistency across departments and locations. It also generates reusable handover documentation that helps successors get up to speed faster.

Start with the most time-sensitive items: knowledge transfer and access revocation. Break each area into specific, actionable tasks with a named owner and deadline. Include both obvious steps (return laptop) and easily forgotten ones (transfer shared mailbox ownership, update external contact lists). Review and improve the checklist after each departure.

Offboarding is the complete process of managing an employee’s departure, including administrative, logistical, and knowledge tasks. Knowledge transfer is one component of offboarding: the specific activity of documenting and handing over the departing person’s expertise, contacts, and institutional knowledge to named colleagues.

Back to all templates

Try this template in Elium

See it on your own knowledge.

Customise it to fit your team's workflow. Get started for free.