Employee Onboarding: What It Is, Phases, 30-60-90 Day Plan and Checklist (2026 Guide)

Almost every company has a hiring process. Far fewer have a process for what happens after the offer is signed: the weeks in which the new hire quietly decides whether accepting was the right call. Those weeks are onboarding, and too often they consist of a laptop that arrives late, a 40-slide welcome deck, and a calendar full of meetings where half the acronyms go unexplained.

This guide covers what employee onboarding is and how it differs from orientation and induction, the 4 Cs every program should cover, the phases from preboarding to the first year, a 30-60-90 day plan with a worked example, a checklist by stage, the meetings that actually speed up integration, how to measure whether it works, and which parts of the job AI can take over. A template you can copy is at the end.

⚠️ This article was independently compiled based on publicly available information and user feedback as of October 2026.

Table of Contents

1. What is employee onboarding?
2. Onboarding vs. orientation vs. induction
3. Why onboarding matters more than it looks
4. The 4 Cs of onboarding
5. The phases of onboarding: from preboarding to the first year
6. The 30-60-90 day onboarding plan
7. Onboarding checklist by stage
8. The onboarding meetings that make the difference
9. Remote, hybrid and international onboarding
10. Common onboarding mistakes
11. How to measure onboarding
12. How AI speeds up onboarding
13. Onboarding plan template to copy
14. Frequently asked questions
15. Conclusion

What is employee onboarding?

Employee onboarding is the structured process by which a company integrates a new hire until they are fully productive and feel part of the team. It starts before day one, the moment the offer is accepted, and it ends long after the first week: most serious programs run between three months and a year. It covers the administrative side (contract, access, equipment), the functional side (what the role does and how it is measured), the cultural side (how this company really works) and the relational side (who to turn to and who to build trust with).

The word is simply "on board": getting someone onto the ship and, more importantly, teaching them how to sail it. Depending on the country and the industry you will also hear orientation, induction, new hire integration or employee welcome, which we untangle in the next section.

One ambiguity is worth clearing up because it trips up anyone searching the term. "Onboarding" is also used for signing customers up to a product (user onboarding) and for identity verification in banking and fintech (digital onboarding or KYC). This article is about employee onboarding, the kind owned by HR and team leads. If you came looking for product onboarding, the underlying logic is similar (shorten the time to first value), but the tools are different.

Onboarding vs. orientation vs. induction

The three terms get used interchangeably, and they are not the same thing. Mixing them up is how a company ends up believing that a welcome morning counts as an onboarding program.

Orientation and induction are parts of onboarding, not alternatives to it. A company can run an excellent induction (the new hire leaves knowing how to use the CRM and what the expenses policy says) and still fail at onboarding, because three months in that person still does not know who to ask when a customer is upset, or why the team made the decisions it made before they arrived.

Why onboarding matters more than it looks

Onboarding gets little attention as a management topic because its costs are invisible. Nobody receives an invoice for a poor onboarding. The effects show up later under other names: first-year turnover, low productivity in the first half year, avoidable mistakes, a team lead spending hours answering what should have been written down.

Three effects deserve particular attention:

• The decision to stay is made early. A large share of voluntary resignations happen in the first year, and the people who leave usually describe a chaotic start: expectations that differed from the interview, unclear responsibilities, a feeling that asking questions was an imposition. Good onboarding does not guarantee retention, but poor onboarding puts it at risk from week one.
• Time to full productivity is a real cost. Every month a qualified person works at half capacity is a month of salary with half the return. In sales and technical roles, cutting that period by a few weeks is worth more than almost any other HR improvement.
• Team knowledge either gets passed on or gets lost. Onboarding is when the new hire absorbs how things are done here. If that knowledge lives only in the heads of two veterans, onboarding depends on their time and goodwill. If it is recorded and searchable, integration stops being a lottery.

There is a fourth effect that gets less airtime: for a few weeks, the new hire is the best auditor your company will ever have. They see with fresh eyes what everyone else has normalized. An onboarding program that makes room for those observations turns every hire into a small process improvement.

The 4 Cs of onboarding

The most cited model for structuring the content of onboarding is the 4 Cs, proposed by researcher Talya Bauer. It works as a checklist to make sure a program does not stop at the administrative layer.

Most programs cover the first C well and the other three poorly, because the first is the only one with a form attached. Clarification requires the manager to sit down and write goals; culture requires conversations, not slides; connection requires other people's time. A complete onboarding program assigns explicit time and owners to all four.

Some practitioners add a fifth C, Check-back: regularly checking how integration is going and adjusting the plan. In practice, that follow-up is what separates a program from a task list, so we treat it as mandatory in the phases below.

The phases of onboarding: from preboarding to the first year

A well-designed onboarding is organized into phases with distinct goals. The exact boundaries vary by company, but the sequence is stable.

1. Preboarding (from offer acceptance to day one). The goal is for the person to arrive with the paperwork done and genuinely looking forward to it. This covers signing the contract and HR documents, shipping equipment, creating accounts, a welcome message from the manager and the agenda for the first week. The costliest mistake in this phase is silence: a new hire who hears nothing between signing and starting begins to wonder.

2. Day one. The goal is a single thing: the person goes home thinking they made the right choice. That means equipment and access that work, a manager who gives them real time (not fifteen minutes between meetings), a team that knew they were coming, and lunch or coffee with people. What should not happen on day one is dense process training, which nobody retains in that state.

3. First week. The goal is orientation: understanding the map (who does what), the basic tools, the team's recurring meetings and the communication norms. This is the induction proper. It helps to include a first small, real task, not a practice one, so the person feels they are already contributing.

4. First month. The goal is context: the projects underway, the history of decisions, the customers or users, and why the current priorities are what they are. This is where introductions with other departments, shadowing (sitting in on colleagues' real work) and the first formal check-in with the manager come in.

5. First quarter (through day 90). The goal is autonomy: the person leads their own work, asks for help when appropriate and knows enough of the context not to repeat past mistakes. The first formal review of the 30-60-90 plan usually sits at the end of this phase, and in many companies so does the end of the probation period.

6. Through the first year. The goal is full integration: the person not only performs but starts improving processes, training others and taking part in decisions. Check-ins get more spaced out (monthly, then quarterly) but do not disappear. An onboarding that ends at 90 days leaves out exactly the stage where commitment is consolidated.

The 30-60-90 day onboarding plan

The 30-60-90 day plan is the most practical tool for delivering clarification (the second C) and has become the standard in many industries. It splits the first three months into three blocks with a different focus each: learn, contribute, lead. The golden rule is that each block's goals must be observable, so that the new hire and the manager can check together whether they were met.

A worked example for an account manager role at a software company:

• Days 1-30. Learn the product to power-user level, listen to at least eight customer calls (recorded or by shadowing colleagues), read the history of the five accounts they will inherit and prepare a one-page summary of each to validate with the manager.
• Days 31-60. Run two accounts with supervision, lead their check-in meetings with a colleague present, write the meeting notes and follow-up emails, and present an improvement proposal for the renewal process.
• Days 61-90. Manage the full portfolio autonomously, lead the quarterly business review with one key account and have held one-on-ones with product, support and finance.

The manager should write the plan before day one and review it with the new hire in the first week. If it only exists in the manager's head, it does not deliver clarity; if the new hire writes it alone, they are guessing.

Onboarding checklist by stage

This checklist collects what must not be missing at each stage. It is meant to be adapted, not copied whole: tick what applies to your company and add what is specific to each role.

Preboarding

• Contract signed and HR documentation complete
• Equipment (laptop, peripherals, phone if needed) ordered and shipped in advance
• Accounts and access created: email, chat, calendar, role-specific tools
• Welcome message from the manager with the first week's agenda
• Buddy or mentor assigned and briefed
• 30-60-90 day plan written by the manager

Day one

• Manager available for at least an hour for the welcome
• Team introduced, with a shared lunch or coffee
• Equipment and access verified on the spot
• Walkthrough of tools and communication channels
• How we work explained: hours, recurring meetings, where things get documented

First week

• Role induction: processes, policies and role-specific tools
• First real task assigned and delivered
• 30-60-90 plan reviewed with the new hire
• One-on-one with each member of the immediate team
• Access to the history: documentation, past meeting notes, key decisions

First month

• Introduction sessions with the departments they will work with
• Shadowing sessions on the team's real work
• 30-day check-in with the manager
• Short onboarding experience survey
• First dedicated slot for the new hire to share fresh-eyes observations

First quarter

• 60-day check-in
• Formal 90-day review with the plan on the table
• Probation decision, where applicable, communicated in advance
• Development plan for the following months
• Monthly check-in schedule through the first year

The onboarding meetings that make the difference

Look closely and almost all of onboarding that is not paperwork happens in meetings: the welcome, the sessions with other departments, the one-on-ones with the manager, call shadowing, the check-ins. The quality of onboarding depends heavily on how those conversations are designed and used. These five carry the most weight.

The welcome meeting with the manager. Not the corporate presentation, but an hour in which the manager explains, in their own words, why they hired this person, what they expect in the first 90 days and how they prefer to work (how they give feedback, how they want problems escalated, when they are available). It is the meeting that reduces the most anxiety and the one most often improvised.

Context sessions with each department. Thirty minutes with someone from product, someone from sales, someone from support, and so on. They work far better with a guiding question ("what would I need to know about your area to avoid causing you problems?") than as generic presentations. The usual problem is that the new hire gets ten of these in two weeks and retains almost nothing, which is why they should be recorded and re-readable.

Shadowing. Sitting in on a colleague's real meetings with customers, users or vendors. It is the fastest way to learn how people talk here, which objections come up and how they are handled. Its limit is the calendar: you can only shadow the meetings that happen to coincide with the new hire's schedule. A library of past meetings, with transcripts and summaries, extends shadowing to everything that happened before they arrived.

Weekly one-on-ones. For the first three months, the one-on-one with the manager should be weekly and non-negotiable. Its agenda is simple: what did you learn, where did you get stuck, what surprised you, what do you need. We have a full guide on how to run good one-on-ones that applies here too.

The 30, 60 and 90-day check-ins. These are extended one-on-ones in which the plan is reviewed with the table in front of you. The key question in each is not "how is it going?" but "which goal in this block is not met, and what is missing to meet it?". Documenting the answers lets the 90-day review rest on facts rather than on the impression left by the last week.

There is a common thread through all five: the new hire receives an enormous amount of spoken information in a short time and has few ways to return to it. Taking notes while trying to understand is already hard; asking the same question a third time is uncomfortable. Solving that recording problem is one of the onboarding levers with the best effort-to-result ratio, and we cover it in the section on AI.

Remote, hybrid and international onboarding

Remote onboarding is not in-person onboarding over video calls. It loses the informal mechanisms that did much of the work without anyone designing them: overhearing conversations, asking the person at the next desk, staying for a drink. Those have to be replaced deliberately.

• More structure, not less. The agenda for the first two weeks should be locked before day one, with every session, every person and every goal. What gets resolved in an office by asking around needs a calendar slot when remote.
• A buddy with allocated time. Remotely, the buddy stands in for the person at the next desk. It works if they have hours reserved for it (two or three a week in the first month) and if it is clear they can receive basic questions without those counting against anyone.
• Documentation that actually exists. Remote onboarding exposes documentation debt. If the answer to "where is that?" is always "ask Carmen", the process depends on Carmen's availability. Our guide on knowledge silos goes deeper on how to get out of that.
• Cameras and presence. In the first weeks' meetings, asking for cameras on and brief personal introductions helps the new hire put faces to names. It seems minor and it is not.

Hybrid onboarding adds a difficulty of its own: coordinating the new hire's office days with those of the people they need to build relationships with. If they come in on Tuesdays and their manager on Thursdays, hybrid becomes remote with a commute.

International onboarding, increasingly common, adds language and culture. Someone joining from another country into a team that works in English, or an English speaker joining a company that operates in German or Japanese, spends part of their capacity in the first weeks following the language rather than the content. Real-time captions and translation in meetings reduce that load and let the person participate from the start, not once their language level allows it.

Common onboarding mistakes

Onboarding programs rarely fail for lack of good intentions. They fail because of a handful of repeated mistakes that design can fix.

• Cramming everything into the first week. The forgetting curve does its work: what was explained on Tuesday of week one without context is gone by the following Monday. Spreading information to the moment it is needed (just in time) beats an intensive week.
• Delegating it entirely to HR. HR can organize the process, but onboarding is done by the direct manager. If the manager shows up on day one and reappears at the 90-day review, there is no onboarding; there is an induction with a final exam.
• Not writing the 30-60-90 plan. Without written goals, the 90-day review runs on feelings, and both the new hire and the manager arrive with different versions of what was expected.
• Assuming the context is understood. Internal acronyms, names of old projects, references to decisions made a year ago: obvious to the team, noise to the new hire. A glossary and access to the decision history save weeks of confusion.
• Forgetting connection. Scheduling training is easy; scheduling relationships feels artificial, so it does not get done. But the person who has nobody to ask informally at day 30 is at risk, however good their training was.
• Ending at 90 days. The end of probation is not the end of onboarding. Months four through twelve are what turn a person who performs into a person who stays.
• Not asking the new hire for feedback. Whoever just went through the process is the best source for improving it. A short survey at 30 and 90 days costs little and avoids repeating the same failures with the next hire.

How to measure onboarding

What is not measured stays a good intention. These metrics are enough for most companies and can be collected without special tooling.

Two usage recommendations. First: define the criterion for full productivity before the person starts, because defining it afterwards is tempting and unreliable. Second: compare across hires, not against an ideal. If time to full productivity drops from fourteen weeks to ten between one hire and the next, onboarding is improving, even if ten weeks still sounds like a lot.

How AI speeds up onboarding

The bottleneck in onboarding is not information, of which there is plenty, but access to it at the right moment without depending on other people's calendars. That is where AI contributes the most, and specifically in the part of onboarding that happens in meetings.

SuperIntern is a botless AI meeting assistant for Mac and Windows. It captures audio directly from the device, so no bot joins the call and it works the same in Zoom, Google Meet, Microsoft Teams, Webex and in-person meetings. For onboarding, it changes four things.

• Context sessions are recorded and can be re-read. Every session with another department, every welcome meeting, every one-on-one produces a transcript with speaker identification and a structured summary. The new hire stops trying to write everything down while understanding half of it, and can return to the exact explanation when they need it, without asking a third time.
• The team's history becomes shadowing on demand. With the Team plan, meetings are shared by project in the Workspace. Someone joining can read the last three months of notes on the account they inherit, hear how a difficult objection was handled, or understand why a decision was made before they arrived. Shadowing stops depending on the meeting happening to fit their calendar.
• Context questions get answered without interrupting anyone. AI chat over your meetings lets you ask in plain language: "what was decided about pricing for this customer, and why?" or "who is the technical contact on this account?". The answer comes from the real content of the meetings, not from the memory of whoever happens to be free.
• Onboarding meetings get their own template. The AI Canvas builds the note in real time with whatever structure you ask for in plain language. For a 30-day check-in, for example: "goals for the block, status of each, blockers, agreements and review date". The 30-60-90 record writes itself during the conversation, and the 90-day review rests on three real documents rather than on recollection.

For international hires there is one more piece: real-time captions and translation in more than 50 languages, with summaries in whichever language each person chooses. Someone joining from another language takes part in meetings from week one with the same access to the content as everyone else.

On limits, plainly: AI solves the capture, record and retrieval layer. Designing the plan, having the real conversations and building the relationship remain the job of the manager and the team. There is a free plan, so a practical way to start is to turn it on for the next hire, in the context sessions and the check-ins, and compare with the previous one.

Onboarding plan template to copy

This template gathers the essentials of the guide into a document the manager can fill in before day one and review with the new hire in the first week.

ONBOARDING PLAN

New hire: [Name]              Role: [Role]
Manager: [Name]               Buddy/mentor: [Name]
Start date: [YYYY-MM-DD]
Reviews: day 30 [date] · day 60 [date] · day 90 [date]

PREBOARDING (before day one)
- Contract and HR paperwork: [owner, status]
- Equipment and access: [owner, status]
- First-week agenda sent: [date]

DAYS 1-30 · LEARN
Observable goals:
1. [e.g. explain the product and the team map in an internal meeting]
2. [e.g. complete training on tools X and Y]
3. [e.g. deliver the first real task: ...]
Context sessions: [department and person] · [department and person] · ...
Shadowing: [meetings or recordings to review]
Day 30 check-in: [date] · Outcome: [pending]

DAYS 31-60 · CONTRIBUTE
Observable goals:
1. [e.g. run ... with supervision]
2. [e.g. lead ... meetings and write their notes]
3. [e.g. present an improvement proposal on ...]
Day 60 check-in: [date] · Outcome: [pending]

DAYS 61-90 · LEAD
Observable goals:
1. [e.g. manage ... autonomously]
2. [e.g. lead ...]
3. [e.g. one-on-ones with ... departments]
Day 90 review: [date] · Outcome: [pending]
Probation decision (if applicable): [deadline]

FOLLOW-UP THROUGH THE FIRST YEAR
Monthly check-ins: [dates]
Development plan: [to be defined at the 90-day review]

RESOURCES
Internal glossary: [link]
Meeting and decision history: [link]
Role documentation: [link]

Two tips. Keep the plan where the new hire and the manager see it daily, not in an HR folder. And update the "Outcome" field at every check-in with one sentence, even if it is just "met" or "pending because of X": that history is what makes the 90-day review useful.

Frequently asked questions

What is meant by onboarding?

It is the process by which a company integrates a new hire from the moment they accept the offer until they are fully productive and feel part of the team. It covers the administrative basics, clarity about the role, the company's culture and relationships with the team, and usually lasts between three months and a year.

What is onboarding in a company, and who leads it?

In a company, onboarding is the program for integrating new employees. HR organizes the process and the administrative side, but the actual integration is led by the direct manager, supported by a buddy or mentor and the rest of the team. Onboarding delegated entirely to HR stays at the level of orientation.

What is the difference between onboarding and orientation or induction?

Orientation is the welcome and the company presentation, usually a day or two. Induction is the initial training on the role, processes and policies, usually one to two weeks. Onboarding includes both and adds cultural integration, relationship building and support through to full productivity, over 90 days or more.

What are the 4 Cs of onboarding?

Compliance (the legal and administrative basics), Clarification (clarity about the role and expectations), Culture (the company's written and unwritten norms) and Connection (relationships with the team and key people). The model was proposed by researcher Talya Bauer and serves as a check that a program does not stop at paperwork.

How long should onboarding last?

At least 90 days, which is the span of the 30-60-90 plan and, in many countries, of the probation period. The most effective programs keep check-ins going through the first year, because months four to twelve are when commitment and full productivity are consolidated.

What is a 30-60-90 day plan and who writes it?

It is a plan that splits the first three months into three blocks with observable goals: learn (days 1-30), contribute (days 31-60) and lead (days 61-90). The direct manager writes it before day one and reviews it with the new hire in the first week, adjusting it at each check-in.

How do you run good remote onboarding?

With more structure, not less: the first two weeks' agenda locked before day one, a buddy with allocated hours, documentation that is real and accessible, cameras on in the first meetings, and a record of the context sessions the new hire can re-read. AI meeting notes and real-time translation tools help especially in distributed and international teams.

Conclusion

Onboarding is the part of hiring that decides whether the hire works out. It starts before day one, it is led by the direct manager, and it does not end at 90 days. The 4 Cs list what it must cover, the phases order the time, the 30-60-90 plan turns expectations into checkable goals, and the checklist prevents the omissions that repeat most often.

Of everything above, the two habits with the highest return are the cheapest: write the 30-60-90 plan before the person arrives, and make sure everything explained to them in meetings is recorded and can be looked up. The first delivers clarity; the second turns weeks of spoken information into a resource to return to, and stops integration from depending on other people's memory and calendars.

Try SuperIntern Free : Botless real-time meeting notes. Every onboarding session, one-on-one and check-in is recorded and searchable for the person joining.