# Offboarding as a workflow: the five capabilities a leaver needs

Process, read 8 Nov 2026

**The short answer.** A leaver flow needs a run that starts from the leaving date, date triggers for the notice period and the thirty-day access check, an audit of who removed what, a webhook to the IT system so access closes in reverse order, and, where the platform has it, provisioning to revoke devices and apps. Shapes documents four; Rippling documents all five.

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 runs](/workflows/starter_leaver_runs/): 13 of 14 document it
- [Date triggers (start date, anniversary, probation)](/workflows/date_triggers/): 7 of 14 document it
- [Audit of who did what](/workflows/audit_who_did_what/): 5 of 14 document it
- [Webhooks](/workflows/webhooks/): 7 of 14 document it
- [Provisioning in other systems (devices, apps)](/workflows/provisioning/): 3 of 14 document it

## Who can run it

| Platform | Documented | Partial | Missing |
| --- | --- | --- | --- |
| [Rippling](/platforms/rippling/) | 5 of 5 | 0 | none |
| [Humaans](/platforms/humaans/) | 4 of 5 | 1 | none |
| [Workday](/platforms/workday/) | 4 of 5 | 1 | none |
| [Shapes](/platforms/shapes/) | 4 of 5 | 0 | Provisioning |
| [HiBob](/platforms/hibob/) | 3 of 5 | 2 | none |
| [BambooHR](/platforms/bamboohr/) | 3 of 5 | 1 | Provisioning |
| [Deel](/platforms/deel/) | 2 of 5 | 2 | Audit |
| [Factorial](/platforms/factorial/) | 2 of 5 | 2 | Webhooks |
| [Gusto](/platforms/gusto/) | 2 of 5 | 2 | Audit |
| [Personio](/platforms/personio/) | 2 of 5 | 0 | Audit, Webhooks, Provisioning |
| [ADP](/platforms/adp/) | 1 of 5 | 3 | Audit |
| [Lattice](/platforms/lattice/) | 1 of 5 | 3 | Provisioning |
| [Paylocity](/platforms/paylocity/) | 1 of 5 | 3 | Audit |
| [Sage](/platforms/sage/) | 1 of 5 | 1 | Audit, Webhooks, Provisioning |

Rippling documents every capability this process needs on 8 Nov 2026.

- [Template: Leaver](/templates/leaver/)

**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: https://www.rippling.com/platform/automations (read 8 Nov 2026)
- Rippling: www.rippling.com/platform/policies: https://www.rippling.com/platform/policies (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/workflows/offboarding/
