Operations

SOP Writer

Turn the way you work into clear procedures anyone on your team can follow.

by Maya Chen

Works with

Google DocsRequired
Notion

Overview

You explain how you do something - in a voice note, rough bullets, a screen-recording transcript, or a quick back-and-forth - and it turns that into a proper standard operating procedure: numbered steps, who does what, which tools are involved, what done looks like, and what to do when things go wrong. It asks the questions you would forget to answer, flags the gaps where a new hire would get stuck, and formats everything so it drops straight into your handbook, wiki, or training doc. You stay the expert; it does the writing.

Try asking

I'm the only one who knows how anything works here - help me get my client-onboarding process out of my head
Turn this voice memo where I explain my weekly bookkeeping routine into a step-by-step SOP
I'm hiring a VA next month - write the procedures they'll need for inbox triage and scheduling
Rewrite this messy Google Doc into a clean SOP with steps, owners, and what done looks like
Every time someone covers for me they do it differently - make a checklist so refunds get handled the same way every time
I want to take a real vacation without the business breaking - document the five tasks only I know how to do

Examples

This creator hasn't published sample artifacts yet.

Limits & risks

It writes procedures but never runs them - it won't send, spend, publish, or change anything in your tools on your behalf unless you explicitly attach a connector and instruct it to
It documents your process as you describe it; it can flag risky steps, but it is not a substitute for compliance, legal, HR, or safety advice from a licensed professional
It won't invent steps you didn't describe - where it has to guess, it marks the gap and asks you instead
It can't watch you work; it only knows what you tell it, paste in, or transcribe for it
It won't produce official regulatory or certification paperwork (ISO, OSHA, HACCP filings) - it drafts working procedures, not audited compliance records

Getting started

Requirements

Bring one process you want out of your head, explained however is easiest for you - a voice note, rough bullet points, a screen-recording transcript, or just answering its questions in chat. If a half-written doc already exists, paste that in too. It also helps to say who the procedure is for (a new hire, a VA, future you) and where it will live (Google Doc, Notion page, printed checklist).

Steps

1Tell it which task you want documented and who will be following the procedure
2Explain the task once, messily - voice note, bullets, transcript, or a quick Q&A; it asks follow-ups where a stranger would get stuck
3Get back a structured SOP: trigger, tools and access needed, numbered steps, decision points, what done looks like, and what to do when things go wrong
4Review the marked gaps and open questions, answer them, and get the corrected version
5Drop the finished SOP into your handbook, wiki, or training doc - and come back when the process changes

What's inside

Model: anthropic/claude-sonnet-4-6

SOP Writeranthropic/claude-sonnet-5
You explain how you do something - in a voice note, rough bullets, a screen-recording transcript, or a quick back-and-forth - and it turns that into a proper standard operating procedure: numbered steps, who does what, which tools are involved, what done looks like, and what to do when things go wrong. It asks the questions you would forget to answer, flags the gaps where a new hire would get stuck, and formats everything so it drops straight into your handbook, wiki, or training doc. You stay the expert; it does the writing.

SOP Writer AI agent on Augex