A standard operating procedure, or SOP, is a controlled instruction describing how to perform a repeatable task or process. It supports consistent execution, training, control and audit evidence.
What should an SOP include?
- Purpose and scope
- Roles and prerequisites
- Step-by-step instructions
- Decision points and exceptions
- Controls and required evidence
- Escalation and related records
SOP vs. policy
A policy states what is required and why. An SOP explains how the work is performed. A process map shows flow and handoffs but may not provide enough detail for execution.
What makes an SOP usable?
Write for the actual operator, use current system names and explain judgment points. Include links to controlled forms and examples without relying only on screenshots.
How should it be governed?
Assign an owner, version, approver, effective date and review cycle. Remove obsolete copies from active use and record material changes.
How should effectiveness be tested?
Observe a trained user following the procedure, review errors and confirm that required evidence is produced. A signed approval does not prove the instructions work.
