Employee offboarding process flowchart
A cross-functional offboarding flowchart with HR, manager, IT, payroll and facilities lanes: notice, handover, exit interview, access revocation, final pay.
How it works
Rename the lanes to your real owners
The template ships with HR, Manager, IT, Payroll and finance, and Facilities. Replace them with the teams that actually exist in your organisation. If IT and security are separate, split the lane. If a single office manager handles both assets and building access, merge Facilities into HR and delete the empty lane.
Set the phase columns to your notice period
The columns run Notice and decision, Offboarding plan, Knowledge transfer, Final week, Exit day, After exit. If your standard notice is three months, add a column between the plan and the handover for the long middle period. If most exits are two weeks, collapse the plan and knowledge transfer columns into one.
Write down your access revocation rule
Decide what triggers the 'Immediate access cut needed?' branch: involuntary exits, anyone with admin or production credentials, anyone with payment approval rights. Put the actual trigger in the node comment and add your target time, for example within one hour of notification, so the diagram states a commitment rather than a preference.
List the assets and systems you actually issue
Replace 'Collect laptop, phone and badge' with your real issue list, and attach the full system inventory to the revocation step. Most missed accounts are the ones bought on a team credit card and never registered with IT, so include a step or a note that tells the manager to name any tool the leaver used that IT does not manage.
Confirm final pay and retention with payroll
Final pay timing, holiday balance payout, benefits end dates and how long personnel records must be kept all depend on your jurisdiction and contracts. Check the 'Calculate final pay and benefits' and 'Archive records per retention policy' steps with payroll and legal before you publish, and record the retention period in the node comment so nobody has to look it up again.
Publish it, assign owners, and review it after real exits
Share the chart with HR, IT, payroll and managers so everyone works from one version rather than a personal checklist. After the next few departures, walk back through the diagram and add the steps that were missed. Version history makes it easy to see what changed and when, which matters when the process is used as evidence in an access review.
Frequently asked questions
What is the difference between voluntary and involuntary offboarding?
A voluntary exit starts with a resignation, so the notice period is known and the process can be sequenced calmly: the manager confirms the last working day, the handover runs over several weeks, and access is usually revoked on the final day. An involuntary exit (dismissal, redundancy, end of contract) needs an HR review before anything is announced, often involves legal or works council input, and frequently requires access to be cut the moment the conversation ends rather than at the end of the notice period. In the chart these are two branches off a single decision, and they rejoin at the shared offboarding checklist so the rest of the process stays the same.
When should we revoke system access during offboarding?
Set two rules and write them into the process. For standard voluntary exits, revocation happens at the end of the last working day, covering SSO, email, VPN, badge, shared mailboxes and any third-party SaaS bought outside IT. For involuntary exits and anyone with privileged access (admins, finance approvers, production credentials), revocation happens the same day the decision is communicated, ideally within the hour. Transfer document and mailbox ownership before disabling the account, otherwise files can become orphaned. The chart makes this an explicit decision in the IT lane so nobody has to guess which rule applies.
Who owns the employee offboarding process?
HR normally owns the process end to end, because HR receives the notice, runs the exit interview and holds the records. But HR cannot execute most of the steps. The manager owns the handover plan and the sign-off that the work has actually been transferred, IT owns account revocation and data transfer, payroll owns final pay and benefits, and facilities owns physical assets and building access. The point of a swimlane diagram is to make each of those owners visible, so the steps that regularly fall through the gap (unreturned laptops, dormant accounts, an undocumented recurring task) have a named owner instead of a shared assumption.
What should an exit interview cover, and when should it happen?
Hold it three to five days before the last working day: late enough that the person is candid, early enough that they still care about being accurate and are still reachable. Cover why they are leaving, what they were offered elsewhere, what would have kept them, what slowed their work day to day, and anything undocumented that the team should know. Keep it separate from the handover meeting, and report findings to managers in aggregate rather than verbatim, otherwise the next five people will give you polite answers. Note in the chart that the exit interview sits on the main path, not as an optional side step, so it does not get skipped when the last week gets busy.