As of 13 August 2026, AI can only partly turn your notes into 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 a document containing the notes and remove unrelated conversations, guesses and duplicate versions.
   2. Gather the current process owner's name, intended users, systems or equipment involved, required records, known exceptions and approval requirements.
   3. Paste the context and notes into the chatbot using the supplied prompt, keeping each unclear instruction visible rather than silently correcting it.
   4. Copy the draft SOP into your normal document system and fill in each [CHECK] and [OWNER TO CONFIRM] item with the process owner.
   5. Ask a colleague who performs the work to follow the numbered procedure using the real tools and records, and note every step that is missing, ambiguous or out of order.
   6. Compare the corrected SOP against the original notes and current workplace instructions, then obtain the normal internal approval before publishing it to the team.

   Prompt

   Turn the notes below into a draft standard operating procedure for a UK workplace. Do not invent facts, steps, timings, measurements, legal requirements, safety controls, names or system details. Preserve every factual instruction from the notes, remove duplication, and flag anything unclear or contradictory as [CHECK]. Where the notes do not provide an answer, write [OWNER TO CONFIRM] rather than guessing.
   
   Use this structure:
   - Title
   - Purpose
   - Scope and exclusions
   - Who is responsible for each part
   - Required tools, materials, records and access
   - Definitions
   - Numbered procedure, with one action per step
   - Decision points and exceptions
   - Quality or completion checks
   - Health and safety or compliance items mentioned in the notes, clearly labelled for owner confirmation if incomplete
   - Records to create or retain
   - Escalation route
   - Version, owner, approval status and review date fields
   
   Make the procedure clear enough for a new team member to follow, but do not claim that it is safe, compliant or ready to use. After the SOP, provide a table with: issue, why it matters, exact information needed, and who should confirm it.
   
   Context:
   Business or team: [BUSINESS OR TEAM]
   Process name: [PROCESS NAME]
   Intended users: [INTENDED USERS]
   Process owner: [PROCESS OWNER]
   
   Notes:
   [PASTE NOTES 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.