01
Anyone can follow it
Verb-first numbered steps make the process repeatable without training.
Turn “how we do it” into a clear SOP
Describe a process roughly and get a full standard operating procedure — purpose, roles, numbered steps, quality checks and pitfalls — clear enough for a new hire to follow.
Overview
What this prompt does
Undocumented processes live in one person’s head and break when they’re away. This prompt turns rough steps into a proper SOP you can hand to anyone.
It structures the messy knowledge into steps, checks and pitfalls, and flags where information is missing.
Best for
Growing teams documenting how things get done so quality stays consistent as they scale.
The prompt
Fill in the blanks, then copy
Describe the process and who does it, then copy the completed prompt into your AI tool.
Click the highlighted blanks and type to complete the prompt, then copy it.
You are an operations manager. Write a standard operating procedure (SOP) someone could follow with no training. CONTEXT - Process name: PROCESS NAME - Rough steps / description: ROUGH STEPS - Who performs it: WHO DOES IT - Tools used: TOOLS USED - The successful outcome: DESIRED OUTCOME DELIVER a document with: Purpose, Scope, Roles, Prerequisites, numbered Steps (each starting with a verb, with settings or values called out), Quality checks / definition of done, and Common pitfalls. Write plainly enough for a new hire to follow, and flag any step where information is missing.
Tip: talk through the process out loud, paste the transcript as the "rough steps", and let it structure the rest.
How to use it
From blanks to output in three steps
Describe the process
Add the process name, rough steps, who does it, tools and the outcome.
Generate the SOP
Run the prompt for a structured, followable document.
Review and store
Fill any flagged gaps and save it to your wiki or handbook.
Why it works
What makes this prompt effective
02
Built-in quality checks
A definition of done keeps output consistent across people.
03
Gaps made visible
It flags missing information instead of glossing over it.
Watch out
Common mistakes to avoid
✕
Vague steps
"Handle the invoice" isn't a step. Each one should be a clear action.
✕
No definition of done
Without a quality check, everyone finishes differently. Keep it in.
✕
Writing once, never updating
An SOP is living. Revisit it when the process changes.
Done-for-you
Want your processes to run themselves?
Makura's Business Process Automation (AI) turns repetitive admin — notes, SOPs, reporting — into workflows your team actually uses.
Keep going
Related prompts
FAQ
Questions about this prompt
A rough walkthrough is enough — it structures and expands it. The more real detail you give, the more accurate the SOP.
In a searchable wiki or handbook (Notion, Confluence, Google Docs) so the team can find and follow them.
Yes — anywhere it needs a value or decision you haven’t provided, it marks it clearly rather than guessing.
Yes — once a process is documented, our Business Process Automation (AI) service can help automate the repetitive parts.
