AI Prompt to Turn a Process Description Into a Clear Standard Operating Procedure (SOP)
This prompt turns a rough, step-by-step description of how a task gets done into a polished Standard Operating Procedure (SOP) — the kind of document operations managers, team leads, and small business owners write once and reuse for months. It's built for anyone who knows a process well enough to do it themselves but struggles to turn that knowledge into something a new hire or teammate could follow without hand-holding.
Instead of just asking an AI model to "write an SOP," the prompt forces structure: numbered steps, clear ownership for each step, required tools or systems, and the edge cases that trip people up. It also asks the model to flag any gaps in the process description itself — missing decision points, unclear handoffs, or steps that assume knowledge the reader may not have — so the output is a usable procedure document rather than a vague summary of what was typed in.
Because the output needs consistent heading levels, numbered lists, and sometimes a table of roles and responsibilities, the raw draft an AI model produces often needs its formatting tightened up before it goes into a wiki or knowledge base. If that happens, running the draft through Prompt Formatter can convert the loose text into clean, consistently structured Markdown that's ready to paste into Notion, Confluence, or a Google Doc.
Prompt template
Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.
Example input
When to use it
- Onboarding a new hire or contractor and you need a written reference instead of repeating verbal instructions
- A process currently lives only in one person's head and needs to survive that person being on vacation or leaving
- You're preparing for an audit, certification, or compliance review that requires documented procedures
- A task has caused repeated errors or inconsistent results across team members and needs a single agreed-upon version
Best practices
- Describe the process in the order it actually happens, including the small steps you'd normally skip because they feel obvious
- Name the specific tools, software, or systems used at each step instead of describing them generically
- Include at least one exception or edge case (a rush order, a missing approval, a system outage) so the SOP doesn't only cover the happy path
- Specify who the SOP is for (a new hire, a cross-trained backup, an external contractor) so the model picks the right level of detail
Common mistakes
- Describing the process at too high a level, which produces an SOP full of vague steps like "review and approve" with no detail on how
- Leaving out who is responsible for each step, which makes the final document impossible to use for accountability or training
- Not mentioning existing templates or formatting standards, so the output doesn't match what the rest of the team's documentation looks like
- Treating the first draft as final instead of checking it against someone who actually performs the process day to day
FAQs
What is a Standard Operating Procedure (SOP) and why do I need one?
An SOP is a written, step-by-step document that describes exactly how a task or process should be performed, including who is responsible for each step. Teams use SOPs to keep output consistent when multiple people do the same task, to speed up onboarding, and to make sure critical knowledge doesn't disappear when one person is unavailable or leaves.
How detailed should an SOP be?
An SOP should be detailed enough that someone unfamiliar with the task could follow it without needing to ask clarifying questions, but not so granular that it becomes tedious to read. A good rule of thumb is to include every decision point and every tool used, while leaving out steps that are truly self-explanatory to the intended audience.
Can ChatGPT, Claude, or Gemini write an accurate SOP on its own?
These models are reliable at organizing and formatting a process you describe, but they cannot know your actual workflow unless you provide it. The output is only as accurate as the raw description you give it, which is why the prompt explicitly asks the model to flag gaps rather than guess at missing steps.
How often should an SOP be updated?
An SOP should be reviewed any time the underlying process, tools, or responsible roles change, and it's worth a periodic check (quarterly or twice a year for most teams) even without an obvious trigger, since small workflow changes tend to go undocumented otherwise.
Which Cuelara tool can help clean up the formatting of my generated SOP?
Prompt Formatter — converts a loosely structured SOP draft into clean, consistent Markdown headings and numbered lists that are ready to paste into a wiki or knowledge base.