Most small businesses already have procedures. They just live in one person’s head, a Slack thread from last spring, and a sticky note that says “check the thing before posting.” When that person is on holiday, the procedure goes with them. This guide shows how to create SOP with AI from the raw material you already have: rough notes, a recorded walkthrough, or the half-remembered steps someone can describe in ten minutes.
Language models are good at turning a messy description into a clean sequence. They cannot know which step the person describing the task forgot to mention. So the method has two halves: AI drafts the structure, then a human who did not write it tries to follow it. Most of the value is in the second half.
What a procedure needs before anyone should trust it
A standard operating procedure (SOP) is a written description of how a repeated task gets done, by whom, and how you know it is finished. The US Environmental Protection Agency’s guidance on preparing SOPs is written for labs, but its core advice transfers well to a four-person marketing team. It says SOPs should be concise and step-by-step, written in the active voice, and detailed enough that someone with limited experience of the procedure, but a basic understanding of the work, can complete it unsupervised. If your new hire needs to ask three questions to finish the task, the document is only a memory aid for the expert.
The same guidance recommends that draft SOPs be tested by people other than the original writer before they are finalized, and that procedures be reviewed periodically (it suggests every one to two years) to confirm they are still current or even needed. For a business whose AI tools change every few months, that is generous.
Choose a task that deserves a procedure
A good candidate repeats at least monthly, involves a handover, and causes real trouble when a step is skipped. Content approval and client onboarding qualify. “Answering email” does not; it is too varied to fit a sequence. If you are deciding which recurring work to systematize first, the selection matrix in our guide to workflow automation for small business works for SOPs too, because a task you can document clearly is usually a task you could later automate.
Pick one task. Writing five procedures at once produces five vague procedures.
Capture the raw material
The input matters more than the prompt. Combine any of these.
Process notes. Ask the person who does the task to write down every step the next time they do it, including the boring ones. Notes written during the task beat notes written from memory, because memory skips the parts that have become automatic, which are exactly the parts a new person will miss.
A recorded walkthrough. Have the person share their screen and narrate while they do the task in a call, then use the transcript. In Microsoft Teams, all participants see a notification when a meeting is being transcribed. OpenAI’s help page for ChatGPT record mode tells users to get the right consents before recording others. Ask first, and use a test record so no client data appears on screen.
A short interview. Ten minutes of “what happens if that fails?” surfaces exceptions a clean walkthrough never shows, because nothing went wrong on the day you recorded.
The extraction prompt
Paste the raw material below the prompt. The key line is the one about gaps; without it, the model will invent plausible steps and the procedure will look complete when it is not. Our article on writing AI instructions that say what to do explains why explicit constraints like this work better than vague requests.
You are turning raw process notes into a standard operating procedure.
Task name: [name]
Who performs it: [role]
Source material: [paste notes or transcript below]
Produce these sections:
1. Purpose (one or two sentences: why the task exists)
2. Scope (when this procedure applies and when it does not)
3. Prerequisites (access, files, tools, information needed before starting)
4. Roles (who does each part, who approves)
5. Steps (numbered, one action per step, active voice, include where the action happens)
6. Checkpoints (where someone must verify something before continuing)
7. Exceptions (what to do when a step fails or a situation is unusual)
8. Done criteria (how the performer knows the task is complete)
Rules:
- Use only information in the source material.
- Where a step, owner, tool, or decision is missing or unclear, write [GAP: describe what is missing] instead of guessing.
- After the procedure, list every GAP as a question for the process owner.Expect several gaps on the first pass. A draft with zero gaps usually means the model filled them in quietly.
SOP template
Use one consistent layout so people know where to look.
| Field | What goes in it |
|---|---|
| Title and ID | Plain task name plus a short code (e.g. SOP-04) |
| Owner | One named person responsible for keeping it accurate |
| Version and date | Version number, date approved, next review date |
| Purpose | Why the task exists, in one or two sentences |
| Scope | When to use it, and when not to |
| Prerequisites | Access, accounts, files, information needed first |
| Roles | Who performs, who reviews, who approves |
| Steps | Numbered actions, one per step, with location |
| Checkpoints | Verifications that must pass before continuing |
| Exceptions | What to do when something fails or is unusual |
| Done criteria | Observable signs the task is complete |
| Change log | What changed, when, and who approved it |
Worked example: a content approval procedure
The example below is illustrative. Copperleaf Garden Supply is a fictional four-person shop that publishes one blog post and a handful of social posts each week. A freelance writer drafts, the marketing lead edits, and the owner approves anything that mentions prices or product claims. This is the procedure after the extraction prompt, the gap questions, and the review described below.
| Field | Copperleaf SOP-04: Blog post approval (illustrative) |
|---|---|
| Owner | Marketing lead |
| Version | 1.1, approved 3 Nov 2026, next review 3 Feb 2027 |
| Purpose | Make sure every blog post is accurate, on brand, and approved before it goes live. |
| Scope | All blog posts. Social posts follow SOP-05. Urgent stock notices skip step 5 if the owner is unavailable and are reviewed afterwards. |
| Prerequisites | Edit access to the shared Drafts folder and WordPress editor role; current price list; brand voice sheet. |
| Roles | Writer drafts. Marketing lead edits and schedules. Owner approves price and product claims. |
| Done criteria | Post scheduled in WordPress, approval recorded in the content tracker, writer notified. |
The steps, as they appear in the finished document:
- Writer saves the draft in Drafts/Blog with the filename format YYYY-MM-DD-topic and sets the tracker status to “Ready for edit.”
- Marketing lead edits for structure, voice, and length within two working days, using the brand voice sheet.
- Marketing lead checks every price, stock claim, and product specification against the current price list. Checkpoint: any figure that cannot be matched is highlighted, not deleted.
- If the post mentions prices, discounts, or product performance, marketing lead sets the tracker to “Needs owner approval.” Otherwise skip to step 6.
- Owner approves or comments in the document within two working days. Exception: if the owner is away for more than three days, the post waits; it does not publish without approval.
- Marketing lead pastes the approved text into WordPress, adds the featured image and alt text, previews on a phone, and schedules it.
- Marketing lead sets the tracker to “Scheduled” and messages the writer with the publish date.
The review: let someone else try to follow it
This is the step most people skip. Give the draft to someone who did not write it and does not normally do the task. Ask them to follow it on a real or test piece of work and stop wherever they would have to ask a question. Each stop is a missing step.
In the illustrative Copperleaf case, a described review (not a real staff test) produced the gaps below. Version 1.0 read fine to the marketing lead, because she already knew everything it left out.
| Where the reviewer stopped | What was missing | Fix in version 1.1 |
|---|---|---|
| Step 1 | No filename rule; drafts arrived as “blog final v3” | Added the date-topic filename format |
| Step 3 | Which price list? There were two in the shared drive | Named the current price list in Prerequisites |
| Step 5 | Nothing said what happens if the owner is away | Added the “post waits” exception |
| Step 6 | Reviewer lacked WordPress access and could not continue | Added editor role to Prerequisites |
Before the human review, AI can play a skeptical newcomer. It catches vague wording cheaply, though it will never notice the two price lists in a shared drive it has never seen.
Read this procedure as a new employee who has basic knowledge of the work
but has never done this task here. Go step by step. For each step, list any
question you would need answered before you could act, any term that is not
defined, and any access or file you would need that is not listed in
Prerequisites. Do not rewrite the procedure.Ownership, versions, and the day the tools change
A procedure without an owner decays quietly. Name one person, not a team, and put a review date on the document itself. For tasks that run through AI tools or automation platforms, set that review date three to six months out rather than one to two years, and add a rule: whenever a tool in the procedure changes (a new plan, a renamed menu, a new person with access), the owner updates the SOP before the next run, not after someone gets stuck.
Keep a short change log at the bottom. It does not need to be elaborate.
| Version | Date | Change | Approved by |
|---|---|---|---|
| 1.0 | 27 Oct 2026 | First draft from notes, gap questions answered | Marketing lead |
| 1.1 | 3 Nov 2026 | Four fixes after walkthrough review | Owner |
Illustrative change log for the fictional Copperleaf example.
Store procedures where people already look. If your team keeps reusable prompts in a shared library, the SOP extraction prompt belongs there too, with the same version and owner fields described in our guide to building an AI prompt library. If any step relies on an AI tool, name the tool and plan in Prerequisites; our overview of AI tools for small business can help you pick one based on the job rather than the hype.
A few honest limits
AI does not observe your business, so a procedure written from a five-minute description will be five minutes deep. It also likes tidy, generic steps (“ensure quality standards are met”) that tell nobody what to do. Replace any step a second person cannot check. And do not call a procedure tested until someone other than the author has followed it.
Start with one task this week and hand the draft to the least experienced person on the team. Their questions are the procedure’s real first draft.
Direktorium publishes practical guides like this for small teams putting AI to work. If you would rather have someone document and systematize your workflows for you, BBDirector can help.
