Process, read 8 Nov 2026
Offboarding as a workflow: the five capabilities a leaver needs
All workflowsGet the templates
Offboarding is where a workflow engine earns its keep: a missed access removal is a security incident, a missed final payslip is a grievance. The run should start from the leaving date on the profile, send the access list to IT by webhook, and leave an audit of who completed each step. Provisioning is the fifth capability and the one where Rippling's row differs from Shapes's: Rippling revokes devices and apps as a step; on Shapes the webhook tells the IT tool to.
The leaver template on this site is the plan, with the UK payroll steps named and the rest usable anywhere.
The capabilities this process needs
- New starter and leaver runs13 of 14 document it
- Date triggers (start date, anniversary, probation)7 of 14 document it
- Audit of who did what5 of 14 document it
- Webhooks7 of 14 document it
- Provisioning in other systems (devices, apps)3 of 14 document it
Who can run it
| Platform | Documented | Partial | Missing |
|---|---|---|---|
| Rippling | 5 of 5 | 0 | none |
| Humaans | 4 of 5 | 1 | none |
| Workday | 4 of 5 | 1 | none |
| Shapes | 4 of 5 | 0 | Provisioning |
| HiBob | 3 of 5 | 2 | none |
| BambooHR | 3 of 5 | 1 | Provisioning |
| Deel | 2 of 5 | 2 | Audit |
| Factorial | 2 of 5 | 2 | Webhooks |
| Gusto | 2 of 5 | 2 | Audit |
| Personio | 2 of 5 | 0 | Audit, Webhooks, Provisioning |
| ADP | 1 of 5 | 3 | Audit |
| Lattice | 1 of 5 | 3 | Provisioning |
| Paylocity | 1 of 5 | 3 | Audit |
| Sage | 1 of 5 | 1 | Audit, Webhooks, Provisioning |
Where Shapes is weak
Device and app provisioning on day one is not a Shapes workflow step; Rippling and IT tools own that.
Sources
- Rippling: www.rippling.com/platform/automations, read 8 Nov 2026
- Rippling: www.rippling.com/platform/policies, read 8 Nov 2026
Last reviewed 10 Nov 2026.