Onboarding Checklist: Getting New Employees Started, From Signature to Day 90

Monday, 8 a.m. The new colleague is standing at reception. Her manager is in a client meeting, IT says the laptop will arrive "sometime this week," the mailbox has been requested. By lunchtime she has read the mission statement and fetched coffee twice. That evening she tells her family she isn't sure anyone was actually expecting her.

In small and midsize companies this scene is not an outlier. It is what happens when onboarding belongs to nobody. The role took months to fill, the contract was negotiated carefully - and then the process breaks off on exactly the day it was supposed to begin. This guide gives you an onboarding checklist in five phases, each item with a named owner, and shows where the process typically tears in firms with 10 to 500 employees.

What the Checklist Has to Do - and What It Doesn't

Onboarding and job training tend to get lumped together. It helps to separate them. Onboarding is the organizational and social frame: contract, hardware, access, workspace, contacts, ground rules, feedback meetings. Job training is the technical part: which tasks the new person learns in which order, and from when on she handles which processes independently. There is a separate onboarding plan template for that part; this article covers the frame in which such a plan can work at all.

The frame rarely fails for lack of ideas. It fails for lack of ownership. That is why every item in this checklist carries one of four roles:

• HR - in smaller firms often the office manager or the owner personally
• IT - internal or the external provider who creates accounts and sets up devices
• Manager - the direct supervisor, not the division head two levels up
• Buddy - an experienced colleague from the team, with no authority to direct, for the questions you don't ask the boss

If at any point while reading you think "nobody here actually does that," you have found your first gap.

The Onboarding Checklist in Five Phases

The items are written so you can adopt them directly. Cut whatever doesn't fit your company - but not the role behind it.

Phase 0: Preboarding - From Signature to the Day Before the Start

There are often three months between the offer being accepted and the first day at work. That period decides whether day one works, and whether the person shows up at all: someone who hears nothing during this phase often keeps listening to other offers.

• HR: File the contract, open the personnel file, request documents (tax ID, social security number, health insurance, bank details)
• HR: Notify IT and the manager in writing of the start date, the role and the systems required, at least three weeks before day one
• HR: Welcome email two weeks before the start: who is meeting the person, when and where, what to bring, what day one looks like
• IT: Order or reserve the device, create the user account, email and calendar, request access to the specialist applications
• IT: Store the credentials so the manager can hand them over on day one - not by email to a mailbox nobody can open yet
• Manager: Arrange workspace, keys, parking; name a buddy; write down a plan for the first five days
• Manager: Test the access yourself the day before the start
• Buddy: Send a short personal message before the start, block out lunch on day one

Phase 1: The First Day

Day one has a single goal: by the evening, the new person should know where she sits, who she works with, how she gets into the systems and what she will be doing this week.

• Manager: Greet her in person and on time. If a client meeting collides, the meeting moves, not the welcome
• Manager: Tour and introductions in the team; who is responsible for what is best shown on a current org chart, not by reeling off twelve names
• IT: Hand over the device, do the first login together, check printer and phone. Success criterion: the person sends an email from her own mailbox before noon
• HR: Formalities in one hour maximum: time tracking, vacation, sick leave, safety briefing, data protection. Plus the rules nobody ever says out loud: dress code, breaks, working from home, first names or last names
• Buddy: Lunch and the unofficial rules: who gets asked about what, what is better settled face to face than by email
• Manager: A short conversation at the end of the day: what is open, what is missing, what is on for tomorrow

Phase 2: The First Week

Now it is about orientation: the map of the company, an overview of the main processes, and first tasks with a visible result.

• Manager: Expectations conversation: what should be achieved after 30, 60 and 90 days, and how it will be measured. Write it down, both sides keep a copy
• Manager: Meetings with the interfaces of the role, 20 minutes per area, with the question "What do you need from this role, and what has gone wrong so far?"
• Manager: Hand over the job training plan, first task with a clear result and a deadline
• IT: Follow-up check on day 3: is an application missing that only became apparent now
• HR: Invitations to team meetings, the staff meeting and the training sessions of the first quarter
• Buddy: Five minutes of checking in every day. In week one nobody asks on their own initiative. Show where documented processes live and how to search them

Phase 3: The First Month

The focus shifts from frame to content. The list gets shorter, the conversations matter more.

• Manager: Feedback conversation after 30 days, 45 minutes, prepared. Three questions: what is going well, what is missing, what surprised you. The third one produces the most candid answers
• Manager: Compare against the job training plan: which processes does the person already handle independently, which not, and why
• HR: Ask about the organizational start: what was missing at the beginning? The answers feed back into this checklist
• IT: Review permissions that were only meant for the training period
• Buddy: Move from daily company to one fixed weekly slot

Phase 4: Through Day 90

The probation period usually runs six months, but for most people the decision to stay or leave falls in the first three. That is why the checklist ends at day 90, with a conversation both sides take seriously.

• Manager: Conversation after 60 days, shorter, focused on independence
• Manager: Conversation after 90 days: status against the expectations from week one, open items, the outlook beyond probation. Record the outcome in writing
• HR: Put the end of probation in the calendar four weeks ahead, so that no decision is made by a deadline quietly passing; close out onboarding formally, briefings documented
• Buddy: End the buddy arrangement officially, stay in touch
• Manager: Give the new person a role in the next onboarding. Whoever just arrived knows best what was missing

Where Onboarding Typically Tears in Midsize Firms

The checklist above is nothing new; most companies have a similar document somewhere. And yet day one often looks like the opening scene. Three gaps come up again and again.

Access Is Missing on Day One

The classic, and rarely IT's fault. Usually IT only learned about the start date once the person was already in the building, or nobody said which specialist applications the role needs. With an external provider, add a two-week lead time for the device. The remedy is in phase 0: the written notice from HR to IT with start date, role and systems - plus the item "access tested" on the manager's list, not on IT's.

Nobody Owns It Because Everybody Owns a Bit of It

HR assumes the manager is taking care of day one. The manager assumes HR has a plan. Both are right that it could be the other one, and that is exactly why nobody does it. A checklist without a role behind each item tends to make this worse, because it creates the impression that things are handled. So also decide who owns the list as a whole - in firms up to 50 employees usually the office manager, above that HR. That person doesn't tick every box personally, but they do follow up.

The Technical Knowledge Is Passed On "On the Side"

The third gap is the most expensive and surfaces last. The organizational part is done after two weeks, and then training begins along the lines of "go sit next to your colleague." The colleague explains whatever comes to mind, in the order the work happens to arrive; edge cases come up if they happen to occur. After three months the new person knows half the processes well and nothing about the other half - and nobody knows which half. A training plan closes this gap only if the processes it works through are described somewhere. In midsize companies that is the exception: the knowledge sits in the heads of three experienced people who have no time to write it down.

This is where wissa.ai comes in. An AI conducts short interviews with your experienced staff, 15 to 20 minutes per person, by chat or voice. If someone names a colleague as the person who "handles the dunning runs," she gets invited next - that is how the system works its way from one knowledge holder to the next. The conversations automatically produce process documentation with a source reference for every statement, an org chart and onboarding plans per role; contradictions between two statements are flagged rather than smoothed over. For onboarding that means the buddy in week one doesn't point at an empty shared drive but at a knowledge base that describes the processes of the new person's own role and updates itself after every further conversation.

Metrics: How to Tell Whether Onboarding Works

Two numbers are enough, and both can be collected in a 30-person company with no HR software.

Early turnover is the late metric: it shows the damage once it has been done. Time to productivity is the early one - and it swings hardest exactly where technical knowledge is passed on informally.

Example: A Building Services Engineering Firm With 30 Employees

A firm with two managing directors, 21 engineers and technicians, three apprentices and four people in administration and site supervision hires Ms. Yildiz as of October 1, a heating and ventilation design engineer with eight years of experience from another firm. There is no HR function in the narrow sense; office manager Ms. Ahrens takes the role. IT is an external provider. The manager is the managing director whose projects Ms. Yildiz will take over. Ms. Kestner, eleven years with the firm, becomes her buddy.

Here is how the previous hire went, a year earlier: after the contract was signed, nothing happened until day one. The licence for the calculation software was ordered on the first working day and arrived nine days later. Until then the new colleague read project files on paper. Training consisted of sitting next to Ms. Kestner whenever she had time. After four months he resigned during probation, saying he had felt he was in the way.

For Ms. Yildiz the sequence looks different. Three weeks before the start, Ms. Ahrens emails the IT provider: start date, role, systems required (calculation and CAD software with rights for the specific projects, document management, time tracking, phone system). The device arrives on September 26; on the 29th the managing director tests the login himself. Ms. Kestner sends a short email: "I'll pick you up at reception at 8, and at lunch we'll go to the Italian place across the street."

On day one the managing director has moved his 9 a.m. meeting to the afternoon. At 10 Ms. Yildiz sends her first email from her own mailbox. Ms. Ahrens gets the formalities done in 40 minutes and says the sentence nobody else says: "Everyone here is on first-name terms except with the managing directors, and on Fridays most people leave at 3." In week one the managing director and Ms. Yildiz agree what should be in place after 90 days: three projects handled independently at detailed design stage, two tender packages prepared, cost tracking for her own projects.

The real difference shows up in the technical part. Over the summer the firm had documented its eight most important processes - from project setup through concept design and tendering to handover and defect management - based on interviews with Ms. Kestner and two other experienced colleagues. Ms. Kestner no longer has to explain everything; she shows where it is written down and answers the questions that come out of it. After 30 days the managing director estimates that Ms. Yildiz works independently on five of the eight processes. With the previous hire, that would have been the figure after four months.

What the firm invested: roughly four hours of Ms. Ahrens's time for the checklist and coordination, three hours from the managing director for the conversations across 90 days, and about two hours per knowledge holder for the interviews. What it saved is what the previous year had cost: a complete refill of the position including four months of salary without full output.

If you want to put the technical part of your onboarding on a documented footing without tying up your experienced people for weeks: wissa.ai interviews your knowledge holders using AI, 15 to 20 minutes per person, and turns that into process documentation and onboarding plans per role - GDPR-compliant with EU hosting, participation voluntary, no performance evaluation. The first three interviews are free, after that 12 interview credits cost €149 net; interviewed employees stay free. Register for free

Conclusion

Good onboarding needs no HR software and no welcome box. It needs a list with roles behind its items, one person who owns the list as a whole, and three fixed conversations after 30, 60 and 90 days. With that structure, the organizational gaps - missing access, unclear ownership - are closed within a single hire. The technical gap closes only once the processes of the role are described somewhere. Tackle both, and you will see it in two numbers: early turnover goes down, and the time to independent work gets shorter and, above all, predictable.

FAQ

What is the difference between onboarding and job training?

Onboarding covers the organizational and social frame: contract, hardware, access, workspace, contacts, ground rules and feedback conversations. Job training is the technical part, meaning the order in which the new person learns the tasks and processes of her role. The two belong together but need different owners: onboarding is steered by HR or the office manager, job training by the direct manager.

How long should the onboarding process last?

Ninety days has proven itself as the frame, split into preboarding, day one, week one, month one and the stretch through day 90. Probation usually runs longer, but for most people the decision to stay falls within the first three months. The technical training plan can run considerably longer depending on the role.

Who is responsible for onboarding new employees?

Four roles with clearly divided tasks: HR for contract, formalities and coordination, IT for devices and access, the manager for the welcome, expectations and feedback conversations, and a buddy from the team for everyday questions. On top of that, one person should own the checklist as a whole and follow up; in smaller firms that is usually the office manager.

What belongs in an onboarding checklist?

For each phase, the concrete tasks with their owner: before the start, documents, the notice to IT and the welcome email; on day one, the welcome, device handover, formalities and a shared lunch; in week one, the expectations conversation and the start of the training plan; after that, the feedback conversations at 30, 60 and 90 days. The most important component is the role behind each item, not the length of the list.

Which metrics show whether onboarding works?

Two numbers are enough: early turnover, meaning the share of new hires who leave within the first twelve months, and time to productivity, meaning the days until the core tasks are handled independently. Both can be collected without HR software. Widely varying times to productivity usually point to job training without documented processes.