Standard Operating Procedure Template + AI Workflow
Get a free standard operating procedure template and a step-by-step AI workflow to turn how you work into a clear SOP your team can follow and improve.
- Time to complete
- 60 to 90 minutes for your first SOP (about 30 minutes for later ones)
Tools:
Any AI chat assistant (ChatGPT, Claude or Gemini; free tiers are enough)
Your phone's voice recorder or a screen recorder
A transcription tool (many phones and AI apps can transcribe a voice note)
A shared folder where your team can find the finished SOP
The free standard operating procedure template in Step 2
You know exactly how a task should be done, but that knowledge lives in your head. When you are busy or away, things slip: an order goes out in the wrong size, a customer is not updated, a payment is not confirmed. A standard operating procedure (SOP) fixes this by writing the task down clearly enough that someone else can do it the same way, every time.
Most people never write SOPs because starting from a blank page is slow. With AI, you talk through how you do the task, and AI turns the rough recording into a clean, structured document. You still check and test it, but the organising and formatting are done for you.
By the end of this workflow, you will have a tested SOP for one real task in your business, a free standard operating procedure template you can reuse for every future process, and a simple routine for keeping your SOPs current.
Before You Start
Pick one task to document first. Choose something that happens often, matters to customers or money, and that you currently do yourself or explain repeatedly: processing an order, onboarding a client, closing the shop at night or reconciling the day's payments. An SOP should cover a single process with a clear start and finish, so avoid anything as broad as "run the business".
If your recording will include customer names, phone numbers or bank details, remove or replace them before pasting anything into an AI tool. If you have not yet agreed rules on what staff can share with AI, our AI policy for small businesses guide gives you a free template to start from.
Step 1: Record Yourself Doing the Task
The fastest way to capture a process is to do it while talking through it. Record a voice note as you work, or use a screen recorder if the task happens on a computer. Explain what you are doing and why, including the small judgement calls: "If the customer has not paid within two hours, I send a reminder."
Rambling is fine; you want the steps you do automatically and would forget to write down. Then transcribe the recording. If you already record team calls, our guide to AI meeting notes shows how to get clean transcripts, and the same approach works here. If recording is not practical, write quick bullet points and let AI interview you to fill the gaps.
I want to write a standard operating procedure for this task: [task name].
I will describe how I do it below. Ask me up to 10 short questions, one at a
time, to uncover steps, decisions, tools and problems I might have forgotten.
Do not write the SOP yet.
My rough description:
[paste your notes or transcript]Checkpoint: You have a raw transcript or notes (plus answers to the AI's questions) covering the task from start to finish, with personal data removed.
Step 2: Set Up Your Standard Operating Procedure Template
Before AI drafts anything, fix the structure. Using the same layout for every SOP means staff always know where to find the steps, who is responsible and what to do when something goes wrong. Copy the template below and save it as your master copy.
STANDARD OPERATING PROCEDURE
Title: [Name of the process]
SOP ID: [e.g. OPS-001]
Version: [1.0] Date: [DD/MM/YYYY]
Owner: [Person responsible for keeping this SOP accurate]
Approved by: [Name]
Next review date: [DD/MM/YYYY]
1. PURPOSE
Why this process exists and what a good result looks like (1-2 sentences).
2. SCOPE
What this SOP covers and what it does not. Where it starts and ends.
3. ROLES AND RESPONSIBILITIES
- [Role]: [What they do in this process]
4. TOOLS AND MATERIALS
- [App, form, account, equipment or template needed]
5. PROCEDURE
Step 1: [Action, written as a clear instruction]
Who: [Role] When: [Time or trigger]
Notes: [Tips, standards, example messages]
Step 2: ...
6. QUALITY CHECKS
- [What must be checked, by whom, before the process is complete]
7. EXCEPTIONS AND PROBLEMS
- If [problem], then [what to do] and inform [role].
8. RECORDS
- [What is saved, where, and for how long]
9. CHANGE LOG
Version | Date | Change | Changed by
1.0 | | First version |For simple tasks you can trim sections, but always keep Purpose, Roles, Procedure, Quality Checks, Exceptions, and the version and owner details.
Checkpoint: The template is saved as a master document, ready to paste into your prompt.
Step 3: Have AI Draft the SOP
Give the AI your transcript and the template together. Be specific about the reader: an SOP for an experienced manager looks very different from one for a new staff member in their first week.
You are helping me write a standard operating procedure for a small business.
Business: [type of business and location]
Process: [task name]
Who will follow this SOP: [e.g. a new sales assistant with basic smartphone skills]
Use this template exactly, filling every section:
[paste your template]
Here is my transcript of how I do the task:
[paste transcript and Q&A answers]
Rules:
- Write each step as a clear instruction starting with a verb.
- One action per step. Keep steps under 30 words where possible.
- Include example wording where staff talk to customers.
- Turn every "if this happens" comment into an entry under Exceptions.
- Mark anything you had to guess with [CHECK] so I can confirm it.
- Use British English.The [CHECK] instruction matters. AI fills gaps confidently, and you need to see where it has assumed something rather than taken it from your words.
Checkpoint: You have a complete first draft in your template format, with guesses clearly marked.
Step 4: Review the Draft Against Reality
Read the draft line by line while doing the task, or with it fresh in your mind. Resolve every [CHECK] item. Rewrite vague steps: "handle the payment" becomes "confirm the transfer has arrived in the business banking app before packing". Make sure every step names a role.
Then ask the AI to critique the draft as a beginner would.
Read this SOP as if you were a new staff member who has never done this task
and cannot ask anyone for help. List:
1. Any step you would not know how to do.
2. Any word or abbreviation you would not understand.
3. Any decision where the SOP does not tell you what to choose.
4. Anything that could go wrong that is not covered under Exceptions.
SOP:
[paste draft]Checkpoint: All [CHECK] markers are resolved, vague steps are rewritten and the beginner review gaps are addressed.
Step 5: Test It With Someone Else
This is the step most people skip, and the one that matters most. Give the SOP to someone who does not normally do the task and ask them to follow it exactly, without help from you. Ask them to note every point where they hesitated, guessed or got stuck.
If no one is available, follow only the document next time, noting every moment you relied on memory.
Checkpoint: At least one person (ideally not you) has completed the task using only the SOP, and you have a list of where they struggled.
Step 6: Refine the SOP From the Test
Take the tester's notes back to the AI and ask it to update the document, recording changes in the change log.
Here is my SOP and feedback from someone who tested it.
Update the SOP to fix every issue in the feedback. Keep the same template.
Do not add new steps unless the feedback requires them.
Add a line to the Change Log describing what changed, and set the version to [1.1].
SOP:
[paste SOP]
Tester feedback:
[paste notes]If the test revealed a real disagreement, such as two people doing a step differently, decide which way is correct before asking AI to rewrite it. AI can format a decision, but it should not make it for you.
Checkpoint: You have version 1.1 with the tester's issues fixed and the change log updated.
Step 7: Store, Share and Schedule Reviews
An SOP nobody can find is useless. Save the final version in one shared place with a clear name such as "OPS-001 Order to Delivery v1.1", and pin a link in your team chat. For phone-based tasks, a one-page summary saved in a staff WhatsApp group works well.
Set a review date every three to six months, or sooner whenever a tool or price changes. Our protect your best hours first workflow helps you block focused time for this kind of maintenance so urgent messages do not crowd it out.
Turn this SOP into a one-page quick reference card with only the numbered
steps and the top 3 exceptions. Use short lines that read well on a phone
screen. Keep the SOP ID and version at the top.
SOP:
[paste final SOP]Checkpoint: The SOP is saved in a shared place, the team knows where it is, a quick reference card exists if needed, and a review date is in the calendar.
Worked Example: A Lagos Online Fashion Store's Order-to-Delivery Process
Chiamaka runs a small online fashion store from Yaba, Lagos. She sells through Instagram, and almost every order is completed on WhatsApp. She has just hired Tolu as a sales assistant to handle orders.
Step 1. On a busy Saturday, Chiamaka records voice notes while handling three orders: confirming item and size, sending account details, checking payment, packing, booking the dispatch rider and updating the customer. She mentions details she would never have written down: she always asks for a nearby landmark, sends a photo of the packed item before it leaves, and never releases an order on a transfer screenshot alone because of fake alerts.
Steps 2 and 3. She pastes the transcript and template into an AI assistant, naming the reader as "a new sales assistant comfortable with WhatsApp Business but new to our store". The draft has 14 steps, three roles (sales assistant, owner, dispatch rider) and five [CHECK] markers, including "Delivery fee for Lekki? [CHECK]".
Step 4. Chiamaka fills the gaps: the same-day cut-off is 1pm, delivery fees are in a pinned price note, and payments are confirmed in the business banking app only. The beginner review flags "book the rider" as unclear, so she adds a booking message with what the rider needs: name, phone, address, landmark and whether to collect cash.
Step 5. Tolu follows the SOP for a full day without asking Chiamaka. She notes three sticking points: what to do when a customer wants to swap sizes after paying, whether to share the rider's number, and what to do if the rider is more than an hour late.
Step 6. Chiamaka decides the answers and the AI adds them as exceptions: size swaps before dispatch are fine if stock allows; the rider's number is shared only after pickup; late riders are chased after 30 minutes and the customer gets a new time. Version 1.1 goes into the shared folder, with a quick reference card pinned in the staff WhatsApp group.
Tolu now handles orders confidently, and when Chiamaka later sets up automated replies, the SOP becomes their source. Our guide to AI customer service on WhatsApp explains how to build those replies from documents like this.
Common Mistakes
Letting AI invent your process. A one-line request like "write an SOP for order processing" produces a generic document that does not match your business. Always start from your own recording or notes.
Writing for yourself, not the reader. You understand shorthand like "check the alert". A new staff member does not. Name the reader in your prompt and test with a real person.
Skipping the test. An untested SOP is a guess. Gaps only appear when someone else tries to follow it.
Ignoring exceptions. Most problems happen when something unusual occurs, so the exceptions section is often more useful than the main steps.
No owner or review date. Prices, apps and suppliers change. Without an owner, the SOP slowly becomes wrong and people stop trusting it.
Next Steps
Once one SOP works, document the next most repeated task. After a few, you will notice which steps are purely routine, such as sending the same confirmation message or copying order details into a spreadsheet. Those are ideal for automation, and our automate your first business task with AI workflow shows how to take that step.
Clear processes also build trust with clients. If you sell services, our workflow to write a business proposal with AI shows how to turn your SOPs into a convincing "how we work" section.
Frequently Asked Questions
What is a standard operating procedure?
A written set of step-by-step instructions for carrying out a routine task the same way every time. It usually includes the purpose, who is responsible, the tools needed, the steps, quality checks and what to do when something goes wrong.
Is this standard operating procedure template free to use?
Yes. Copy it, adapt it for your business and use it as often as you like. Save it as a master document so every new SOP starts from the same structure.
Which AI tool is best for writing SOPs?
Any capable assistant works, including the free tiers of ChatGPT, Claude and Gemini. Your recording and testing matter far more than the tool.
How long should an SOP be?
As short as possible while still complete. Most small-business SOPs fit on one to three pages. If yours is much longer, it probably covers more than one process and should be split.
How often should I update my SOPs?
Review each one every three to six months, and immediately whenever a tool, price, supplier or responsibility changes. Record each change in the change log so your team knows which version is current.
Is it safe to put business information into an AI tool?
Avoid sharing customer personal data, passwords, bank details or confidential pricing. Replace real details with placeholders. A written AI policy helps your whole team follow the same rules.
More in Productivity Workflows.