How to Write an SOP: Step-by-Step Guide

A standard operating procedure (SOP) documents a repeatable process so anyone on your team can follow it without asking for help. Most teams skip SOPs because writing them feels like administrative busywork. This step-by-step guide shows you how to write an SOP that is concise, usable, and easy to maintain. Whether you are documenting a technical workflow or a simple daily task, the goal is the same: consistency and clarity.

What Is a Standard Operating Procedure?

A standard operating procedure (SOP) is a document that provides clear, step-by-step instructions on how to complete a specific task. Unlike a policy (which outlines what must be done and why), an SOP explains how to do it.

Effective SOPs reduce errors, streamline onboarding, and ensure that critical tasks don't rely on tribal knowledge. If a key employee leaves, the SOP ensures the process stays.

SOP vs. Policy vs. Process

Document Type	Purpose	Example
Policy	Rules and guidelines (The "What" & "Why")	"All customer data must be encrypted."
Process	High-level workflow (The big picture)	"Customer data lifecycle management."
SOP	Specific instructions (The "How")	"How to enable AES-256 encryption in the database."

How Do You Write an SOP from Scratch?

Writing an SOP doesn't require a technical writing degree. It requires a logical approach to breaking down tasks. Follow these six steps to create a functional SOP writing guide for your team.

1. Define the Scope and Audience

Before writing a single step, determine exactly what the procedure covers and who it is for.

• Scope: Where does the process start and stop? (e.g., "From receiving a refund request to processing the payment in Stripe.")
• Audience: Is this for a new hire, a subject matter expert, or a client? An SOP for a developer will look very different from one for a customer support agent.

2. Choose Your Format

Select a format that fits the complexity of the task.

• Simple Steps: Best for short, linear tasks (under 10 steps).
• Hierarchical Steps: Best for complex processes with sub-steps and detailed explanations.
• Flowchart: Best for processes with many decision points ("If X happens, do Y").

3. Capture the Process

You cannot write an SOP from memory. You must perform the task or watch someone else do it.

• Walk through it: Do the task yourself and note every click, decision, and input.
• Record it: Use a screen recording tool to capture the workflow. This ensures you don't miss "invisible" steps like logging in or navigating to a specific URL.

4. Write the Steps (Action-First)

Write clearly and directly. Start every step with an action verb.

• Bad: "The user should then click on the blue button labeled 'Save'."
• Good: "Click Save."

Keep sentences short. If a step requires explanation, add a "Note" or "Warning" box rather than burying the instruction in a paragraph of text.

5. Add Visuals

A wall of text is hard to follow. Visuals act as anchors for the reader.

• Screenshots: Essential for software workflows. Highlight exactly where to click.
• Diagrams: Useful for showing how data moves between systems.
• Videos: Good for overview, but hard to skim. Use them as supplements, not replacements for text.

6. Test and Review

Hand the draft to someone who has never done the task. Ask them to follow it without asking you questions. If they get stuck, your SOP has a gap. Fix the gap, then publish.

What SOP Format Should You Use?

The format dictates how readable your document is. Don't force a complex decision tree into a numbered list.

Step-by-Step Format

Use this for routine, linear tasks.

1. Log in to the portal.
2. Click Settings.
3. Select Users.
4. Click Add New.

Hierarchical Format

Use this when steps require context or sub-instructions.

1. Prepare the Data

• 1a. Export the CSV from Salesforce.
• 1b. Delete columns A, C, and F.
• 1c. Save as "Monthly_Report_Date.csv".

2. Upload to Dashboard

• 2a. Navigate to the Import tab.
• 2b. Drag and drop your clean CSV file.

Flowchart Format

Use this for logic-heavy processes.

• Start: Receive Ticket.
• Decision: Is it a bug?
  • Yes: Assign to Engineering.
  • No: Reply with Knowledge Base article.

What Makes a Good SOP Template?

A standardized template ensures consistency across your organization. Every SOP should include these core elements:

1. Title: Specific and action-oriented (e.g., "How to Process a Refund," not "Refunds").
2. Identification: unique ID number and version number (e.g., OPS-001 v2.0).
3. Effective Date: When the SOP was last updated or approved.
4. Purpose/Goal: One sentence explaining why this task exists.
5. Prerequisites: What tools, permissions, or inputs are needed before starting.
6. The Procedure: The actual steps (numbered list).
7. Troubleshooting: "What to do if X fails."
8. Owner: The job title responsible for maintaining the document.

Where Traditional SOP Writing Falls Short

The biggest challenge in how to write an SOP isn't the writing—it's the maintenance. Processes change faster than documentation.

The Manual Screenshot Trap

Most teams write SOPs using Google Docs or Word. They take a screenshot, paste it, crop it, draw a red box around a button, and type "Click here."

• It's slow: Creating a 10-step guide takes 30–60 minutes.
• It breaks easily: If the software interface updates (e.g., a button changes color or moves), the screenshots are instantly obsolete.
• It lacks context: Screenshots often lack the metadata (URLs, field names) that help users understand where they are.

The Automated Alternative

Modern documentation tools solve this by capturing the underlying code (DOM) of the application while you work.

Tools like Glyde record your screen as you perform the task. Instead of a flat video, they generate a step-by-step guide with:

• Perfectly cropped screenshots for every click.
• Auto-generated text descriptions ("Click 'Submit Request' in the top right").
• Contextual data about the elements you interacted with.

This shifts the workflow from "writing from scratch" to "recording and refining." You perform the task once, and the SOP is 90% done instantly. Other tools in this space include Scribe and Tango, which offer similar capture capabilities for browser-based workflows.

Best Practices for SOP Maintenance

An outdated SOP is worse than no SOP because it destroys trust. If a team member follows instructions that don't work, they won't use the documentation next time.

• Assign Ownership: Every SOP must have a specific role (not a person) assigned as the owner.
• Scheduled Reviews: Set a recurring reminder (quarterly or bi-annually) to verify the process is still accurate.
• Easy Feedback Loop: Viewers should be able to flag steps that are broken or confusing directly in the document.
• Version Control: Keep a history of changes so you can revert if a new process fails.

Learn More About Standard Operating Procedures

For a complete framework on building and managing your operations documentation, see our guide on the complete guide to standard operating procedures, including templates and examples for different departments.