A new hire asks how refunds work. Someone points them to a doc from last year that mentions a tool you stopped using. They ask a coworker instead, who explains it slightly differently than the last person did.

That's what a missing or stale SOP looks like. An SOP, a standard operating procedure, is just the written steps for a job your team does over and over. This guide shows how to use AI to write them faster and keep them current, in seven steps.

Why SOPs fail

Every business runs on procedures, written down or not: onboarding, invoice approval, publishing content. They break down for three reasons.

They take too long to write. So teams write a few and stop. Describing the process to a model and having it lay out the steps cuts that to something a busy person will actually do.

They go stale. Tools get swapped, steps change, and the document just sits there being wrong. People skip steps because the real instructions are buried in an old file, and new hires spend their first weeks guessing. A model can compare a procedure against what changed and flag it.

Nobody follows them. A forty-page PDF nobody can find or open on a phone gets skipped. A short, searchable, current procedure gets used.

Fix those three and the rest is mechanics.

Step 1: List your processes

Write down every job in the business that repeats: marketing campaigns, qualifying sales leads, sorting support tickets, managing vendors, approving expenses, onboarding customers.

For each one, ask:

Who owns it?
How long does it take right now?
How many people need to learn it?
How often does it go wrong?
What does a mistake here cost?

Fix the expensive ones first. A customer onboarding process that runs all the time and eats hours for every new hire comes before the yearly board-meeting agenda.

You'll end up with more processes than you can handle at once. Pick the few that cost the most time or cause the most mistakes, and start there.

Tip

Gather whatever notes already exist, even if they're scattered: Slack threads, email templates, Google Docs, wiki pages. Give them all to the model. Turning fragments into a clean draft is much faster than starting from a blank page.

Step 2: Pick one template

Every SOP should follow the same layout. Once people learn where things are in one, they can find them in all of them.

A standard layout:

Overview: what this process is and why it matters
Prerequisites: what needs to be true before starting
Numbered steps: clear actions in sequence
Decision points: "If X, then do Y"
Common mistakes: errors people actually make
Compliance notes: regulatory requirements, if any apply
Glossary: team-specific terms

Give this layout to the model with your notes, and every draft comes back in the same shape without you policing it.

Choose the template before you generate anything. If every SOP looks different, people have to relearn how to read each one.

Step 3: Write the first draft with AI

There are two ways to do it: record yourself doing the task, or describe it in writing.

Record the task

Scribe, Tango, and Glitter watch your screen while you do the task. They grab screenshots, read what's on screen, and turn it into a step-by-step guide.

Best for: click-by-click computer work, like software setup, data entry, and publishing content.

How: install the browser extension, do the task, let the tool make a draft, then edit and publish.

You'll need to fix clicks it labeled wrong and add context the screenshots miss. But you skip writing the steps from scratch.

Describe it in writing

Claude, ChatGPT, Waybook's SOP writer, and Process Street's AI Workflow Generator take a written description of a process and turn it into an SOP.

Best for: processes with lots of judgment calls, and anything that doesn't happen on a screen.

How: write an overview of the process, list the tools and the decision points, let the model write a full draft, then have the team review and fix it.

Expect more editing than with a recorded draft, since the model is working from your description instead of watching the work happen.

Your first one

Start with a process you know cold. Write a short overview of what happens and why, and note the tools, systems, and people involved.

Give that to Claude, or whichever tool you picked, with a prompt like this:

Create a comprehensive SOP for [process name]
following this structure:

Overview
Prerequisites
Steps (numbered)
Decision points
Common mistakes
Compliance notes (if applicable)

Use clear, direct language. Each step should be
actionable in under 60 seconds. Target audience:
team members with basic platform familiarity.

The model gives you a full first draft. Your team reviews it, you fix what's wrong, add what's specific to your company, and publish. Writing the draft is quick. The review is where the time goes.

Step 4: Choose where they live

Decide this before you write many of them. If people can't find a procedure, they won't use it.

Options:

Notion: free plan, connects to most tools, searchable, easy to edit together
Confluence: better for large company wikis with lots of cross-links
Waybook: built for SOPs, with AI drafting included
Process Street: turns procedures into checklists and assigns tasks
Internal wiki: GitHub, GitBook, or similar
A plain Google Drive folder: not ideal, but better than docs scattered everywhere

What matters most is that people can search for an SOP and link to it. An SOP nobody can find might as well not exist.

Organize by department. Marketing SOPs in one place, sales in another, and one index page linking to all of them.

Prices below are from each vendor's pricing page on September 27, 2026, in USD. Most charge per user, so multiply by your team size before comparing.

Tool	Best for	Where the AI comes in	Free plan	Paid from
Scribe	Screen-capture how-tos	Writes steps from a recorded session	Yes	$25 per seat a month, billed yearly
Tango	Visual step documentation	Captures screenshots and drafts steps	Yes, 5 shared workflows	$22 per user a month billed annually, $15 at 3+ users
Waybook	A dedicated SOP library	AI SOP writer	No, 7-day trial	$99 a month billed annually, for 20 seats
Process Street	Enforcing a checklist	AI Workflow Generator	No, 14-day trial	Contact sales
Notion	Flexible documentation	Paste in drafts from any AI assistant	Yes	$10 per member a month, billed yearly
Confluence	Enterprise wikis	Paste in drafts from any AI assistant	Yes, up to 10 users	$6.70 per user a month at 10 users, billed monthly

Notion, Scribe, and Tango all have free plans, so any of them is a cheap place to start. Move to a specialized tool later if you outgrow it.

Step 5: Test it on someone new

You don't know if an SOP works until someone who didn't write it tries to follow it.

Pick someone with the least inside knowledge, like a new hire or someone from another team. Hand them the SOP and ask them to do the task using only the document. Don't help. Watch where they get stuck.

Note:

How long does it actually take?
Where do they get stuck?
What did we assume that isn't obvious to someone else?
What steps are missing?
What terminology confused them?

Fix what you saw, not what you expected. Most SOPs need more than one round.

Write for someone who knows nothing about your business. "Open Salesforce" is clear. "Pull the contact list" isn't. Which list, in which system, with which fields?

Step 6: Roll them out

An SOP nobody's told about sits in a folder nobody opens.

Announce them. Tell the team these are now the way the work gets done.
Walk through them. Go through the first one together instead of assuming people will read it on their own.
Watch whether people follow them. You can't tell if it's working otherwise.
Ask for feedback. After the first week, ask what was confusing or missing.
Update often at first. Revise a lot in the first month, then settle into a slower schedule.

For onboarding, pair each new SOP with a walk-through from a team lead. People can't use a procedure they don't know exists.

Step 7: Keep them current

This is where most SOP efforts stall. The docs get written and rolled out, then the business changes and the docs don't.

Set a review date. Look at each SOP on a schedule. Quarterly is reasonable. Tools change, processes improve, rules shift.

Give each one an owner. One person keeps it current. Not the original writer, but whoever does the work now.

Notice when people skip steps. When someone skips a step or something goes wrong, check the SOP first. Usually either the steps are unclear or the process itself needs to change.

Date your changes. "Updated March 2026, added new approval workflow" tells people more than "Current" does.

Confluence and Notion both keep page history. Use it, and still write the change note, because history shows what changed but not why.

What you get back

The payoff from current SOPs comes in a few concrete ways.

Faster onboarding. A new hire with clear steps gets to working on their own sooner than one guessing from a stale doc or asking around.

Fewer mistakes. A current procedure catches the mistakes a stale one lets through. That means less redoing work and fewer problems sent up the chain.

Fewer interruptions. Every question an SOP answers is one your most experienced people don't have to answer in person.

Room to grow. Written-down processes let you add people without adding the same amount of supervision. Undocumented ones depend on someone heroic remembering everything.

Easier audits. Current, followed procedures are what an auditor wants to see.

None of this shows up right away. It shows up as fewer "how do I..." questions and new hires who stop needing someone to shadow.

Common mistakes

Covering every case at once. The first version doesn't need every exception. Write the normal path and add exceptions when they actually come up.

Writing like a contract. SOPs are for people. Use plain words, short sentences, and say who does what. A procedure that reads like a legal document won't get followed.

Leaving out the why. People follow a step better when they know the reason. "Use this format" lands worse than "use this format so the system can read it."

Writing it alone. Include the people who actually do the work. How you think a process runs and how it actually runs are usually different.

Treating them as finished. A procedure starts going stale the day you publish it. Plan regular updates and give people an easy way to flag what's wrong.

Skipping the test. An SOP nobody outside the team has followed is still a draft.

Start with one process

Pick the process from your list that costs the most time or causes the most mistakes. Write down what happens, let the model draft it in your template, have someone who didn't write it follow it, fix it once, and publish it where people already look.

Then do the next one. Give each SOP an owner and a review date the day it goes live. Procedures that stay current are worth more than a perfect first batch.

How to Create AI-Powered SOPs for Your Entire Business