Skip to content
Best Onboarding Software

First 90 Days template, role, read 8 Nov 2026

The first 90 days of a software engineer in the UK, as a workflow

Download as CSVAll templates

Before day oneDay oneWeek oneDay 30Day 60Day 90

The UK engineer's first 90 days break in two places: the right-to-work check that nobody has dated, and the laptop that arrives on day three. The template puts the check fourteen days out, with the share code or the original document recorded against the profile, and puts the equipment order on the same day as the signed contract, so the day-one ticket is raised by the flow and not by the manager at 9am.

The engineering steps are deliberately small: a repository and a first ticket in week one, a merged change by day 14, an on-call shadow by day 60. Each one is a task with an owner, so the flow can nudge the person who is late rather than the new starter who is waiting.

Day by day

  • Day -14Check the right to work online with a share code, or examine the original document, and record the date and the method on the profile (GOV.UK right-to-work check)People team
  • Day -14Send the contract and the written statement of particulars for signature, employer first, then the engineer (Contract of employment)People team
  • Day -12Collect the P45 or the HMRC starter checklist, the National Insurance number and bank details (HMRC starter checklist)New starter
  • Day -10Order the laptop and raise the day-one access ticket: email, source control, CI, the on-call toolIT
  • Day -7Assign a buddy from the same team and book the first-week calendarManager
  • Day 0Deliver the laptop, confirm access works, walk through the security policy and the password manager (Acceptable use policy)IT
  • Day 1Assign the first ticket and the repository; pair for the afternoonManager
  • Week 1Enrol in the workplace pension scheme and the benefits platform; confirm the written statement was received (Pension enrolment letter)People team
  • Day 14First change merged; the 30-day goals written down with the managerManager
  • Day 30Thirty-day check-in: goals, blockers, the buddy's viewManager
  • Day 60Shadow one on-call rotation; sixty-day check-inManager
  • Day 90Probation decision recorded with the evidence; the review signed by both (Probation review)Manager

The checks at 30, 60 and 90 days

Day 30
Right-to-work check dated on the profile. Laptop delivered on or before day one. First change merged.
Day 60
Pension enrolment confirmed within six weeks of the start. On-call shadow completed. Thirty-day goals reviewed in writing.
Day 90
Probation decision recorded and signed. Every task in the flow closed by its owner. The buddy's feedback filed.

What the template needs from the platform

Which platforms can run it unattended

No platform documents every capability this template needs, on the map read 8 Nov 2026.
PlatformDocumentedPartialMissing
Rippling6 of 70Sign in order
Shapes6 of 70Provisioning
Workday5 of 72none
Humaans5 of 71Sign in order
Deel4 of 71Conditional tasks, Sign in order
Factorial4 of 71Conditional tasks, Sign in order
Personio4 of 71Sign in order, Provisioning
HiBob3 of 73Sign in order
ADP3 of 72Conditional tasks, Sign in order
Gusto3 of 72Conditional tasks, Sign in order
Paylocity3 of 72Conditional tasks, Sign in order
BambooHR3 of 71Conditional tasks, Sign in order, Provisioning
Lattice2 of 72Conditional tasks, Sign in order, Provisioning
Sage2 of 72Conditional tasks, Sign in order, 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

  1. GOV.UK: checking a job applicant's right to work, read 8 Nov 2026
  2. GOV.UK: tell HMRC about a new employee, read 8 Nov 2026
  3. GOV.UK: workplace pensions for employers, read 8 Nov 2026
  4. Shapes: run workflows for new starters and leavers, read 8 Nov 2026

Last reviewed 10 Nov 2026.