The best way to use an AI SOP generator is to give it your real process (notes, an old procedure, a walkthrough of the task) and let it turn that into clear, numbered steps that your team then reviews. AI is very good at structure and plain language. It does not know the step your most experienced colleague does without thinking, so the workflow below is built around getting that knowledge into the document.
What a Good SOP Contains
- Purpose and scope: what the procedure achieves and when it applies
- Roles: who does each part, and who owns the document
- Prerequisites: tools, access, materials, training
- Procedure: numbered steps, one action each
- Checks: how to confirm a step worked, and what to do if it did not
- Records: what to log and where
- Revision history: what changed, when, and by whom
Writing an SOP with AI in Fable
1. Gather what already exists
Create a project for your procedures and import whatever you have: an old SOP as a Word file or PDF, a checklist, meeting notes from a walkthrough. Each file becomes an editable document. See import and export.
2. Say what to write
Open a blank document and type or speak an instruction that includes the process itself. For example: "Write an SOP for closing the warehouse at night. Purpose, scope, roles, then numbered steps. The steps are: walk the floor for stragglers, check the loading dock doors are locked, set the alarm from the office panel, and log the time in the shift sheet. If the alarm shows a fault, call the on-call manager before leaving." Speaking works well here because you can describe the task the way you would explain it to a new hire. If the source is in other documents, the project assistant can draft the SOP from them as a new document for you to approve.
3. Tighten it
Revise with short instructions: "make every step start with a verb," "split step 4 into two steps," "add a check after setting the alarm." Each edit shows what changed. More on phrasing in editing with AI.
4. Review it with the people who do the work
Invite the team as Viewers or Editors. Viewers select a step and leave a typed or spoken suggestion ("we also check the side gate"), and the owner accepts or rejects it. That is how the unwritten details get in. See suggestions.
5. Keep the history and publish
Every edit is saved to the version history with its author and a diff, which gives you a record of how the procedure evolved. Export to PDF or DOCX for your binder, shared drive or training material.
Tips for Better SOPs, With or Without AI
- Write for the newest person on the team. If a step needs context they will not have, add it.
- One action per step. "Lock the door and set the alarm" is two steps.
- Explain the critical steps. A one-line reason ("so the overnight scan does not flag false alarms") makes people less likely to skip them.
- Test it. Have someone who has never done the task follow the SOP exactly, and fix every point where they hesitate.
- Set a review date. Procedures drift when tools and people change.
When to Use Which Tool
Fable is for writing and maintaining SOPs together: drafting, revising, collecting suggestions and keeping a history. If your industry requires formal document control, such as signed approvals, training acknowledgments or audit trails tied to a regulatory standard, keep using a quality management or document control system for publishing and sign-off, and use an editor like Fable for the writing that happens before it. For more on team review, see how to give writing feedback that helps.
Frequently Asked Questions
Can AI write an SOP?
AI can write a solid first draft of an SOP from your notes, an old procedure or a description of how the work is done, and it is good at turning loose notes into numbered steps. It cannot know the details of your process that nobody wrote down, so the people who do the work still need to review and test it.
What should I give an AI SOP generator?
Give it the real process: existing checklists, an old version of the SOP, notes from someone walking through the task, the roles involved and anything that must never be skipped. The more of your actual process it has, the less it has to guess.
What sections should an SOP include?
Most SOPs include a purpose, scope, roles and responsibilities, definitions, prerequisites such as tools or access, the numbered procedure, checks or quality controls, what records to keep, and a revision history with dates and owners.
How do I keep SOPs up to date?
Give each SOP an owner and a review date, let the people who follow it suggest changes, and keep a revision history. In Fable, every edit is saved with its author and a diff, and the project assistant can find every SOP that mentions a changed tool or step and propose the updates together.