Standards, workflows, SOPs, and the three everyone forgets
Your business already produces all six kinds of documentation. The question is whether they are separated, so people can find and trust them, or piled into one folder where a rule from January sits next to a checklist from March and a diagram nobody has opened since. Six types, one job each, and a quick test that tells you which one you are writing before you write it.
Open the shared drive of almost any business under ten million and you find one folder called Processes. Inside it: rules, diagrams, checklists, blank forms, and last March's filled-in copies, all shoulder to shoulder. Nobody can find anything, so nobody looks, so the documentation is technically there and practically dead. The fix is not more documents. It is knowing that there are only six kinds, each with one job, and never letting one document try to do two jobs. The grouping that makes six easy to hold: one kind describes the business, five describe the work.
The six layers, one job each
Blueprints : the shape
The business drawn as structure, not motion: the org chart, the value stream map, the business model on a page. Lines mean this sits under that, never then this happens.
The job: Diagnose and design. A blueprint comes as a pair: the as-is, how the business is actually shaped today, and the to-be, the target shape. The gap between the two pictures is literally your build plan.
An as-is is a dated snapshot, redrawn when reality changes. A to-be is a plan, retired when reached or replaced. No software retires it for you; a person decides the target has been hit.
The test that it is a blueprint: it shows what sits where, not what happens next. One caution: a blueprint shows seats and reporting lines. The moment it starts carrying how well someone fills a seat, it has crossed into private people material and no longer belongs on a shelf anyone can open.
Standards : the rules
A call that was made and is still in force, written as one sentence plus who set it and when. Product titles follow this format. Refunds above this amount need an owner sign-off. That kind of thing.
The job: Settle arguments before they happen. When two people would do a thing differently, the standard picks the winner so nobody re-litigates it in a meeting that costs six salaries an hour.
A standard is never edited. It is superseded by a newer call, so the history of what you used to believe stays visible. And it binds the company, a department or a process, never one person. A rule about one person is a task or a note, not a standard.
The test that it is a standard: it fits in one sentence, and you can name who decided it and when. If you cannot, it is not a rule yet, it is a habit.
Workflows : the map
The whole process drawn visually, start to finish: every step, every handoff between people. Boxes and arrows, one verb per box.
The job: Show how work flows across people. A workflow answers what happens next and who does it. It never answers how exactly, because the moment it tries, the diagram becomes unreadable.
Redrawn only when the flow itself changes: a step added, a handoff moved. A manager reads a workflow. The person doing step four rarely needs to.
The test that it is a workflow: it crosses more than one person's desk. If one person does the whole thing in one sitting, you are looking at an SOP wearing a diagram costume.
SOPs : the how-to
The detailed instructions for one step of a workflow. One workflow step, one SOP. Purpose, trigger, a named owner, numbered steps that start with verbs, and a definition of done.
The job: Make one task runnable by anyone. The bar is simple: someone who has never done the job can do it from this document alone. This is where delegation actually happens, or does not.
Revised by its named owner whenever the task changes. An SOP with no owner is a photograph of how the job used to be done.
The test that it is an SOP: it needs numbered steps. If it fits in one sentence, it was a standard. If it spans three people, it was a workflow.
Templates : the blank form
A fill-in-the-blanks document an SOP tells you to grab. The SOP says copy the weekly log template and fill it in. The template is the thing you copy.
The job: Make output consistent without making people think about format. The structure does the remembering: if the form has a field for it, it gets captured, and if it does not, it quietly never does.
One maintained copy, updated when you learn the form is missing a field. Improving the template is one of the highest-leverage edits in a business, because every future copy inherits the fix.
The test that it is a template: someone copies it before using it. If people type over the original, you do not have a template, you have a fire waiting for a match.
Records : the filled-in copy
A completed template: this week's log, this month's report, Tuesday's meeting summary. The paper trail the work leaves behind.
The job: Proof and memory. Evidence the process actually ran, and the raw material for every review, renewal conversation, and end-of-year argument about what changed and why.
Records accumulate and are never edited after the fact. You maintain the other four types. Records you just keep.
The test that it is a record: it is dated and it is done. Editing last month's numbers to look better is not documentation, it is fiction.
Where the lines blur
Four pairs cause nearly all the confusion. Each one has a clean cut.
Blueprint vs standard
A standard is one rule; a blueprint is the picture many rules add up to. If it fits in a sentence it is a standard; if you have to draw it, it is a blueprint. When the drawing and a written call disagree, the call wins and the drawing gets redrawn. Adopting a to-be is itself a standard, one dated sentence pointing at the picture.
Blueprint vs workflow
What the lines mean. Arrows that mean then this happens are a workflow. Lines that mean this sits under that are a blueprint. An org chart tells you nothing about what happens next; a workflow tells you nothing about who reports to whom.
Standard vs SOP
A standard says what the rule is. An SOP says how to comply, step by step. One SOP can cite five standards. The cut: one sentence means standard, numbered steps means SOP.
Workflow vs SOP
Zoom level. The workflow is the whole journey across people. The SOP is one stop on that journey in full detail. If it crosses desks, map it. If one person finishes it in one sitting, write it up.
Template vs record
The same document, before and after. Blank is the template: one copy, maintained. Filled is a record: many copies, accumulated. Never edit a filled copy back into the blank one.
Standard vs record
We decided X on Tuesday, sitting in meeting notes, is a record. Pulled out into X is now the rule, with who and when, it becomes a standard. The note proves it happened. The standard makes it binding.
The workflow and SOP pair deserves its own page, because it is where most process documentation dies. That one is here: Workflow or SOP: where the detail belongs.
The five-question test
Before you write or file anything, run down this list in order and stop at the first yes.
- 01Is it a picture of how the business is shaped, or should be shaped, rather than how work flows or gets done? Blueprint.
- 02Is it a rule in one sentence that settles a recurring argument? Standard.
- 03Does it show multiple people, steps and handoffs? Workflow.
- 04Is it step-by-step instructions one person follows to finish one task? SOP.
- 05Is it a blank thing someone copies and fills in? Template.
- 06Is it a filled-in copy from a specific day, week or client? Record.
Still stuck? Ask what happens when it changes. The business gets reshaped or the target gets reached (blueprint). Rules get superseded (standard). Maps get redrawn (workflow). Instructions get revised by an owner (SOP). Forms get a new field (template). Filled copies never change at all (record).
What stays out of the stack
One thing is left out on purpose: who owns what. Role descriptions, scorecards, and how you grade your team are not a seventh document type. The blueprint shows which seats exist and who reports to whom, but never how well anyone fills a seat. Roles describe the humans doing the work, and mixing the two is how a process folder turns into an HR file nobody should be reading.
If you want the grading half of that story, it lives in Player Levels: how to grade your team honestly.
Installing this stack is most of what I do
The documents are the visible half. Getting a team to actually run on standards, workflows and SOPs, and keeping them current after I leave, is the real work. The strategy call is free and you keep the diagnosis either way.