If you’ve ever tried to build an operations documentation system, you’ve probably encountered the terminology problem: Is this a policy? An SOP? A work instruction? A procedure? A runbook?
The terms get used interchangeably, which creates confusion and poorly structured documentation. In our experience helping businesses build their ops documentation, the teams with the clearest systems use a consistent hierarchy — and understanding that hierarchy makes the whole project easier.
The Documentation Hierarchy
Think of operational documentation in three levels, from high-level to granular:
- Level 1: Policy — What we do and why (the rule)
- Level 2: SOP (Standard Operating Procedure) — How we do it, at a process level (the process)
- Level 3: Work Instruction — The step-by-step mechanics of a specific task within the process (the task guide)
Each level answers a different question. Confusing them leads to documents that try to do everything and end up doing nothing well.
What Is a Policy?
A policy is a high-level statement of what the organization does — or doesn’t do — in a given area, and why. Policies set standards and intent. They rarely contain step-by-step instructions.
Examples:
- Returns Policy: “We accept returns within 30 days of purchase for items in original condition.”
- Expense Policy: “Employees may expense business meals up to $75/person with manager approval.”
- Data Security Policy: “All customer data must be stored in approved systems and never shared via personal email.”
When to write a policy: When you need to establish a standard or rule that governs behavior across the organization. Policies are enforced; SOPs and work instructions describe how to execute within the policy.
What Is a Standard Operating Procedure (SOP)?
An SOP describes how a process is executed from start to finish. It’s more detailed than a policy but not as granular as a work instruction. A good SOP documents the flow of a process — who does what, in what order, with what inputs and outputs — but doesn’t necessarily describe every click or keystroke.
Examples:
- Returns Processing SOP: Steps from return request received → label generated → item received at warehouse → inspected → restocked or dispositioned → refund issued
- New Supplier Onboarding SOP: Steps from supplier identified → qualification checklist completed → contract signed → first PO issued → receiving and quality check
- Customer Escalation SOP: Steps from ticket flagged as escalation → assigned to CS lead → customer contact attempt → resolution documented → follow-up confirmation
When to write an SOP: For any repeatable, multi-step process that involves more than one person, more than one tool, or has significant consequences if done incorrectly. SOPs are the core of most operations documentation systems.
For a deep dive into writing SOPs, see our guide: How to Write SOPs for Small Business.
What Is a Work Instruction?
A work instruction is the most granular level of documentation — it describes how to perform a specific task within a process. If the SOP is the process map, the work instruction is the turn-by-turn navigation. Work instructions are particularly useful for tasks that are technically complex, performed infrequently, or done by people with varying skill levels.
Examples:
- Work Instruction for creating a purchase order in your inventory system: Log in → navigate to Purchasing → click “New PO” → select supplier from dropdown → enter line items with SKU, quantity, and price → set expected delivery date → submit for approval
- Work Instruction for processing a return in Shopify: Navigate to Orders → search order number → click Return Items → select items and quantities → generate return shipping label → send to customer
When to write a work instruction: For complex or technical tasks, tasks with zero-tolerance for error, or tasks that need to be performed consistently by people who aren’t system experts. Work instructions often include screenshots.
How They Work Together: A Practical Example
Take returns as an example. Here’s how the three levels work together:
- Policy: “We accept returns within 30 days for items in original, unused condition. Return shipping is the customer’s responsibility.”
- SOP: Returns Processing SOP — covers the end-to-end process from customer return request to inventory update and refund issuance. Identifies roles (CS team, warehouse team, finance).
- Work Instructions: “How to process a return in Loop Returns” (step-by-step for CS team), “How to inspect and grade a returned item” (step-by-step for warehouse team), “How to issue a refund in Shopify” (step-by-step for CS or finance).
The policy sets the rule. The SOP defines the process. The work instructions handle the execution details.
Other Document Types You May Encounter
- Runbook — an IT/engineering term for a work instruction or set of procedures used during incidents or recurring operations tasks
- Playbook — often used in sales and marketing contexts; describes strategies and tactics for a specific scenario (e.g., “competitor takeout playbook”)
- Process Map / Flow Chart — a visual representation of an SOP; useful for communication but not a substitute for the written steps
- Checklist — a subset of a work instruction; the actionable list without the explanatory context
Frequently Asked Questions
What is the difference between an SOP and a work instruction?
An SOP describes a complete process at a high level — who does what, in what order. A work instruction is more granular — exactly how to perform a specific task within that process, often step by step with screenshots. SOP = process map; work instruction = turn-by-turn directions for one task.
What is the difference between a policy and an SOP?
A policy states what the organization does or doesn’t do — it sets standards and intent. An SOP describes how to execute a process to meet that standard. Returns policy = the rules; returns SOP = the step-by-step process for handling a return.
Do small businesses need all three types of documentation?
Not all at once. Start with SOPs for critical processes. Policies matter for HR and compliance-sensitive areas. Work instructions become valuable as you scale and need consistent task execution across varying skill levels.
Can an SOP include work instructions?
Yes — for simpler processes, embedding work instruction detail within the SOP works fine. For complex processes with multiple roles or systems, keeping them separate makes documentation easier to maintain and use.
Get Your Documentation System Right From the Start
OpsStack helps businesses build documentation systems with the right structure — policies, SOPs, and work instructions that work together without becoming a maintenance burden. Talk to us about your documentation needs.
