Why onboarding is a routine and not an event
Companies with 50 to 500 employees hire, in my experience, between fifteen and eighty people a year. Each of them gets some version of the same sequence: a contract, a laptop, a first-day welcome, an introduction to the systems, a first task, a first feedback. In most of the HR teams I have joined, that sequence existed in three places at once: partly in a checklist from two years ago, partly in the head of the HR colleague who usually does it, and partly nowhere, because the manager was supposed to handle it.
The cost shows up twice. First in HR time: rewriting the welcome mail, chasing IT for the account, reminding the manager that the new colleague starts Monday. Second in retention: a new employee who spends the first week waiting for access and the first month without a clear task has, by the 30-day mark, already decided whether the company is organised. German employment law adds a third cost, because the probation period is where a mis-hire can still be corrected cheaply, and a manager who has not prepared for the probation review usually lets it pass.
Where AI helps
Everything in this grid is text and scheduling, produced from information the company already holds. That is why it works in the tools you already license. Copilot in Outlook and Teams covers the texts and reminders. A planner or ticketing tool that IT already runs covers the checklists. The AI part is the template that turns a role, a team, and a start date into a consistent set of documents in minutes instead of an afternoon.
The 90-day plan in five phases
- Week 0: preboardingContract signed, kit ordered, accounts requested, welcome text sent with the first-day logistics. Owner: HR. The new employee should know where to be and whom to meet before the first day.
- Week 1: systems, buddy, teamAccess works on day one, buddy assigned, first meetings scheduled, the FAQ set handed over. Owner: manager with IT. The most common failure point, and the easiest to fix with a checklist.
- Weeks 2 to 4: first tasks and 30-day check-inA real, bounded task with a visible result, then a structured 30-day conversation. Owner: manager. The check-in questions come from the template so that no manager has to invent them.
- Weeks 5 to 8: own responsibility and 60-day feedbackThe new colleague owns a process or a client. The 60-day conversation is the first honest feedback in both directions. Owner: manager, with HR informed of concerns.
- Weeks 9 to 12: preparation for the probation reviewHR reminds the manager, the manager collects evidence, the review is held in week twelve or thirteen, well before the six-month deadline. Owner: HR and manager together.
Probation in Germany: why the plan ends where it does
Most German employment contracts include a probation period (Probezeit) of six months, during which either side may terminate with two weeks' notice under Section 622 of the German Civil Code (BGB). After six months in a company with more than ten employees, the Protection Against Dismissal Act (Kündigungsschutzgesetz, KSchG) applies, and a termination needs a justified reason and, where a works council exists, its prior hearing. The practical consequence is that the decision to keep a new employee is effectively made in the first three to four months, whether anyone makes it consciously or not.
That is why the plan runs to week twelve and ends with a prepared probation review, not with a party at the end of week one. A manager who arrives at month five with no documented conversations has no evidence either way, and the default outcome is that the probation passes. Sometimes that is the right outcome. Sometimes it is a mis-hire that the company will now carry for years. The routine does not make the decision, it makes sure the conversations happened and were written down.
Where it stops
Works council and data
The routine as described plans and reminds. It does not measure whether the new employee completed tasks on time, and it does not produce a score. That distinction keeps it outside the consent right of the works council (Betriebsrat), the elected employee body in German companies, under Section 87 (1) no. 6 of the Works Constitution Act (BetrVG), which covers technical devices capable of monitoring performance or behaviour. The moment a tool tracks completion rates per employee and reports them to the manager, that changes, and a works council agreement comes first. The three criteria are explained under Co-Determination and AI Under German Law.
On data: the welcome text and the plan need the role, the team, the start date, and the names of buddy and manager. They do not need the salary, the interview notes, or anything from the medical check. The tool that generates them must have an enterprise data processing agreement with the company, because even a start date and a name together are personal data. The FAQ set is the one component where I recommend a separate check, because the answers come from the handbook and the handbook has to be current. An FAQ set that quotes last year's holiday policy is worse than none. How to keep that knowledge base clean is the subject of AI for Employee Questions.
Onboarding processes built in HR Operations and HR Manager roles for teams across twelve countries, from working students to VP level. Practical knowledge, not legal advice. More about me
90-day onboarding plan template
The five-phase plan as a workbook: one sheet per role family with milestones, owner, due date, and status, a sheet with the 30-, 60-, and 90-day check-in questions, and a sheet with the reminder schedule to paste into your calendar tool. Plus the prompt that generates the role-specific version from three inputs.
Frequently asked questions
Does AI onboarding replace the buddy or the manager?
No, and if it did the routine would have failed. The buddy, the first conversation with the manager, and the team lunch are the parts that decide whether someone stays. AI takes the checklists, the reminders, and the answers to standard questions so that the people involved have time for the human part.
Is an onboarding routine subject to co-determination?
Preparing texts and plans is not. Tracking whether a new employee completed tasks on time, or scoring their progress, would be monitoring of performance and would fall under Section 87 of the Works Constitution Act. The routine as described here plans and reminds. It does not evaluate.
Why 90 days and not 30?
Because the German probation period is usually six months, and the first three of them are where the decision to keep someone is effectively made. A 30-day plan ends before the first honest feedback conversation. A 90-day plan carries the new employee to the point where the manager has enough evidence for the probation review.
What data goes into the tool?
Role, team, start date, the systems the role needs, and the names of buddy and manager if the tool has an enterprise data processing agreement. No health data, no salary, no notes from the interview. The welcome text needs none of that.
Does this work for remote and hybrid starts?
Better than in-person onboarding, in my experience, because remote starts depend entirely on structure. A remote new employee with a clear 90-day plan and a reminder before each milestone knows what to do on day three. One without it waits for someone to notice.
How long does it take to set up?
One afternoon for the plan template and the prompt set, one week for the role-specific variants with the managers, and one first cohort to tune it. From the second cohort on, HR spends under an hour per new starter on preparation.