Employee offboarding template

When someone leaves, the work does not stop at “goodbye”. IT has to revoke access before the account becomes a security gap, Finance has to settle the final pay, the manager needs the knowledge out of one head and into a document, and People owes the person a proper exit interview. Run that by memory and something always slips. An offboarding template turns the whole leaver process into a single Epic in Jira, with every sub-task pre-written and pre-assigned, so the only decision left is who picks up each piece. Copy the template above straight into a Jira issue, or read on for the full offboarding checklist, a strong-versus-weak example, and how to turn the structure into a reusable template with Process Templates for Jira.

What this template captures and why

Done well, the departure is professional, nothing leaks, and the team keeps running without the gaps a hurried exit leaves behind.

This template is built as an Epic so the work fans out into clear sub-tasks. Saved once with Process Templates for Jira, it recreates the parent Epic and every child task in seconds, with the right owners, descriptions and links already in place. You stop rebuilding the same checklist for every leaver and start from a known-good structure each time.

Field-by-field breakdown

• Departing employee, job title, department. The basics every downstream team needs to act. Capture the role and department so IT and Finance can scope exactly which systems and entitlements are in play.
• Last working day. The hard deadline. Every sub-task due date references it, which is where a date variable and a smart value pay off: set the leaving date once and let due dates derive from it instead of editing each task by hand.
• Reason for departure. A dropdown (resignation, end of contract, retirement, other) keeps reporting consistent and lets you spot patterns over time.
• Tasks to complete. The master list of what has to happen before the last day, with deadlines and dependencies. These become the sub-tasks of the Epic.
• Equipment and access to return. Laptop, badge, phone, and the access permissions to revoke. Treat this as the security spine of the offboard: every line is something that should be off before the person is gone.
• Knowledge transfer plan. Who picks up the owned services, which runbooks and docs need updating, and which handover sessions to book so nothing critical walks out the door.
• Exit interview. Date, time and interviewer. Capturing it in the Epic means it actually gets scheduled rather than forgotten in the rush.
• Final pay and benefits. Final pay date, outstanding bonuses, expense reimbursements, and when benefits end. This is where Finance and People stay aligned.
• Stakeholders to notify. Manager, IT, Finance, Security and project leads, so the right people hear about the departure on time and through the same channel.

Best practices

• Trigger the Epic the moment notice is given, not on the last day. The earlier the sub-tasks exist, the more buffer IT and Finance have.
• Make access revocation a same-day-as-departure task, never “sometime that week”. An active account for a former employee is the most common offboarding security gap.
• Drive every due date off the last working day using variables rather than hard-coding dates in the template. One value updates the whole plan. See creating variables in templates.
• Assign sub-tasks to roles, then reassign to people. Keep the template owner-agnostic where you can, and use prefill on the create screen to slot in the manager and stakeholders at creation time.
• Keep equipment and access as separate, checkable items so nothing is “mostly done”. Each laptop, badge and admin role is its own line you can close.
• Review the template after each departure. If a step was missing or fired late, fix it once in the template and every future offboard improves.

A strong offboarding Epic vs a weak one

A weak offboarding ticket reads like a note to self: a single task titled “Offboard Jamie”, description “remove access and get the laptop back”. There is no owner for each step, no due date tied to the leaving day, no record of what was revoked, and the exit interview is never mentioned. Two weeks later nobody can say whether the VPN profile was actually disabled.

A strong offboarding Epic, generated from this template, is itemised and accountable: a parent Epic “Offboarding: Jamie Rivera, last day 2026-06-30” with sub-tasks for each access revocation, each piece of equipment, the knowledge-transfer sessions, the final-pay calculation and the scheduled exit interview, every one with an owner and a due date derived from the last working day. Because the work lives in Jira, you keep a clear access record and approval trail: who closed which entitlement, and when. That audit trail is the difference between hoping the offboard went cleanly and being able to show it did.

How to use this template in Jira

1. Build the offboarding Epic once and save it as a template with the fields above using Process Templates for Jira. See creating issue templates.
2. Add variables for the parts that change per leaver, such as the departing employee, last working day and reason, using template variables so each leaver only needs a few inputs.
3. Create issues from the template when notice comes in with create issues from the template. The Epic and all sub-tasks appear with owners and dates already set.
4. Generate them in bulk for a wave of departures (a closing office or team reduction) by launching the template once per leaver, each launch creating the full offboarding Epic.

Frequently asked questions

What should an employee offboarding checklist include? A complete offboarding checklist covers access revocation, equipment and asset return, knowledge transfer, final pay and benefits, the exit interview, and notifying the right stakeholders. Capturing each as its own checkable item in a Jira Epic means nothing is left to memory.

Why run offboarding as an Epic in Jira? Offboarding involves several teams in parallel: IT closes accounts, Finance settles pay, the manager handles knowledge transfer, and People runs the exit interview. Modelling it as an Epic fans the work out into owned, dated sub-tasks, so the whole leaver process is tracked and auditable in one place.

When should the offboarding process start? Trigger the Epic the moment notice is given, not on the last working day. The earlier the sub-tasks exist, the more buffer IT and Finance have, and access revocation can be scheduled for the day of departure rather than left to chance.

How do I create a reusable offboarding template in Jira? Install Process Templates for Jira, build the offboarding Epic once with the fields on this page, save it as a template, then add variables for the departing employee, last working day and reason so each leaver needs only a few inputs.

Related templates

Pair the offboarding Epic with the rest of your people workflow: the Employee onboarding template for the other end of the lifecycle, the Recruitment template for filling the role, and the Customer onboarding template for a similar multi-team checklist. Or browse the full template library for matching formats across HR, software and ITSM work.