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

First 90 Days template, role, read 8 Nov 2026

**The short answer.** Twelve tasks from offer to day 90 for an engineer joining a UK entity: right-to-work check and the HMRC starter information before day one, the contract signed in order, laptop and repository access on the morning of day one, a buddy, the first merged change inside week one, and pension enrolment within six weeks. Four owners, three checks.

Before day one / Day one / Week one / Day 30 / Day 60 / Day 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 -14: Check 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 -14: Send the contract and the written statement of particulars for signature, employer first, then the engineer (Contract of employment) [People team]
- Day -12: Collect the P45 or the HMRC starter checklist, the National Insurance number and bank details (HMRC starter checklist) [New starter]
- Day -10: Order the laptop and raise the day-one access ticket: email, source control, CI, the on-call tool [IT]
- Day -7: Assign a buddy from the same team and book the first-week calendar [Manager]
- Day 0: Deliver the laptop, confirm access works, walk through the security policy and the password manager (Acceptable use policy) [IT]
- Day 1: Assign the first ticket and the repository; pair for the afternoon [Manager]
- Week 1: Enrol in the workplace pension scheme and the benefits platform; confirm the written statement was received (Pension enrolment letter) [People team]
- Day 14: First change merged; the 30-day goals written down with the manager [Manager]
- Day 30: Thirty-day check-in: goals, blockers, the buddy's view [Manager]
- Day 60: Shadow one on-call rotation; sixty-day check-in [Manager]
- Day 90: Probation 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

- [New starter and leaver runs](/workflows/starter_leaver_runs/): 13 of 14 document it
- [Conditional tasks](/workflows/conditional_tasks/): 4 of 14 document it
- [E-sign inside the flow](/workflows/esign_in_flow/): 12 of 14 document it
- [Sign in order](/workflows/sign_in_order/): 1 of 14 document it
- [Date triggers (start date, anniversary, probation)](/workflows/date_triggers/): 7 of 14 document it
- [Task views for employees](/workflows/task_views/): 13 of 14 document it
- [Provisioning in other systems (devices, apps)](/workflows/provisioning/): 3 of 14 document it

## Which platforms can run it unattended

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

No platform documents every capability this template needs, 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: checking a job applicant's right to work: https://www.gov.uk/check-job-applicant-right-to-work (read 8 Nov 2026)
- GOV.UK: tell HMRC about a new employee: https://www.gov.uk/new-employee (read 8 Nov 2026)
- GOV.UK: workplace pensions for employers: https://www.gov.uk/workplace-pensions-employers (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)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/templates/engineer-uk/
