PROMPT ENGINEERING

AI Prompts for SOPs: Capture How Your Team Works

Twenty new prompts that turn voice notes, terminal history and the know-how in your head into procedures your staff can actually follow, train on and keep up to date.

·10 min read

Quick Answer

The best AI prompts for SOPs start from how the work is really done: a voice note, a transcript, your command history or an interview. They tell the AI to use only that material, split steps into single actions and list missing steps as questions instead of guessing. You then test the draft on a real person.

The best AI prompts for SOPs don't ask the AI to write a procedure from scratch. They hand it a record of how the work is really done, like a voice note of you closing the till or the commands you ran during last night's deploy, and ask it to turn that into numbered steps. Then they tell it to stop and ask whenever a step seems to be missing.

That second part matters more than it sounds. Ask a chatbot to "write an SOP for receiving supplier deliveries" and you'll get something tidy and generic. It reads well, but it isn't your process. It doesn't know your supplier always delivers late on Fridays, or that you check the chiller temperature before signing anything. Staff can tell straight away when a procedure was written by someone who has never done the job, and they quietly ignore it.

So this week's twenty prompts are about capturing real know-how. Two went into each of the ten categories, and every one of them works from your material, not the model's imagination.

What Are the 20 New Prompts For?

They fall into four groups.

Capture. Turn a Voice Note Into a Step-by-Step SOP, Interview Me to Capture a Process Only I Know, Turn Shell History Into a Deployment Runbook, Write a README Setup Guide From a Fresh Install Test, and Turn a Task You Repeat Weekly Into a Checklist. These get knowledge out of someone's head and onto a page.

Improve. Rewrite an SOP So a New Hire Can Follow It, Find the Gaps in an SOP Before an Audit, Turn Government Guidelines Into a Staff Checklist, and Update an Outdated SOP Without Rewriting It. These fix procedures you already have.

Teach and roll out. Turn an SOP Into a 20-Minute Training Session, Write a Quiz That Checks Staff Understood an SOP, Announce a New Process to Your Team by Email, Ask a Colleague to Review an SOP Draft, and Write Instructions to Delegate a Task You Always Do. A procedure nobody has been taught is just a file.

Make it visual and local. Write a Bilingual SOP for a Multilingual Workforce, Generate Step-by-Step Illustrations for a Visual SOP, Create a Clear Safety Sign for Your Workplace, Write a Posting Workflow SOP for Your Social Team, Turn Your Best Post Into a Repeatable Content Recipe, and Document the Processes You Own Before Your Review.

The interview and audit prompts sit in Business. The bilingual SOP and government checklist prompts are in SEA Business, because they lean on how work is organised in this region.

Why Should a Small Business Write SOPs With AI?

Because in a small business, the procedure usually lives in one person's head, and that person is busy.

The cost of that shows up in research, though the best-known study is a few years old. A 2018 Panopto survey, run with YouGov, asked 1,001 US employees at organisations with at least 200 staff how long they wait for information, guidance or training that only a colleague can give them. The average was 5.3 hours a week. Panopto's Workplace Knowledge and Productivity Report then estimated that inefficient knowledge sharing costs a company of about 17,700 employees around $47 million a year in lost productivity. Your business isn't that big. But in a team of ten, the person everyone waits on is often the owner, and every hour they spend answering "how do I do this again?" is an hour not spent on the business.

Writing SOPs has always been the fix, and it has always been the job nobody gets round to. It's slow, it's boring, and the people who know the process best are the worst at explaining it, because they've stopped noticing the steps. That's where AI is genuinely useful. Talking through a task for five minutes is easy. Turning a rambling transcript into clean numbered steps is exactly the kind of work a language model does well.

And you stay in charge of the content. Microsoft's 2026 Work Trend Index for Singapore, a survey of 20,000 AI-using knowledge workers across 10 markets, found 88% of AI users in Singapore say they stay responsible for the thinking when they use AI, and 66% say they're producing work they couldn't have created a year ago. SOPs are a good example of both. The AI does the drafting. You decide what the process is.

How Do You Stop AI From Inventing Steps?

Give it a source and three rules. Every capture prompt this week uses the same pattern.

Use only what is in the material. The voice note prompt says "Use only what is in the transcript." The runbook prompt works only from the commands you pasted. Without that line, a model will helpfully fill gaps with steps that are common in other businesses, and a plausible extra step is worse than a missing one, because nobody questions it.

List gaps as questions. Instead of guessing, the AI ends with a list of things it couldn't work out. "You mentioned counting the float, but not what to do if it's short." Those questions are the most valuable part of the output. They're the steps you do without thinking, which are exactly the ones a new person will miss.

One action per step. "Check the delivery and sign the docket" is two steps, and the second one should only happen if the first one passes. Splitting steps makes the procedure easier to follow and shows where the real decisions are.

The coding prompts add one more rule: show what you removed. When the runbook prompt cleans up your terminal history, it lists the typos and failed attempts it dropped, so you can confirm none of them was actually important. If you work with numbers or facts in your procedures, our guide to verifying AI output covers the checks worth adding before anything gets printed.

When Should the AI Interview You Instead?

When the process involves judgement, not just steps.

A voice note works well for tasks with a fixed order, like opening up the shop or running a backup. It works badly for tasks where you make decisions, like pricing a custom order, deciding which customer complaint to escalate or choosing a supplier. You don't think of those as steps, so you won't mention them when you talk.

The Interview Me to Capture a Process Only I Know prompt flips it round. The AI asks one question at a time and waits for your answer. It starts with what triggers the process, then works through it in order, asking about the decisions you make by instinct, the exceptions and the people you contact. When you type done, it writes the SOP and puts every judgement call into a separate section called Decision rules, with the examples you gave.

That section is the part your team will actually use. "If the order is under 20 pax and the venue is in the CBD, we don't charge delivery" is a rule someone can follow. "Use your judgement on delivery fees" isn't. The delegation prompt in the career category uses the same interview approach for a single task you want to hand over, and adds a list of decisions the other person can make alone.

One tip that works for both: answer with real examples from the last few weeks, not general principles. A specific example tells the next person far more than a rule of thumb.

How Do You Write SOPs for a Multilingual Team?

Write it simply in one language first, then translate step by step, then have a fluent colleague check it.

This matters a lot in Southeast Asia. The Ministry of Manpower's foreign workforce figures for June 2026 count 1,655,900 foreign workers in Singapore. That includes 1,243,600 on Work Permits, of whom 490,700 work in the construction, marine shipyard and process sectors and 323,800 are migrant domestic workers. Plenty of them read English as a second or third language, and some read it very little. A dense English SOP stuck on the wall of a central kitchen doesn't keep anyone safe.

The bilingual SOP prompt does three things in order. It shortens each step to one simple sentence before translating, because translating a long, complicated sentence just gives you a long, complicated sentence in another language. It places each English step directly above its translation, so supervisors and workers can point at the same line. And it suggests a simple icon for each step for people who read less.

It also marks the result as a draft. AI translation into Bahasa Indonesia, Tamil, Burmese or Bengali is good enough to start from, but safety words and machine names need a check by someone who speaks the language and knows the work. The tip that goes with it: ask a worker to read the translated step aloud to a colleague. If they rephrase it, use their words.

The two image prompts back this up. One makes a series of wordless step illustrations in a consistent style. The other designs a safety sign with a strong pictogram and an empty band for text in the languages your staff read. Both leave the words out on purpose, because image models still misspell text, and you'll want to add captions yourself in Canva or a slide tool.

How Do You Keep SOPs From Going Out of Date?

Make small updates often, and make the AI show you exactly what it changed.

Most SOPs don't fail because they were written badly. They fail because the business changed and the document didn't. You switch from paper forms to a Google Form, a supervisor leaves, the supplier changes the delivery day. Six months later the SOP describes a business that no longer exists, and staff learn to ignore all of it.

The Update an Outdated SOP Without Rewriting It prompt is built for that. You paste the current procedure and list what has changed. It edits only the affected steps, shows each change as Before and After, and flags other steps that probably depend on the change without touching them. It also adds a one-line change log at the end, so the next person knows what happened.

The instruction not to reword correct steps is deliberate. If you let an AI "improve" a whole SOP every time something changes, your team has to relearn the entire document, and real changes get lost among cosmetic ones. Small, visible edits keep trust in the procedure.

The audit prompt works the same way from the other direction. It compares your SOP with the clauses you're audited against and gives you a table of gaps, ranked by risk. It won't tell you you're compliant, only what to check, which is the honest answer an AI can give. If you'd like to turn the prompts you use most into your own reusable templates, our guide to reusable AI prompt templates for teams shows how.

Which Prompts Should You Run First?

Start with the one process that would cause the most trouble if the person who knows it got sick tomorrow.

For most owners, that's something only they do: pricing, payroll, the supplier you've known for ten years. Run the interview prompt on it this week, even if you only get halfway. Then record a voice note of one routine task, like opening or closing, and turn it into an SOP with the voice note prompt. Give that draft to your newest staff member and watch where they hesitate.

After that, the training and quiz prompts help you roll it out, and the announcement email tells everyone what changed. Software teams should run the runbook prompt after their next deploy, while the commands are still in the history. It takes ten minutes and saves a stressful hour the first time someone else has to do it.

What Else Do People Ask?

Can AI write an SOP without any input from me?

It can write a generic one, but it won't describe your process. Without your material it fills gaps with steps common in other businesses. Give it a voice note, a transcript, your notes or answers to its questions, tell it to use only that, and ask it to list missing steps as questions.

What is the difference between an SOP and a checklist?

An SOP explains how to do a task, including the purpose, what you need, the steps and how to check the result. A checklist is a short list you tick off while doing it. Many teams write the SOP once for training and keep a one-screen checklist where the work happens.

Is it safe to paste internal procedures into an AI tool?

Check first. Your AI plan's data settings, your company policy and laws such as Singapore's and Malaysia's PDPA affect what you can share. Remove passwords, keys, customer names and personal details before pasting, and use a business plan with data controls for sensitive processes.

Do these prompts work in ChatGPT, Claude and Gemini?

Yes. All twenty are plain text with fill-in variables and work in ChatGPT, Claude, Gemini and similar tools, including free plans. The two image prompts need a tool that generates images, and the interview prompts work best in a chat where you can answer one question at a time. If you are choosing a model for drafting SOPs and other long documents, WhichAIBest's best AI for writing comparison shows how the main assistants compare.

How often should you review an SOP?

Review it every six months, and straight after any change to tools, staff or suppliers that affects the task. Small, frequent updates keep a procedure trusted. Use a prompt that edits only affected steps and shows each change as before and after, so staff only relearn what changed.

Sources: Panopto, Workplace Knowledge and Productivity Report and its July 2018 press release, for time lost waiting on information. Microsoft, 2026 Work Trend Index Singapore release, for AI use and responsibility figures. Ministry of Manpower, Foreign workforce numbers, for Singapore's foreign workforce.