Skip to content
Best Onboarding Software

First 90 Days template, process, read 8 Nov 2026

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

Download as CSVAll templates

Before day oneDay oneWeek oneDay 30Day 60Day 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 daySet the leaving date on the profile; the flow starts from the date changePeople team
  • Notice dayAcknowledge the resignation or confirm the termination in writing; confirm the last day and the notice terms (Leaving letter)People team
  • Notice +2Handover plan written: the work, the documents, the people, each with a receiver (Handover plan)Manager
  • Notice +5Send the access removal list to IT by webhook: every system granted at onboarding, in reverse orderIT
  • Last day -7Collect the personal email and address for the final documents; confirm holiday balance and any deductionsPeople team
  • Last day -3Exit conversation booked and held; notes filed on the record (Exit notes)Manager
  • Last dayEquipment returned and recorded against the equipment record; building pass cancelled (Equipment record)IT
  • Last dayAccess removed at close of business; the identity provider account disabledIT
  • Last day +1Leaving date reported to HMRC in the next Full Payment Submission; P45 issued (P45)Payroll
  • Last day +7Final pay calculated with holiday and deductions; payslip sent to the personal addressPayroll
  • Last day +14Reference request process set; the record marked as a former employee with the retention datePeople team
  • Last day +30Thirty-day check: every access closed, equipment logged, final pay clearedPeople 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

Which platforms can run it unattended

Rippling, Shapes, Workday can run every step without a person building around a gap, on the map read 8 Nov 2026.
PlatformDocumentedPartialMissing
Rippling6 of 60none
Shapes6 of 60none
Workday6 of 60none
Humaans5 of 61none
BambooHR4 of 62none
HiBob3 of 63none
Gusto3 of 61Any-field trigger, Audit
Personio3 of 61Webhooks, Audit
Lattice2 of 64none
ADP2 of 63Audit
Deel2 of 63Audit
Factorial2 of 63Webhooks
Paylocity2 of 63Audit
Sage2 of 61Any-field trigger, Webhooks, Audit

Where Shapes is weak

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

Sources

  1. GOV.UK: what to do when an employee leaves, read 8 Nov 2026
  2. Shapes: run workflows for new starters and leavers, read 8 Nov 2026
  3. Shapes: automations can send webhooks, read 8 Nov 2026

Last reviewed 10 Nov 2026.