In business an SOP is the middle layer of three, and almost every argument about what should be in one comes from somebody collapsing the layers. Above it is policy: what the organisation requires and why. Below it is the work itself, which changes daily and is not worth writing down. The SOP is the stable description of how a role does one job. This page sets out the three layers, what belongs in each, and what happens when they are merged.
Policy is the requirement, and it is short
All expenses over $500 need prior approval. That is a policy: a rule the organisation has decided, usually signed off by somebody who owns the risk, and typically unchanged for years. It says nothing about which form to use or who to email, because those change and the rule does not.
The procedure is how a role satisfies it
Raise the request in the system, attach the quote, send it to your manager, wait for the approval mail, then order. That is an SOP: specific, role-bound, and revised whenever the system or the approver changes. It is longer than the policy and shorter than most people write, because everything that is obvious to a trained person can be left out.
The work is not a document
Which supplier you happen to use this quarter, who is covering for whom this week, the workaround for the current outage: none of that belongs in a procedure, because writing it down guarantees the document is wrong within a month. This is the single most common reason registers rot.
What collapsing the layers costs
Merge the three and you get four enormous documents that mix rules with keystrokes, and nobody reads them. Split them properly and a small organisation lands near the worked example on this site: 12 processes with 4 procedures each, which is 48 documents, each short enough that reviewing one is a 2.5-hour job rather than a project.
Questions people ask about sop meaning in business
What is the difference between a policy and an SOP?
A policy is the requirement and changes rarely. An SOP is how a role satisfies it and changes whenever the system, supplier or team changes.
How long should a business SOP be?
Short enough that a trained person can skim it. Everything obvious to somebody who does the job already can be left out.
Should an SOP name individuals?
Name roles, not people. A procedure naming somebody who left is the most common thing in a neglected register.