Guides · Updated 2026-10-31

How to Write SOPs with AI: Free Template and 22 Prompts for Small Businesses (2026)

Most small businesses run on one person's memory. The owner knows how to quote a job, open the shop, onboard a client, process a refund and what to do when the card machine fails. That works until you're sick, on holiday, hiring your first employee or trying to sell the business. Then every question comes back to you.

Standard operating procedures (SOPs) fix that: short written instructions for how a recurring task is done in your business. Owners rarely write them because it feels like a week of paperwork. With AI it isn't. You talk through a task for five minutes, paste the transcript into ChatGPT, Gemini or Copilot, and get a clean, numbered first draft you can check in another ten.

Short answer: to write an SOP with AI, (1) pick one task you do at least weekly that others keep asking you about, (2) record yourself explaining or doing it out loud, (3) paste the transcript into a free AI tool with the template and prompt below, (4) correct every step, price and rule the AI got wrong, (5) have someone who has never done the task follow it while you watch, and (6) fix the gaps and save it where your team can find it. A good small-business SOP fits on one page: purpose, when it's used, who owns it, what you need, numbered steps, quality checks and what to do when something goes wrong.

This works with any free AI chat tool. It's general guidance; for safety-critical, food-safety, medical, financial or legally regulated procedures, follow your regulator's or industry body's requirements and have a qualified person sign off.

What AI does well with SOPs, and what it doesn't

The rule: you supply the knowledge, AI supplies the structure. Never let it fill gaps with guesses. Tell it to write [CHECK] wherever it isn't sure.

Step 1: Choose which SOPs to write first

Don't try to document the whole business. List every task you or your team repeat, then score each one:

Start with the three highest totals. For most small businesses these are things like:

• Customer-facing: answering a new enquiry, sending a quote, taking a booking, handling a complaint or refund, onboarding a new client.
• Money: sending invoices, chasing late payments, cashing up, paying suppliers.
• Operations: opening and closing, stock ordering, job completion and sign-off, cleaning and equipment checks.
• People: a new employee's first day, booking leave, what to do when someone calls in sick.

Write one SOP per task, not one giant manual. Short SOPs get read; manuals get ignored.

Step 2: Get it out of your head (the talk-it-through method)

The slowest part of writing an SOP is the blank page. Skip it:

1. Record yourself the next time you do the task, or straight afterwards. Use your phone's voice recorder or dictation, a screen recording for computer tasks, or simply talk to the voice mode of your AI app.
2. Say everything out loud: what you open first, what you check, where you click, what you look out for, and what you do when it goes wrong. "If the customer hasn't paid the deposit, I…" is gold.
3. Get a transcript. Most phones, Google Docs voice typing, Microsoft Word dictation and AI apps can turn speech into text. It doesn't need to be tidy.
4. Remove anything sensitive before you paste: customer names, account numbers, passwords and door or alarm codes. Write [customer], [supplier] or [stored in password manager] instead. Our guide is ChatGPT safe for customer data? explains what never to paste.
5. Paste it into AI with the template below (prompt 1).

Five minutes of talking usually becomes a solid first draft.

Step 3: Use a one-page SOP template

Give AI the same template every time so all your SOPs look the same. Copy this:

• SOP title: [verb + task, e.g. "Send a quote for a new enquiry"]
• Purpose: why this task matters, in one sentence.
• When: what triggers it (e.g. a new web enquiry, every Friday at 4pm).
• Owner: the role responsible (not a person's name), and who to ask if stuck.
• You'll need: systems, templates, tools, materials. No passwords.
• Steps: numbered, one action per step, starting with a verb. Include the expected result where useful ("you should see a green 'Sent' label").
• Quality check: 3–5 things to confirm before the task counts as done.
• If something goes wrong: the most common problems and what to do, plus when to stop and call the owner.
• Time it should take: [minutes].
• Version and date: v1, [date], reviewed by [role].

Keep it to one page. If an SOP needs more than about 15 steps, split it into two.

Step 4: Check it, then test it on a real person

AI drafts look finished. They aren't. Before anyone relies on an SOP:

1. Read every step against reality. Check names of systems, buttons, prices, timeframes and policies. Delete anything AI invented.
2. Resolve every [CHECK].
3. Do the "new person" test. Ask someone who has never done the task (a new hire, a family member, a colleague from another role) to follow the SOP while you watch without helping. Every time they hesitate or ask a question, the SOP has a gap.
4. Fix the gaps and re-test until they can do it alone.
5. Get sign-off from a qualified person for anything involving safety, hygiene, money handling rules or regulated advice.

The prompts

Paste a short business brief at the start of your chat (what you sell, team size, the systems you use, your tone), or save it in your AI tool's custom instructions, so you don't repeat it.

Drafting SOPs

1. "Here is a transcript of me explaining how we [task] in my [type of business]: [paste]. Turn it into a one-page SOP using this template: [paste template]. Use only what's in the transcript. Wherever information is missing or unclear, write [CHECK] instead of guessing. Plain English, one action per step, each step starting with a verb."
2. "Before you write the SOP, ask me up to 10 questions about anything missing from this transcript: exceptions, tools, timings, who approves what, and what goes wrong most often. Ask them one at a time."
3. "Here are my rough bullet notes for [task]: [paste]. Turn them into an SOP using the template. Don't add steps I didn't mention; list anything you think is missing separately at the end as 'Possible gaps'."
4. "Here is an existing SOP that nobody reads: [paste]. Cut it to one page without losing any required step, and move background information into a short 'Why' line at the top."
5. "List every recurring task a [type of business] with [number] staff typically does, grouped into customer, money, operations and people. I'll mark which ones apply to us."
6. "Score these tasks for which SOP I should write first, using frequency, how often staff ask me and how bad a mistake is: [paste list with my notes]. Show a table and your top 3."

Making SOPs easy to use

7. "Turn this SOP into a printable checklist with tick boxes, under 12 lines, for staff to use on the job: [paste]."
8. "Make a quick-reference card from this SOP: the 5 most important steps and the 3 most common mistakes, short enough to laminate: [paste]."
9. "Rewrite this SOP for a new starter on their first week, with no jargon and a one-line explanation of any term they might not know: [paste]."
10. "Translate this SOP into [language] for a team member whose first language is [language]. Keep the step numbers, system names and placeholders exactly the same: [paste]." Have a fluent speaker check it.
11. "Turn this SOP into a simple flowchart described in text: decisions as questions with yes/no branches: [paste]."
12. "Write a 5-question quiz with answers to check that a new employee understands this SOP: [paste]."

Exceptions, problems and quality

13. "Here is our SOP for [task]: [paste]. List the 8 most likely things that could go wrong when someone follows it, and for each, suggest what the 'If something goes wrong' section should say. Mark any that should go straight to the owner."
14. "Read this SOP as a sceptical new employee. Which steps are vague, assume knowledge or could be done two different ways? Quote each one and suggest clearer wording: [paste]."
15. "Compare these two versions of the same SOP and list every difference in steps, timings or rules, so I can decide which is right: [paste both]."
16. "Write the quality check section for this SOP: 3–5 checks a manager could verify in under two minutes: [paste]."

Customer, money and people SOPs

17. "Draft an SOP for handling a customer complaint in my [type of business]: acknowledge within [time], gather facts, what staff can offer without approval (up to [limit]), when to escalate to [role], and how to record it. Use [CHECK] for anything you'd need me to confirm." Pair it with our negative review reply guide.
18. "Draft an SOP for chasing an overdue invoice, with the reminder steps on day [x], [y] and [z], the tone at each step and when to stop and call." Our invoice reminder templates give you the wording.
19. "Draft a first-day SOP for a new [role]: what to prepare before they arrive, the first-day schedule, which SOPs they should read in week one and who they shadow. Don't include any personal or payroll details."
20. "Create an index of all our SOPs from this list: [paste titles]. Group them by area, give each a short code (e.g. CUS-01, FIN-02) and suggest a review date six months from [date]."

Keeping SOPs up to date

21. "Here is our SOP and a note about what changed: [paste both]. Update the SOP, increase the version number, and list the changes at the bottom in one line each so I can tell the team."
22. "Write a short message to my team announcing this updated SOP: what changed, why, and from when. Under 80 words, friendly, for WhatsApp or email." You send it, not the AI.

Where to keep SOPs so people use them

• One shared folder (Google Drive, OneDrive, Dropbox or Notion) with one document per SOP, named with its code and title, e.g. CUS-01 Answer a new enquiry.
• One index page linking to every SOP, pinned where staff will see it.
• Print the checklists for tasks done away from a computer, such as opening, closing, cleaning and job sign-off.
• Never store passwords, alarm codes or bank details in an SOP. Point to your password manager instead.
• Review each SOP every six months, or whenever someone says "that's not how we do it any more". An out-of-date SOP is worse than none.

From SOP to AI employee: the same document, a new reader

Here's the part most owners miss: a clear SOP is exactly what an AI assistant needs too. The tasks you document for staff, such as answering enquiries, following up quotes, chasing invoices or preparing a weekly report, are often the first ones you can hand to an AI employee.

With Grok Bot, for example, you create a bot, give it a role, and paste your SOP into its instructions in plain English. Connect the apps the task needs (such as Gmail or Outlook, Google Calendar and Google Drive), store any logins in Grok Bot's Vault rather than in the SOP, and turn a task that works once into a scheduled routine (for example every weekday at 8am). Add "Ask first" rules in Auto-review for sending, publishing, deleting and purchasing, so the bot does the legwork and every customer-facing action waits for your approval. For example:

"You are our quotes assistant. Follow SOP CUS-02 'Follow up a sent quote' (pasted below) exactly. Every weekday at 9am, check the Quotes sheet in my Drive for quotes sent more than 3 days ago with no reply, and draft a follow-up email for each using step 4 of the SOP. If a quote is over [amount] or the customer has complained, don't draft anything: flag it to me. Draft only: I approve every email before it's sent."

Two habits make this work: when the bot gets something wrong, fix the SOP, not just the chat, so the same rule applies next time, and keep your staff SOP and bot instructions in sync. Check current Grok Bot plans and availability. The SOPs themselves work in any free AI tool.

A 7-day SOP sprint (about 20 minutes a day)

1. Day 1: list your recurring tasks and score them (prompts 5 and 6). Pick your top 3.
2. Day 2: record yourself talking through SOP #1. Draft it with prompts 1 and 2.
3. Day 3: check every step, resolve the [CHECK]s and run the new-person test.
4. Day 4: do SOPs #2 and #3 the same way.
5. Day 5: make checklists and quick-reference cards (prompts 7 and 8). Set up your shared folder and index (prompt 20).
6. Day 6: share them with your team and ask each person to find one gap.
7. Day 7: update from their feedback (prompt 21), and pick one SOP to hand to an AI assistant or routine.

After a month of one SOP a week, the questions that interrupt you every day start answering themselves.

Frequently asked questions

Can ChatGPT write SOPs for my business?

Yes, as a first draft. ChatGPT, Gemini and Copilot are good at turning a voice-note transcript or rough notes into clear, numbered steps in a consistent template. They don't know how your business actually works, so tell them to use only what you give them and mark gaps with [CHECK], then correct every step and test the SOP on someone who has never done the task.

What should a small-business SOP include?

Keep it to one page: a title starting with a verb, the purpose, when it's used, the role that owns it, what you need, numbered steps with one action each, a short quality check, what to do when something goes wrong, how long it should take, and a version number and date. Never include passwords, alarm codes or bank details.

Which SOPs should a small business write first?

Start with tasks that happen often, that staff keep asking you about and where mistakes are costly: usually answering new enquiries, sending quotes, taking bookings, handling complaints and refunds, invoicing and chasing payment, opening and closing, and a new employee's first day. Score your tasks and write the top three first.

How long should an SOP be?

Short enough to follow while doing the task, usually one page and no more than about 15 steps. If it's longer, split it into separate SOPs. Turn the steps into a printable checklist for jobs done away from a computer.

Is it safe to put my business processes into AI?

Your general processes are usually fine to paste. Remove customer names and details, passwords, door or alarm codes, bank details and anything confidential before you paste a transcript or notes, and use your AI tool's privacy settings or a business plan for regular work. See our guide on whether ChatGPT is safe for customer data for a full what-never-to-paste list.

Can an AI employee follow my SOPs?

Yes. A clear SOP makes a good set of instructions for an AI assistant. In Grok Bot you can paste an SOP into a bot's instructions, connect the apps the task needs, run it as a scheduled routine and add "Ask first" approval rules so emails, posts and payments wait for you. When it makes a mistake, update the SOP so the fix sticks.

More help: learn the basics in how to use ChatGPT for small business, see the best free AI tools for small business, and plan your first AI employees with Grok Bot. Want copy-paste prompts and AI-employee blueprints in one place? See our AI playbooks and plans and pricing.

Get a personalised AI plan for your business free: take the 2-minute quiz.