On day one, the new colleague has a laptop, an email address and a bunch of flowers on his desk. On day two he sits next to an experienced co-worker and watches. On day thirty he is still sitting there - asking the same question for the third time, because the answer is not written down anywhere.
That is how onboarding runs in a lot of mid-sized companies. Not out of carelessness, but because what an onboarding plan has to deliver keeps getting confused with what an onboarding checklist delivers. This guide shows how to build an onboarding plan that structures the build-up of professional knowledge: the four phases of onboarding, a copyable template for 90 days, a filled-in example from the order processing team of a freight forwarder - and the catch that trips up almost every plan in daily practice.
What an onboarding plan has to deliver
Two things get thrown into one pot. One is the organizational side: contract, IT access, workstation, safety briefing, introductions. That belongs in an onboarding checklist and is largely ticked off after the first week. The other is the professional side: what does the new person have to be able to do, in what order does she learn it, who teaches her, and how do both sides know it has stuck? That is the onboarding plan - and it occupies you for three months, not three days.
A usable onboarding plan answers four questions for every time period:
Objective: What should the person be able to do at the end of the period - not know, but do? "Knows the ERP" is not an objective. "Creates a standard order without asking" is one.
Content: Which topics, workflows and special cases belong in this period? The sequence lives here: first the normal case, then the deviations, then the cases that only come up every few weeks.
Contact person: Who explains what? By name, not by role. That is where the onboarding plan differs from a standard operating procedure: the new person has to know which desk to walk to. An up-to-date org chart helps her place people, but it does not replace the concrete assignment "customs paperwork is explained by Mr. Falk".
Evidence: How do you know the objective has been reached? A completed job, a four-eyes check, a short conversation with the team lead. Without evidence the plan turns into a wish list that nobody revisits at the end of the probation period.
Fill those four columns and you have the core. Everything else - formatting, Excel or Word, color codes - is a matter of taste.
The four phases of onboarding
Across industries, a four-phase pattern has proven itself. The week ranges are guide values for an administrative or skilled-specialist role; for simpler work it goes faster, for management or specialist roles it takes longer.
Phase 1: Orientation (week 1)
The new person gets to know the environment: who sits where, which systems exist, what a typical day in the team looks like. She watches, asks questions, does not yet handle anything on her own. The goal of this phase is not productivity but a picture of the whole: where do the jobs come from, where do they go, who works on them before and after. Skip this week and start assigning jobs immediately and you save three days, then pay them back over the next three months in follow-up questions.
Phase 2: Working under guidance (weeks 2 to 4)
Now the new person handles real standard cases - but every one of them is checked by the colleague doing the onboarding before it leaves the building. This is where the official workflows are learned: how an order is created, which fields are mandatory, how approval works. By the end of phase 2, the normal case should run without guidance.
Phase 3: Independent with a safety net (weeks 5 to 8)
The new person takes over an area of her own - a set of customers, a region, a product group - and works it independently. Control shifts from "every job" to "spot checks plus ask when unsure". This is the phase of the special cases: the customer with a different invoice address, the shipment that needs a customs declaration, the complaint that fits no pattern. Exactly these cases decide whether somebody is genuinely onboarded after 90 days or has merely mastered the normal case.
Phase 4: Full handover (weeks 9 to 12)
The new person carries her area completely, covers for a colleague's absence for the first time and becomes the go-to contact for individual topics herself. At the end comes the probation review - and that is not only an assessment of the new person but also an assessment of the plan: what was missing? What should have come earlier? What was in the plan but nobody could explain it?
The template: onboarding plan as a weekly table
You can transfer the following table straight into Excel, Word or any other tool. One row per phase is enough as a skeleton; for complex roles, split phases 2 and 3 into individual weekly rows. The entries in the cells are deliberately generic - they show what kind of entry belongs in which column.
| Period | Objective (can, by the end ...) | Content | Contact person | Evidence / milestone |
|---|---|---|---|---|
| Week 1 (orientation) | ... explain the path of a job from start to finish and name everyone involved | Introductions, neighboring departments, systems overview, watching 3 to 5 real jobs | Team lead; onboarding colleague | Friday conversation: the new person explains the workflow in her own words |
| Weeks 2-4 (under guidance) | ... handle standard cases herself, with every job double-checked | Standard workflow step by step, mandatory fields, approvals, most frequent sources of error | Onboarding colleague (daily); subject contact per topic | 20 standard jobs with no corrections in the four-eyes check |
| Weeks 5-8 (independent) | ... run an area of her own, spot special cases and know whom to ask | Own customer group or area, special cases and exceptions, interfaces to neighboring departments, escalation routes | Subject contact per special case; team lead for spot checks | Weekly spot check with no objections; list of special cases fully worked through |
| Weeks 9-12 (handover) | ... carry the area completely and cover for a colleague for the first time | Cover week, monthly or quarterly tasks, open questions from phase 3 | Team lead | Probation review looking back at the plan |
Three notes on filling it in. First: phrase the objective as an activity you can observe. "Understands the pricing logic" cannot be checked; "prepares a quote for an existing customer without asking" can. Second: enter a back-up for every contact person. If the onboarding colleague is ill or on holiday in week 3, the plan otherwise stalls. Third: make the evidence countable. "20 jobs without corrections" is a milestone; "going well" is not.
Example: order processing clerk at a freight forwarder with 120 employees
A haulage company in East Westphalia, 120 employees, its own fleet, groupage and part loads nationally plus regular exports to Switzerland. Order processing consists of six people. Mr. Demir starts as a clerk because Ms. Reuter retires in four months. He is onboarded by Ms. Lindner, who has been in the team for eight years; the team lead is Mr. Brauer, customs and dangerous goods are Mr. Falk's territory, and dispatch is run by Ms. Sommer.
His onboarding plan looks like this:
| Period | Objective (can, by the end ...) | Content | Contact person | Evidence / milestone |
|---|---|---|---|---|
| Week 1 | ... sketch the path of a transport order from customer enquiry to invoice and name everyone involved | Tour of dispatch, warehouse, accounting; overview of the transport management system (TMS) and customer portal; three days shadowing Ms. Lindner; customer structure (contract customers, spot business) | Mr. Brauer; Ms. Lindner | Friday: Mr. Demir draws the order path on a sheet of paper, Mr. Brauer fills in the gaps |
| Weeks 2-4 | ... create national groupage orders in the TMS, produce freight documents and hand over to dispatch | Order creation, tariff check, consignment note and loading list, pre-advice, handover to dispatch, invoice release; most frequent errors (wrong cost center, missing customer reference) | Ms. Lindner (daily); Ms. Sommer for the handover | 25 orders with no corrections in the four-eyes check, signed off by Ms. Lindner |
| Weeks 5-8 | ... look after the North region customer group independently, spot special cases and know whom to ask | Takeover of North region (14 customers); special cases: dangerous goods orders, Swiss exports with customs declaration, pallet exchange, framework customers with deviating billing; complaints and damage reports | Ms. Lindner (queries); Mr. Falk (customs, dangerous goods); Mr. Brauer (weekly spot check) | Twelve special cases worked through; first Swiss shipment handled alone; four spot checks with no objections |
| Weeks 9-12 | ... carry the North region completely and cover Ms. Lindner in the South region for a week | Cover week; month-end close (open orders, back-charges); customer visit with sales; open points from phase 3 | Mr. Brauer | Probation review; feedback from Mr. Demir on what the plan was missing |
The plan is concrete, has names, has countable milestones. It is better than what most companies have. And still, the row for weeks 5 to 8 contains the reason it often fails to carry in practice.
The real problem: the plan lists topics, the knowledge behind them is nowhere
Look at the content for weeks 5 to 8: "dangerous goods, Swiss exports, pallet exchange, framework customers". Four keywords, and behind each of them sit years of experience. What does "pallet exchange" mean at this particular forwarder? That the customer Hagedorn insists on exchange pallets, but only Euro pallets, no Düsseldorf ones. That three consignees in the Ruhr area do not exchange at all, because that was agreed years ago. That the pallet accounts in the TMS go wrong if you forget one particular checkbox during pre-advice. None of that is in the process manual from 2021, which still describes the workflow before the TMS migration. Ms. Lindner knows it. And Ms. Reuter, who leaves in four months, knows thirty more things of that kind that Ms. Lindner does not.
The plan says: "Contact person Ms. Lindner." If Ms. Lindner is on holiday in week 6, the plan stalls. If Ms. Lindner resigns, it is worthless - and not just for this one onboarding, but for every future one. What can still be rescued during a notice period is described in the guide on securing knowledge when an employee leaves; the better moment, though, is beforehand.
That is the heart of the problem: an onboarding plan is only as good as the documentation behind each of its lines. It organizes the transfer of knowledge, but it does not contain the knowledge. As long as the special cases sit only in people's heads, onboarding stays a matter of watching to a timetable, and every new person learns the exceptions the same way again - in whatever order they happen to occur. If you want to break that pattern, you have to break the knowledge monopolies before the next new colleague starts: write down the special cases per area, let the stand-in run the workflow herself, spread the knowledge across more than one head.
The snag: Ms. Lindner has no time to write it down. And if she does sit down on a Friday afternoon, half of it will not come to mind - because the special cases are so self-evident to her that she no longer perceives them as knowledge at all. The rule for the customer Hagedorn only comes back to her when Mr. Demir exchanges the wrong pallets in week 7.
This is where wissa.ai comes in. An AI interviews employees by chat or voice, 15 to 20 minutes per person, and asks not "how should the workflow be?" but "what exactly did you do on the last Swiss export - and when did it run differently?" If Ms. Lindner names Mr. Falk as the person who knows the customs declaration, he is automatically invited next; that way the system works its way through the department from one knowledge holder to the next. Out of the conversations comes not only process documentation with a source reference for every statement, but also the onboarding plan for the role - automatically, with the workflows as they are actually lived rather than the official ones from the manual, including the pallet rule for the customer Hagedorn. If Ms. Reuter says something different from Ms. Lindner, the contradiction is flagged instead of smoothed over. And after each further conversation the documentation updates itself with a diff against the previous version. The plan for the new colleague after next is therefore already more current than the one for this one.
Keeping the onboarding plan current
An onboarding plan goes stale for the same reasons as any other process documentation: systems get replaced, responsibilities move, customers come and go. Three rules keep it usable.
The plan has an owner, usually the team lead, and carries a date and version in its header. After every onboarding it gets one round of revision - and the best source for that is the person who has just been onboarded, because she still remembers what was missing and what came in the wrong order. And every change to a system or a responsibility triggers a short look at the plan, rather than waiting for the next new hire.
If you would rather not organize the hardest part yourself - getting the knowledge out of people's heads: wissa.ai interviews your colleagues and turns the result into process documentation and onboarding plans, GDPR-compliant with EU hosting, voluntary participation, no performance assessment, works council friendly. The beta is open, the first three interviews are free, after that 12 interview credits cost 149 euros net; interviewed employees pay nothing. Register for free
Conclusion
A good onboarding plan is not a checklist of access rights and welcome folders but a road map for building professional knowledge: four phases over 90 days, an observable objective for each period, concrete content, a contact person by name and countable evidence. The template for it fits on one page. The real work is not in the plan but in what has to stand behind every line: the documented knowledge of the colleagues who fill the role today. Secure that before the next hire and you speed up not just this one person's onboarding, but everyone's after her.
FAQ
How long should onboarding a new employee take?
For administrative and skilled-specialist roles, 90 days has proven itself, sitting comfortably inside the usual six-month probation period. Simple work is learned in four to six weeks; management and specialist roles often need half a year. What matters is less the duration than whether the special cases are mastered at the end, not only the normal case.
What belongs in an onboarding plan?
Four things per time period: an observable objective, the content including special cases, a contact person by name plus a back-up, and countable evidence or a milestone. Organizational items such as IT access or contract paperwork do not belong here but in a separate onboarding checklist.
What are the four phases of onboarding?
Orientation (week 1): watching, getting to know the environment and the systems. Working under guidance (weeks 2 to 4): handling standard cases, every job checked. Independent with a safety net (weeks 5 to 8): own area, special cases, spot checks instead of full control. Full handover (weeks 9 to 12): carrying the area, covering for the first time, probation review looking back at the plan.
Who is responsible for the onboarding plan?
The plan belongs to the direct line manager, not to HR. HR can supply the template and set the date for the probation review, but only the team knows the objectives, the content and the contact people. A proven split: the team lead creates and maintains the plan, an experienced colleague runs the day-to-day onboarding.
Is an onboarding plan template in Excel enough?
As a skeleton, yes - the weekly table from this article transfers straight into Excel or Word. But the template is only worth as much as the documentation its content points to. If "special cases North region" is backed by no document but only a name, the plan is unworkable as soon as that person takes holiday or resigns.