How to Write SOPs for AI Automation
The 7-section framework that turns implicit knowledge into AI-executable procedures.
The instruction mindset
“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 NOTHINGabout your specific processes.”
The test
“If I disappeared tomorrow, could someone pick up this document and execute this process without asking a single question?”
The 7 required sections
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.
Title & Metadata
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?
- SOP Name- Descriptive and action-oriented. “Process Inbound Sales Lead” not “Sales Stuff”.
- Owner- A role, not a person name. “Head of Sales” not “Mike.” Roles persist when people change.
- Frequency - How often this runs: daily, weekly, per-event, or on-demand.
- Trigger- What causes this SOP to start. “New lead submitted via website form” or “Client sends cancellation email.”
- Estimated time - How long this takes to complete (helps AI schedule capacity).
- Last updated - Date of last review. Stale SOPs are dangerous SOPs.
- Automation level - Level 1 (human-executed, AI monitors), Level 2 (AI-assisted, human approves), or Level 3 (fully autonomous, human audits).
Purpose
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.
- Why this exists - One sentence. “Ensures every inbound lead receives a response within 2 hours.”
- What outcome it produces - The tangible deliverable. “Lead is qualified and either scheduled for a demo or archived with reason.”
- What happens if not done - Stakes. “Leads go cold, pipeline stalls, revenue lost.”
- Success criteria - How you know it was done correctly. Measurable, not subjective. “Lead has a status of Qualified or Archived in the CRM within 2 hours of submission.”
Prerequisites
Everything the executor needs before they begin. Missing a prerequisite mid-procedure wastes time and introduces errors. List everything upfront.
- Tools needed- With exact URLs or file locations. “HubSpot CRM (app.hubspot.com)” not “the CRM.”
- Permissions required - “Admin access to HubSpot” or “Write access to the shared Google Drive folder.”
- Information needed before starting - Data inputs this procedure consumes. “Lead’s email address, company name, and source channel.”
- Dependent SOPs - Other SOPs that must be completed first. Link them directly so the chain of dependencies is navigable.
Steps (the core)
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.
Rules for writing steps
- Every step starts with an action verb: Open, Click, Navigate, Enter, Select, Verify, Send.
- Each step has three parts: Action + Expected Result + What Could Go Wrong.
- Decision points use explicit
IF / THEN / ELSElogic. Never “use your judgment.” - Use substeps for complex actions (4a, 4b, 4c) rather than cramming everything into one step.
- Include exact click paths: “Click Settings → Team → Invite Member→ Enter email → Set role to Admin → Click Send.”
“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.’”
Decision Trees
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.
- All if-then logic extracted - Pulled out of prose and formatted as structured decision blocks.
- Edge cases documented - The 10% of situations that cause 90% of confusion. “What if the client has two accounts?” “What if the payment is in a foreign currency?”
- Escalation paths defined - When to stop executing and hand off to a human (or a more senior agent).
- “When in doubt” defaults - Every decision tree must have a fallback. If no condition matches, what happens? Never leave a dead end.
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
Outputs & Handoffs
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.
- Artifacts produced - Documents created, records updated, notifications sent. Be specific: “CRM contact record updated with status and qualification notes.”
- Who receives them - And how. “Account Manager receives Slack notification in #new-leads channel.”
- Next SOP triggered - Name it and link it. This creates navigable procedure chains.
- Verification checks - How you confirm the output is correct. “Open the CRM record and verify status is Qualified and notes field is populated.”
Exceptions & Escalation
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.
- Known exceptions - Specific situations and exactly how to handle each one. “If the lead is an existing customer, skip qualification and route directly to their Account Manager.”
- When to deviate from this SOP - Conditions that make this procedure inapplicable. “Do not use this SOP for enterprise RFP responses; use the Enterprise Sales SOP instead.”
- Escalation chain (by role) - Ordered list. “1. Sales Manager → 2. VP Sales → 3. CEO.” Always by role, never by personal name.
- SLAs- Time-sensitive procedures need explicit deadlines. “Escalation must be acknowledged within 1 hour during business hours.”
Levels of detail
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 |
Level 1 -- Minimum
- -Title + Purpose + Steps
- -AI can monitor and remind
- -Good for: low-frequency tasks
- -Time: 15-30 minutes to write
Level 2 -- Standard
- -All 7 sections + basic decision trees
- -AI can suggest automations
- -Good for: weekly procedures
- -Time: 1-2 hours to write
Level 3 -- Agent-Ready
- -Exhaustive decision trees + tool refs
- -AI can execute autonomously
- -Good for: daily, high-value tasks
- -Time: 2-4 hours to write
Writing tips
Six rules that separate a useful SOP from a wall of text nobody reads.
Use active voice
Name specific tools
Include exact click paths
Add timing
Define success
Name roles, not people
Common mistakes
These five patterns are responsible for most SOP failures. Each one shows what people write versus what they should write.
Too high-level
“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”
Assumed knowledge
“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”
Missing decision logic
“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.”
No error handling
“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.”
Outdated references
“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)”
The complete template
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]
Ready to write your first SOP?
Browse our templates for a head start, or see real examples from teams that have already documented their processes.
View Templates