How to Create SOPs With AI

Quick Answer

Brain-dump your process in rough notes, then use AI to structure it into a numbered, clear SOP with consistent formatting. AI handles structure and language. You supply the actual process knowledge. Review the draft by pretending you’re a new team member who has never done this before.

What This Workflow Helps You Do

• Document processes before you forget how you actually do them
• Create consistent, professional SOPs without writing from scratch
• Build an operations library your team can actually use

Step-by-Step Process

Step 1: Brain-dump the process first

Before opening AI, write rough notes on the process:

• What triggers this process to start?
• What are the main steps, in rough order?
• What tools or platforms are involved?
• Who does each step (if multiple people)?
• What does the finished output look like?
• What are common mistakes or edge cases?

Even 10 bullet points is enough for AI to build from.

Step 2: Generate the SOP structure

Create a standard operating procedure (SOP) from the following rough notes.

Process name: [title the process]
Who this is for: [the role or person who will follow this SOP]
When this process runs: [what triggers it, how often]
Rough steps: [paste your notes]

Format it as a complete SOP with:
- Purpose (1–2 sentences on why this process exists)
- Scope (who this applies to, what it covers and doesn't)
- Prerequisites / tools needed (before starting)
- Step-by-step instructions (numbered, with sub-steps where needed)
- Expected output / definition of done (what success looks like)
- Common mistakes and how to avoid them
- Version / last updated date placeholder

Write it clearly enough for someone unfamiliar with this process to follow without asking questions.

Step 3: Add edge cases and exceptions

Review this SOP I've drafted: [paste SOP]

Add a "Common Scenarios and How to Handle Them" section that covers:
[List 3–5 real edge cases or exceptions that come up in this process]

Format each scenario as:
- Situation: [describe the edge case]
- How to handle it: [the correct response or decision]

Step 4: Create a quick-reference checklist

From this SOP, create a condensed one-page checklist version that covers just the key steps.

The checklist is for experienced team members who know the process and just need a reminder of the sequence and key checkpoints.

Format as: [ ] Checkbox — Step name (brief description if needed)

Group into phases if the process has distinct phases.

Step 5: Write the SOP in plain language

After the draft is generated, review it with this checklist:

Review this SOP for clarity: [paste your SOP]

1. Identify any steps that are vague or could be misunderstood
2. Find any assumed knowledge a new person might not have
3. Flag any steps where you'd need to see a screenshot or example to understand
4. Suggest where numbered sub-steps would make a complex step clearer
5. Note any jargon that should be defined or replaced with plain language

Common Mistakes

Brain-dumping and expecting AI to know your process. AI can only document what you tell it. Vague notes produce vague SOPs. The more specific your input, the more useful the output.

Not testing the SOP on an actual new person. The best test of a SOP is giving it to someone unfamiliar with the process and watching where they get stuck. Use those moments to improve the doc.

Writing SOPs that immediately go out of date. Include a last-updated date and assign someone to review SOPs when the underlying tools or process changes. An outdated SOP is worse than no SOP. It creates confusion.