'Do we need a policy for that, or an SOP?'
If you've ever been in a room where that question was asked and watched it spiral into a 20 minute debate, you're not alone. The terms get used interchangeably. They're not the same thing. And for businesses trying to scale consistently, getting it right matters a great deal.
What is a standard operating procedure (SOP)?
A standard operating procedure (SOP) is a set of step-by-step instructions for carrying out a specific task or process, so that it is done the same way every time.
The U.S. Environmental Protection Agency's Guidance for Preparing Standard Operating Procedures (EPA QA/G-6) defines it this way: "A Standard Operating Procedure (SOP) is a set of written instructions that document a routine or repetitive activity followed by an organization."
Policies set the standard and explain why it matters
A policy is a statement of intent. It defines your organisation's rules, principles and standards, setting the foundation for consistent operations and ensuring compliance with regulations and brand standards across every location.
Think of a policy as the rule. It answers the question: what are we committed to?
Examples:
- A food safety policy stating that all food handling staff must complete certified training before working unsupervised
- A workplace health and safety policy committing to a drug and alcohol-free environment
- A customer complaints policy setting an expected response timeframe of 48 hours
Policies are typically high level. They don't tell anyone how to do something. They set the expectation that something must be done, and to what standard.
What is policy management?
Policy management is the process of creating, approving, publishing, communicating, reviewing and retiring your organisation's policies. It keeps every policy current, owned by a named person and easy for staff to find.
Good policy management means:
- One central, version-controlled home for every policy
- A clear owner and review date for each policy
- An approval workflow, so only signed-off versions are published
- A way to confirm staff have read and understood each policy (see policy attestation below)
- An audit trail showing who changed what and when
Without it, outdated versions circulate, sites follow different rules and proving compliance becomes a scramble. For multi-site operators, a central policy and contract management solution keeps every location working from the same version.
What is an information security policy?
An information security policy is a documented set of rules for how your organisation protects its information assets, including customer data, financial records and intellectual property. It sets out who can access what, how data must be handled and what staff must do if something goes wrong. Its aim is to protect the confidentiality, integrity and availability of information.
It is a good example of why you need both documents. The policy states the commitment, for example that access to customer data is restricted to authorised staff. SOPs then show how each site delivers it: joiner and leaver access checks, password resets and reporting a suspected data breach.
Many organisations align their information security policy with ISO/IEC 27001, which expects documented information security policies that are approved by management, published and communicated to relevant staff and reviewed at planned intervals.
What is policy attestation?
Policy attestation is the formal process of staff confirming that they have read, understood and agree to follow a policy. Each confirmation is recorded with the person's name, the policy version and the date.
It matters because publishing a policy doesn't prove anyone has read it. Attestation gives you auditable evidence that your people have been told what is expected, which regulators and auditors often ask to see. It is typically requested at onboarding, whenever a policy is updated and on a regular cycle such as annually.
Across 10, 30 or 100 locations, tracking this manually is hard. A policy management platform can send attestation requests, chase outstanding responses and report on completion by site.
SOPs show every employee how to meet that standard
Where a policy states the expectation, the SOP explains how to meet it.
Think of an SOP as the instruction manual. It answers the question: how do we do this, every time?
SOPs are task-specific and designed to be followed consistently by anyone in the role, regardless of experience or location. They ensure consistency in execution and serve as practical instructions for employees at every site.
Why a policy without an SOP leaves gaps
A policy without an SOP is just good intentions. You've stated that something matters. You haven't given anyone the tools to deliver it.
An SOP without a supporting policy is a floating procedure. It tells people what to do, but without the organisational context for why it matters or what standard it's trying to uphold.
Take workplace safety as an example. A WHS policy commits your business to providing a safe working environment for all staff. The accompanying SOPs cover how that commitment is actually executed: incident reporting steps, equipment checks, emergency procedures, induction signoffs. One without the other leaves gaps.
Why 10, 30 or 100 locations make the difference more costly
For businesses operating across a single location, the line between policy and SOP can sometimes be blurry without causing significant harm. The owner knows what they meant. The team asks when they're unsure.
That breaks down fast when you're running 10, 30 or 100 locations.
When your business spans multiple sites, every location is making daily decisions about how to interpret your standards. Without clear policies, those interpretations vary. Without SOPs, execution varies. The cumulative effect is a business that looks and operates differently depending on which location a customer walks into.
Yo-Chi know this better than most. With more than 60 locations across Australia and internationally, getting every site operating to the same standard is central to the brand. Jake Patane, General Manager of Capability and Development, describes what the shift to a centralised platform made possible: "Being able to power down those old ways of working and then power up something like [Ideagen Procedure Management] allowed us to really just centralise all the information, set the standard from the start and then make sure that everyone knows exactly where to go when they need to find that information."
That's what a functioning SOPs and policies framework looks like in practice: one place, one standard, accessible to everyone. Read the full Yo-Chi case study.
Consistency is a franchise brand promise. It's also a legal and compliance obligation in many industries. Policies and SOPs are what make consistency repeatable and provable.
How the policy sets the bar and the SOP gets every site over it
Policies and SOPs aren't interchangeable. The policy sets the bar. The SOP shows people how to reach it. Together, they give every location the same foundation to operate from, regardless of who's on shift or which location they're in. To manage policies, attestations and review cycles in one place, explore Ideagen's policy and contract management solution.