How to write an SOP that people will follow

A good SOP tells someone exactly what to do, in what order, and why it matters. That’s it. If your SOP doesn’t do those three things in plain language, it won’t get used - no matter how polished the formatting looks.

Procedures are what make your business repeatable. Your company already has processes - the work people do every day. Approving invoices, fulfilling orders, onboarding new hires.

A Standard Operating Procedure (SOP) is the documented version. It captures the steps, the scope, who’s responsible, and what success looks like.

After watching hundreds of teams try this helping teams document their workflows at Tallyfy, we’ve found SOPs are genuinely useful for two things:

• Onboarding people faster - Nobody remembers every step of every process. Documentation gives new hires a clear path to follow instead of bugging coworkers with questions all day
• Locking in best practices - There’s always one version of a process that works better than the others. An SOP makes that version the default for everyone

Here’s something that surprised me. One services company we spoke with went from 65+ employees down to 15 - not through layoffs, but because their SOPs revealed massive duplication. Four execution levels were doing overlapping work. The SOPs exposed it. They eliminated the redundancy and kept only what mattered.

That’s the real power of writing things down. You see what’s broken.

What goes into an SOP

Before jumping into the writing process, you should know what sections a typical SOP includes. This varies by industry (ISO-9000 compliance demands more structure, for example), but most SOPs cover:

• Title page - Process name, department, owner, version number
• Table of contents - Only if the document runs long enough to need one
• The procedure itself
  • Scope - Which team, department, or role does this apply to? Be specific here or you’ll end up with a bloated document nobody reads
  • Terminology - Define abbreviations and acronyms upfront so people aren’t guessing
  • Steps - The actual process documentation - maps, checklists, or written instructions
  • Supporting info - Equipment locations, safety warnings, login credentials, anything someone needs to complete the work
• Metrics - How will you measure whether this process is working? Without metrics, you’ve got no way to know when things drift

Most of that’s straightforward. The hard part is documenting the procedure itself, especially if you’re not experienced with process management. Here’s how to do it right.

Five steps to write an SOP that works

Talk to the people who do the work

You probably aren’t the person running this process daily. You might have a general idea of how it works, but you don’t know the small details that affect outcomes.

Set up a meeting with the people who actually execute the process. Ask them to walk you through it step by step. Every little detail. The workarounds they’ve developed, the things that go wrong, the steps they skip because “they don’t matter” (they usually do).

From what I’ve seen, the gap between how managers think a process works and how it actually runs on the ground is enormous.

Draw a line around the scope

This is where most SOP projects fall apart. Processes bleed into each other across teams and departments. If you don’t define boundaries early, you’ll end up with a 40-page document that nobody finishes reading.

Take our content publishing process as an example:

1. Writer creates a draft
2. Editor reviews and gives feedback
3. Loop until the article is ready
4. Editor uploads and optimizes for SEO
5. Marketing gathers contact info for outreach
6. Marketing sends outreach emails

If you’re onboarding a new writer, they only need steps 1 through 4. Marketers need 5 and 6. Don’t combine them into one massive SOP. Two focused documents beat one bloated one every time.

Document the actual procedure

This is the bulk of the work. You’ve got three main options depending on complexity:

Option 1: A simple checklist. Works for linear processes with no decision points. Think of it like a grocery list - here are the tasks, do them in order.

Basic publishing process checklist using Todoist

Option 2: A workflow diagram. Better for processes with branches, approvals, or multiple outcomes. You create a flowchart showing different paths based on decisions.

Client onboarding procedure flowchart

The simplest option is a process flowchart, though you could also use a Swimlane Diagram or SIPOC depending on what you’re mapping.

Option 3: Business process management software. Instead of static documents or diagrams, you build the process digitally. This is where Tallyfy shines - you get real-time tracking, bottleneck detection, and automatic deadline management built in.

The difference? With a Word doc or PDF, you’re hoping people follow the process. With software, you can see whether they did.

Feedback we’ve received from regulated industries confirms this. A lab testing company we spoke with needed SOPs for sample handling with full traceability for compliance. Their pain point was managing accuracy across lab procedures. The digital SOP became both their training tool and their audit trail at the same time.

Add the supporting details

A process flowchart alone won’t tell someone everything they need. They might need to know where equipment is located, what credentials to use, or how to handle edge cases.

List out anything required to finish the process:

• Methodology - The right way to execute a step. If you’re onboarding an employee, “input employee information to HR software” needs to specify what information - name, date of birth, tax ID, emergency contact
• Tools needed - Which software, which room, which machine. Be specific: “use the CNC machine in room 201” or “log into the CRM at [specific URL]”
• Safety warnings - If any step carries health risks, document precautions. This isn’t optional in industries like manufacturing, healthcare, or lab work

Define metrics and keep improving

You’ve got your SOP. You could stop here and call it done. But I’d push you further. You probably spotted improvement opportunities while documenting the process. Most organizations don’t look back at their processes after defining them. That “don’t fix what isn’t broken” attitude costs more than people realize. In our experience with workflow automation, the teams that review their SOPs quarterly outperform the ones that write them once and forget about them. You can’t improve what you can’t measure. For manufacturing, track product output. For marketing, leads generated. For any process, measure cycle time - how long from start to finish. The metrics are what turn a static document into a living system that gets better over time.

Then look at these three improvement angles:

• Streamline it - Are any steps taking too much time or resources? Can you cut them or replace them with something faster?
• Automate it - Can software handle parts of the process? Most repetitive tasks can be automated
• Outsource it - Is part of the process grunt work that anyone could do? Consider a virtual assistant for those pieces

Why SOPs are the one thing you need before AI can help

Here’s what most people miss in the rush to adopt AI: Without a solid process, AI just automates your mistakes.

If your process is a mess - unclear steps, no ownership, inconsistent execution - throwing an AI agent at it just creates a faster mess. The AI will faithfully execute your broken workflow at machine speed.

SOPs are the foundation that makes AI useful. When you’ve defined clear, sequential steps with decision points and ownership, an AI agent can actually follow them. Without that structure? You’re asking AI to improvise, and improvisation at scale is chaos.

This pattern drove every design decision in Tallyfy. The workflow patterns - sequential, parallel, evaluation loops - give AI something concrete to execute against.

Getting your SOP into people’s hands

Writing the SOP is half the battle. The other half is making it accessible.

The best approach is putting it online. You can use Google Docs or similar file-sharing tools, or you can use process management software like Tallyfy if you want tracking and accountability baked in.

Everyone who needs the SOP should have access. If you’re old-school, print copies and keep extras around the office. But digital wins here - it’s searchable, updatable, and you can see who’s actually using it.

Start with proven SOP templates

Example Document

Purchase Request SOP

Your go-to guide for requesting purchases. You'll find out when you need approval, what the spending limits are for your role, which vendors to use, and how to submit your request. If you follow this process, your purchases stay tracked and you won't blow the budget.

View template

Example Procedure

Employee Onboarding

1Save offer letter to employee file

2Send welcome email to new hire

3Set up HR system account

4Create onboarding task list

5Schedule onboarding activities

View template

Example Procedure

Blog Post Creation & Publishing Workflow

1WordPress

2System 1

3System 2

4Choose your topic

5Research and outline

+5 more steps

View template

Common questions about SOPs

Why do SOPs matter so much?

They’re your business’s recipe book. Without them, everyone cooks the dish differently, and some versions are terrible. SOPs also protect you when key people leave - their knowledge is already written down instead of walking out the door with them.

What’s a real-world SOP example?

Think about how a coffee shop makes a latte. Heat the milk to exactly 150 degrees F. Pull the espresso shot for 25-30 seconds. Pour the milk in a specific pattern. That’s an SOP. Another example: the opening routine for a retail store - unlock doors, count the register, boot up computers, turn on lights. Same order, every morning.

How long should an SOP be?

As long as it needs to be, but not a word longer. The sweet spot is usually 2-5 pages, though complex procedures might run longer. Think of it like giving directions - enough detail to prevent wrong turns, not so much that someone gets lost in the instructions themselves.

Who should write it?

The best SOPs come from a team that includes both the people doing the work and the people supervising it. Managers miss details that frontline workers catch every day. You need both perspectives.

How often should you update SOPs?

Review them at minimum once a year. Update sooner if processes, equipment, or common problems have changed. Think of it like updating apps on your phone - regular updates keep everything running smoothly and patch bugs before they cause real problems.

Can an SOP be too detailed?

Absolutely. Over-detailed SOPs become impossible to follow and a nightmare to maintain. Hit the balance between too vague and too specific. You want enough detail to prevent mistakes, not so much that people give up reading halfway through.