The 7-section framework that turns implicit knowledge into AI-executable procedures.
“Write every SOP as if you’re giving instructions to someone who has never worked at your company. They’re smart, motivated, and have access to all your tools - but they know NOTHING about your specific processes.”
“If I disappeared tomorrow, could someone pick up this document and execute this process without asking a single question?”
Every SOP follows this structure. The sections build on each other: metadata orients the reader, purpose justifies the work, prerequisites remove blockers, steps deliver the outcome, decision trees handle complexity, outputs confirm completion, and exceptions cover edge cases.
The metadata block is the first thing a human or AI reads. It answers: what is this, who owns it, and when does it run?
One paragraph that justifies this SOP’s existence. If you cannot articulate the purpose clearly, the procedure may not need to exist - or it needs to be broken into smaller ones.
Everything the executor needs before they begin. Missing a prerequisite mid-procedure wastes time and introduces errors. List everything upfront.
This is where the work lives. Every step is a discrete, verifiable action. The quality of this section determines whether the SOP is useful or decorative.
IF / THEN / ELSE logic. Never “use your judgment.”“Update the CRM.”
“Open HubSpot → Navigate to Contacts → Search for [lead name] → Click Edit → Change Status to ‘Qualified’ → Add note: [qualification summary] → Click Save → Expected: green banner ‘Contact updated.’”
Most SOPs break down at decision points. The steps section handles the happy path; decision trees handle everything else. Extract all if-then logic and make it explicit.
Example decision tree
IF lead.company_size >= 100 employees THEN assign to Enterprise Sales AND schedule demo within 48 hours ELSE IF lead.company_size >= 10 employees THEN assign to Mid-Market Sales AND send product overview email ELSE IF lead.company_size < 10 employees THEN assign to Self-Serve queue AND send onboarding guide link ELSE THEN assign to General Sales ESCALATE TO Sales Manager for triage
Every procedure produces something and triggers something else. Without a defined output, you cannot verify the procedure was completed. Without a handoff, the next step in the chain never starts.
The final section is a safety net. It covers the situations where this SOP should not be followed, and the chain of command when things go wrong.
Not every SOP needs to be a 10-page manual. Match your investment to the frequency and value of the procedure.
| Level 1 -- Minimum | Level 2 -- Standard | Level 3 -- Agent-Ready |
|---|---|---|
| Title + Purpose + Steps | All 7 sections + basic decision trees | Exhaustive decision trees + tool refs |
| AI can monitor and remind | AI can suggest automations | AI can execute autonomously |
| Good for: low-frequency tasks | Good for: weekly procedures | Good for: daily, high-value tasks |
| Time: 15-30 minutes to write | Time: 1-2 hours to write | Time: 2-4 hours to write |
Six rules that separate a useful SOP from a wall of text nobody reads.
These five patterns are responsible for most SOP failures. Each one shows what people write versus what they should write.
“Handle the customer complaint”
“Open Zendesk → Find ticket → Read complaint → Check if refund eligible per refund policy SOP → If eligible: issue refund via Stripe → Reply with refund confirmation template → Close ticket”
“Process the invoice normally”
“Open QuickBooks → Navigate to Expenses → Click New → Select vendor from dropdown → Enter invoice number from email subject → Attach PDF → Set category to "Operating Expenses" → Click Save & Close”
“Respond appropriately”
“IF billing complaint → apologize + offer $25 credit. IF product issue → escalate to Engineering with screenshot. IF shipping delay → check tracking number in ShipStation + offer replacement if 7+ days overdue.”
“Submit the form (no guidance for failures)”
“Click Submit. Expected: green "Success" banner. If red error banner appears → screenshot the error → check all required fields are filled → retry once → if still failing, escalate to IT Support with screenshot.”
“Log into the old admin panel and update the record”
“Open the current admin dashboard at admin.company.com → Search for the record by ID → Click Edit → Update the relevant fields → Click Save. (Last verified: Feb 2026)”
Copy this template and fill in the brackets. Every SOP you write should follow this structure. The template includes all 7 sections with placeholder text you can replace.
# [SOP Title] ## 1. Metadata - **Owner:** [Name / Role] - **Frequency:** [Daily / Weekly / Per-event / On-demand] - **Trigger:** [What causes this SOP to start] - **Estimated Time:** [Minutes] - **Last Updated:** [Date] - **Automation Level:** [Level 1 / Level 2 / Level 3] ## 2. Purpose **Why this exists:** [One sentence explaining the outcome this SOP produces] **What happens if not done:** [Consequence of skipping this procedure] **Success criteria:** [How you know this was done correctly] ## 3. Prerequisites **Tools needed:** - [ ] [Tool name] - [URL or location] - [ ] [Tool name] - [URL or location] **Permissions required:** - [ ] [Permission / access level] **Information needed before starting:** - [ ] [Data point or input required] **Dependent SOPs (must be completed first):** - [ ] [SOP name] - [link] ## 4. Steps ### Step 1: [Action verb] [what] **Action:** [Specific instruction - click path, exact fields, copy/paste values] **Expected result:** [What you should see after completing this step] **If something goes wrong:** [Troubleshooting for this specific step] ### Step 2: [Action verb] [what] **Action:** [Specific instruction] **Expected result:** [What you should see] **Decision point:** - IF [condition A] → [do this] - IF [condition B] → [do that] - IF unsure → [default action / escalation] ### Step 3: [Action verb] [what] **Action:** [Specific instruction] **Expected result:** [What you should see] *[Continue numbering steps sequentially...]* ## 5. Decision Trees ### Decision: [What decision needs to be made] ``` IF [condition] THEN [action] AND [follow-up action] ELSE IF [other condition] THEN [different action] ELSE THEN [default action] ESCALATE TO [person/role] ``` ### Edge Cases - **[Edge case 1]:** [How to handle] - **[Edge case 2]:** [How to handle] ## 6. Outputs & Handoffs **Artifacts produced:** - [ ] [Document / record / update created] - [ ] [Notification sent to whom] **Handoff to:** - [ ] [Person/role] receives [what] - [ ] [Next SOP triggered]: [SOP name] **Verification checklist:** - [ ] [Check 1 - confirm output exists] - [ ] [Check 2 - confirm quality] ## 7. Exceptions & Escalation **Known exceptions:** - [Exception 1]: [How to handle] - [Exception 2]: [How to handle] **When to deviate from this SOP:** - [Condition that makes this SOP not applicable] **Escalation chain:** 1. [First person to contact] 2. [Second person if first unavailable] 3. [Emergency contact] **SLA:** [Expected completion time / response time]
Browse our templates for a head start, or see real examples from teams that have already documented their processes.
View Templates