How Long Should an SOP Be?
By Lisa González, Certified EOS Implementer® and co-author of Process! (The EOS Mastery Series). Published August 5, 2026.
One to three pages for most processes. Document the 20 percent of steps that drive 80 percent of the result, put the major steps as headers with a few bullets each, and stop. If an SOP runs past five pages, that is usually a sign to split it or simplify it, not proof of rigor.
I'm Lisa González, co-author of Process! How Discipline and Consistency Will Set You and Your Business Free, the official EOS® book on process, and a Certified EOS Implementer®. I have watched hundreds of leadership teams write procedures nobody used. The length was almost always the reason. A 40-page SOP is not thoroughness. It is fear, written down.
The rule: one to three pages
A usable SOP fits on one to three pages. That is enough room for the major steps, a short note on why each one matters, and the handful of details that prevent expensive mistakes. It is short enough that a person can open it mid-task and actually find the step they need.
Length is a usability decision, not a completeness contest. The goal is a document people reach for, not a manual they avoid.
Why the 20/80 rule sets the length
Every process has a small number of steps that produce most of the outcome. Document those. The 20/80 rule says to capture the 20 percent of steps that drive 80 percent of the results, and to leave the rare edge cases out of the main flow.
This is what keeps an SOP to a few pages. You are not describing every possible variation. You are describing the path that works almost every time, clearly enough that a trained person can follow it.
What a right-sized SOP contains
A tight SOP has a clear title, the trigger that starts the process, the major steps as headers, a few bullets under each step, and the owner's name. It names the tools used and flags the one or two steps where an error is costly. That is the whole document.
It does not contain a glossary, a history of the process, or a paragraph of policy language before the first step. Those push the length up and the readership down.
When a longer document is the right call
A few situations justify more detail. A step where an error is dangerous, expensive, or hard to reverse deserves a precise checklist. A regulated task may require specific recorded language. A complex piece of equipment may need a dedicated reference.
Handle these by linking out, not by bloating the main SOP. Keep the core process to a few pages and attach the detailed checklist to the one step that needs it. The reader gets a short map and the depth only where it matters.
The real test
The real test is whether the right person in the right seat can follow it. Hand the SOP to the person who owns that seat and ask them to run the process straight from the document. If they can, the length is right. If they stall or lose the thread, it is too long, too vague, or both. Trim it until it works.
If you run on EOS, this is the discipline inside the Process Component, and the tool is the 3-Step Process Documenter. For the deeper question of why finished SOPs still get ignored, see Why Employees Don't Follow SOPs.
Frequently asked questions
How long should an SOP be?
One to three pages for most processes. Document the essential steps, not every edge case. If a document runs past five pages, split it or simplify it.
How many pages is too long for an SOP?
Past five pages, most people stop using the document mid-task. Long procedures usually contain edge cases and background that belong in a linked reference, not the main flow.
What is the 20/80 rule for SOPs?
Document the 20 percent of steps that produce 80 percent of the results. Capture the path that works almost every time and leave rare exceptions out of the core document.
Should an SOP include every possible exception?
No. Exceptions belong in a linked checklist attached to the specific step that needs them. Loading every exception into the main SOP is the fastest way to make it unusable.
Who should write the SOP?
The person who does the work should lead the documentation, with leadership review and approval. Frontline authorship produces an accurate document and built-in buy-in.
Have SOPs nobody uses? That gap is exactly what I help leadership teams close. Book a discovery call.
