Free Employee Onboarding SOP Template
An onboarding SOP that gets every new hire set up the same way.
Part of our free sop templates.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
1.Title Block & Document Control
| SOP Title | {{SOP Title}} |
|---|---|
| SOP ID | {{SOP ID}} |
| Version | {{Version}} |
| Effective Date | {{Effective Date}} |
| Review Date | {{Review Date}} |
| Document Owner | {{Document Owner}} |
| Approver | {{Approver}} |
Keep this block on page one so anyone can audit the document at a glance. Set a Review Date 6–12 months out and assign a single Document Owner who is accountable for keeping it current.
2.Purpose
State in one or two sentences why this procedure exists and what result it delivers when followed correctly.
Write the “why”, not the steps. Example: “This SOP ensures every customer refund is processed accurately, within policy, and within two business days.”
3.Scope
Define which teams, locations, systems, and situations this SOP applies to — and explicitly note what it does not cover.
Naming the boundaries prevents the procedure from being applied to the wrong cases. List any exclusions on their own line.
Onboarding Timeline
| Phase | Tasks | Owner | Done by |
|---|---|---|---|
| Pre-boarding | {{Offer signed, accounts/equipment requested}} | {{HR / IT}} | {{Before start date}} |
| Day 1 | {{Welcome, paperwork, access, intro to buddy}} | {{Manager / HR}} | {{Start date}} |
| Week 1 | {{Role training, team intros, first task}} | {{Manager}} | {{End of week 1}} |
| 30 / 60 / 90 days | {{Check-ins and goal reviews}} | {{Manager}} | {{Day 30 / 60 / 90}} |
Onboarding is a sequence, not an event. Assign an owner and a deadline to every task so nothing (laptop, login, payroll setup) slips through the cracks before or on the start date.
4.Definitions & Abbreviations
| Term | Definition |
|---|---|
| {{Term}} | {{Plain-language definition}} |
| {{Abbreviation}} | {{What it stands for}} |
Only define terms that could be misread by someone new to the process. If there are none, keep this section and write “None” — auditors expect it to exist.
5.Roles & Responsibilities
| Role | Responsibility |
|---|---|
| {{Role}} | {{What this role is accountable for in this procedure}} |
| {{Role}} | {{What this role is accountable for in this procedure}} |
Assign responsibilities to roles, not named individuals, so the SOP survives staff changes. Keep each role to one or two lines.
6.Prerequisites, Materials & Equipment
- {{Access or permission required before starting}}
- {{Tool, system, or login needed}}
- {{Material or document that must be on hand}}
List everything that must be ready before step one. A short checklist here prevents half-finished runs.
7.Safety & Compliance
Note any safety precautions and the regulations or internal policies this procedure must comply with.
If this procedure has no safety or compliance angle, keep the section and write “N/A”. Reference the specific policy or regulation by name where one applies.
8.Procedure (Step-by-Step)
| Step | Action | Owner | Expected Result |
|---|---|---|---|
| 1 | {{Start with a verb — one action per step}} | {{Role}} | {{What “done right” looks like}} |
| 2 | {{Next action}} | {{Role}} | {{Expected result}} |
| 3 | {{Next action}} | {{Role}} | {{Expected result}} |
Aim for roughly 5–15 numbered steps. Begin each with a verb, keep it to one action, and make the Expected Result observable so anyone can confirm the step is complete.
9.Quality Checks & Acceptance Criteria
- {{Measurable check that confirms the work was done correctly}}
- {{Second acceptance criterion}}
Write 2–4 checks that are measurable — a reviewer should be able to answer each with a clear yes or no.
10.Troubleshooting & Exceptions
| Failure scenario | What to do | Escalate to |
|---|---|---|
| {{Common thing that goes wrong}} | {{Corrective action}} | {{Role / contact}} |
| {{Edge case}} | {{How to handle it}} | {{Role / contact}} |
Capture the failures you have actually seen. Naming the escalation point keeps exceptions from stalling.
11.Related Documents & References
- {{Form, checklist, or policy this SOP relies on}}
- {{Upstream or downstream SOP}}
Link the forms, policies, and adjacent SOPs a reader will need next.
12.Revision History
| Version | Date | Author | Summary of change |
|---|---|---|---|
| 1.0 | {{Effective Date}} | {{Document Owner}} | Initial release |
| {{Version}} | {{Date}} | {{Author}} | {{What changed}} |
Update this table every time the SOP changes. The v1.0 row is pre-filled as an example.
13.Approval
Both sign-offs confirm the procedure is accurate and authorised for use.
A worked example for onboarding a new employee at a small SaaS company, from offer to day 90.
1.Title Block & Document Control
| SOP Title | New Hire Onboarding |
|---|---|
| SOP ID | HR-003 |
| Version | 1.0 |
| Effective Date | June 1, 2026 |
| Review Date | June 1, 2027 |
| Document Owner | People Operations Lead |
| Approver | Head of People |
2.Purpose
This SOP gives every new hire a consistent, welcoming start — accounts ready on day one, clear first-week goals, and structured check-ins — so they reach productivity faster and stay longer.
3.Scope
Covers onboarding of full-time employees from offer acceptance through day 90. It does not cover recruiting and offers (HR-001) or contractor setup, which follows the vendor procedure.
Onboarding Timeline
| Phase | Tasks | Owner | Done by |
|---|---|---|---|
| Pre-boarding | Send welcome email; order laptop; create accounts; collect I-9 docs | HR + IT | Before start date |
| Day 1 | Office/remote welcome; payroll & benefits enrollment; tool access; meet buddy | Manager + HR | Start date |
| Week 1 | Role training plan; team intros; ship one small first task | Manager | End of week 1 |
| Day 30 / 60 / 90 | Structured check-ins; confirm ramp goals; gather feedback | Manager | Day 30 / 60 / 90 |
4.Definitions & Abbreviations
| Term | Definition |
|---|---|
| Pre-boarding | Everything done between offer acceptance and the start date |
| Buddy | A peer assigned to help the new hire settle in |
| HRIS | Human Resources Information System |
5.Roles & Responsibilities
| Role | Responsibility |
|---|---|
| People Operations | Owns the checklist, paperwork, and HRIS setup |
| Hiring Manager | Runs the training plan and 30/60/90 check-ins |
| IT | Provisions equipment and account access |
| Buddy | Answers day-to-day questions in week one |
6.Prerequisites, Materials & Equipment
- Signed offer letter on file
- Equipment budget approved
- Access to the HRIS and IT provisioning queue
- Role-specific training plan drafted by the manager
7.Safety & Compliance
Complete Form I-9 employment verification within the legal window and store it securely. Capture required policy and handbook acknowledgements. Grant system access on the principle of least privilege and revoke it promptly if the hire does not start.
8.Procedure (Step-by-Step)
| Step | Action | Owner | Expected Result |
|---|---|---|---|
| 1 | Send the welcome email with start details | People Operations | Hire has logistics and a point of contact |
| 2 | Order equipment and request account access | IT | Laptop and logins ready before day 1 |
| 3 | Set up payroll, benefits, and the HRIS record | People Operations | New hire can be paid and enrolled |
| 4 | Run day-1 welcome and complete I-9 + policies | Manager + HR | Paperwork done; access confirmed |
| 5 | Assign a buddy and a first task | Manager | Hire ships something small in week 1 |
| 6 | Hold 30/60/90-day check-ins | Manager | Ramp goals reviewed; feedback captured |
9.Quality Checks & Acceptance Criteria
- Accounts and equipment are working on day 1
- I-9 and policy acknowledgements are complete and filed
- The new hire completes a first task within week 1
- All three 30/60/90 check-ins are held and documented
10.Troubleshooting & Exceptions
| Failure scenario | What to do | Escalate to |
|---|---|---|
| Equipment not ready by day 1 | Issue a loaner; expedite the order | IT Lead |
| Hire postpones or declines before start | Pause provisioning; revoke any access | People Operations |
| Ramp goals slipping at day 30 | Adjust the plan; add support; document | Hiring Manager |
11.Related Documents & References
- HR-001 Recruiting & Offers
- Employee handbook
- IT provisioning checklist
- 30/60/90 check-in template
12.Revision History
| Version | Date | Author | Summary of change |
|---|---|---|---|
| 1.0 | June 1, 2026 | People Operations Lead | Initial release |
13.Approval
How it works
- Preview the onboarding SOP, including the pre-boarding to 30/60/90 timeline.
- Download Word/PDF, or copy the text to paste into Google Docs.
- Assign an owner and deadline to each task, then tailor the training plan to the role.
Frequently asked questions
What should an employee onboarding SOP include?
An onboarding SOP should sequence the work across phases — pre-boarding, day 1, week 1, and 30/60/90-day check-ins — with an owner and deadline for each task, plus compliance steps like I-9 verification and policy acknowledgements. This template includes that timeline and the standard SOP sections.
What is pre-boarding?
Pre-boarding is everything done between offer acceptance and the start date: ordering equipment, creating accounts, sending a welcome email, and collecting required documents. Doing it before day 1 is what lets a new hire be productive on their first day instead of waiting on logins.
What is a 30/60/90-day check-in?
It is a structured manager conversation at day 30, 60, and 90 to review ramp goals, give feedback, and surface blockers early. Scheduling all three in the SOP keeps onboarding from ending after week one, which is when many new hires disengage.
Does this onboarding template handle compliance?
It includes the common compliance steps — Form I-9 employment verification within the legal window, policy and handbook acknowledgements, and least-privilege access — in the Safety & Compliance and procedure sections. Adapt the specifics to your jurisdiction and HR system.