How to create an employee offboarding process
How to design an employee offboarding process: date every step from the last working day, draw access revocation twice, and give the involuntary exit (the case with no lead time at all) a route of its own.
An employee offboarding process runs from a departure notice to an archived personnel record, and it is governed by dates rather than by sequence: every step is due at a fixed distance from the last day.
The short version
- Onboarding deadlines are knowable at the offer; one offboarding case sets them all at once.
- Every step is due at a distance from the last working day, not merely after the step before it.
- Late revocation is a security finding rather than an inconvenience, so give it a clock time.
- Revocation appears twice: same-day where the risk demands it, in full as the final shift ends.
- The record and the retention clock outlive the exit, so the process does not end on the last day.
The exit where every offset collapses to zero
Offboarding is nearly always written down as an ordered list, and the ordering is the least useful thing on the page. What decides whether an exit goes cleanly is when each step falls due relative to the last working day: the affected teams told while there is still a team to tell, the handover drafted with a fortnight to run, the accounts closed as the final shift ends. A list carries none of that, and is satisfied in full by a single busy morning.
Planning backwards from a fixed date is the technique an onboarding process uses too, and offboarding has the harder version of it. Onboarding's deadlines are all knowable the day an offer is accepted. Offboarding has one case in which the notice and the last working day are the same instant: in an involuntary exit every offset collapses to zero, and revocation, asset collection and the internal announcement all fall due as the conversation ends. Nothing in onboarding behaves that way.
So the example below forks at "Voluntary or involuntary?" before anything is planned. Its phases are the schedule rather than a grouping ("Notice and decision", "Final week", "Exit day", "After exit"), and every row inherits its due date from the one it sits in. "Handover signed off?" carries the chart's only backward route, its No branch returning to "Hand over projects and accounts", a second pass whose days have to be in the plan before anybody needs them.
Six phases, one leaving date
Employee offboarding across five owners, HR to Facilities. Access is revoked twice here: which of the two does the leaving date actually set?
Two exits, two schedules
"Voluntary or involuntary?" is the second row on the chart, and it is not there for tone. "Voluntary" leads to "Confirm last working day" and a notice period to plan inside; "Involuntary" leads to "Complete involuntary exit review", where the notice and the last day are the same conversation.
Risk dates this step, not sequence
An access decision is taken two rows before the handover is drafted, so the account can be closed before anyone has written down what is inside it. "Immediate access cut needed?" reaches "Revoke access same day" on its "Yes", due the hour it is agreed, and "Draft handover plan" on its "No".
Date the final week backwards
The phase does the dating, so "Final week" ends with "Conduct exit interview" and "Calculate final pay and benefits", both counted back from the leaving date, not queued behind the handover. A No on "Handover signed off?" returns to "Hand over projects and accounts", a second pass that needs days.
Where the leaving date stops
Revocation appears a second time, dated to the last shift rather than to the answer given on day one: "Revoke all remaining access" is the final row the leaving date governs. "Release final pay and documents" runs on a payroll cycle, "Archive records per retention policy" on a retention clock.
How it works
Fix the leaving date and the exit type
Two facts govern every other date: the confirmed last working day and whether the departure is the employee's choice. Get both in writing the day the notice arrives, then express each step's due date as a distance from the leaving date: last day minus ten working days. Distances survive a leaving date that moves, and leaving dates move.
Decide what the involuntary case changes
List the steps whose due date changes when the exit is not the employee's choice. It is usually three (access revocation, asset collection and the internal announcement), and in that case all three fall due at once, while everything else keeps its normal distance. Draw the fork rather than leaving it to judgement on the day.
Type the steps as rows and number the routes
Each row's Box text is a step and the Line to column holds the number of the row it leads to, so the sequence is data rather than geometry. Set Shape to Decision on the departure-type question, then put Voluntary and Involuntary into Line text in the same order as the numbers beside them.
Put the schedule in the horizontal lanes
The Vertical lane column takes the accountable function (HR, Manager, IT, Payroll and finance, Facilities) and the Horizontal lane column takes the phase. In an offboarding chart the phases are time windows, so type Final week, Exit day and After exit into it: the schedule then becomes something a reader can see rather than infer.
Draw the revocation twice
One row for the same-day cut on risky exits, one for the full close-down on the last working day, each naming its systems: SSO, email, VPN, badge, shared mailboxes, third-party SaaS. Transfer ownership of files and calendars before disabling the account, or the handover you signed off becomes unreachable.
Resolve the offsets against one real date
Take a single leaving date and write the actual calendar date against every row, in full: the impossible rows surface at once, starting with any step that needs the leaver's account after revocation. Then write it again for an involuntary exit, where every distance collapses to zero. If the two are identical, the fork on row 2 is decoration.
Mistakes to avoid
Listing the steps without dating them
Every item is due at offboarding, which is not a date. The steps with real lead time (asset recovery, licence reassignment, a second handover pass) are the ones that then get done late, or not at all.
Revocation with no named owner
An unowned revocation gets completed eventually and evidenced never. Name the function, name the systems and put a time against it: a dormant account with valid credentials is a finding waiting for an auditor.
Drawing the resignation, using it at a dismissal
A map built around a notice period is the one ignored during a dismissal, which is the exit where timing matters most. Fork on the departure type early and let the two cases differ in simultaneity, not only in tone.
Paying out before the assets are in
"Calculate final pay and benefits" falls before facilities have anything back, and only the release is dated after "All assets returned?". That gap is a deduction from money you still hold rather than a debt to chase.
Build your own offboarding schedule
Open the example as your own chart, resolve every step against a real leaving date, and name who revokes what and when.
Related guides
Frequently asked questions
What are the steps in an employee offboarding process?
Six phases, each defined by a deadline rather than by its position in a list. Notice and decision: acknowledge the departure, classify it, confirm the last working day. Offboarding plan: open the checklist, notify the affected teams, decide whether access must be cut immediately. Knowledge transfer: draft and execute the handover, update the runbooks, get it signed off. Final week: exit interview, final pay calculation. Exit day: assets in, remaining access out. After exit: release final pay, archive the record.
When should IT access be revoked when someone leaves?
At the end of the last working day for an ordinary resignation, and at the moment of notification for a dismissal or any exit carrying credible risk to data, customers or colleagues. The example draws both, which is the whole point: "Immediate access cut needed?" is answered on day one, while "Revoke all remaining access" is dated to the exit day. Move ownership of files, calendars and shared mailboxes first: disabling the account before that turns a signed-off handover into a support ticket.
How does involuntary offboarding differ from voluntary?
It is the same set of steps with the timing collapsed. In a resignation they run across a notice period and access ends with the final shift; in a dismissal, revocation, asset collection and the internal announcement all happen within the hour of the conversation, and the handover has to be reconstructed from whatever documentation already exists. That is why classification belongs immediately after the notice rather than in a policy appendix: it is the input that resets every downstream deadline.
Who is responsible for the offboarding process?
HR owns the process and the personnel record, the line manager owns the handover and the confirmed leaving date, IT owns revocation, payroll owns the final calculation and facilities owns the assets. The distinction worth drawing is between owning a step and being able to start it: IT, payroll and facilities all work to a date none of them sets, so each needs the leaving date and the departure type as a written input on the day the notice arrives.
