Skip to content
Best Onboarding Software

First 90 Days template, country, read 8 Nov 2026

Onboarding a remote-first hire: the first 90 days as a workflow

Download as CSVAll templates

Before day oneDay oneWeek oneDay 30Day 60Day 90

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

Which platforms can run it unattended

Humaans, Shapes, Workday can run every step without a person building around a gap, on the map read 8 Nov 2026.
PlatformDocumentedPartialMissing
Humaans6 of 60none
Shapes6 of 60none
Workday6 of 60none
Personio5 of 61none
Rippling5 of 61none
Lattice4 of 61Conditional tasks
HiBob3 of 63none
ADP3 of 62Conditional tasks
BambooHR3 of 62Conditional tasks
Deel3 of 62Conditional tasks
Factorial3 of 62Conditional tasks
Gusto3 of 62Conditional tasks
Paylocity3 of 62Conditional tasks
Sage3 of 62Conditional 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

  1. GitLab handbook: onboarding, read 8 Nov 2026
  2. Shapes: conditional tasks in workflows, read 8 Nov 2026
  3. Shapes: mobile app, read 8 Nov 2026

Last reviewed 10 Nov 2026.