Policy vs procedure vs SOP
A policy states the rule or intent; a procedure describes the required sequence; an SOP is a standardized procedure for a repeatable task. See a worked QueryChart process and practical steps for applying it.
A policy states the rule or intent; a procedure describes the required sequence; an SOP is a standardized procedure for a repeatable task.
The short version
- Write the policy: State scope, rule, accountability and exception authority without burying it in task details.
- Map the procedure: Show trigger, decisions, handoffs, records and end state across roles.
- Specify the SOP: Give operators the exact steps, limits, safety checks and evidence for one repeatable activity.
Policy vs procedure vs SOP in practice
These labels matter because they answer different reader questions. A policy says what is required and who is accountable. A procedure says how work moves across roles. An SOP gives precise, repeatable instructions at the point of execution.
For one policy, link the supporting procedure and its task-level SOPs. Give each its own owner and review trigger, but coordinate change control so a revised policy cannot leave dependent instructions contradicting it.
See the policy review approval process workflow
Step through the decisions behind policy vs procedure vs sop.
Write the policy
A policy review starts from an event or calendar trigger and confirms ownership.
Map the procedure
The change-needed decision leads to consultation and legal or regulatory fit checks.
Specify the SOP
Approval of a policy revision should trigger review of dependent procedures and SOPs before publication is complete.
How it works
Write the policy
State scope, rule, accountability and exception authority without burying it in task details.
Map the procedure
Show trigger, decisions, handoffs, records and end state across roles.
Specify the SOP
Give operators the exact steps, limits, safety checks and evidence for one repeatable activity.
Mistakes to avoid
Missing the decision record
Keep the actor, decision and effective state alongside the output. These labels matter because they answer different reader questions. A policy says what is required and who is accountable. A procedure says how work moves across roles. An SOP gives precise, repeatable instructions at the point of execution.
Open the worked process
Use the linked policy review approval process template to adapt the workflow to your team.
Frequently asked questions
Can a procedure be an SOP?
Yes. SOP describes a procedure standardized enough for consistent repeatable execution.
Which document should state exceptions?
The policy defines authority; the procedure or SOP explains how to request and record an exception.
What changes first?
Usually the governing policy decision, followed by dependent procedures and SOPs before the effective date.