SOP Writer: Turn Messy Process into Clear Documentation with Failure Modes

Full prompt

You are an operations documentation expert. Convert the following process description into a clear, actionable SOP.

Process Name: {{processName}}
Current Description: {{processDescription}}
Team Size: {{teamSize}}
Frequency: {{frequency}}
Critical Dependencies: {{dependencies}}

Structure the output as:

1. **Process Overview**
   - Owner and stakeholders
   - Purpose and business impact
   - Frequency and SLA

2. **Prerequisites**
   - Required access, tools, and data
   - Preparation steps

3. **Step-by-Step Instructions**
   - Number each step
   - Include decision points (if X, then do Y)
   - Note time estimates per step
   - Specify who performs each step

4. **Failure Modes & Recovery**
   - List 3–5 common failure points
   - For each: what goes wrong, how to detect it, recovery steps
   - Include prevention measures

5. **Success Criteria**
   - How to verify the process completed correctly
   - Key metrics or outputs to check

6. **Escalation & Support**
   - Who to contact if stuck
   - When to escalate

7. **Related Processes**
   - Upstream and downstream dependencies

Be specific. Avoid vague language like "ensure quality" or "communicate as needed." If a step requires judgment, explain the decision framework. If tools or systems are mentioned, note the exact field names or menu paths.

How to use

1. Identify a process that's currently undocumented or poorly documented. 2. Gather the current description—ask the person who owns it to explain it, or compile notes from Slack, emails, or wikis. 3. Fill in each placeholder with specific details. 4. Run the prompt through your AI tool. 5. Review the output for accuracy and completeness. 6. Refine failure modes with the team—they'll catch edge cases you missed. 7. Version the SOP and share it with the team. 8. Update it quarterly or after process changes.

Customization tips

• Tailor failure modes to your actual pain points. Ask the team: 'What breaks most often?' and document those specifically.
• If the process involves multiple decision trees, consider adding a flowchart diagram or decision table alongside the text.
• Include time estimates for each step so new hires know if they're on track.
• For processes with high turnover, add a 'Common Mistakes' section based on what new people get wrong.
• Link to related SOPs or systems documentation at the end so the SOP doesn't exist in isolation.
• Version your SOP (v1.0, v1.1) and date it. Update after process changes and note what changed.