You document a workflow for a machine the same way you would train a new hire who takes nothing on faith: write every trigger, every step, every decision rule, and every exception in plain order, with no “it depends” left unexplained. A model cannot infer the judgment you never wrote down. SOPs come before AI because the SOP is what the AI reads.
Last updated: July 16, 2026
What does it mean to document a workflow for a machine?
It means writing the process down so completely that someone with zero context could run it without asking a single question. That someone is the machine, and the machine will never ask. A human reading a thin SOP fills the gaps with common sense. A model reading the same thin SOP fills the gaps with confident invention.
I spend most of my week inside real operations, and the shape of the problem is always the same. There is a person, usually the one who has been there longest, who is the process. They know which step to skip when the account is a renewal, which flag means stop and call the customer, which exception is fine and which one is a fire. None of it is on paper. It is a people business, and the knowledge lives in the people. That works right up until you ask a machine to do the job, because now you need every one of those silent judgments spelled out where the machine can read it.
Why do SOPs have to come before the AI?
Because the SOP is the raw material the AI runs on. Point a model at a documented workflow and it amplifies that workflow. Point it at a process that mostly lives in someone’s head and it amplifies your guesses. There is no version where the build supplies the documentation you skipped.
This is the sequence people get backwards, and it is expensive. MIT’s Project NANDA found that 95% of enterprise generative AI pilots delivered no measurable return on the P&L (MIT Project NANDA, via Fortune). When you go looking for why, you do not find a story about weak models. You find a story about the process underneath, the part nobody wrote down before they automated it. The whole argument sits in one line: AI only amplifies what it can read, which I unpack in full in AI only amplifies what it can read. The SOP is the thing it reads.
How is documenting for a machine different from writing a normal SOP?
A normal SOP is allowed to be a little lazy, because a human reader covers for it. A machine-runnable SOP has no such luck. Every place where a person would use judgment has to become a written rule, because the machine has no judgment to fall back on.
Take a line most SOPs actually contain: “review the file and follow up as appropriate.” A human knows what “as appropriate” means after a year on the job. A machine reads “as appropriate” and has nothing. So documenting for AI means hunting down every “as appropriate,” every “use your best judgment,” every “it depends,” and replacing it with an explicit rule. If the account is over this dollar amount, do that. If the last contact was more than this many days ago, do the other thing. The judgment does not disappear. It moves from the person’s head onto the page, where the machine can finally see it.
What does a machine-runnable SOP actually contain?
It contains six things, and a workflow is not ready until all six are on the page. Miss any one and the machine hits a wall it cannot climb, because the wall is exactly the thing you left in someone’s head.
| Element | What it answers | What breaks if it is missing |
|---|---|---|
| Trigger | What starts this workflow, precisely | The machine does not know when to act |
| Inputs | What information and records it needs to begin | It runs on partial data and produces partial nonsense |
| Steps in order | Exactly what happens, in what sequence | It skips, reorders, or invents steps |
| Decision rules | The explicit rule at every “it depends” fork | It guesses at your judgment and sounds sure |
| Exceptions | What the unusual cases are and how to handle them | The first oddball case sends it off a cliff |
| Definition of done | What finished and correct actually looks like | It never knows whether it succeeded |
None of this is exotic. It is the boring discipline of writing down what you actually do, in order, with the forks named. Simplicity is king, and a good machine-runnable SOP is the simplest possible honest description of a real process.
Where do most workflows fall apart when you try to write them down?
At the exact moment you try to capture what an experienced person does without thinking. You get four steps in, everything is smooth, and then somebody says “well, it depends,” and the room goes quiet because nobody has ever made that rule explicit. That silence is the whole point of the exercise.
That gap is not a detour. It is the destination. The undocumented “it depends” is precisely where an AI build would have failed, and writing the SOP is how you find it before you have paid to automate around it. The cost of leaving those gaps in people’s heads is not just AI risk, either. McKinsey found that employees spend an average of 9.3 hours a week just searching for and gathering information rather than doing the work (McKinsey Global Institute). That is a day a week lost to knowledge that was never written down where anyone, human or machine, could find it. Documentation pays off long before the AI shows up.
What if we don’t have time to document everything?
Then do not document everything. Document the one workflow you actually want to automate first, all the way through, and leave the rest for later. This is the Operational Foundations work, and it is deliberately narrow. You are not writing a company manual. You are writing the one process the machine is about to run.
The honest-no lives here too. If you sit down to document the target workflow and cannot finish it, that is not a scheduling problem you push to next quarter. That is the process telling you it is not ready to be automated yet, and no amount of clever tooling changes that answer. Write it down first, then automate the written-down version. That order is the difference between a build that works and a build that joins the 95%.
Your next step
If you are not sure whether your workflows are documented well enough to build on, start with the diagnostic. The AI Readiness Audit sits with your target workflow, tries to write it down completely, and shows you exactly where it breaks. It is $750 and it credits toward the build.
To see why documentation is the whole game, read AI only amplifies what it can read. To understand where the audit fits in the sequence, read What is an AI Readiness Audit, and why does it come before any AI build?. And if you want to sanity-check whether you are actually ready or just feeling the pressure, read AI readiness vs. AI hype. Rather talk it through first? Get in touch.