The real reason your SOPs and policies aren't being followed

Most businesses have SOPs and policies. Most businesses also have SOPs and policies that no one reads, no one follows and no one updates until something goes wrong. 

If you manage a franchise network, a multi-site hospitality business or any operation running across multiple locations, you already know this problem. You've invested time writing the procedures and the policies. You've shared them with the team. And somehow, every location still does things slightly differently. 

The issue usually isn't the content. It's how your SOPs and policies were written, where they live and whether they were ever built to be followed in the first place. 

Here's how to get it right. 

Start with the why, not the what

Most SOPs open with a wall of procedure steps, and most policies open with dense regulatory language. Before your frontline team has any context, they're already three steps into a process they don't understand the purpose of. 

A one or two sentence explanation of why this procedure or policy exists changes everything. 'We follow this process to ensure every customer receives the same experience, regardless of which location they visit.’ That framing makes the steps that follow feel purposeful rather than mandatory. 

People follow processes they understand. They skip the ones that feel arbitrary. 

Write for the person doing the task, not the person approving it

This is where most SOPs and policies fall apart. They're written by managers, reviewed by compliance teams and approved by executives. The person actually doing the job is an afterthought. 

Before you write, answer these questions: 

• Who is reading this? 
• What do they already know? 
• What tools or equipment are they using? 
• What environment are they working in? 

A customer-facing onboarding SOP and a back-of-house safety procedure should read completely differently. The same applies to your policies. Use plain language. Short sentences. Active voice. If a new team member couldn't pick it up and act on it in their first week, it needs a rewrite. 

Be specific about inputs and outputs

Vague SOPs and policies produce vague results. 'Clean the equipment' is not an SOP step. 'Clean the equipment using the approved solution, following the manufacturer's guidance, and record the time and staff member in the log' is. 

Every step in your SOP should be specific enough that two different people, in two different locations, would complete it the same way. Policies should be equally clear about what the expected standard is and who is accountable for upholding it. 

Define what good looks like. Include tolerances, time limits, quantities or quality benchmarks where relevant. If there's a photo or diagram that would help, include it. 

There must be one source of truth

This is where a lot of multi-site businesses come unstuck. SOPs get passed between regions, added to and adapted until nobody is quite sure which version is current. Policies sit in a shared drive that half the team doesn't know exists. 

Yo-Chi, the Australian premium frozen yogurt and acai brand with more than 60 locations, experienced this firsthand as they scaled. As Jake Patane, General Manager of Capability and Development, puts it: "We realised we needed to really make sure that we have one source of truth for all of our SOPs, our resources and content for every single region." 

That clarity is the foundation everything else is built on. Read the full Yo-Chi case study here. 

Keep it short enough to be useful

If your SOP is 12 pages long, it won't be read at the point of need. It will be filed away and forgotten. The same goes for a policy document that takes 10 minutes to get to the actual expectation. 

Break complex processes into smaller, focused documents. Each SOP should cover a single task or process. Policies should be concise statements of commitment and expectation, not exhaustive manuals. If someone needs to reference either document mid-task, it should be scannable in under two minutes. 

Short doesn't mean incomplete. It means everything that's in there earns its place. 

Version control is not optional

An outdated SOP or policy is often worse than none at all. It creates false confidence and inconsistent practice. 

Every document needs a version number, an owner and a review date. When something changes, every location needs to receive the update. Old versions need to be retired so teams aren't working from conflicting documents. 

For businesses running across multiple sites, this is where document management infrastructure matters. Shared drives and email attachments don't cut it at scale. 

Make it accessible where the work actually happens 

If your SOPs and policies live in a folder that requires three clicks and a login to access, your frontline teams won't check them. Procedures and policies need to be available at the point of need, whether that be on the floor, in the store or on-site. 

Mobile accessible, role specific and searchable. That's the bar for document delivery in a modern multi-site operation. Anything less and you're relying on people to have memorised everything correctly. 

Build in acknowledgement 

Writing great SOPs and policies is only half the job. You need to know who has read them and confirmed they understand them, especially when something changes. 

Acknowledgement tracking closes the loop between publishing a document and trusting it's been received. It also gives you an audit trail if something goes wrong. 

Review before things break 

SOPs and policies should be reviewed proactively, not only when an incident occurs. Set a review schedule that works for your business, and assign an owner who is accountable for keeping each document current. 

The best time to update an SOP or policy is before the process changes, not after your team has already started doing things differently. 

The bottom line 

Great SOPs and policies are clear, specific, accessible and current. They're written for the person doing the task, not the person who signed them off. And they live somewhere your team can actually find them when they need them. 

For franchise and multi-site operators, the stakes are higher. Inconsistency across locations isn't just an operational inconvenience. It's a brand and compliance risk.