Keywordsai for standard operating proceduresBlogai for workai at workworkplace aiai for professionalshow to use ai at workai productivity
Related searchesai for sopschatgpt standard operating procedureai process documentationdraft sop with chatgptsop owner and exceptionsai for standard operating procedures
A draft SOP is not a live procedure
AI is useful on standard operating procedures because most SOPs begin as a mess: screenshots in a slide, a leaver's notes, three versions of the same form. A model can turn that mess into a draft with steps, inputs, outputs, and a checklist. That draft is not the live procedure. The live procedure includes the exception, the workaround that is not in the slide, and the owner who will be called at four o'clock. Those arrive when a person walks the process and writes what actually happened. Using AI for SOPs without that walkthrough is how you publish a tidy fiction. Tidy fiction is dangerous because people will follow it until something breaks.
The temptation is to prompt from a job title. Write the SOP for accounts payable. The model will produce a generic payable path that could belong to any firm. Your firm has a different system, a different approval limit, and a different person who holds the exception stamp. The generic path will still look complete. Completeness is the hazard. An incomplete human draft at least looks incomplete. A generated SOP looks finished. Finished-looking documents get filed. Filed documents get followed. Followed fictions become incidents. The method is therefore to start from evidence of the process you run, not from the name of the team.
This essay sits beside process documentation and human-in-the-loop. SOPs are the stricter artefact: they tell someone what to do when the usual person is away. That is why owners, version, and exceptions are not optional fields. If you cannot name the person who will be called, stop generating. You are writing a brochure. Brochures are for websites. SOPs are for the moment something is on fire and a colleague needs the next lawful step, not a paragraph of purpose statements. Write the call tree before you write the purpose. Purpose without a name is decoration.
Do not publish an SOP the model invented from a job title. Publish the version a named owner has walked, with exceptions dated on the page.
What AI can draft, and what a walkthrough still owns
AI can draft headings, turn a recorded walkthrough into steps, propose a checklist, and flag missing fields such as input, output, system, and owner. It can compare two versions and list differences. It cannot know the unofficial queue, the person who actually approves, or the step that exists because of an incident last year. Those are walkthrough facts. Your job is to paste or attach the evidence of the process you already ran, then require empty cells where evidence is missing. Empty cells are honest. Filled cells with plausible systems are not. Plausible systems are how a new joiner clicks the wrong product and still thinks they followed the SOP.
Keep the SOP in the place operators already look, with a version and a review date. A generated draft in a chat history is not a controlled document. Controlled means an owner, a date, and a way to retire the old file. When the process changes, the brief changes. When an exception becomes the norm, the SOP changes. AI can help you rewrite the page. It cannot notice that the process moved. Noticing is the owner's job. Put that job in the document, not in a hope that the next model will watch your systems.
| SOP part | Let AI draft | Walkthrough must confirm |
|---|---|---|
| Purpose and scope | Clear sentences from your notes | What is in and out of this procedure |
| Happy-path steps | Numbered steps from the recording | Systems, clicks, and actual sequence |
| Exceptions | A list of gaps it noticed | The real workarounds and who may use them |
| Owner and call tree | A placeholder field | The named role who will be called |
Turn a messy process into a checkable SOP
Walk the process once with a colleague who actually runs it. Record notes or an allowed recording. Paste that evidence into an approved tool. Ask for an SOP with purpose, scope, steps, inputs, outputs, systems, exceptions, owner, and version. Ban invented systems. Ask for missing where a field has no evidence. Then the owner runs the draft as if they were new. Every stuck point is an edit. Only after that run do you publish. Publishing before the run is how you create two processes: the page and the truth. People will follow the wrong one and both will look official.
Schedule a review when a system changes, not only on a calendar. Use the model to diff the old SOP against new notes. Keep the owner as the signer. Project managers can chase the review. They cannot sign a procedure they do not run. If the process has no owner, you do not have an SOP project. You have a writing project. Writing projects do not keep customers safe. Owners do. Put the owner's name and a deputy on the page before you generate a second draft. A second draft without a signer is still a brochure, only longer.
Role: You are drafting a standard operating procedure I will walk before it is live.
Task: Turn the walkthrough notes I paste into an SOP with the fields I name.
Context: Process name, systems in the notes, and the owner who will be called.
Constraints:
- Use only the notes. If a system or exception is not in them, write missing.
- Do not invent a generic industry path from the job title.
- Keep steps numbered, one action each, with the system named when known.
- Separate happy path from exceptions.
Output: SOP draft plus a list of missing fields and risky assumptions.
Quality checks: List steps a new joiner would not be able to perform from this page.The quality list is the walkthrough agenda. If a new joiner could not perform a step, the page is not live. Fix the step with evidence from the floor, not with a more confident sentence. Confidence is what got the fiction filed in the first place. Walk the stuck points with the owner in the same week. A gap that waits for a later version will still be a gap when the substitute is already following the published page.
Procedures nobody would actually run
Generic industry SOPs are the first failure. They name systems you do not have and skip the one you do. The second is missing exceptions. The happy path works in the document and fails at 16:00 on month-end. The third is owner theatre: a team name in a footer and no person who will answer. The fourth is version pile-up: three PDFs, all generated, all slightly different, all in circulation. Operators will pick the shortest. The shortest is often the one that dropped the control. Your control is one live version, one owner, and a walkthrough date on the page.
A subtler failure is using AI to write purpose-heavy pages with no steps. They read well in an audit folder and do nothing on the floor. Require action verbs and systems. If the draft cannot say which screen, it is not an SOP. It is a policy. Policies have their place. They do not tell a substitute how to close the day. Do not let a fluent purpose section stand in for the click path. Auditors may like it. The substitute on Saturday will not. If Saturday is when the process runs, Saturday is the reader. Write for that person.
| Mistake | What it looks like | What to do instead |
|---|---|---|
| Job-title prompt | Generic payable path | Walkthrough notes from the live process |
| No exception list | Happy path only | Month-end and failure paths dated |
| Team as owner | Nobody to call | A named role and a deputy |
| Three PDFs live | Operators pick the shortest | One version, one location |
If the SOP has no named person who will be called, it is not a procedure. It is a document. Documents do not close the day.
Related reading on StudyGrid
Read next: AI for Process Documentation How to Keep a Human in the Loop AI for Project Managers. Those essays sit beside this one. Use them when you need the neighbouring skill, not as a substitute for the check you still have to make.
What to do this week
Walk one messy process with the person who runs it. Capture notes in the approved place. Draft the SOP from those notes only, with missing left visible. Fill missing fields on the floor with the owner watching each gap. Publish only after the owner runs the draft cold, as if new. Retire the old PDFs the same day. That is AI for standard operating procedures without inventing a second, prettier process.