# Onboarding in Germany: the first 90 days as a workflow

First 90 Days template, country, read 8 Nov 2026

**The short answer.** Nine tasks for a hire in a German entity: the written employment contract with the essential terms the Nachweisgesetz requires, the tax identification number and social insurance number collected, registration with the health insurer and the social insurance before the first payroll, the works council informed where one exists, and the six-month probation checks. Four owners, three checks.

Before day one / Day one / Week one / Day 30 / Day 60 / Day 90

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 -21: Draft the contract with every essential term the Nachweisgesetz lists; send for signature (Employment contract) [People team]
- Day -14: Inform the works council of the hire, where one exists, as a conditional task [People team]
- Day -10: Collect the tax identification number, the social insurance number, the health insurer and bank details (Personal data form) [New starter]
- Day -5: Register the hire with the health insurer and the social insurance; set up payroll [Payroll]
- Day 0: Induction: working time recording, the holiday entitlement, the data protection notice (Data protection notice) [Manager]
- Week 1: Confirm the working time recording method and the first entries [Manager]
- Day 30: Thirty-day check-in recorded [Manager]
- Day 60: Sixty-day check-in recorded [Manager]
- Day 90: Probation 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 runs](/workflows/starter_leaver_runs/): 13 of 14 document it
- [Date triggers (start date, anniversary, probation)](/workflows/date_triggers/): 7 of 14 document it
- [E-sign inside the flow](/workflows/esign_in_flow/): 12 of 14 document it
- [Conditional tasks](/workflows/conditional_tasks/): 4 of 14 document it
- [Task views for employees](/workflows/task_views/): 13 of 14 document it

## Which platforms can run it unattended

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

Humaans, Rippling, Shapes, Workday can run every step without a person building around a gap, 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

- Nachweisgesetz (NachwG), gesetze-im-internet.de: https://www.gesetze-im-internet.de/nachwg/ (read 8 Nov 2026)
- Shapes: conditional tasks in workflows: https://shapes.co/releases/conditional-tasks-in-workflows (read 8 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestonboardingsoftware.com/templates/germany/
