Employee Onboarding SOP: A 30-60-90 Day Operating Template

Onboarding is the most important operational process that many companies run by memory. A new person's first weeks shape how quickly they become productive, how they feel about the company and whether they stay. Yet in many organizations, the process depends on whichever manager happens to be organized, a chain of emails to IT and HR and a laptop that arrives on the wrong day.

A good onboarding procedure is not about welcome swag or a long slideshow. It is a coordinated set of handoffs across HR, IT, finance, facilities and the hiring manager, designed so that the new hire arrives to a working desk, working accounts and a clear plan. It then gives them structure for the first ninety days, so that expectations, support and feedback are explicit.

This guide gives you an operating template: the phases, the owners, the checklists, the controls and the metrics. Adapt it to your size, industry and jurisdiction. If you are writing the procedure from scratch, our guide on how to write an SOP people follow explains the structure and testing approach used here.

Why a standard process matters

When onboarding is ad hoc, the costs show up in predictable ways.

• Wasted early weeks. The new hire waits for equipment, access and information.
• Inconsistent experience. Some teams do it well and others do not, which feels unfair and affects retention.
• Security gaps. Over-permissioned accounts, missed security training and unmanaged devices.
• Compliance misses. Required forms and acknowledgments not completed on time.
• Manager overload. Each manager reinvents the plan from scratch.
• Lost knowledge. Good practices stay in one person's head.

A standard process turns onboarding from a series of favors into a reliable system, with room for personalization where it counts.

Roles and ownership

Clear ownership prevents tasks from falling between teams. A typical split:

Role	Primary responsibilities
Hiring manager	Role plan, goals, team introductions, weekly check-ins, feedback
Onboarding buddy	Day-to-day questions, culture and informal norms
HR or People Operations	Offer paperwork, compliance forms, benefits, orientation, process ownership
IT	Equipment, accounts, access, security setup
Finance or Payroll	Payroll setup, expenses and any corporate card
Facilities or Office Operations	Desk, badge, building access, or remote equipment shipping
Security or Compliance	Required training and policy acknowledgments
Department or functional leads	Role-specific training and systems

Name a single process owner, often in HR or People Operations, accountable for the end-to-end experience and for keeping this SOP current.

Phase 0: Pre-boarding (offer accepted to day one)

The goal is to remove friction so that the new hire arrives ready to start. Begin as soon as the offer is accepted.

HR or People Operations

• Send the welcome message with start date, time, location or video link, who to contact and what to expect on day one.
• Collect required personal and employment information through your secure HR system, not by email attachment.
• Prepare employment paperwork and policy acknowledgments. In the United States, this includes tax withholding forms and employment eligibility verification, which have specific timing rules. Confirm your obligations and deadlines with your HR advisor or counsel, as requirements depend on your situation.
• Enroll the person in payroll and benefits workflows, with deadlines communicated clearly.
• Create the new-hire record in the HR system, which should serve as the trigger for other teams.

IT

• Order or allocate equipment based on a standard kit for the role, and ship or prepare it with enough lead time.
• Create accounts and mailbox based on a role-based access template, with the minimum permissions needed. Do not copy the access of a predecessor, which often includes outdated or excessive rights.
• Prepare the device with required security configuration, such as disk encryption, endpoint protection and device management.
• Prepare multi-factor authentication enrollment instructions.

Hiring manager

• Draft the 30-60-90 day plan (see below).
• Schedule the first week: introductions, training sessions and a first one-to-one.
• Assign an onboarding buddy.
• Tell the team about the arrival, and prepare their first tasks.

Facilities

• Prepare the workspace and building access, or arrange shipping to the remote employee's address.

Control point: the day before the start date, the process owner confirms that equipment, accounts and the first-week schedule are ready. If anything is missing, they escalate immediately, since a poor first day is hard to recover from.

Day one

The aim is simple: the new hire feels welcome, can log in and knows what happens next.

Morning

• Welcome and orientation by the hiring manager, including the schedule for the week.
• Equipment handover or confirmation, and sign-in to core systems.
• Multi-factor authentication setup with IT support.
• Meet the onboarding buddy.
• Completion of any remaining day-one paperwork within required timeframes.

Afternoon

• Overview of the company, mission, structure and how the team fits.
• Introduction to key tools and where to find help.
• A first small task that gives a quick sense of progress.
• End-of-day check-in: how did it go, what is unclear, is anything blocked?

Security note: new hires should receive security and acceptable use guidance in the first days, before they have significant access to sensitive systems.

First week

• Complete required compliance and security training, with a deadline.
• Meet key stakeholders across the teams they will work with.
• Begin role-specific training and shadowing.
• Review the 30-60-90 plan with the manager and agree on priorities.
• Hold a first-week check-in: what has gone well, what has been confusing, what is needed?

Ask the new hire for feedback now. Their fresh view of your onboarding process is valuable, and early issues are easier to fix.

The 30-60-90 day plan

A simple structure gives clarity on expectations. Customize by role.

Days 1 to 30: Learn

Goal: understand the company, the team, the tools and the work.

• Complete all required training.
• Learn the core systems and processes relevant to the role.
• Meet the key colleagues and internal customers.
• Shadow experienced team members.
• Take on small, well-defined tasks with support.
• Understand the goals of the team and how success is measured.
• Agree on goals for the next 60 days.

Check-in at day 30: review progress, address gaps, collect feedback on onboarding and confirm priorities.

Days 31 to 60: Contribute

Goal: begin delivering independently on defined responsibilities.

• Own specific tasks, projects or accounts, with decreasing supervision.
• Identify one or two improvements or questions about current processes.
• Build working relationships with partners in other teams.
• Receive and act on regular feedback.
• Review the access they hold and confirm it is appropriate for the role.

Check-in at day 60: assess the quality of work, review how the role is shaping up, adjust the plan and discuss development.

Days 61 to 90: Own

Goal: operate with full responsibility for the role and plan ahead.

• Fully own the core responsibilities of the position.
• Deliver a meaningful result or project that demonstrates impact.
• Contribute ideas for improvement based on what they have seen.
• Set goals for the next quarter in alignment with the team plan.
• Share observations on the onboarding experience.

Check-in at day 90: a structured review of performance, fit and development. For roles with a probationary or introductory period, document the outcome according to your policy and applicable law.

The specific tasks will vary widely. What matters is that goals, support and feedback are explicit at each stage.

Access and security controls

Onboarding is where access is granted, so it is also where the most avoidable security problems begin.

• Role-based access. Define standard access bundles per role and grant only those. Additional access requires a request with justification and an approval from the system owner.
• Least privilege. Start with the minimum and add as needed.
• Approval trail. Record who requested and approved each access grant.
• Multi-factor authentication. Required before the new hire accesses sensitive systems.
• Device security. Managed devices with encryption and security tools.
• Acceptable use and confidentiality. Provide the policy and obtain acknowledgment.
• Access review at 30 and 90 days. Confirm that access still matches the role. Remove anything unnecessary.
• Link to offboarding. The same inventory of accounts and equipment should feed the offboarding procedure so that nothing is forgotten when someone leaves.

Remote and hybrid considerations

Distributed onboarding needs more deliberate design, because the casual hallway moments are missing.

• Ship equipment early and test it, with clear setup instructions and a contact for help.
• Schedule video introductions and short, frequent check-ins during the first weeks.
• Provide a written guide to how the team communicates, which channels to use and what response times to expect.
• Make the buddy relationship explicit, with a weekly slot.
• Consider timing across time zones, and avoid scheduling the first week entirely outside the person's working hours.
• Share how to find answers independently, such as a documentation hub, and encourage questions.

The onboarding checklist

Use a shared, trackable checklist. Whether it lives in an HR system, a project tool or a spreadsheet, it should show every task, owner, due date and status.

PRE-BOARDING (before start)
[ ] Offer accepted; new-hire record created (HR)
[ ] Welcome message sent (HR)
[ ] Employment paperwork prepared and sent (HR)
[ ] Payroll and benefits enrollment initiated (HR / Payroll)
[ ] Equipment ordered and configured (IT)
[ ] Accounts created with role-based access (IT)
[ ] Workspace or remote shipment ready (Facilities)
[ ] Buddy assigned (Manager)
[ ] First-week schedule and 30-60-90 plan drafted (Manager)
[ ] Day-before readiness check complete (Process owner)

DAY ONE
[ ] Welcome and orientation (Manager)
[ ] Equipment received; sign-in and MFA complete (IT)
[ ] Paperwork items completed within required timeframes (HR)
[ ] Security and acceptable use guidance delivered (Security)
[ ] Intro to buddy and team (Manager)
[ ] End-of-day check-in held (Manager)

WEEK ONE
[ ] Required training completed (New hire)
[ ] Key stakeholder meetings held (Manager)
[ ] 30-60-90 plan reviewed and agreed (Manager + New hire)
[ ] First-week feedback collected (HR / Manager)

DAY 30 / 60 / 90
[ ] Check-in held and documented (Manager)
[ ] Access review completed (IT / Manager)  [30 and 90]
[ ] Onboarding feedback collected (HR)  [30 and 90]

Measuring whether onboarding works

If you do not measure onboarding, you cannot improve it. Track a small set of indicators.

Readiness measures

• Percentage of new hires with working equipment and accounts on day one.
• Time to first meaningful task.
• Number of onboarding tasks completed late.

Experience measures

• New hire satisfaction at day 30 and day 90, using a short survey with a few consistent questions.
• Manager satisfaction with the process.

Outcome measures

• Time to productivity, defined by the manager for each role, such as time to complete a first independent project.
• Retention at 90 days and one year, compared with historical figures.
• Compliance completion rates and timeliness.

Review these quarterly with HR, IT and managers, and act on what you find. Share improvements with the people who gave feedback so they know it matters.

Common mistakes

Starting too late. Waiting for the start date to order equipment and create accounts guarantees a rough first day.

Information overload. Sixty slides on day one help no one. Spread learning across the first weeks.

No owner for the end-to-end process. Each team does its part, and nobody sees the whole.

Copying a predecessor's access. This carries over unnecessary permissions.

Skipping the manager's role. Even a perfect process cannot replace a manager who sets goals and gives feedback.

Ignoring remote employees. They need more structure, not less.

Never asking the new hire. They are the best source of insight into what is broken.

Treating it as finished after week one. The first ninety days are the full journey.

Key takeaways

• Onboarding is a cross-functional process, so name a process owner and assign every task to a role.
• Begin at offer acceptance. Prepare equipment, accounts, paperwork and the first-week plan before day one.
• Use a 30-60-90 day structure to make goals, support and feedback explicit.
• Build in access controls: role-based bundles, least privilege, approval trails, multi-factor authentication and reviews at 30 and 90 days.
• Adapt for remote work with earlier shipping, more check-ins and clearer communication norms.
• Measure readiness, experience and outcomes, and improve based on what you learn.

A strong onboarding process says something important to a new colleague: we were ready for you, and we want you to succeed.

Sources and further reading

Links were checked on October 11, 2026. Pricing, limits and rules change, so confirm on the source before you act.

• USCIS: I-9 Central. The official source for Form I-9 employment eligibility verification, including completing, correcting and retaining the form.