First 90 Days template, process, read 8 Nov 2026
The relocation flow: moving an employee to another office or country, as a workflow
Before day oneDay oneWeek oneDay 30Day 60Day 90
A relocation is a policy change wearing a travel plan. The holiday calendar, the time-off policy, the working time rules and the payroll entity all change on the move date, and a flow that runs from the location field can reassign them on that date rather than when someone remembers.
Cross-border moves add the right-to-work check in the destination and the tax and social insurance registrations, which the template keeps as tasks for payroll and the immigration adviser; it is a plan, not legal advice.
Day by day
- Day -60Move approved; the planned location and move date set on the profile; the flow starts from the field changePeople team
- Day -55Right to work in the destination checked; visa or permit tasks run as a conditional branch (Right-to-work record)People team
- Day -45Contract addendum or new local contract drafted with the destination terms; sent for signature (Contract addendum)People team
- Day -30Payroll: the entity, the tax and social insurance registrations in the destination, the last payroll in the originPayroll
- Day -14Relocation package and expenses policy confirmed; the moving dates agreed (Relocation policy)Manager
- Move dateTime-off policy, holiday calendar, working time and payroll policies reassigned by the flow on the datePeople team
- Move dateOffice access, desk and local equipment arrangedIT
- Move +30First payslip in the destination checked; thirty-day check-in recordedManager
- Move +90Ninety-day check-in; the relocation record closedManager
The checks at 30, 60 and 90 days
- Day 30
- Destination right to work checked. Addendum signed before the move. Policies reassigned on the move date.
- Day 60
- First destination payslip correct. Origin payroll closed. Expenses settled under the policy.
- Day 90
- Ninety-day check-in recorded. Every task closed by its owner. Relocation record closed.
What the template needs from the platform
- Triggers from any field3 of 14 document it
- Relocation and policy assignment3 of 14 document it
- Time off and attendance policies inside flows3 of 14 document it
- Conditional tasks4 of 14 document it
- E-sign inside the flow12 of 14 document it
- Date triggers (start date, anniversary, probation)7 of 14 document it
Which platforms can run it unattended
| Platform | Documented | Partial | Missing |
|---|---|---|---|
| Rippling | 6 of 6 | 0 | none |
| Shapes | 6 of 6 | 0 | none |
| Workday | 6 of 6 | 0 | none |
| Humaans | 3 of 6 | 3 | none |
| HiBob | 2 of 6 | 4 | none |
| Personio | 2 of 6 | 4 | none |
| Deel | 1 of 6 | 4 | Conditional tasks |
| ADP | 1 of 6 | 3 | Relocation, Conditional tasks |
| BambooHR | 1 of 6 | 3 | Relocation, Conditional tasks |
| Factorial | 1 of 6 | 3 | Relocation, Conditional tasks |
| Paylocity | 1 of 6 | 3 | Relocation, Conditional tasks |
| Gusto | 1 of 6 | 2 | Any-field trigger, Relocation, Conditional tasks |
| Lattice | 1 of 6 | 2 | Relocation, Policies in flows, Conditional tasks |
| Sage | 0 of 6 | 3 | Any-field trigger, Relocation, 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
- Shapes: workflows assign time and payroll policies, read 8 Nov 2026
- Shapes: start a workflow from any employee field, read 8 Nov 2026
- GOV.UK: checking a job applicant's right to work, read 8 Nov 2026
Last reviewed 10 Nov 2026.