Employee offboarding process map

A swimlane map of offboarding from notice to the weeks after someone has left, across HR, the manager, IT, payroll and finance, and facilities. It is deliberately laid out on a clock: the steps that must happen before the last working day are separated from the ones that happen on exit day itself.

Open this map in the editor

Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.

What is in this map

20 steps across 5 swimlanes and 6 phases, with 4 decision points.

Swimlanes (who does the work): HR, Manager, IT, Payroll and finance and Facilities
Phases (left to right): Notice and decision, Offboarding plan, Knowledge transfer, Final week, Exit day and After exit

Why map this process

Offboarding is the process most often held together by one person's memory, and it is the one where the cost of a missed step lands somewhere else entirely: an account that stays live for eight months, a final salary payment that has to be clawed back, a customer relationship nobody was handed. None of those surface at the time, which is why nobody notices the process is broken until an audit or an incident finds it.

The map's value is the timing, not the list. Knowledge transfer has to start while the person is still motivated to do it; access revocation has to complete the moment they stop being an employee, not when someone gets round to the ticket. Putting both on the same page, in lanes, is what makes it obvious that those two deadlines pull in opposite directions and need different owners.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

Every step in the Employee offboarding process process map, in the order the editor numbers them.
#	Step	Shape	Swimlane	Phase	Goes to
1	Departure notice received	Start	HR	Notice and decision	2
2	Voluntary or involuntary?	Decision	HR	Notice and decision	3 (Voluntary), 4 (Involuntary)
3	Confirm last working day	Process	Manager	Notice and decision	5
4	Complete involuntary exit review	Process	HR	Notice and decision	5
5	Open checklist and notify teams	Process	HR	Offboarding plan	6
6	Immediate access cut needed?	Decision	IT	Offboarding plan	7 (Yes), 8 (No)
7	Revoke access same day	Process	IT	Offboarding plan	8
8	Draft handover plan	Process	Manager	Knowledge transfer	9
9	Hand over projects and accounts	Process	Manager	Knowledge transfer	10
10	Update runbooks and documentation	Document	Manager	Knowledge transfer	11
11	Handover signed off?	Decision	Manager	Final week	12 (Yes), 9 (No)
12	Conduct exit interview	Process	HR	Final week	13
13	Calculate final pay and benefits	Process	Payroll and finance	Final week	14
14	Collect laptop, phone and badge	Process	Facilities	Exit day	15
15	All assets returned?	Decision	Facilities	Exit day	16 (No), 17 (Yes)
16	Log unreturned assets with payroll	Process	Payroll and finance	Exit day	17
17	Revoke all remaining access	Process	IT	Exit day	18
18	Release final pay and documents	Process	Payroll and finance	After exit	19
19	Archive records per retention policy	Stored data	HR	After exit	20
20	Offboarding complete	End	HR	After exit	End

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

2. **Voluntary or involuntary**?

Owned by HR · Notice and decision
- Voluntary → step 3
- Involuntary → step 4
6. Immediate **access cut** needed?

Owned by IT · Offboarding plan
- Yes → step 7
- No → step 8
11. Handover signed off?

Owned by Manager · Final week
- Yes → step 12
- No → step 9
15. All **assets returned**?

Owned by Facilities · Exit day
- No → step 16
- Yes → step 17

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

7. **Revoke** access same day: Time critical. For involuntary or high-risk exits, disable SSO, email, VPN and admin accounts **within the hour**, before the news circulates.
12. Conduct exit interview: Book it three to five days before the last day. Report themes in aggregate so people answer honestly.
17. **Revoke** all remaining access: Everything ends on the last working day: SSO, email, VPN, badge, shared mailboxes and third-party SaaS. Transfer file ownership before disabling.
19. Archive records per *retention policy*: Keep the personnel file for the retention period that applies to you, then delete or anonymise what falls outside it.

Making it yours

Work backwards from the exit-day column. Every step to its right is recovery and reconciliation; every step to its left has a real deadline attached to a date you already know. When adapting, the Notes column is where the deadline belongs: 'same day for privileged accounts' next to the revocation step is worth more than a separate policy document, because it is read by the person doing the step.

What to watch out for

The involuntary-exit branch is not optional. A resignation and a dismissal share maybe two thirds of these steps; the third that differs (immediate access revocation, escorted exit, different notice handling) is precisely the part that goes wrong under pressure, so it needs to be on the map before you need it.
Do not put access revocation only in the IT lane. Most companies have accounts IT does not administer: the CRM, the bank portal, the shared inbox, the supplier extranets. Either give those a step in the owning lane or accept that the map is describing a smaller process than the one you run.
Returning equipment and revoking access look like one step and are not. Someone can hand back a laptop and keep an active VPN certificate; someone can lose access and still have the laptop. Two rows, two owners.

Frequently asked questions

How is this different from an offboarding checklist?

A checklist tells you what to do; it cannot tell you what is blocking what, or who is waiting. On this map the knowledge-transfer steps sit in the manager's lane while access revocation sits in IT's, and both feed the exit-day column, so the moment either is late, the diagram shows which downstream step stalls. That is not something a list can represent.

Should the leaver have their own swimlane?

This map gives the manager and HR their own lanes and keeps the leaver's actions inside them, because the leaver is not accountable for the process completing. If the handover in your company is genuinely owned by the person leaving (common for specialists), add a lane for them, and note in the Notes column what happens if they stop cooperating.

Can I use the same map for someone moving to another internal team?

Partly. Internal moves share the knowledge transfer and the access-change steps but have no final-pay or equipment-return path, and the access step becomes 'adjust' rather than 'revoke', which is the one people get wrong, because old rights get kept alongside the new ones. Branch it early with a decision on exit type rather than copying the map.

Open the map and start editing

The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.

Open this map in the editor