ChatGPT Prompts for SOPs: Write Standard Operating Procedures Fast
ChatGPT prompts for writing SOPs and process documentation. Step-by-step procedures, decision trees, and training-ready process guides for any business function.
The Prompt
Act as an operations manager who specializes in process documentation for scaling businesses.
Write a Standard Operating Procedure (SOP) for:
Process name: {what this SOP covers}
Department/team: {who owns and uses this process}
Trigger: {what starts this process — a specific event or condition}
End state: {what does 'done' look like for this process}
Key stakeholders: {who is involved — roles, not names}
Tools/systems used: {software, platforms, or physical resources}
Describe the current process (rough): {walk through how it works now — imperfect is fine}
Frequency: {daily / weekly / monthly / triggered by event}
SOP document structure:
1. Document header:
| Version | Date | Author | Approved by | Next review date |
2. Purpose (1-2 sentences: why this process exists and what problem it solves)
3. Scope (who this SOP applies to and any exceptions)
4. Prerequisites (what must be in place before starting — access, materials, prior steps)
5. Step-by-step procedure (numbered, each step actionable):
- Step N: [Action verb] + [specific action] + [where/what system] + [expected output]
- Decision points: clearly marked as [IF X → GO TO STEP Y] or [IF X → GO TO STEP Z]
6. Quality checks (what to verify at key checkpoints)
7. Troubleshooting (3-5 common failure points and how to recover)
8. Related SOPs / links
Constraints:
- Each step must be one action — not a paragraph of instructions
- Decision branches must use explicit conditional language (IF/THEN/ELSE)
- Avoid role-specific instructions that only work for one person — write for a trained newcomer
- Include screenshots or diagram placeholders [INSERT SCREENSHOT: X] where visual aids are needed
Variables to fill in
-
{process name}What this SOP covers -
{trigger and end state}What starts and what completes this process -
{tools/systems}Software, platforms, or resources used in the process -
{current process description}How it works now — rough notes are fine
How to use this prompt
- Walk through the process yourself while writing the rough notes for this prompt
- Have someone follow the SOP as written on their first try — gaps reveal themselves immediately
- Add [INSERT SCREENSHOT] placeholders and fill them after writing — don't let screenshots block you
- Review and update every SOP quarterly — processes change faster than documentation
SOPs are for newcomers, not veterans
The person who wrote the SOP already knows the process — they don’t need it. The people who need the SOP are the ones doing it for the first time, or returning to it after months away. Writing for a ‘trained newcomer’ forces you to include every piece of context that seems obvious to the expert — which is exactly the information that prevents costly mistakes.
Decision branches are where SOPs fail
Most processes work fine in the happy path. They break down at decision points: what do you do if the client doesn’t respond? What if the system throws an error at step 7? SOPs that only document the happy path create bottlenecks every time an exception occurs — which is when your team needs the SOP most. The explicit IF/THEN/ELSE branching in this prompt forces documentation of the most common exceptions.
Version control is an SOP quality indicator
An SOP without a version number and review date is likely out of date. The document header in this prompt includes version, date, author, and next review date — which creates a forcing function for keeping SOPs current. An SOP reviewed quarterly and marked with version numbers builds institutional trust in the documents; one that hasn’t been updated in 2 years gets ignored.
Related free tools
- Free AI Prompt Generator — build structured prompts instantly
- AI Token Counter — estimate API costs
- AI ROI Calculator — calculate the business value of AI adoption