AI Prompts for SOP and Operating Routine Drafting

A standard operating procedure exists so that the process is performed the same way by every person every time — and so that when it is not, someone can tell. Most SOPs fail on one of two counts: they describe the ideal rather than the actual process, or they are written at a level of detail nobody reads. The operating routines around them (daily meetings, handovers, escalation paths) matter as much as the documents.

These prompts draft an SOP from a real process description, design a daily operations meeting that fits on one board, and review an existing SOP for the gaps that cause variation. The model drafts structure and wording; it cannot know your process, so the input has to be how the work is actually done.

Before you use these

Have these ready to replace the highlighted [variables]:

• A description of the process as actually performed, step by step, including decisions and exceptions
• Roles involved and who is accountable for what
• Controls: checks, records, tolerances, escalation rules
• Existing documents to review, if any

The prompts

• 1. Draft an SOP from a process description
• 2. Design the daily operations meeting
• 3. Review an existing SOP for gaps and ambiguity

1. Draft an SOP from a process description

Act as an operations documentation specialist drafting an SOP for [process] at [site / team].

Process as performed: [step-by-step, including who does it, tools/systems used, decisions and exceptions, typical problems and workarounds]
Roles: [role, responsibilities]
Controls: [checks, tolerances, sign-offs, records kept, escalation rules]
Related documents: [work instructions, forms, policies]

Draft the SOP:
1. Header: title, ID placeholder, version, owner, approval, effective date, review date.
2. Purpose and scope: what the SOP covers and explicitly what it does not.
3. Definitions and abbreviations.
4. Roles and responsibilities as a RACI for the key steps.
5. Procedure: numbered steps in sequence; each with actor, action, system or tool, input, output, and the check or record if any. Decision points as explicit branches ('If X, go to step n'). Exceptions and escalation as their own section.
6. Records: what is recorded, where, by whom, retention.
7. KPIs or checks that show the SOP is being followed.
8. Training and competency requirement.
9. Change control: how the SOP is revised.

Write at the level of an experienced operator, not a novice. Then list every step where the description was ambiguous or where the workaround differs from the intended method, with a question to resolve each. Do not invent steps to fill gaps.

2. Design the daily operations meeting

You are designing a daily operations meeting (tiered huddle) for [team / site].

Attendees: [roles, number] Time available: [minutes] Frequency and time of day: [e.g. 08:15 daily]
Metrics that matter daily: [safety, quality, delivery/output, cost, people — the specific measures]
Typical issues raised: [examples]
Escalation: [what goes to the next tier meeting and when it happens]

1. Agenda with minute-by-minute timing: safety first, then yesterday's performance versus plan by metric, today's plan and risks, open actions, escalations. Total within the time available.
2. Board layout: metric tiles with target/actual/trend, an action list (issue, owner, due, status), an escalation column, and a recognition space. Specify what is updated before the meeting and by whom.
3. Rules: standing, no problem-solving in the meeting (log it), every red gets an owner and a date, actions older than [n] days escalate.
4. Facilitation guide: opening line, how to run through the board, how to handle a long discussion, how to close.
5. Link to the next tier: what is escalated, in what format, and what comes back down.
6. First-two-weeks plan to embed the routine and the signs it is working (meeting on time, action closure rate, fewer repeat issues).

Keep it to one page. Avoid metrics that cannot be updated daily.

3. Review an existing SOP for gaps and ambiguity

Act as a quality and operations reviewer auditing an SOP.

SOP text: [paste]
How the process actually runs: [known deviations, workarounds, steps skipped]
Incidents or errors linked to this process: [list]
Systems and equipment currently in use: [to check references]

Review and report findings in these categories, each with severity (high/medium/low) and the specific text:
1. Ambiguity: steps with unclear actor, sequence, tolerance or decision criteria ('as appropriate', 'periodically', 'ensure').
2. Gaps: activities that happen in practice but are not in the SOP; exceptions with no defined handling; missing escalation paths.
3. Controls: checks without a record, records without a reviewer, tolerances without a response when exceeded.
4. Currency: references to systems, forms, roles or equipment that no longer exist or have changed.
5. Practice divergence: where the documented method and the actual method differ — and whether the SOP or the practice should change.
6. Usability: length, structure, and whether an operator could follow it under time pressure.

Then: rewrite the three highest-severity steps in clear procedural language, and list the questions for the process owner that the review cannot answer. Do not rewrite the whole SOP — target the findings.

Related prompts

• Process Improvement
• Root Cause Analysis
• Operational KPI Reviews
• Warehouse Operations Improvement
• Production Planning and Scheduling
• Supply Chain Disruption Response
• Meeting notes & agendas prompts

Logical next step

After this, most operations teams move on to Process Improvement.

All Operations & Supply Chain prompts · Search the full library