How to Build an Employee Onboarding SOP: 90-Day Template

Most companies can tell you they have an onboarding process. Few can tell you what happens if the person who normally runs it is out sick on someone’s first day.

An employee onboarding SOP is how you make sure that starting point isn’t left to chance. Not a checklist someone half-remembers, but a documented process with clear phases, clear owners, and steps specific enough that it runs the same way whether the founder handles it or someone brand new to the role does.

I’m walking you through the actual 90-day structure, a template you can copy, and how to use AI to draft your own version instead of starting from a blank page.

What Is an Employee Onboarding SOP?

An employee onboarding SOP is a documented, step-by-step process that defines who does what, when, and to what standard, from offer acceptance through the new hire’s first 90 days. Unlike a checklist, it assigns ownership and timing, not just tasks. Unlike an employee handbook, it covers the onboarding process itself, not company policy.

Without one, onboarding lives in whoever’s memory happens to be running it that day, and changes depending on their schedule and mood. That gap costs more than convenience: according to Gallup’s State of the Global Workplace: 2026 report, global employee engagement fell to 20% in 2025, its lowest level since 2020, and for a lot of employees, that decline starts on day one. 

ProProfs KB AI Coach
Ask anything about building a knowledge base
AI can make mistakes. Try Knowledge Base Free Terms

What Does a 90-Day Onboarding SOP Actually Look Like?

A 90-day onboarding SOP breaks into five phases, each with its own owner and specific actions. Here’s what each one actually covers.

Phase 1: Preboarding (Offer Acceptance to Day 1)

Owner: Hiring manager

This covers everything between a signed offer and the new hire’s first morning: system access provisioned, equipment ordered and shipped, a welcome email with logistics, and an assigned onboarding buddy notified ahead of time. This SOP works alongside the other onboarding documentation a new hire receives, the welcome letter, role-specific training manual, and handbook, rather than replacing any of them.

A prompt for this step would look like this:

Write a preboarding checklist for a new Customer Support Specialist hire at a 30-person SaaS company. Cover: system and equipment provisioning, a welcome email template with placeholders for start date and buddy name, and a 3-day-before-start reminder task. Format as a table with columns for Task, Owner, and Deadline relative to the start date.

What a completed version looks like:

Task Owner Deadline
Confirm signed offer letter and start date HR/Hiring Manager Day of acceptance
Submit IT ticket for laptop, monitor, and peripherals Hiring Manager 7 business days before start
Provision email, Slack, and helpdesk software accounts IT 5 business days before start
Order equipment shipment if remote Office Manager 7 business days before start
Assign onboarding buddy Hiring Manager 5 business days before start
Draft and send welcome email Hiring Manager 3 business days before start
Confirm equipment delivered and access working IT 1 business day before start
Send Day 1 reminder with agenda attached Hiring Manager 1 business day before start

Phase 2: Day One

Owner: Hiring manager and direct supervisor

This covers the actual first day: system access confirmed working, a company overview, a 1:1 welcome meeting, introductions to the team, and an end-of-day check-in to catch anything that fell through.

Example: A 30-minute company overview at 9:30, a team lunch at noon, and a 15-minute end-of-day check-in at 4:30 covering one question: what’s still unclear.

Phase 3: Week One (Days 2-5)

Owner: Direct supervisor and onboarding buddy

This covers role-specific training, shadowing the actual job being performed, and daily short check-ins, not a single first-day check-in and then silence for a week.

Example: A daily 15-minute morning check-in with the supervisor, plus shadowing three real instances of the core job function before attempting it solo.

Phase 4: Days 8-30

Owner: Hiring manager

Check-ins reduce from daily to twice weekly. The new hire starts handling core responsibilities under supervision, building toward the first formal review at day 30.

Example: A structured 30-day review covering three questions: what’s going well, what’s unclear, and what needs to change before day 60.

Phase 5: Days 31-90

Owner: Hiring manager

Weekly check-ins continue, independent responsibility increases, and formal reviews happen at day 60 and day 90, ending in full transition to standard performance management.

Example: The day 90 review confirms full role ownership and formally closes out the onboarding period, moving the employee onto whatever review cycle the rest of the team follows.

Rather than build an employee onboarding SOP template from scratch, ProProfs has a free SOP template with the standard sections already structured: purpose, scope, roles and responsibilities, and step-by-step procedure, so you’re filling in your own phases and owners rather than designing the document format yourself.

Build Your Onboarding SOP Faster With a Ready-Made Template

How to Build an Employee Onboarding SOP?

Once you’ve mapped out Preboarding, Day One, Week One, Days 8-30, and Days 31-90, here’s how to create SOPs for new employee training and onboarding, not just on paper.

1. Choose a Template or Start From Scratch

SOP Template

Begin by setting up a dedicated site for your onboarding SOP. You can use ProProfs’ ready-made SOP template or build from scratch with the Visual Builder.

Here’s how:

  • Go to Sites > +Create New
  • Pick a layout and organize folders by phase: Preboarding, Day One, Week One, Days 8-30, Days 31-90

Pro Tip: Start with the five-phase structure from the start, it’s easier to expand a phase later than to reorganize a flat document once it’s already full.

2. Customize for Your Organization

Customization screenshot

Personalize the SOP to reflect your actual team and workflows.

Here’s how:

  • Use Edit Home to change layout, navigation, fonts, and colors
  • Add your company logo and rename categories to match your phase names and department owners (Hiring Manager, Supervisor, Buddy)

Pro Tip: Use your team’s actual job titles and phase names, not generic labels; it makes the SOP easier for a new manager to search and follow later.

3. Import Existing SOPs or Drafts

Import existing docs

If your onboarding process currently lives in a scattered doc, spreadsheet, or a folder of half-finished checklists, bring it in rather than starting from zero.

Here’s how:

  • Go to Settings > Import Files
  • Upload your existing onboarding docs in bulk for formatting and review

Pro Tip: Tag each imported file by phase immediately; sorting a pile of old onboarding notes later is far more painful than tagging them on the way in.

4. Draft or Improve Phases Using the AI Writer

Draft using AI Writer

Whether you’re starting a phase from scratch or fixing a vague one, use the AI Writer to generate a clear first draft.

Here’s how:

  • Click +New Page, select Article
  • Click Generate Article with AI
  • Use a prompt like:
“Create a knowledge base article about a preboarding SOP for a new Customer Support Specialist hire at a 30-person SaaS company. Cover system and equipment provisioning, a welcome email template with placeholders for start date and buddy name, and a 3-day-before-start reminder task. Format the steps as a table with columns for Task, Owner, and Deadline relative to start date.”

Pro Tip: Name the role, company size, and required output format in the prompt; a vague prompt gets a vague draft back.

Create Onboarding Phases Faster With AI-Powered Writing

5. Structure Each Phase for Clarity and Ownership

Break each phase into numbered steps with a named owner and the tools required, the same shape we used for Preboarding through Days 31-90.

Here’s how:

  • Add a Merge Tag to pull in related content, like linking Day One’s agenda directly to the Week One training plan
  • Enable the Table of Contents in Article Settings so the system scans your headings and subheadings automatically, creating clickable navigation

Pro Tip: If a phase needs more than about 10 steps, that’s usually a sign it should split into two linked articles instead of one long one.

6. Add Multimedia, Links, and Cross-References

Add Multimedia, Links, and Cross-References

Onboarding SOPs get followed more consistently when they’re visual, not just a wall of text.

Here’s how:

  • Drag and drop your actual 90-day timeline graphic into the editor
  • Copy-paste an org chart or a flowchart showing how phases hand off from one owner to the next

Pro Tip: Annotated screenshots, arrows pointing at where to click, highlights around the field to fill in, help a first-time onboarding owner more than plain text ever will.

7. Assign SOP Owners and Review Cycles

Assign SOP Owners and Review Cycles

Assign ownership so each phase gets updated by the person actually responsible for it, not left to whoever remembers.

Here’s how:

  • Use role-based access to define who can view, edit, or manage each phase
  • Create roles like Hiring Manager, Supervisor, and Buddy, and assign each to the phase they own

To set a review workflow:

  • Set an article’s status to Ready for Review when a phase needs a check
  • Once reviewed, change the status to Published

Pro Tip: Assign a specific review date to each phase, not just an owner, an owner with no deadline tends to review “eventually,” which usually means never.

8. Map Phases to Compliance Requirements

This is where onboarding SOPs carry more legal weight than most other procedures. I-9, W-4, and state new-hire reporting deadlines all live inside the Preboarding and Day One phases, and missing them costs real money, not just time.

Here’s how:

  • Use metadata tags to flag compliance-critical steps (I-9, W-4, state reporting)
  • Track revision history so you can prove what the process looked like on any given hire date, not just today

Pro Tip: Do this step as soon as Preboarding and Day One are drafted, not after the rest of the SOP is finished; retrofitting compliance tags onto a completed document is where deadlines get missed.

Use Revision History and Review Dates to Keep Onboarding SOPs Current

9. Preview, Publish, and Keep It Current

Preview and Publish

Before rolling this out to your next hire, confirm it actually reads clearly end to end.

Here’s how:

  • Use Preview to test the layout and navigation across all five phases
  • Click Save & Done to publish, or export as PDF for anyone who needs an offline copy

Pro Tip: Have someone who’s never run onboarding before test the document. If they hesitate anywhere, that’s the exact spot a real new hire’s onboarding would stall too.

What Mistakes Break Onboarding SOPs?

Writing the five phases is the easy half. Most onboarding SOPs fail somewhere after that, not because the phases were wrong, but because of what happened once the document was technically done.

1. Nobody Owns It After Launch

A phase gets written, then it becomes nobody’s job to check whether it still matches reality. Six months later, the welcome email still references a tool the company stopped using in March. Assign a named owner to each phase, not a vague sense that HR handles it.

2. It Assumes the Same Person Always Runs It

An SOP for employee onboarding that only makes sense if the founder personally runs it isn’t really an SOP, it’s a habit written down. The real test is whether someone brand new to the role could follow it without a single clarifying question.

3. Compliance Gets Bolted On Instead of Built In

I-9, W-4, and state reporting deadlines get treated as a separate afterthought instead of living inside the Preboarding and Day One phases where they actually happen; the same HR documentation discipline that governs onboarding paperwork applies here too. This is exactly how a missed 3-business-day I-9 deadline turns into a real penalty, not a paperwork inconvenience.

4. Check-Ins Stop the Moment the First Week Ends

A lot of onboarding SOPs are strong through Week One and then go silent. Days 8-30 and 31-90 matter just as much; that’s where a new hire either becomes genuinely independent or quietly struggles without anyone noticing until the 90-day review.

5. The SOP Never Gets Tested With a Real Hire

A document that reads clearly to the person who wrote it can still confuse someone experiencing it for the first time. Have an actual new hire follow it start to finish and flag every spot they hesitated; that’s the real quality check, not a read-through by someone who already knows the process.

FREE. All Features. FOREVER!

Try our Forever FREE account with all premium features!

Start With Preboarding, Not All Five Phases at Once

An onboarding SOP doesn’t fail because nobody tried hard enough. It fails because it got written all at once instead of one phase at a time, tested against a real hire. Fix the order, and the rest holds up on its own.

Start with Preboarding, the shortest phase with the clearest owner. Write it, run it on your next hire, fix what breaks, then move to Day One. Once it’s live, keep it that way: update it the same week your process changes, not at the next scheduled review.

Building this inside a proper platform means one place to update, not a template scattered across shared drives and old email threads.

ProProfs Knowledge Base is genuinely the easiest customer support help center & internal employee knowledge base in one. Try it on the free forever plan, up to 25 articles, no credit card required.

Frequently Asked Questions

How is an onboarding SOP different from a 30-60-90 day plan?

A 30-60-90 day plan sets performance goals for the new hire, what they should achieve by each milestone. An onboarding SOP defines what the company does to support them, who owns each phase, what gets provisioned, and when. Most teams need both, and the SOP is often what makes a 30-60-90 plan actually achievable. Without the SOP side, a 30-60-90 plan just sets expectations nobody's actually equipped to help the new hire meet.

Can one onboarding SOP work for every role in the company?

The five-phase structure works universally, but Week One's training content should differ by role. Keep the core SOP the same for everyone and add a role-specific appendix for what changes; a developer's Week One looks different from a sales hire's. The mistake is either writing one generic SOP that fits nobody well, or writing a completely separate SOP per role that becomes unmaintainable within a year.

Does a small company with no dedicated HR person still need an onboarding SOP?

Especially then. Without an HR team, onboarding usually depends entirely on whoever's available that week, which is exactly the inconsistency an SOP is built to prevent. It doesn't need to be elaborate; a two-page version covering the five phases is enough to start. The founder or office manager running onboarding today is exactly who benefits most from writing it down, since they're the ones who'll eventually hand it off.

How do you know if an onboarding SOP is actually working?

Track whether new hires reach independent responsibility by day 90 without extra hand-holding, and whether 90-day retention holds steady. If either one is slipping, the gap is usually in Week One or Days 8-30, not the paperwork-heavy Preboarding phase. A new hire who's still asking basic logistics questions in week three is a signal the SOP itself has a gap, not that the person is struggling.

What happens to the SOP when your onboarding process changes?

It needs updating the same week, not at the next scheduled review. An SOP describing a process you no longer follow is worse than having no SOP, since it creates false confidence that onboarding is documented when it's actually wrong. This is exactly why assigning a named owner to each phase matters more than having a review date on the calendar.

Should the same person own every phase of the SOP?

No. Ownership should follow who's actually present for that phase: the hiring manager for Preboarding and Day One, the direct supervisor and buddy for Week One, and the hiring manager again for the later reviews. One person owning all five phases usually means it only gets updated when they remember to, which tends to be right after something goes wrong, not before.

Can AI write the entire onboarding SOP in one prompt?

It can draft one phase well if you give it the role, company size, and required elements. Asking for all five phases in a single prompt tends to produce something generic, since there's no room to specify the details that make each phase actually usable. Treat each phase as its own prompt with its own specifics, then assemble the five into the full SOP once each one holds up on its own.

Is a remote-first company's onboarding SOP fundamentally different?

The five phases stay the same, but Preboarding needs to shift earlier, equipment shipped at least a week out instead of two days, and Day One needs to be rebuilt around video calls with a structured hour-by-hour agenda instead of an office tour. The phases people most often forget to adjust are Week One's shadowing step and the buddy system, both of which need a deliberate video-call substitute instead of just assuming they'll happen informally the way they would in an office.

FREE. All Features. FOREVER!

Try our Forever FREE account with all premium features!

About the author

ProProfs Knowledge Base Editorial Team is a passionate group of knowledge management experts dedicated to delivering top-notch content. We stay ahead of the curve on trends, tackle technical hurdles, and provide practical tips to boost your business. With our commitment to quality and integrity, you can be confident you're getting the most reliable resources to enhance your knowledge management initiatives.