As of 13 August 2026, AI can only partly create a standard operating procedure.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the existing process documents, forms, policy pages and system instructions for the workflow, and copy the relevant text into one working document.
   2. Ask the person who performs the process to describe the normal route, common exceptions, approval points, records kept and escalation contact, then add those notes to the working document.
   3. Paste the working document into a chatbot with the copyable prompt and replace the bracketed process name, team or role and source material sections.
   4. Save the generated SOP in your team document system, including its owner, version and review date, and mark every [NEEDS CONFIRMATION] item for an answer.
   5. Ask the process owner to run the numbered procedure from start to finish using a normal case and an exception case, recording any step that is missing, unclear or impossible.
   6. Compare each corrected step against the current forms, permissions, system screens and relevant internal policies, then update the SOP without accepting unsupported AI additions.
   7. Send the final draft to the responsible manager or policy owner for approval, publish it in the agreed location and remove or label any superseded version.

   Prompt

   Create a practical standard operating procedure for [PROCESS NAME] for [TEAM OR ROLE]. Use only the information in the source material below and clearly mark every missing detail as [NEEDS CONFIRMATION]. Do not invent steps, timings, systems, permissions, legal requirements or safety controls.
   
   Produce the SOP with these sections:
   1. Title, version and document owner
   2. Purpose and scope
   3. When to use it and when not to use it
   4. Roles and responsibilities
   5. Required access, tools and inputs
   6. Numbered procedure, with one action per step
   7. Decision points and exceptions
   8. Quality checks and records to keep
   9. Escalation route
   10. Review date and change log
   
   For each step, state who performs it, what they do, what information or system they use, and what successful completion looks like. Keep the language plain and specific. Separate confirmed facts from assumptions. At the end, provide a short list of questions that the process owner must answer before this SOP is published.
   
   Source material:
   [PASTE PROCESS NOTES, EXISTING DOCUMENTS, FORMS, POLICIES AND SYSTEM INSTRUCTIONS HERE]

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.