A note to our readers. Synthese AI is pausing operations as we step back to reassess our direction. Rather than continue down a path we're not fully confident in, we want to rethink what this platform should be — not just another news feed, but something meaningfully useful. Thank you for reading and engaging with us. If and when we return, it will be with a clearer vision.

← Back to Prompts
Productivity & Workflows

Workflow SOP Builder

Transform repeated tasks into clean step-by-step SOPs that teams can actually follow.

Use case

Creating standard operating procedures from informal process descriptions

Works best with

ClaudeChatGPT

Input needed

Informal description of the process (verbal dump is fine), the audience who will follow it, tools used, and any compliance requirements

Output format

Step-by-step SOP with numbered procedures, decision points, responsible parties, tool references, and exception handling

Example use

Describe how your team handles customer refund requests in a rambling paragraph. Get back a structured SOP with clear steps, decision trees for different refund amounts, tool references, and escalation paths.

Editor’s Note

Excellent for turning tribal knowledge into documented processes. The AI is good at identifying implicit decision points you didn't explicitly mention. Review carefully for accuracy — it may infer steps that don't match your actual workflow. Best validated with the team members who actually do the work.

Full Prompt

You are an operations manager. Turn the recurring task below into a practical SOP that a new team member could execute without confusion.

Task / Workflow:
[DESCRIBE THE TASK]

Context:
[TEAM, TOOLS, CONSTRAINTS, EDGE CASES]

Output:
1. SOP Title and Purpose
2. When To Use This SOP
3. Required Inputs / Access
4. Step-by-Step Procedure
- Numbered steps
- Include decision points as "If X, then Y"

5. Quality Check
- How to verify the work was done correctly

6. Common Failure Modes
- Mistakes people usually make
- How to avoid them

7. Escalation Rules
- When to stop and ask for help

Rules:
- Optimize for clarity and repeatability
- Avoid vague verbs like "handle" or "process"
- Make each step observable and actionable

Tags

operationsSOPprocess designdocumentation

More Productivity & Workflows Prompts