First 90 Days template, country, read 8 Nov 2026
Onboarding a remote-first hire: the first 90 days as a workflow
A remote hire's first day is a list of links, so the template is built around the written plan rather than the induction meeting. The statutory steps are the work country's and run as a conditional branch keyed to the country field; the rest is the same for every hire: equipment shipped early, access granted before the first call, a buddy whose working day overlaps.
The public GitLab handbook, read on 8 Nov 2026, is the reference for the shape: a two-week onboarding issue of asynchronous tasks, a welcome call before the start, and the manager and the People team closing their tasks before day one.
Day by day
- Day -21Run the work country's statutory branch: contract, tax forms, identity and right to work, as conditional tasks on the country fieldPeople team
- Day -14Ship the laptop and the peripherals to arrive at least three working days before the start (Equipment record)IT
- Day -7Welcome call with the manager and the buddy; the first-week calendar sharedManager
- Day -3Every access granted and tested: identity provider, chat, documents, the team's toolsIT
- Day 0Open the written onboarding plan; the hire works through it and marks each task done (Onboarding plan)New starter
- Day 1Buddy call at the start of the hire's day; the team's working hours and response norms explainedBuddy
- Week 1Policy acknowledgements signed from the mobile app or the browser: security, expenses, equipmentNew starter
- Day 30Thirty-day check-in on video, recorded in the flowManager
- Day 60Sixty-day check-in; the first in-person or team meetup booked where budget allowsManager
- Day 90Ninety-day review recorded and signed (Ninety-day review)Manager
The checks at 30, 60 and 90 days
- Day 30
- Country branch complete for the work country. Laptop arrived before day one. Onboarding plan tasks closed by the hire.
- Day 60
- Two check-ins recorded. Policy acknowledgements on file. Buddy calls logged in the first month.
- Day 90
- Ninety-day review signed. Every task closed by its owner. Equipment record complete for the leaver flow.
What the template needs from the platform
- New starter and leaver runs13 of 14 document it
- Conditional tasks4 of 14 document it
- Date triggers (start date, anniversary, probation)7 of 14 document it
- Task views for employees13 of 14 document it
- Mobile14 of 14 document it
- Nudges and batch nudges5 of 14 document it
Which platforms can run it unattended
| Platform | Documented | Partial | Missing |
|---|---|---|---|
| Humaans | 6 of 6 | 0 | none |
| Shapes | 6 of 6 | 0 | none |
| Workday | 6 of 6 | 0 | none |
| Personio | 5 of 6 | 1 | none |
| Rippling | 5 of 6 | 1 | none |
| Lattice | 4 of 6 | 1 | Conditional tasks |
| HiBob | 3 of 6 | 3 | none |
| ADP | 3 of 6 | 2 | Conditional tasks |
| BambooHR | 3 of 6 | 2 | Conditional tasks |
| Deel | 3 of 6 | 2 | Conditional tasks |
| Factorial | 3 of 6 | 2 | Conditional tasks |
| Gusto | 3 of 6 | 2 | Conditional tasks |
| Paylocity | 3 of 6 | 2 | Conditional tasks |
| Sage | 3 of 6 | 2 | Conditional tasks |
Where Shapes is weak
Device and app provisioning on day one is not a Shapes workflow step; Rippling and IT tools own that.
Sources
- GitLab handbook: onboarding, read 8 Nov 2026
- Shapes: conditional tasks in workflows, read 8 Nov 2026
- Shapes: mobile app, read 8 Nov 2026
Last reviewed 10 Nov 2026.