Workbranch › Guides
GuideHow to write an SOP with AI
Most processes live in one person's head or in a messy doc nobody trusts. ChatGPT, Claude or Gemini can turn your notes or a recording of someone doing the job into a clear standard operating procedure. Here's the prompt, how to check the draft, and how to keep it current.
Quick answer: capture the process first, as rough notes or a transcript of someone walking through it, then give it to ChatGPT, Claude or Gemini with the prompt below. Ask for numbered steps with an owner, inputs and a "done when" check for each, and have the AI flag anything it had to guess. Then test the draft with someone who doesn't know the task, save the final version where your team works, and set a review date.
Product details below were checked against OpenAI's, Anthropic's and Google's help pages on 13 November 2026. The prompt works in any of the three.
Step 1: Capture how the work is really done
The AI can only describe the process you give it. Pick one of these starting points:
- Rough notes. List the steps in order, the tools involved, who does what, and the mistakes that usually happen. Bullet fragments are fine.
- A recording. Ask the person who does the job to talk through it while they work. ChatGPT can transcribe uploaded audio such as MP3, M4A or WAV files on paid plans (not on Free); as of November 2026 a recording can run up to 6 minutes in a regular chat. Gemini accepts audio up to 10 minutes in total, or up to 3 hours with Google AI Pro or Ultra; upload it with Add files > Upload Files.
- A transcript. Claude's file uploads cover documents and images, so for Claude, upload the transcript as a TXT, DOCX or PDF file with + > Add files or photos.
- Existing documents. Old instructions, email threads or a checklist someone keeps for themselves. Attach them too.
OpenAI notes that telling speakers apart may not be reliable, so check who does what, plus names, numbers and system names, against the recording.
Step 2: Run the SOP prompt
Paste your notes or attach the files in a new chat, then send:
"Write a standard operating procedure for [process name] at [team or company], based only on the material above. Don't invent tools, people or approvals. Before drafting, ask me up to 6 questions about anything unclear and wait for my answers. Then use these sections: purpose, scope (when this applies and when it doesn't), roles, what you need before starting, numbered steps, exceptions and what to do when something goes wrong, and a revision history table. For each step give one action starting with a verb, who does it, the input or system, and a 'done when' check. Mark any assumption with [CHECK]. Write for someone doing this for the first time, in plain language, under 1,000 words."
Why it's built this way:
- Questions first surface the decisions nobody wrote down, such as who signs off or what happens on a weekend.
- One action per step keeps steps checkable. If a step needs "and then", it should be two steps.
- "Done when" checks tell the reader how to know a step worked before moving on.
- [CHECK] tags turn hidden guesses into a short list for the process owner.
Prefer a document view? In Gemini on the web, click Add Files and then Canvas before sending the prompt. You can edit the text directly, and Share & export > Export to Docs turns it into a Google Doc.
Step 3: Review the draft with this checklist
OpenAI's prompting advice treats a first answer as something to refine, so fix problems with targeted follow-ups rather than starting over.
- Every [CHECK] is resolved by the person who does the job.
- Nothing is invented. Ask: "For each step, quote the line in my notes or transcript it came from." Steps without a source need checking.
- The scope is clear: when to use this SOP and when another one applies.
- Each step has one owner. "The team" isn't an owner.
- Exceptions are covered: missing information, a system that's down, an unhappy customer, a deadline that slips.
- Safety, legal and data rules your company requires are included word for word from the official policy, not paraphrased by the AI.
- A newcomer can follow it. Give it to someone who has never done the task and note every place they stop or ask a question.
Step 4: Keep it updated
An SOP goes stale the first time a tool or a person changes. A simple routine:
- Give it a home. In ChatGPT, select New project in the sidebar, upload the final SOP to the project, and use the ••• menu > Project settings to add your SOP format as instructions. In Claude, open Projects, click + New Project, use Set project instructions, and add the SOP with the + button.
- Set an owner and a review date at the top of the SOP, and record every change in the revision history table.
- Update from new material. When the process changes, attach the current SOP and the new notes and ask: "Compare these. List every step that's now wrong or missing, then rewrite only the affected steps and add a revision history entry."
- Collect problems as they happen. Ask people using the SOP to note where they got stuck, and feed those notes into the next review.
Step 5: Turn the steps into tasks
An SOP is most useful when someone runs it as a checklist. Ask: "Turn the numbered steps into a checklist I can copy into a task tool: one line per step with the owner, and mark which steps must happen before others." For one-off rollouts, such as training a new hire on the SOP, ask for tasks with dates instead. For the general approach, see how to turn AI answers into tasks, and for processes that start in a meeting, turning meeting notes into action items.
Good to know
- Upload limits. ChatGPT allows 5 files per project on Free, 25 on Go and Plus, and 40 on Pro, Business, Enterprise and Edu (as of November 2026). Claude takes up to 20 files per chat, and its Free plan allows up to five projects.
- Privacy. SOPs often describe internal systems. OpenAI doesn't use content from business offerings such as ChatGPT Enterprise to train its models; for personal accounts it depends on your data settings. Follow your company's rules on which account to use.
- The AI isn't the authority. The person who owns the process approves the SOP, not the chat.
If it doesn't work
- The SOP is generic. The source material was too thin. Add a recording or more detailed notes, and repeat "based only on the material above".
- The audio won't transcribe in ChatGPT. Check it's a supported audio format, not a video file, and keep it under 6 minutes. OpenAI suggests converting it to WAV and uploading again.
- Steps are merged or out of order. Ask it to split any step with more than one action and to list the order it assumed so you can correct it.
- It's too long to use. Ask for a one-page quick-reference version of the steps alongside the full SOP.
Running the SOP as a checklist
Workbranch, a separate AI workspace whose answers come from Google Gemini, shows an answer as a point-by-point checklist with progress, so a drafted SOP can be worked through step by step. Flags, due dates and reminders help you remember the next review date, and a side thread on any point lets you rework one step without losing the rest. There's a 3-day free trial.
Sources
- Uploading files and audio to ChatGPT (OpenAI Help Center, checked 13 November 2026)
- Prompt engineering best practices for ChatGPT (OpenAI Help Center, checked 13 November 2026)
- Projects in ChatGPT (OpenAI Help Center, checked 13 November 2026)
- Upload files to Claude (Claude Help Center, checked 13 November 2026)
- How can I create and manage projects? (Claude Help Center, checked 13 November 2026)
- Upload & analyze files in Gemini Apps (Gemini Apps Help, checked 13 November 2026)
- Create docs, apps & more with Canvas (Gemini Apps Help, checked 13 November 2026)
Frequently asked questions
How detailed should an SOP be?
Detailed enough that a new person who has never done the task can finish it without asking anyone. If a step needs judgment, the SOP should say what to look at and when to escalate, rather than pretending every case is the same.
Can the AI write an SOP for a process it hasn't seen?
It can write a generic one, but it will invent steps, tools and approvals that don't match how your team works. Always give it your own notes or a recording, and tell it to mark anything it had to assume.
Should I use a recording or written notes?
A recording of someone doing the task usually catches small steps people forget to write down. Notes are fine if they list every step in order. Either way, have the person who does the job read the draft.