SOP Document: Formats, How to Write, and Examples
What is an SOP document? 4 SOP formats, 7 steps to write one, 8 essential components, onboarding SOP playbook, and examples for growing businesses.
SOP Document
What it is, the 4 standard formats, how to write one, and why your first SOP should be your onboarding process
The third time a new hire asked me "how do I submit an expense report?" I realized the problem was not the new hire. It was that the answer existed only in my head. Every process at the company, from onboarding a client to requesting PTO to setting up a new laptop, lived in someone's memory. When that person was busy, on vacation, or left the company, the process left with them.
A standard operating procedure (SOP) document is how you get processes out of people's heads and into a format that anyone can follow. It is not bureaucracy. It is the difference between answering the same question for the 50th time and pointing to a document that answers it permanently.
This guide covers SOP documents from start to finish: what they are, how they differ from policies and work instructions, the four standard SOP formats, eight essential components, how to write one in seven steps, a complete onboarding SOP playbook, examples by industry, where to store and manage SOPs, and the mistakes that make SOPs useless. The what is an SOP guide covers the concept at a higher level. The knowledge management guide covers the broader system for organizing company knowledge. This article covers how to actually write, format, and implement SOPs at a growing business.
What Is an SOP Document?
A standard operating procedure (SOP) document is a written set of step-by-step instructions that describes how to complete a specific process or task. It ensures that the process is performed the same way every time, by every person, regardless of their experience level. An SOP answers the question: "If someone who has never done this before needed to do it right now, what would they need to know?"
SOPs exist on a spectrum of complexity. An expense report SOP might be 8 steps on one page. An employee onboarding SOP might be 30 steps across 4 phases spanning 30 days. Both are SOPs. The format and length match the complexity of the process, not a predetermined template.
SOP vs Policy vs Work Instruction
These three documents are frequently confused. Each serves a different purpose and operates at a different level of detail.
| Document | What It Answers | Level of Detail | Example |
|---|---|---|---|
| Policy | 'What is the rule?' | High-level: states the expectation without explaining how to meet it | 'All employees must complete harassment prevention training within 30 days of hire.' |
| SOP (Standard Operating Procedure) | 'How do we follow the rule?' | Process-level: step-by-step instructions for completing a process | 'Step 1: Assign harassment training module via HR platform. Step 2: Employee completes module. Step 3: Employee signs acknowledgment. Step 4: Manager verifies completion in dashboard.' |
| Work Instruction | 'How do I perform this specific task?' | Task-level: granular, detailed instructions for a single step within an SOP | 'To assign a training module: log in to [platform] > navigate to Training > click Assign > select employee > select module > set due date > click Send.' |
The practical relationship: policies set the standard, SOPs describe how to meet the standard, and work instructions provide step-by-step detail for individual tasks within the SOP. A growing business needs policies for HR and compliance, SOPs for recurring processes, and work instructions for complex tool-specific tasks. The OSHA workplace safety guidelines use exactly this hierarchy: safety policies set requirements, SOPs describe how to work safely, and work instructions cover specific equipment and procedures. The employee handbook guide covers the policy layer that sits above SOPs.
Why SOPs Matter More for Growing Businesses
SOPs prevent problems that get worse as the team grows. Here are the trigger points where the absence of SOPs starts costing real time and money.
| Trigger Point | What Happens Without SOPs | What SOPs Solve |
|---|---|---|
| 5th employee | The founder starts repeating explanations. The same onboarding walkthrough happens for the 5th time, slightly different each time. | Document the onboarding process once. Every hire after that follows the same steps. |
| 15th employee | The founder cannot personally train everyone. New hires learn from whoever is available, producing inconsistent knowledge. | SOPs ensure every new hire receives the same training content regardless of who is available. |
| 30th employee | Processes start breaking. Different people do the same task differently. Quality varies. Mistakes increase. | SOPs create a single source of truth for how each process works. Consistency improves. Errors decrease. |
| First employee departure | The person who knew how to do [critical process] is gone. Nobody else knows the steps. | SOPs capture institutional knowledge in documents that survive personnel changes. |
| First compliance audit | The auditor asks 'how do you ensure employees receive harassment training?' and you cannot produce documentation. | SOPs with e-signature acknowledgments create the audit trail that proves compliance. |
The Office of Personnel Management maintains SOPs for virtually every HR process in the federal workforce. The principle scales down to any size: documented processes produce more consistent, more efficient, and more auditable results than processes that exist only in people's memories.
4 Standard SOP Formats
Not every process needs the same format. Four standard SOP formats serve different types of processes. Choose the format that matches your process complexity.
| Format | Use When | Example Process | Complexity |
|---|---|---|---|
| Step-by-step | The process is linear and order matters | New employee onboarding, expense reimbursement, client setup | Low |
| Checklist | All items must be completed but order is flexible | Pre-launch quality check, compliance document collection, office opening/closing | Low |
| Hierarchical | Steps contain sub-steps or multiple actions | Multi-department approval workflow, complex client onboarding with branches | Medium |
| Flowchart | The process branches based on conditions or decisions | Customer complaint escalation, IT troubleshooting, exception approval | Medium-High |
For most growing businesses, 80% of SOPs will be step-by-step format. It is the simplest to write, the easiest to follow, and covers the majority of business processes. Start with step-by-step. Use other formats only when the process genuinely requires them. The compliance training guide covers which compliance processes need SOPs with documented acknowledgment.
8 Essential Components of an Effective SOP
| Component | What It Contains | Why It Matters |
|---|---|---|
| 1. Title and document ID | Descriptive name (e.g., 'Employee Onboarding SOP') and a unique identifier for version control | Employees can find the right SOP quickly. Version tracking prevents using outdated documents. |
| 2. Purpose | One to two sentences explaining why this SOP exists and what problem it solves | Gives context so the reader understands the importance of following the procedure, not just the steps. |
| 3. Scope | What the SOP covers, who it applies to, and when it is used | Prevents confusion about whether this SOP applies to a specific situation or role. |
| 4. Roles and responsibilities | Who performs each step, listed by role title (not person name) | SOPs survive personnel changes. New employees know which steps are theirs. |
| 5. Procedure | The step-by-step instructions: the core of the SOP | This is the SOP. Everything else is supporting context. |
| 6. Resources | Links to templates, tools, forms, related documents, and contacts | Eliminates searching. The reader has everything they need within the SOP. |
| 7. Revision history | Date of last review, who reviewed it, and what changed | Ensures the SOP is current. Outdated SOPs produce errors. |
| 8. Acknowledgment | E-signature confirming the employee has read and understood the SOP | Creates an audit trail for compliance-critical processes. Proves the employee received the procedure. |
How to Write an SOP in 7 Steps
This process works for any SOP at any company size. Total time for your first SOP: 2-4 hours. Subsequent SOPs take 1-2 hours because you understand the format.
The Bureau of Labor Statistics projects continued growth in training and development roles through 2034, reflecting increasing organizational investment in structured process documentation. SOPs are the foundation of that documentation: before you can train someone on a process, you need to document what the process is. The training program guide covers how SOPs connect to broader training program design.
SOP for Employee Onboarding: The Complete Playbook
If you are going to write one SOP, make it your employee onboarding process. Onboarding is the process you repeat most frequently (every hire), affects the most people (every employee goes through it), and has the highest cost of inconsistency (a poorly onboarded employee is unproductive for months). Here is the complete onboarding SOP broken into four phases.
This onboarding SOP integrates with your onboarding checklist and training program. Each step in the SOP becomes a task in the onboarding workflow, assigned automatically when a new employee profile is created. Compliance steps (handbook acknowledgment, harassment training) include e-signature for documentation. The onboarding documents guide covers what paperwork and documents new hires need alongside the SOP. The Department of Labor structures apprenticeship programs with documented onboarding SOPs, demonstrating that structured onboarding documentation improves outcomes at every level of formality.
SOP Examples for Growing Businesses
| Industry | SOP Example | Format | Key Steps |
|---|---|---|---|
| SaaS startup (15 employees) | Client onboarding SOP | Step-by-step | Account creation, data migration, kickoff call, training session, 30-day check-in, handoff to support |
| Marketing agency (10 employees) | New project intake SOP | Hierarchical | Client brief review, scope definition, team assignment, timeline creation, kickoff meeting, weekly status cadence |
| Dental practice (20 employees) | Patient intake SOP | Checklist | Insurance verification, medical history form, HIPAA acknowledgment, X-rays, exam room prep, provider introduction |
| Restaurant (25 employees) | Opening procedures SOP | Checklist | Equipment check, food safety temp logs, prep station setup, POS system boot, team briefing, door unlock |
| E-commerce (12 employees) | Returns and exchanges SOP | Flowchart | Return request received > check return window > approve/deny > issue refund or exchange > update inventory > follow up |
| Construction (30 employees) | Job site safety SOP | Step-by-step + checklist | PPE verification, hazard assessment, tool inspection, work zone setup, emergency procedures review, daily safety sign-off |
| Accounting firm (8 employees) | New client onboarding SOP | Step-by-step | Engagement letter, document request list, system access setup, initial data import, introductory meeting, first deliverable timeline |
Every example follows the same principle: document the process that new employees need to learn first and that experienced employees need to follow consistently. The format varies (step-by-step for linear processes, checklist for verification, flowchart for branching), but the goal is the same: anyone should be able to follow this SOP and produce the correct result. The course creation guide covers how to turn SOPs into training modules that new hires complete during onboarding.
Where to Store and Manage SOPs
| Tool | Best For | SOP Features | Cost |
|---|---|---|---|
| HR platform with document management | 5-50 employees: SOPs alongside onboarding, training, and compliance | Document storage, task workflow assignment, e-signature acknowledgment, employee profile integration | $98-$198/month flat |
| Google Drive / SharePoint | Any size: simple document storage with folder organization | Version history, sharing permissions, search. No assignment or acknowledgment tracking. | Free-$12/user/month |
| Notion / Confluence | Teams wanting a general wiki that includes SOPs | Collaborative editing, search, templates, nested pages. No e-signature or compliance tracking. | Free-$10/user/month |
| SOP-specific tools | Companies with heavy SOP needs across operations | Screen capture (Scribe), AI generation, template libraries, analytics. Usually no HR integration. | $100-$500+/month |
| Training/playbook platforms | Companies focused on training alongside SOPs | Course-style SOP delivery, completion tracking, quizzes. Often per-user pricing. | $200-$400+/month |
For most growing businesses, the choice depends on what system you already use. If your HR platform has document management, store SOPs there alongside employee records and onboarding workflows. If you use Google Drive, create a structured SOP folder with consistent naming. The tool matters less than two things: can employees find the SOP in 60 seconds, and can you track who has acknowledged it? The training matrix guide covers how to track SOP acknowledgment alongside training completion in one system. The HR document management guide covers how to organize all company documents including SOPs.
Common Mistakes When Writing SOPs
Six mistakes consistently make SOPs ineffective, especially at growing businesses writing SOPs for the first time. The cross-training guide covers how SOPs enable cross-functional capability by documenting processes that multiple employees can follow.
Frequently Asked Questions
What is an SOP document?
A standard operating procedure (SOP) document is a written set of step-by-step instructions that describes how to perform a specific process or task consistently and correctly. SOPs ensure that work is done the same way every time, regardless of who performs it. They cover everything from employee onboarding to expense reporting to client delivery. An effective SOP is specific enough to follow without prior knowledge of the process and short enough to reference quickly during execution.
What are the 4 types of SOP formats?
Four standard SOP formats: (1) Step-by-step (sequential): numbered instructions performed in order, best for linear processes. (2) Checklist: items to verify or complete in any order, best for quality checks and compliance audits. (3) Hierarchical (nested steps): step-by-step with sub-steps under each main step, best for complex multi-stage processes. (4) Flowchart (decision-based): visual diagram with yes/no decision points, best for troubleshooting and exception handling. Most growing businesses start with step-by-step because it is the simplest to write and follow.
What is the format of a standard operating procedure?
A standard SOP format includes 8 components: (1) Title and document ID. (2) Purpose statement: why this SOP exists. (3) Scope: what the SOP covers and who it applies to. (4) Roles and responsibilities: who does what. (5) Procedure: the step-by-step instructions. (6) Resources: tools, templates, and references needed. (7) Revision history: when the SOP was last updated and by whom. (8) Acknowledgment: e-signature confirming the employee has read and understood the procedure. The procedure section is the core. Everything else is supporting context.
How do you write an SOP?
Seven steps: (1) Identify the process to document (start with the most confusing or error-prone processes). (2) Define scope and purpose in one sentence. (3) Choose the format (step-by-step, checklist, hierarchical, or flowchart). (4) Write each step as a clear action with specific details. (5) Add supporting details: roles, resources, exceptions, time estimates. (6) Add an e-signature acknowledgment step for compliance-critical SOPs. (7) Have someone who does the process review it for accuracy, then publish and set a review schedule.
What is the difference between an SOP and a policy?
A policy states what the company expects (the rule). An SOP explains how to implement that expectation (the procedure). Example: the policy says 'all expenses must be approved before reimbursement.' The SOP says 'submit the expense form in [system], attach the receipt, select your manager as approver, and allow 5 business days for processing.' Policies set the standard. SOPs operationalize it. A work instruction goes one level deeper than an SOP, covering a single task in minute detail.
What are the 5 parts of an SOP?
The five essential parts: (1) Purpose: why this SOP exists and what problem it solves. (2) Scope: what the SOP covers, who it applies to, and when it is used. (3) Responsibilities: who performs each step (by role, not by person name). (4) Procedure: the step-by-step instructions for completing the process. (5) References: tools, templates, related documents, and escalation contacts. Many SOPs also include revision history and acknowledgment sections, bringing the total to 7-8 parts.
Who writes SOPs in a company?
The person who does the work writes the SOP, with review from a manager or process owner. This is the most effective approach because the person doing the work knows the actual steps, shortcuts, common errors, and edge cases. The manager reviews for accuracy and completeness. At growing businesses without dedicated operations staff, the founder often writes the first SOPs. As the team grows, the person who owns each process takes over writing and maintaining the SOP for that process.
How long should an SOP be?
Most SOPs should be 1-3 pages (10-30 steps). If an SOP exceeds 3 pages, the process is either too complex for a single SOP (split it into multiple SOPs) or the writing includes unnecessary context (move background information to a separate policy document). The test: can someone follow this SOP in real time while doing the work? If they have to flip between pages and re-read paragraphs, it is too long or too complex.
What is the difference between an SOP and a work instruction?
An SOP covers a complete process from start to finish (e.g., employee onboarding from offer letter to 30-day review). A work instruction covers one specific task within that process in detailed, granular steps (e.g., how to set up a new employee's email account in Google Workspace). SOPs reference work instructions when a step requires more detail than fits in the SOP. Think of the SOP as the map and work instructions as turn-by-turn directions for specific segments.
How often should SOPs be reviewed?
Quarterly for SOPs covering frequently changing processes (onboarding, tool-dependent workflows). Annually for SOPs covering stable processes (expense reimbursement, PTO requests). Immediately when tools, policies, roles, or regulations change. Every SOP should display a 'last reviewed' date. If the date is more than 12 months old, the SOP needs review regardless of how stable the process seems.
Do small businesses need SOPs?
Yes, starting from about 5 employees. Below 5, the founder can explain everything verbally. Above 5, verbal explanations become inconsistent, time-consuming, and error-prone. The trigger points: hiring the 5th employee (you start repeating yourself), the 15th (you cannot personally train everyone), and the 30th (processes break without documentation). Start with 3-5 SOPs covering the processes that cause the most confusion, then expand as the team grows.