How to write an SOP or work instruction that a person and an AI employee can follow
If you're looking up how to write an SOP, you usually have a specific reason: someone new is starting, a colleague is going on parental leave, or a procedure is supposed to go to an AI employee. In all three cases, someone else is supposed to do something that until now only one person could. A good SOP makes exactly that possible. A poor one only reminds you of the order of things and assumes the reader already knows the rest. In this article, we show how an SOP is structured, how to check it with one simple question, and how to write it so that it works equally well for a person and for an AI employee. The outline is included in the article as a text template.
SOP, work instruction, process profile: what the difference is
Three terms come up often when it comes to writing down procedures.
SOP stands for standard operating procedure. The term comes from industry. An SOP is a set of instructions someone follows to carry out a specific piece of work. It's concrete: these steps, in this order, with these exceptions.
Work instruction essentially means the same thing. Anyone searching for how to write an SOP, or for an SOP template, usually means exactly that: a work instruction.
Process profile is our word for the frame of a process: trigger, start, work per variant, end and report, plus the escalation path.
The process profile sets where a process starts and ends and what exists at the end. The SOP is more detailed. It describes how the work in between is done, step by step.
So you don't need both for every process. With us, the process profile comes first. An SOP is added when the steps themselves have so many fine details that the process profile can't carry them. How to write the process profile is covered in How to document business processes: the template for handing a process to an AI employee.
How an SOP is structured
An SOP that someone else can carry out without asking questions covers seven parts. Four of them, the trigger, the variants, the handoff and the escalation path, are usually already in the process profile.
Purpose
One or two sentences: why does this work exist, and what's different at the end? The purpose helps whoever carries out the work to judge correctly, in an unclear case, whether they may continue or should ask.
An example: "File incoming invoices so that bookkeeping finds all of them at the end of the month." A rule already follows from this sentence: an invoice that can't be matched goes to a person instead of ending up in some random folder. Without a purpose, whoever does the work would have to guess that.
Trigger
When is the work done? At a fixed time, when something comes in, or when someone asks for it? And what's on the table then? "The documents" isn't enough. "All new PDF files in the incoming folder since the last run" is enough.
Steps
Numbered, one action per step, the verb first. At every point where the path splits, a question with yes or no and the path for both answers. How to write steps so that they can be carried out is covered in detail in Writing a process flow description: trigger, steps, variants and handoffs before someone else takes over.
Variants
Every case in which something is done differently gets its own line: how you recognize it and what's different then. A different name or a different amount is not a variant. A different sender, a different layout or a different place to file is one.
Hard limits
What must not happen under any circumstances, no matter what the document says? For example: delete nothing, send nothing outside the business, make no payments, calculate no deadlines.
On top of that, we apply a house rule: we keep a human involved when decisions are about people, about money or about anything with legal consequences. If a procedure contains a step like that, it gets an approval point, where a person explicitly says yes every single time.
Handoff
Who gets the result, in what state, and how do they find out about it? And what do you as the owner get at the end? With us, that's a report after every run: what's done, what's still open, where there was an exception.
Escalation path
What does whoever carries out the work do when a case doesn't fit? Whom do they turn to, who stands in, and what happens to the case in the meantime? With us, the answer is: the case goes to a person on your team, waits until then and, after the feedback session, is trained in as a new rule.
Template: an SOP outline
The trigger, the variants, the handoff and the escalation path are already in the process profile. The SOP refers to it and adds what only it has: the purpose, the detailed steps and the limits for exactly this piece of work. As a text template, this short form is enough:
- SOP: a name with a verb.
- Belongs to process: the name from the process map; see the process profile there.
- Responsible: a person. As of: a date.
- Purpose: one or two sentences.
- Steps: numbered, one result per step. For a question: yes, then continue with which step; no, then continue with which step; unclear, then escalation path.
- Hard limits: what must not happen, and the steps with an approval point.
The fill-in version of the process profile with all its fields is in the article on the process profile linked above.
The "Responsible" line matters. An SOP without a responsible person goes out of date quickly, because nobody feels it's their job to update it after a change.
The test: can someone who can't ask you carry it out?
An SOP is finished when it passes this test. Give it to someone who doesn't know the work. Before they do anything, have them explain: "What would you do now?" Go through the SOP step by step as you do.
Every question they ask is a gap. Typical gaps are:
- Words only you understand. "The usual folder", "like last time".
- A missing end. How do they notice that they're finished?
- A case without a path. What happens if the document doesn't fit any of the variants?
- A limit that only exists in your head. "Nobody would do that" is not a limit. If something must not happen, it's written in.
In an SOP for an AI employee, the same test keeps running in daily work. With us, the AI employee doesn't guess at a case it can't match with certainty; it sends the case to a person through the escalation path. After the feedback session, the answer goes into the SOP as a new rule. So every escalation email points you to a gap the test missed.
Writing for a person and an AI employee at once
An SOP that both can carry out doesn't need a second version. It's the same work instruction, a little stricter in three places.
Limits stated explicitly. A colleague often notices when something is odd. With us, the limit for an AI employee is written down in black and white.
Uncertainty as a path of its own. Every unclear case has a set place to go: a person on your team, through the escalation path.
Content is not an instruction. Whatever is written in a document or an email is content for the AI employee. If something in it sounds like an instruction to the AI employee, that's a case for the escalation path.
For the person on your team, this has a side effect: the SOP gets clearer. Once you've written something in a way that an AI employee can work with too, you often write more precisely afterwards.
What this looks like for us
With us, the SOP for an AI employee comes about during training. Training has four steps: watching how the team does it; sitting next to the AI employee and demonstrating each variant once; noting and asking through the escalation path and the feedback session; and signing off after four clean runs, then monitoring side by side for a while, then running on its own with a completion email.
The AI employee writes down the exact steps itself while someone demonstrates each variant once. The process profile sets the frame, the demonstration fills it in.
At a tax advisory firm, this is exactly how it went for filing tax assessment notices. It started with watching the office team: Kevin saw which types of assessment come in and how each one gets filed. Then came the demonstration, one type of assessment at a time, with someone sitting next to it. There are many variants there: the assessment notice process distinguishes around 45 rules, because there are many types of assessment, letters from the city with different layouts, different types of tax and types of letter.
At this firm, it took 2 weeks from the first round of watching to sign-off. That's what happened in this one case, not a time promise for your business.
Anything the AI employee can't match with certainty goes to the office team by email, and the AI employee is trained on it afterwards. That way, its SOP gets a little longer with every unclear case. Both of the firm's processes, the digital notices and the notices that arrive on paper, are at Autonomy Level 2, Autopilot (as of September 2026).
What happens at the first level, while your team checks every run, is described in Autonomy Level 1, Assisted: when your team checks every run.
Runs without me
Every two weeks, one process that runs without the owner: what came in, what the AI did, where a person decided. Two minutes to read.
Worksheet
Process Potential Check
With five questions and a first process list to fill in, you find the process that could run on its own first. Comes as a PDF by email once you confirm your sign-up.
Strategy session
In a 20-minute strategy session, you tell us where things get stuck. We'll tell you honestly whether an AI employee is a good fit for you.
Book a strategy sessionFrequently asked questions
How long should an SOP be?
As short as possible and long enough to pass the test. The edges, the limits and the escalation path have to be precise. For the steps, one line per step is often enough, as long as the variants are listed separately.
What's the difference between an SOP and a process profile?
The process profile, our word for a process description, shows the frame: where the process starts and ends, who is involved, what exists at the end. The SOP is more detailed and describes how the work is done, step by step.
Can I use an SOP from quality management for an AI employee?
As a basis, yes. Check it with the test above, and pay particular attention to the escalation path: does it say where an unclear case goes? If not, add it before an AI employee works with it.
Who writes the SOP?
The person who does the work today, together with you. They know the cases, you ask the questions. With an AI employee, the demonstration is added: it writes the steps down as you go, and the person reads them through.
How do I keep an SOP up to date?
Tie maintaining it to an event that happens anyway. With us, that's the escalation path: every unclear case lands with a person, and after the feedback session, the new variant is added as a rule. On top of that, every SOP carries a responsible person and a date. That way, you see who's in charge and how old the current version is.
The step before
If you're right at the beginning and only just thinking about how AI gets into your business at all, Kevin has a place to start: Bringing AI to a Small Business. This article was about the step at which a whole procedure is written down so that someone else can take it over.
Your next step
An SOP that passes the test makes a procedure independent of the one person who could do it until now. On a call, we look at which work in your business only one person can do today, and whether it should be the first to get an SOP.