Policy vs Procedure: What's the Difference?

← Systems & processes glossary

Glossary

Policy vs Procedure: What's the Difference?

The short answer

A policy is the rule: what your business will and won't do and why. A procedure is the how: the steps people follow to carry the policy out. Policies change rarely. Procedures change whenever the way you work improves.

Policy, process and procedure side by side

PolicyProcessProcedure
AnswersWhat's the rule and why?What happens end to end?How do I do this task?
Refund exampleFull refund within 30 days of purchase.Request, check, approve, pay, follow up.Process a refund request, step by step.
ChangesRarely, with sign-offSometimesOften, as you improve
Owned byLeadershipDepartment headThe person who does the work

Why keeping them separate helps

  • You can improve the steps without reopening the rule. Change the software you refund through and only the procedure changes.
  • Sign-off goes where it matters. Policies often need legal or leadership approval and team acknowledgement. Procedures need to be accurate and easy to follow.
  • People know where to look. "Are we allowed to?" is a policy question. "How do I?" is a procedure question.

How to write each

A policy states its purpose, who it applies to, the rule itself, who owns it and when it is reviewed. Keep it short and plain. If it reads like a contract, nobody will read it.

A procedure is an SOP: a trigger, numbered steps written as actions and a definition of done. Link the procedure to the policy it carries out.

Common mistakes

  • Burying rules inside steps. "Step 4: only refund if under 30 days" hides a policy where nobody will find it to update it.
  • Policies nobody has acknowledged. A policy only protects you if the team has read it and agreed to it. Track who hasn't signed off, not who has viewed it.
  • Writing policies for problems you don't have. Start with the rules your team actually asks about.

In systemHUB, policies live in their own library with team sign-off, alongside your systems and training. See how a playbook, handbook and SOP fit together too.

Questions

Frequently asked questions

Do small businesses need written policies?

Yes. Start with only a few: the rules your team asks about most, the ones that protect you legally and the ones that affect customers, such as refunds, privacy and complaints. Add more as real questions come up.

Which comes first, the policy or the procedure?

Usually the policy, because the procedure carries it out. In practice many businesses document the procedure first because that's what the team does every day, then pull the rules out into a policy once they spot them.

Put your systems in one place

systemHUB is SOP software built around the SYSTEMology method. Document how your business runs, train your team and connect your AI to the real thing.

14-day free trial. No credit card required.