What to provide
Process goal, trigger, roles, current steps, tools, approvals, exceptions, and evidence.
What you will get
An editable SOP with roles, steps, controls, exceptions, and a review checklist.
Copy the full prompt
Customize the bracketed fields.
Use approved business information and have a person review the result before acting.
Help me draft a standard operating procedure for [process name].
Goal: [desired outcome]
Trigger and frequency: [when it starts and how often]
Roles: [people involved]
Current steps: [what happens today]
Tools and records: [systems, forms, or files]
Approvals: [required human decisions]
Known exceptions or failures: [examples]
Ask questions for missing facts before drafting. Produce an editable SOP with purpose, scope, definitions, prerequisites, roles and responsibilities, numbered steps, approval points, required evidence, exception handling, escalation, and completion criteria. Separate confirmed process facts from recommendations. Include a version history table and a short test in which a person unfamiliar with the process follows it using fictional data. Do not invent policies, legal requirements, system permissions, or approval authority.
Response requirements:
- Begin with a short summary of the goal, confirmed facts, assumptions, and missing information.
- Ask focused clarification questions before completing the work when a missing answer would materially change the result.
- Use clear headings, tables, checklists, or numbered steps where they make the output easier to use.
- Keep source facts separate from recommendations. Quote or cite supplied evidence when the task depends on source material.
- Mark unsupported details, decisions, owners, dates, costs, credentials, and commitments as [TO CONFIRM].
- Identify the three most important risks, failure conditions, or quality checks.
- End with a practical next-action checklist that names the responsible role and the evidence needed to confirm completion.
- Include a final self-review: check the answer against this prompt, list any unmet requirement, and correct it before responding.
- Do not claim that you accessed a system, verified an external fact, completed an action, or tested the result unless evidence in this conversation proves it.Version 1.0 · Updated 2026-10-10 · Free starter template. Evaluate the output in your approved environment.