An SOP is not a document written to prove that a business has processes. It is a practical guide that lets a capable person complete recurring work correctly without relying on memory or one unavailable colleague.
AI makes the first draft much faster. But it has one obvious limitation: it only knows the process you show it. If the process is inconsistent or contains hidden judgment, a generated manual will preserve the confusion in better formatting.
Choose a process that is ready to document
Start with work that happens often, has a recognizable good outcome and causes disruption when only one person knows how to do it. Examples include onboarding a client, publishing a post, issuing an invoice or handling a common support request.
Avoid starting with a process that is still changing every week. First stabilise it through a few real runs. Then document the version that has survived contact with actual work.
Capture the work while it happens
Ask the process owner to perform the task once while recording a screen walkthrough or making rough notes. Capture:
- what triggers the work;
- required access, files and inputs;
- each meaningful decision point;
- the expected output;
- exceptions and escalation rules;
- where the final record is stored.
Do not demand perfect prose from the person doing the work. A messy explanation is enough material for AI to organise.
Use AI to make the first structure
Give the model the transcript or notes and use a constrained brief:
Turn this walkthrough into a draft SOP. Include purpose, owner, trigger, required inputs, numbered steps, quality checks, exceptions and escalation rules. Preserve unknowns as questions. Do not create steps, permissions, timings or policies that are not in the source.
The output should read like a working checklist, not a consultancy report. Short steps, exact names for tools and clear checks beat elegant paragraphs.
Review the procedure where it can fail
The process owner should verify the draft alongside someone who has not done the task before. That second person reveals the missing assumptions experts no longer notice.
| Review point | Question |
|---|---|
| Starting point | Could a new colleague find the right input and access? |
| Decision points | Does the SOP explain what changes the route? |
| Quality | Is there a clear definition of done? |
| Exceptions | Does it say when to stop and ask for help? |
| Ownership | Is a named person responsible for keeping it current? |
Correct the document after a real test run, not only after a reading session.
Make maintenance part of the system
Every SOP needs a review date and an owner. Add a small header with the last verified date, the person responsible and links to the systems it uses. Review it after a major tool change, a serious error or every quarter for high-frequency work.
When someone finds a missing step, make updating the SOP part of closing the issue. That is how the document becomes a living asset instead of an obsolete folder.
The rule
Use AI to accelerate documentation. Use real work to prove that the documentation is true.
Start small.
Make it repeatable.
- Input: Define the job, audience, constraints and source material.
- Draft: Use AI for structure and options, not the final unchecked answer.
- Review: Check facts, judgment, tone and the consequence of a mistake.
- Deliver: Put the useful output where work actually happens.
- Learn: Record what improved, failed or should change next time.
Make the workflow yours.
Get the H² AI Workflow Starter Pack: five practical systems, prompts and decision frameworks to turn useful AI ideas into repeatable work.
Get the free Starter Pack ↘Ready to make it
operational?
The AI Business Operations Pack turns the core workflow into six reusable systems, prompts and templates for small-business operations.
Explore the €29 Operations Pack ↗