AI Prompt for Writing SOPs

Turn any process into a clear SOP with this AI prompt. Steps, roles, and checkpoints in a format teams actually follow. Free to copy and use today.

The prompt

ROLE: You are an operations consultant who writes SOPs that frontline teams actually follow.

CONTEXT: Process name: [PROCESS_NAME]. What it accomplishes: [PURPOSE]. Who performs it: [ROLES]. How often: [FREQUENCY]. Current way it is done (describe messily, that is fine): [CURRENT_DESCRIPTION]. Tools involved: [TOOLS].

TASK: Write a complete Standard Operating Procedure.

FORMAT: 1. Header (process name, owner role, version date, review frequency). 2. Purpose (2 sentences). 3. Scope (what is included and excluded). 4. Roles and Responsibilities (table: role, responsibility). 5. Procedure: numbered steps, each with action, expected result, and time estimate. Mark decision points with IF/THEN. 6. Quality Checkpoints (where errors are caught). 7. Exceptions (what to do when the normal process breaks). 8. Revision History table. End with a 5-question quiz to test whether someone understood the SOP.

CONSTRAINTS: Write for a new hire on day one: no assumed knowledge, define every acronym. Each step must be observable and verifiable. Keep steps to one action each; compound steps get skipped.

Variables to fill in

Replace each [variable] in the prompt with your own details:

[PROCESS_NAME] [PURPOSE] [ROLES] [FREQUENCY] [CURRENT_DESCRIPTION] [TOOLS]

Example input

PROCESS_NAME=monthly client reporting, PURPOSE=deliver accurate performance reports by the 5th, ROLES=account manager, data analyst; FREQUENCY=monthly, CURRENT_DESCRIPTION=analyst pulls data whenever, AM formats in slides, sometimes late; TOOLS=GA4, Sheets, Slides

How to use this prompt

Describe the messy current reality honestly, generate the SOP, then have the person who does the work red-pen it before publishing.

Tips for the best results

The best SOP test: hand it to someone new and watch silently; every question they ask is a gap to fix.
Review SOPs when the process breaks, not on a calendar; pain is the best review trigger.
Keep SOPs under 2 pages; longer ones get skimmed and the skipped steps cause the errors.