30-60-90 day onboarding plan: a guide for SMBs

A new hire receives system access, tours the workplace and attends several presentations. Three weeks later, they still do not know which decisions they can make independently. Their manager believes onboarding was completed on the first day.

A 30-60-90 day onboarding plan organizes learning, working relationships and expected progress across the first months. Its purpose is to make expectations observable and open to discussion, rather than fill a calendar with activities. This guide includes an adaptable model, a fictional example and an original text template to download. The three periods are proposed management checkpoints, rather than legal deadlines or a guarantee of independence. Adjust them to the role, experience, working conditions and support your small business can actually provide. A useful plan makes the manager’s contribution as clear as the employee’s learning goals.

A 30-60-90 day onboarding plan starts with the work

Before scheduling introductions, describe what the person needs to understand and accomplish. Which responsibilities will they own? What mistakes must they avoid? Who can validate a decision? An orientation activity matters when it supports a useful skill, relationship or understanding of how the business operates.

BDC emphasizes planning, regular communication and spreading onboarding activities over time. Source: new employee onboarding steps, updated in July 2025. The staged model below is an original proposal to adapt to your own operations, rather than a universal standard for every job.

Define the contributions of the manager, HR and the colleague supporting the new hire. A workplace buddy cannot answer every question while carrying an unchanged workload. Allocate time for support and explain the boundaries of that person’s role. Questions about priorities may need the manager rather than the buddy.

Prepare equipment, authorized access and essential information before arrival. Give someone responsibility for confirming each item. If a resource is missing, name an owner and a temporary arrangement instead of leaving the new employee to discover and solve the problem on the first morning.

Days 1 to 30: understand and practise with support

The first stage should establish how the organization works, what the role contributes and how important tasks are performed. Introduce people the employee will depend on. Explain quality expectations, priorities and situations requiring validation. Knowing who can answer a particular question makes asking for help easier.

Choose a few representative tasks to observe and then practise with guidance. Ask the employee to explain the process in their own words. Attending a presentation and saying it was understood does not establish that someone can perform the work in an actual situation with competing demands.

At the first checkpoint, discuss what is understood, what has been practised and what remains blocked. A difficulty may reflect missing access, conflicting instructions or a learning need. Distinguish these possibilities before interpreting it as a lack of effort. Record the next support action and who will provide it.

Keep documentation brief: intended learning, activity, resource person, evidence observed and next support step. Limit notes to useful work information. Route sensitive matters to authorized people rather than turning the onboarding plan into a collection of personal comments unrelated to the task.

Days 31 to 60: expand a defined area of ownership

The second stage broadens the work performed without immediate assistance. Specify what the employee can decide, what they must report and what needs approval. Independence includes recognizing a limit and escalating appropriately. It should not be interpreted as an expectation that a new colleague never asks questions.

Assign a complete activity with an expected outcome and a realistic deadline. Observe handovers to other colleagues as well as individual task completion. The new employee needs to understand how their work affects the next person in the process. Confirm that those colleagues know the new arrangements too.

At the checkpoint, ask which obstacles still make the work difficult. A repeated question may reveal an ambiguous procedure rather than simple forgetfulness. Improve the process where needed and confirm that the people involved now use consistent instructions. Otherwise the plan can ask an employee to solve a problem the organization has not addressed.

Days 61 to 90: consolidate progress and agree on next steps

The third stage helps establish a steady contribution and the next development priority. Return to the initial expectations. What can be observed in the work? Which resources are still needed? Which objectives should change because the context has changed? Discuss the evidence rather than treating the calendar as proof of progress.

Entirely fictional example: a coordinator joins a Quebec City business. During the first month, she observes file preparation and practises with a colleague. During the second, she owns a group of files with a planned validation point. During the third, she handles the agreed scope and helps improve an internal handover.

Her manager discovers that late internal approvals are blocking several files. He works with the team to adjust that process rather than simply asking for greater independence. The review separates the coordinator’s learning from the conditions she needs to do the job. It becomes easier to choose an appropriate next step.

They select a development priority, a support arrangement and a follow-up date. Day 90 does not end the management relationship. It provides a transition into the normal feedback and development practices appropriate to the person and role. Further learning can continue without treating every remaining question as a failure of onboarding.

Download the original text template. It includes role expectations, the three stages, support responsibilities and checkpoint questions. You can copy it into your working document without needing a particular application or subscription.

Connect onboarding with responsibilities and development

M360 Compass is a people management operating system for SMBs. Its HR operations describe 30-60-90 day onboarding and HR follow-ups. RoleAlign supports the responsibilities and expectations that give the onboarding path its purpose. The plan should make sense in the context of actual work.

Performance and individual development plan capabilities can then connect learning with development priorities. That continuity helps prevent the welcome plan from becoming disconnected from later conversations. It does not replace manager availability, useful practice opportunities or support from experienced colleagues. Those remain part of the organization’s work.

Before implementation, ask to see a path based on your role and confirm the steps available in your configuration. Establish who prepares activities, who can see the information and who follows up. The platform should support the onboarding method you need, rather than require a generic sequence without examining its value.

Questions managers ask about onboarding

Should every role use the same plan?

Use a shared structure while adapting responsibilities, learning activities and evidence to the role. Technical and administrative positions need different practice opportunities and support. A common form should not make those differences disappear.

Who owns the plan?

The manager owns expectations and checkpoint conversations. HR can coordinate the path, and colleagues can support learning. Make the responsibilities explicit so an essential step does not remain unassigned between departments.

What if the expected independence has not developed?

Review the evidence, available resources and clarity of expectations. Adjust support and priorities with the employee. Employment decisions specific to the situation should follow the applicable rules and appropriately qualified advice.

Which indicators keep the process manageable?

Look at useful activities completed, tasks practised, obstacles resolved and checkpoints held. A completed checklist does not by itself establish learning. Seek observable evidence in the work and a clear next support action.

Begin with one expected outcome and the person who will help achieve it. To connect onboarding, responsibilities and development, request a demonstration of M360 Compass.