# The leaver flow that forgets nothing: from notice to the final payslip, as a workflow

First 90 Days template, process, read 8 Nov 2026

**The short answer.** Twelve tasks from the day notice is given to thirty days after the last day: the leaving date on the profile as the trigger, handover owned by the manager, access removed in the reverse order it was granted, equipment returned and recorded, final pay and the leaver documents issued, and the record locked. Four owners, three checks.

Before day one / Day one / Week one / Day 30 / Day 60 / Day 90

A leaver flow fails at the edges: the access that stays open, the laptop that never comes back, the final payslip that goes to a personal address nobody collected. The template starts from the leaving date field, so setting the date runs the flow, and it ends thirty days after the last day with a check that every access is closed.

The UK steps are named because the site is British: the P45 and the leaving date in the Full Payment Submission. For other countries replace the two payroll tasks with the local equivalents and keep the rest.

## Day by day

- Notice day: Set the leaving date on the profile; the flow starts from the date change [People team]
- Notice day: Acknowledge the resignation or confirm the termination in writing; confirm the last day and the notice terms (Leaving letter) [People team]
- Notice +2: Handover plan written: the work, the documents, the people, each with a receiver (Handover plan) [Manager]
- Notice +5: Send the access removal list to IT by webhook: every system granted at onboarding, in reverse order [IT]
- Last day -7: Collect the personal email and address for the final documents; confirm holiday balance and any deductions [People team]
- Last day -3: Exit conversation booked and held; notes filed on the record (Exit notes) [Manager]
- Last day: Equipment returned and recorded against the equipment record; building pass cancelled (Equipment record) [IT]
- Last day: Access removed at close of business; the identity provider account disabled [IT]
- Last day +1: Leaving date reported to HMRC in the next Full Payment Submission; P45 issued (P45) [Payroll]
- Last day +7: Final pay calculated with holiday and deductions; payslip sent to the personal address [Payroll]
- Last day +14: Reference request process set; the record marked as a former employee with the retention date [People team]
- Last day +30: Thirty-day check: every access closed, equipment logged, final pay cleared [People team]

## The checks at 30, 60 and 90 days

- **Day 30:** Leaving date set and the flow started from it. Handover plan written with receivers. Access removal list sent to IT.
- **Day 60:** Equipment returned and recorded. Access removed on the last day. P45 issued and the FPS updated.
- **Day 90:** Final pay cleared. Thirty-day access check passed. Record locked with the retention date.

## What the template needs from the platform

- [New starter and leaver runs](/workflows/starter_leaver_runs/): 13 of 14 document it
- [Triggers from any field](/workflows/trigger_any_field/): 3 of 14 document it
- [Date triggers (start date, anniversary, probation)](/workflows/date_triggers/): 7 of 14 document it
- [Webhooks](/workflows/webhooks/): 7 of 14 document it
- [Audit of who did what](/workflows/audit_who_did_what/): 5 of 14 document it
- [Task views for employees](/workflows/task_views/): 13 of 14 document it

## Which platforms can run it unattended

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

Rippling, Shapes, Workday can run every step without a person building around a gap, on the map read 8 Nov 2026.

**Where Shapes is weak.** Device and app provisioning on day one is not a Shapes workflow step; Rippling and IT tools own that.

## Sources

- GOV.UK: what to do when an employee leaves: https://www.gov.uk/employee-leaving (read 8 Nov 2026)
- Shapes: run workflows for new starters and leavers: https://shapes.co/releases/run-workflows-for-new-starters-and-leavers (read 8 Nov 2026)
- Shapes: automations can send webhooks: https://shapes.co/releases/automations-can-now-send-webhooks (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/templates/leaver/
