Guide, 8 Nov 2026, read 8 Nov 2026
The leaver flow that forgets nothing
The leaving date is the trigger
Set the leaving date and the flow should start; that is the whole design. Shapes runs workflows for new starters and leavers (Oct 2026) and starts a workflow from any field; HiBob's task sequences trigger on a departure date; Rippling's offboarding spans HR, IT and payroll. A leaver flow that someone starts by hand runs late by exactly the number of days it took them to remember.
Access closes in reverse
Every access granted at onboarding is a line on a list, and the leaver flow walks the list backwards: the most sensitive first, the identity provider account last, at close of business on the last day. On the map that is the webhooks column (the flow tells the IT tool) or the provisioning column (the flow revokes it): Rippling revokes devices and apps as a step; Shapes's automations send webhooks; Deel IT and Factorial's IT modules revoke too.
The documents and the money
In the UK the leaving date goes to HMRC in the next Full Payment Submission and the P45 goes to the employee; the final pay carries the holiday balance and any deductions and goes to a personal address collected before the last day. The template names those two steps; elsewhere, replace them with the local equivalents and keep the rest.
The thirty-day check
- Every access on the list is closed, confirmed by the IT tool rather than by the ticket.
- Equipment is back and logged against the equipment record.
- Final pay has cleared and the leaver documents were issued.
- The record is marked as a former employee with its retention date, and the audit log shows who did each step.
Sources
- GOV.UK: what to do when an employee leaves, read 8 Nov 2026
- Shapes: run workflows for new starters and leavers, read 8 Nov 2026
- HiBob: offboarding, read 8 Nov 2026
Last reviewed 8 Nov 2026.