What an SOP is actually for
An SOP exists so that the quality of an outcome does not depend on who performed the task. It is a transfer mechanism for judgment that would otherwise stay in one person's head.
That framing matters: an SOP is not a control document. It is a teaching document that happens to be reusable.
What belongs in one
- The trigger — when this procedure applies.
- The outcome — what the finished result looks like.
- The steps in order, with the owner of each.
- The known failure modes and what to do about them.
- Who to ask when the situation falls outside the procedure.
Why most SOPs go unread
Three common causes: they are too long, they live somewhere separate from the work, and they were written once and never corrected.
The practical fix is to keep them short, attach them to the point in the workflow where they apply, and update them the first time reality disagrees with them.