L0Lesson 2Free

Your first SOP in 10 minutes

Write a complete standard operating procedure from a plain-English description

After this, you'll be able to write a usable standard operating procedure for any process in your organization by describing it to Claude in plain English, without any formatting knowledge or operations background.

Before you start

Before diving in, complete What process debt is and what it costs you so you have a specific high-risk process in mind to document in this lesson.

The idea

You can write a complete standard operating procedure (SOP) in 10 minutes by telling Claude how a process works in plain English. You need no formatting knowledge, no templates, and no operations background; the description you would give a new colleague over coffee is enough. Claude turns that into a numbered, header-organized, decision-aware first draft in under 3 minutes.

A recurring operations task for Your first SOP in 10 minutes sits between loose notes, tool tabs, and an unclear owner.

Here is the before and after: A small business owner trying to document her client onboarding process spends an afternoon organizing her thoughts, formatting a Word doc, and ending up with something she is never fully satisfied with. With Claude, she describes the process in one unstructured paragraph, starting with "here is how we currently handle new clients," and gets back a structured SOP with section headers, numbered steps, a summary paragraph, and a note about the most common point of failure.

Now try it: Pick the process your business depends on most right now. Describe it to Claude in one paragraph starting with "Write an SOP for how we [process name]. Here is how it currently works: [describe it]."

Describe current reality, not the ideal, and you will have a usable first draft in under 3 minutes.

Your first SOP in 10 minutes mapThe process document works when the source, check, and owner stay connected.

Try it (10 min)

Watch out for

Describing the ideal process instead of how it actually works. Claude can only produce a usable SOP when you describe current reality, not the version you wish existed.
Leaving out what tools are used. Without tool names, Claude produces generic steps that do not match your team's actual workflow.
Accepting the first draft without reviewing it. Claude may produce plausible-sounding steps that do not match your specific constraints; read every step before sharing it.
Treating 'write an SOP' as the whole prompt. Adding output format instructions (like the numbered structure in the exercise) noticeably improves the first response.

Paste this into Claude

Write an SOP for how we handle [choose a real process from your work, e.g., "onboard a new client", "respond to a customer complaint", "process a vendor invoice", "conduct a weekly team standup"].

Here is how it currently works:
[Write 3-5 sentences describing the process in your own words. Include who does each step, what tools are used, and where things typically go wrong. Write it as if you were explaining it to a new hire.]

Please format the SOP as:
1. A one-paragraph summary of the process and its goal
2. Numbered steps, each with a title and 2-3 sentence description
3. A "common issues" section noting the 2-3 most frequent failure points
4. A "success criteria" section with 3 things that indicate the process was completed correctly

What good looks like

The SOP has a summary paragraph, numbered steps with titles, a common issues section, and a success criteria section
The steps are specific to your process, not generic placeholders
At least one step describes a decision point or exception path
You could hand this to a new team member and they could follow it

ProofMove through Your first SOP in 10 minutes, check proof, then fix only the weak part.

Go deeper (5 min)

Paste this into Claude

I just wrote an SOP using Claude and I want to make it shorter without losing anything important.

Here is the SOP I just created:
[paste your SOP from the first exercise]

Please:
1. Identify any steps that could be combined without losing clarity
2. Flag any language that is vague or could be misinterpreted
3. Rewrite it at half the length while keeping all the essential decision points

My goal is a version someone could follow from memory after reading it once.

What good looks like

The revised SOP is at least 30% shorter than the original
No critical decision points were removed
The success criteria and common issues sections are preserved
You prefer the shorter version to the longer one

When this breaks

Breaks when your description is just a sentence or two, because Claude fills the gaps with generic steps that fit any company. Name the tools, the people, and the failure points, and the SOP gets specific to you.
Produces over-engineered output when you ask for an SOP for a simple process without specifying length constraints. Ask Claude for the minimal version first: 'What are the 5 most important things someone needs to know to execute this process?'

AI can help with this

Use Claude, ChatGPT, Gemini, Microsoft Copilot, Codex, Notion AI, or another approved work AI based on the system your team actually uses. Paste the lesson prompt with one real process or workflow, require the assistant to separate facts from assumptions, then verify the owner, exception path, and human review point before you use the output.

The task becomes one named process with inputs, review, and a trusted handoff marked by the golden dot.

You can now

You can complete the lesson outcome against a real operations process, source, or recurring workflow.

You can verify that the SOP has a summary paragraph, numbered steps with titles, a common issues section, and a success criteria section.
You can verify that the steps are specific to your process, not generic placeholders.
You can verify that at least one step describes a decision point or exception path.
You could hand this to a new team member and they could follow it.

Key takeaways

A plain-English description of a process is everything Claude needs to produce a structured, usable SOP. You do not need formatting skills, templates, or operations experience.

Describing a process in plain English gives Claude enough to produce a formatted SOP in under 3 minutes.
Specificity in your description (who, what tools, where it breaks) determines quality more than any other factor.
Ask for the minimal version first. Longer SOPs have lower compliance rates.
The first draft is a starting point, not a final document. Review every step before sharing.
Adding an output format instruction to your prompt (numbered steps, summary, common issues) structures the response from the first reply.

Go deeper

Was this helpful?

Up nextThe SOP prompt structure: four inputs

← Back to AI for Operations

Write an SOP for how we handle [choose a real process from your work, e.g., "onboard a new client", "respond to a customer complaint", "process a vendor invoice", "conduct a weekly team standup"]. Here is how it currently works: [Write 3-5 sentences describing the process in your own words. Include who does each step, what tools are used, and where things typically go wrong. Write it as if you were explaining it to a new hire.] Please format the SOP as: 1. A one-paragraph summary of the process and its goal 2. Numbered steps, each with a title and 2-3 sentence description 3. A "common issues" section noting the 2-3 most frequent failure points 4. A "success criteria" section with 3 things that indicate the process was completed correctly

I just wrote an SOP using Claude and I want to make it shorter without losing anything important. Here is the SOP I just created: [paste your SOP from the first exercise] Please: 1. Identify any steps that could be combined without losing clarity 2. Flag any language that is vague or could be misinterpreted 3. Rewrite it at half the length while keeping all the essential decision points My goal is a version someone could follow from memory after reading it once.