New Employee Onboarding Checklist and 30-60-90 Day Plan Template
employee onboardinghuman resourcesnew hire trainingsmall businessoperations

New Employee Onboarding Checklist and 30-60-90 Day Plan Template

CChecklist.top Editorial Team
2026-11-16
7 min read

Use this employee onboarding checklist and 30-60-90 day plan to organize access, equipment, training, feedback, and ownership.

A consistent employee onboarding process helps a new hire become productive without leaving managers, operations teams, or the employee to guess what happens next. This reusable employee onboarding checklist covers the work to complete before the start date, on the first day, during the first few weeks, and across a practical 30-60-90 day plan.

Overview

Onboarding is more than sending a welcome message and creating an email account. It is a coordinated business process that connects administration, access, equipment, policies, introductions, training, and feedback. A small business onboarding template should make each task visible, assign a completion owner, and show when the task is due.

Use the checklist below for a new employee, internal transfer, or returning team member. Adapt it to the role rather than treating it as a fixed script. A customer-facing role may need product and service training early, while a technical role may need a longer access review and structured project handoff. For repeated roles, save the completed version as an operations checklist or SOP so future managers do not have to rebuild the process.

For broader workflow planning, pair this checklist with a project kickoff checklist when the employee will join a new initiative. If the hire needs several applications, document those decisions with a small business software stack checklist.

Suggested ownership model

  • Manager: Owns role expectations, goals, training priorities, introductions, and regular check-ins.
  • Operations or HR owner: Coordinates forms, policies, records, and the overall onboarding workflow.
  • IT or system owner: Prepares equipment, accounts, permissions, and security steps.
  • Buddy or peer contact: Helps the new hire understand everyday team practices and where to ask questions.
  • New employee: Completes assigned reading, training, forms, and questions, and confirms when access works.

Checklist by scenario

Before the first day

Start as soon as the start date and role details are confirmed. Give every item an owner and target date. A simple tracker can use the columns: Task, owner, due date, status, link or evidence, and notes.

AreaChecklist itemsCompletion owner
Role setupConfirm title, reporting line, work location, schedule, first-week priorities, and role-specific outcomes.Manager
AdministrationSend required employment documents, explain where to find policies, and confirm how questions about administration should be raised.Operations or HR owner
EquipmentPrepare the laptop or other required equipment, accessories, workspace, and any role-specific materials.IT or operations
AccessCreate only the accounts and permissions needed for the role, test sign-in instructions, and record the system owner for each account.IT or system owner
SecurityPlan device protection, password or sign-in guidance, data-handling expectations, and the process for reporting a suspected access problem.IT or manager
IntroductionsSchedule a welcome meeting, key one-to-ones, team introductions, and any customer, vendor, or cross-functional meetings that are useful in week one.Manager
TrainingPrepare a first-week learning plan, product or service material, process documentation, and a small task that demonstrates the workflow.Manager or buddy

Send a short first-day agenda before the start date. Include where and when to arrive or sign in, who will meet the employee, what to have ready, and how to get help if access does not work. Avoid sending a large collection of links without context; group resources by what the employee needs to do first.

First day

  • Welcome the employee and explain the plan for the day.
  • Confirm equipment, account access, communication channels, and calendar access.
  • Review the team structure, reporting relationship, regular meetings, and preferred communication methods.
  • Explain the role's immediate priorities and what a successful first week should look like.
  • Walk through essential policies, recurring procedures, and where the current versions of documents are stored.
  • Introduce the employee to close collaborators and explain each person's role.
  • Complete a low-risk, practical task so the employee can use the main tools with support.
  • Leave time for questions and ask what remains unclear before ending the day.

First week

The first week should establish context and working habits rather than overload the employee with every available document. Use a daily checklist when the role involves many systems or handoffs.

  • Review the role description and translate it into a short list of near-term priorities.
  • Demonstrate the most important business processes, including where work enters the team and how it is completed.
  • Assign required training in a sensible sequence, with an owner for each module or shadowing session.
  • Have the employee observe a real workflow, then complete a similar task with review.
  • Explain quality standards, approval points, escalation routes, and expected response times where relevant.
  • Schedule a first-week check-in to discuss access, workload, questions, and any missing resources.
  • Capture improvements to the onboarding checklist while the experience is fresh.

30-60-90 day plan template

A 30-60-90 day plan should be specific enough to guide action but flexible enough to reflect the employee's actual progress. Set outcomes, not just a list of meetings attended. Each milestone should have a measure or observable result, a support owner, and a review date.

PeriodPrimary focusExample outcomesCheck-in questions
Days 1-30Learn and contribute with supportUnderstands core responsibilities, completes essential training, uses required systems, and delivers an initial task or work sample.What is clear? Where is access or context still missing? Which task needs another demonstration?
Days 31-60Build independence and consistencyOwns recurring responsibilities, follows the relevant SOP checklist, collaborates with key partners, and receives feedback on quality and pace.Which responsibilities can now be handled independently? What pattern should be improved?
Days 61-90Own outcomes and improve the workflowMeets agreed role expectations, manages priorities, identifies one practical process improvement, and agrees on longer-term goals.What results demonstrate readiness? What support or development should come next?

Write the plan in the employee's own task system or a shared team workflow template. Keep the number of major outcomes manageable. For recurring procedures, link to an approved SOP creation checklist rather than copying an outdated process into the plan.

What to double-check

Before marking onboarding complete, review the details that are easy to overlook:

  • Access matches the role: Confirm that the employee can reach required tools and cannot access systems or data that are unrelated to the role. Remove temporary access when it is no longer needed.
  • Documents have clear owners: Every important policy, process, and template should have a location and a person responsible for keeping it current.
  • Equipment is usable: Check that the employee can sign in, connect to meetings, use required peripherals, and recover from a basic access problem.
  • Expectations are written down: Record priorities, decision rights, deadlines, communication norms, and the definition of acceptable work.
  • Training includes practice: Reading a process is not the same as completing it. Include observation, guided practice, and reviewed work.
  • Feedback is two-way: Ask the new employee what is confusing, repetitive, missing, or unnecessarily difficult. These observations often reveal weak workflow documentation.
  • Local requirements are verified: Employment administration can vary by location and situation. Have the appropriate internal owner or adviser confirm which forms, notices, records, and policies apply rather than relying on a generic checklist.

Keep an audit-friendly completion record without storing sensitive personal information in a general task list. Link to the approved system of record where appropriate, and limit access to confidential documents.

Common mistakes

Assigning every task to the manager

Managers should own the outcome, but they do not need to perform every administrative or technical step. Assign tasks to the person best placed to complete them and use one tracker to show progress.

Creating accounts too early or too broadly

Premature or excessive access creates avoidable confusion and risk. Prepare what is needed, confirm the role, and use the organization's normal approval and access-removal process.

Focusing on information instead of decisions

A new hire does not need to memorize every document. Explain which resources matter now, which decisions the employee can make, and when to ask for approval.

Skipping the first-week review

Small access problems, unclear priorities, and missing introductions become more expensive when they remain hidden. Schedule a deliberate review rather than assuming silence means success.

Using the same plan for every role

A shared employee onboarding checklist is useful, but role-specific outcomes make it meaningful. Keep the common foundation and add a short section for systems, processes, customers, and skills unique to the position.

When to revisit

Review this new hire checklist before each seasonal planning cycle and whenever the employee onboarding process changes. A quarterly or periodic review is especially useful for teams that hire regularly. Compare the checklist with the most recent onboarding experience and remove steps that no longer apply.

Update the template when you change collaboration, payroll, project management, identity, or documentation tools. Recheck account owners, invitation instructions, permission groups, and links after a software migration. Review security and privacy steps whenever the way your team stores, shares, or accesses information changes.

Also revisit the plan after an internal transfer, a significant role change, or feedback from several new employees. To improve the process:

  1. Ask the manager and employee which steps helped and which created friction.
  2. Identify missed tasks, duplicate instructions, and unclear ownership.
  3. Convert repeated questions into a short guide, checklist item, or SOP.
  4. Assign an owner and review date to every important update.
  5. Test the revised checklist with the next hire and adjust it again if needed.

Save a clean master copy, then create a role-specific version for each hire. That approach keeps the onboarding process consistent while leaving room for the practical differences between roles.

Related Topics

#employee onboarding#human resources#new hire training#small business#operations
C

Checklist.top Editorial Team

Productivity and workflow editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.