SOP Builder Template

Turn messy process notes into a clear SOP that someone else can follow consistently without guessing.

Use this template to document a repeatable business process — onboarding, fulfillment, QA, handoff, or any repeatable workflow. Paste rough notes and get a complete SOP with roles, step table, quality checks, exception handling, and a training checklist.

Best for

What you'll need to provide

• [Insert Process Name]
• [Insert Department or Team]
• [Insert Process Goal]
• [Insert Trigger: When Does This Process Start?]
• [Insert Required Tools]
• [Insert People or Roles Involved]
• [Insert Current Steps or Notes — paste rough notes here]
• [Insert Common Mistakes]

Paste-ready framework

You are an elite operations architect and SOP writer. Your job is to turn rough process notes into a clear, repeatable standard operating procedure that a trained team member can follow without guessing.

Context:
Process name: [Insert Process Name]
Department or team: [Insert Department or Team]
Process goal: [Insert Process Goal]
Trigger: [Insert Trigger — what event starts this process?]
Required tools: [Insert Required Tools]
People or roles involved: [Insert People or Roles Involved]
Current steps or notes: [Insert Current Steps or Notes]
Common mistakes: [Insert Common Mistakes]

Task:
Create a complete SOP for this process. The SOP should be clear enough for onboarding, delegation, quality control, and repeatable execution.

Constraints:
- Do not write vague steps such as "handle the request" or "complete the task."
- Break complex work into specific, observable actions.
- Include decision points and exception handling for edge cases.
- Include quality checks at critical steps before completion.
- Use plain language throughout.
- Do not assume tools or approvals that were not provided. Label missing information as "Needs confirmation."

Output format:
1. SOP title and purpose.
2. Scope: what is included and excluded.
3. Roles and responsibilities.
4. Required tools, access, and materials.
5. Trigger and expected completion time.
6. Step-by-step procedure table with columns: Step Number, Owner, Action, Tool Used, Quality Check, Expected Output.
7. Decision points and exception handling.
8. Common mistakes and how to prevent them.
9. Definition of done.
10. Training checklist for a new team member.

What you'll get

1. SOP title, purpose, and scope
2. Roles and responsibilities section
3. Required tools, access, and materials list
4. Trigger event and expected completion time
5. Step-by-step procedure table — owner, action, tool, quality check, output
6. Decision points and exception handling
7. Common mistakes and prevention
8. Definition of done
9. Training checklist for new team members

Quality constraints built in

• No vague steps like "handle the request" or "complete the task"
• No assumed tools or approvals not provided in input
• Missing information labeled "Needs confirmation" rather than guessed
• Decision points and exceptions made explicit

Paste messy process notes directly — the template structures them. Clean input is not required.