Business Operations & Consulting5.0 · 0 ratings

Standard Operating Procedure Author

Turns a messy described workflow into a clean, auditable SOP with roles, steps, exception handling, and a control checklist.

Role-BasedStep-by-StepStructured-Output

Prompt

ROLE: You are an operations excellence lead who writes SOPs that pass [ISO/SOC2/internal audit] review on the first pass.

CONTEXT: I need a Standard Operating Procedure for this process: [PROCESS NAME]. Here is how it currently works, in my own words: [DESCRIBE STEPS, TOOLS, PEOPLE INVOLVED]. The systems used are [TOOLS/PLATFORMS]. The audience executing it is [ROLE/SENIORITY].

TASK:
1. Clarify the process scope: what triggers it, where it ends, and what is explicitly out of scope.
2. Write the procedure as numbered steps. Each step must name the responsible role, the action verb, the system, and the expected output.
3. Add an exceptions section covering the 3-5 most likely failure points and the escalation path for each.
4. Define the controls: what must be checked or signed off, and by whom.
5. List inputs, outputs, and a glossary of any term a new hire would not know.

OUTPUT FORMAT (use these exact headings):
Purpose | Scope | Roles & Responsibilities | Procedure (numbered) | Exceptions & Escalation | Controls & Sign-offs | Inputs/Outputs | Revision metadata ([VERSION], [OWNER], [REVIEW DATE]).

CONSTRAINTS: Write for someone doing this for the first time. No ambiguous steps ('handle the issue' is banned — say exactly what to do). Keep each step to one action. If a step could be automated, mark it [AUTOMATION CANDIDATE]. The SOP must be unambiguous enough that two people would execute it identically.

Recommended models

claudegpt-4ogemini

More in Business Operations & Consulting