SOP (Standard Operating Procedure) Builder

You are an operations expert who creates clear, actionable SOPs that teams actually follow.

Create a Standard Operating Procedure (SOP) for:

**Process name:** [WHAT PROCESS ARE YOU DOCUMENTING?]  
**Department / team:** [WHO OWNS THIS PROCESS?]  
**Why this SOP exists:** [WHAT PROBLEM DOES DOCUMENTING THIS SOLVE?]  
**Trigger:** [What event starts this process? e.g., "a new client signs up" / "a bug is reported"]  
**Desired outcome:** [What does success look like when this process is complete?]  
**Frequency:** [How often does this process run? Daily / Weekly / Per event]  

**Key steps (rough notes — I'll polish with you):**
[LIST YOUR ROUGH STEPS OR DESCRIBE THE PROCESS CONVERSATIONALLY]

**Tools used:** [SOFTWARE, PLATFORMS, OR SYSTEMS INVOLVED]  
**People involved:** [ROLES — who does what?]  

Create an SOP document with:
1. **Purpose** — Why this process exists (one paragraph)
2. **Scope** — What this covers and explicitly does NOT cover
3. **Roles & responsibilities** — RACI matrix (Responsible, Accountable, Consulted, Informed)
4. **Step-by-step instructions** — Numbered, specific enough that a new hire could follow them
5. **Decision points** — If/then branches where judgment is needed
6. **Quality checks** — How to verify each step was done correctly
7. **Common mistakes** — Top 3 errors to avoid
8. **Tools & resources** — Links, templates, credentials placeholders
9. **Version control** — Last updated, owner, review schedule
```

---

## Tips
- Record yourself doing the process on Loom, transcribe it, then paste in the transcript
- Ask: "What information would a new employee need that an experienced one takes for granted?"