First 90 Days template, country, read 8 Nov 2026
Onboarding in Germany: the first 90 days as a workflow
Germany's list is about the contract and the registrations. The Nachweisgesetz sets out which terms must be documented in writing, so the contract step carries that list as a check. The health insurer and social insurance registrations need the social insurance number and the tax ID, both collected before the start. A works council, where there is one, is informed of the hire before it takes effect.
German probation is commonly six months, so the 90-day check is the midpoint, not the decision. It is a plan, not legal advice; the authority page under Sources is the reference.
Day by day
- Day -21Draft the contract with every essential term the Nachweisgesetz lists; send for signature (Employment contract)People team
- Day -14Inform the works council of the hire, where one exists, as a conditional taskPeople team
- Day -10Collect the tax identification number, the social insurance number, the health insurer and bank details (Personal data form)New starter
- Day -5Register the hire with the health insurer and the social insurance; set up payrollPayroll
- Day 0Induction: working time recording, the holiday entitlement, the data protection notice (Data protection notice)Manager
- Week 1Confirm the working time recording method and the first entriesManager
- Day 30Thirty-day check-in recordedManager
- Day 60Sixty-day check-in recordedManager
- Day 90Probation midpoint review recorded; the six-month decision date set as a trigger (Probation midpoint review)Manager
The checks at 30, 60 and 90 days
- Day 30
- Contract signed with every listed term. Registrations complete before the first payroll. Works council informed where applicable.
- Day 60
- Working time recorded from day one. Two check-ins recorded. Data protection notice acknowledged.
- Day 90
- Probation midpoint review recorded. Six-month decision trigger set. Every task closed by its owner.
What the template needs from the platform
- New starter and leaver runs13 of 14 document it
- Date triggers (start date, anniversary, probation)7 of 14 document it
- E-sign inside the flow12 of 14 document it
- Conditional tasks4 of 14 document it
- Task views for employees13 of 14 document it
Which platforms can run it unattended
| Platform | Documented | Partial | Missing |
|---|---|---|---|
| Humaans | 5 of 5 | 0 | none |
| Rippling | 5 of 5 | 0 | none |
| Shapes | 5 of 5 | 0 | none |
| Workday | 5 of 5 | 0 | none |
| Personio | 4 of 5 | 1 | none |
| HiBob | 3 of 5 | 2 | none |
| ADP | 3 of 5 | 1 | Conditional tasks |
| BambooHR | 3 of 5 | 1 | Conditional tasks |
| Deel | 3 of 5 | 1 | Conditional tasks |
| Factorial | 3 of 5 | 1 | Conditional tasks |
| Gusto | 3 of 5 | 1 | Conditional tasks |
| Paylocity | 3 of 5 | 1 | Conditional tasks |
| Lattice | 2 of 5 | 2 | Conditional tasks |
| Sage | 2 of 5 | 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
- Nachweisgesetz (NachwG), gesetze-im-internet.de, read 8 Nov 2026
- Shapes: conditional tasks in workflows, read 8 Nov 2026
Last reviewed 10 Nov 2026.