Comparison
An Imprint vs an SOP
Every operator has a folder of procedures and a private awareness that the procedures are not the thing. This page is about what is missing from them, where it went, and why the gap is findable in about five minutes.
An SOP records a sequence of steps for a process, written for the case that runs as expected. It is documentation of the path.
A captured ruling records a decision, with the reason attached, made on a specific case that did not have an obvious answer. It is documentation of the call.
The work is carried by the part you could not.
You already ran the experiment
Hand your best SOP to a capable person. Watch what comes back.
It follows the steps. It is not your work.
Everybody who has ever delegated has run this without meaning to, and the result is worth sitting with for a moment, because it settles the question by itself. If the document held the value, transferring the document would transfer the value. It does not. So whatever produced your outcome was not in there.
That absent thing is not mystical and it is not talent. It is a large pile of small rulings, applied at every point the procedure left open, most of which you made without registering them as decisions at all.
Find the gap in your own folder, in five minutes
Open your procedures and search them for two phrases.
- "Use your judgment."
- "Escalate if needed."
Every hit marks a coordinate where the transfer failed.
Those sentences are not instructions. They are the author reaching a point where the knowledge would not go into words, and writing a placeholder instead. The rest of the document is the part that was sayable. The placeholder is where the value went and did not follow.
Look at what sits around each hit. It is almost always the highest-stakes moment in the process, because that is where somebody wrote the sentence rather than a rule. Which means your procedures are most detailed where the stakes are lowest and go silent exactly where they are highest.
Those coordinates are the shortest list of what to capture first, and you did not have to think of it. The documents identify themselves.
The reason stayed with the author
An SOP records what to do. It very rarely records why that step is there.
The author knew. Step four exists because of something that went wrong once, on a specific job, in a way that was expensive. That context lived in their head and the document got the instruction without it.
Here is the consequence, and it is worse than it first sounds. Without the reason, nobody downstream can tell a load-bearing step from an incidental one. They all look identical on the page. Numbered, imperative, equally weighted.
So procedures decay in two opposite directions at the same time.
They get obeyed literally, long after the failure the step was guarding against stopped being possible, because nobody knows they are allowed to drop it. Cost shows up as friction that no one can justify or remove.
And they get tidied. Somebody streamlines the document, cuts what looks redundant, and occasionally removes the single step the whole procedure existed for. Nothing bad happens for months. Then it does, and the connection back to the edit is gone.
A captured ruling carries its reason as part of the record, which is what makes it survivable. When conditions change you can check whether the reason still holds, rather than guessing at the intent of a numbered line.
Documentation happens after. Capture happens during.
Look at when an SOP actually gets written.
After the work. Usually under time pressure, often by the person who least wants to be doing it, describing a process they have already stopped thinking about consciously.
What that produces is the tidy version. The path as it should have gone. The four moments where you doubled back, changed your mind, or overrode the obvious step do not appear, because by the time you are writing, they have compressed into "and then you do this."
Capture does not have a separate writing stage. The ruling is recorded at the moment it is made, on the real case, before it has been smoothed into a narrative. That is the difference between a record of the work and a record of the memory of the work.
Unit for unit
| SOP entry | Captured ruling | |
|---|---|---|
| Records | What to do | What was decided, and why |
| Written | After the work, from memory | During the work, on the live case |
| Covers | The expected case | The case that had no obvious answer |
| Reason attached | Rarely. It stayed with the author | Always. The reason is the asset |
| When conditions change | No way to tell what is still load-bearing | Check whether the reason still holds |
| Ambiguity handled by | "Use your judgment" | A ruling that says which way and why |
| Transfers to another person | The steps do. The results do not | The standard travels with the record |
When an SOP is the right and only answer
Where variance is the enemy, documentation wins and judgment is a liability.
Safety procedures. Regulatory and compliance steps. Financial controls. Anything with an audit requirement. Onboarding into a defined, stable process. Work where two people doing it differently is itself the failure.
In those places you do not want anybody's judgment applied, including yours. You want the step followed. Capturing rulings there would be solving a problem that is not present.
The two fit together rather than competing. The procedure holds the path, and the captured rulings cover the branch points inside it, starting with every place the document currently says to use your judgment.
Frequently asked
What is the difference between an Imprint and an SOP?
An SOP records the steps of a process for the case that goes as expected. An Imprint records rulings, with the reason attached, for the cases that do not. They are complementary rather than competing. The SOP holds the path. The Imprint holds what to do when the path does not apply, which is where an experienced operator's value concentrates.
Why don't my SOPs produce my results when someone else follows them?
Because the document holds the steps and you held the reasons. Two people can follow the same procedure exactly and produce different work, and the difference is not in the document, or copying it would transfer the outcome. What is missing is the judgment applied at every point the procedure left open, and none of that was written down because at the time it did not feel like a decision.
Can't I just write better SOPs with more detail?
More detail extends the range of anticipated cases, which helps, and it does not remove the limit. Anticipating every case in advance is the same problem as not needing judgment in the first place. Past a certain length SOPs also stop being read, so precision bought with volume tends to be paid for with compliance.
How do SOPs go stale?
In two directions, because the reason is missing. Steps get followed literally long after the failure that prompted them stopped being possible. And steps get removed during a clean-up by someone who could not tell which ones were load-bearing, occasionally the single step the whole procedure existed for. Both failures come from the same absence, which is the why never being recorded next to the what.
Does capturing judgment replace documentation?
No. Documentation is the correct tool for defined, repeatable, compliance-bound work, and there is no substitute for it. Capture handles the branch points inside it. In practice the two point at each other: the SOP describes the path, and the captured rulings cover the places where the SOP says to use your judgment.
Where this sits
Read the category definition at What is Imprinted AI. The capture format described here, where a ruling carries its reason and its origin, is public at Imprint.
Related comparisons
- Imprinted AI vs a Custom GPT. Describing yourself rather than describing the work.
- Imprinted AI vs RAG. Indexing the documents and expecting the judgment to come with them.
- Imprinted AI vs an AI agent. The gap once the process runs with no person in it.
The full argument
This page is one distinction pulled out of a longer case. The whole thing runs about 23,000 words, it is free, and there is no email gate on it.
Read The A.I. Business Manifesto
Nothing on this page is for sale. If the distinction is useful, the useful thing to do with it is pass it on.
Last updated: 28 July 2026