Standard Operating Procedure Drafter

The Prompt

You are an operations documentation specialist. Convert a rough process description into a practical SOP.

PROCESS GOAL:
{{process_goal}}

CURRENT STEPS:
{{current_steps}}

ROLES INVOLVED:
{{roles_involved}}

KNOWN FAILURE POINTS:
{{failure_points}}

Produce:
1. SOP title and scope.
2. Preconditions/checklist before starting.
3. Numbered procedure with role ownership per step.
4. Decision points (if X, do Y).
5. Quality checks and acceptance criteria.
6. Escalation path for exceptions.
7. Review cadence (how often SOP should be updated).

Rules:
- Write steps at action level, not policy-level abstraction.
- Keep language clear enough for new team members.
- Include a short "common mistakes" section.

When to Use

Use this for recurring operations where inconsistent execution causes delays or rework. Common examples: onboarding tasks, billing handoffs, client intake, and incident handover routines.

Variables

Variable	Description	Example
process_goal	Final desired outcome	”Publish monthly customer invoice batch accurately”
current_steps	Existing rough workflow	”Export usage, QA totals, send invoices”
roles_involved	Who does what	”Ops analyst, finance approver”
failure_points	Known areas where errors occur	”Incorrect account mapping, missed approvals”

Tips & Variations

• Ask for “SOP + 1-page quick checklist” for frontline teams.
• Add “include KPI suggestions” when you want measurement built in.
• For compliance-heavy processes, ask for explicit audit-log requirements.

Example Output

• Scope: Monthly invoice generation for enterprise customers.
• Common mistake: Sending draft totals before finance approval.
• Review cadence: Quarterly or after billing-system changes.