What should an SOP include?

A clear title, a reference number and version, the owner, an effective date, the purpose, the scope (when it applies and when it does not), anything needed before starting, the numbered steps, and a review date. Anything else is usually optional.

How detailed should each step be?

Detailed enough that a competent newcomer does not have to ask a question, and no more. Over-specified SOPs stop being read; under-specified ones get improvised around. Test it on someone who has never done the task.

What is the difference between an SOP and a process document?

A process describes the flow of work across people and stages at a high level. An SOP is the step-by-step instruction for one task inside that process. A process shows what happens; an SOP tells you exactly what to do.

How often should SOPs be reviewed?

Every six to twelve months for stable work, and immediately after anything changes — a new tool, a new rule, or a mistake that the SOP should have prevented. The review date field exists to force the question.

SOP Generator

Free SOP Template

Write a standard operating procedure your team will actually follow, then download it as a PDF. No signup, no watermark.

Document header

SOP title (name the task)

SOP #

Version

Owner

Effective date

Review by

Purpose & scope

Purpose (why this exists)

Scope (when it applies, when it does not)

Before you start (access, tools, info needed)

Steps

Start each with a verb. One action per step.

Notes, exceptions, escalation

Standard Operating Procedure

Untitled procedure

Reference: SOP-001

Version: 1.0

Procedure

1.
—

How to write an SOP in 5 steps

Most SOPs fail not because they are wrong but because nobody opens them. These five things are what separate a document people use from one that sits in a folder.

1
Name the task, not the department
"Onboard a new client" is findable. "Client Services Procedure v2" is not. People search for the task they are trying to do, so title it that way.
2
State why it exists before how it works
A one-line purpose stops people improvising around a step they think is pointless. When someone knows why a check exists they stop skipping it.
3
Write one action per step
Start each with a verb: open, check, send, confirm. If a step contains "and", it is probably two steps. The test is whether someone new could follow it without asking a question.
4
Name the owner and a review date
An SOP with no owner rots. Put a name against it and a date to revisit, or in six months nobody will know whether it is still accurate.
5
Have someone else run it once
Hand it to the person least familiar with the task and watch them follow it without helping. Every place they hesitate is a step you wrote for someone who already knew the answer.

Keep going

Customer satisfaction surveyCheck the procedure is actually producing a better experience.Proposal generatorStandardise how you pitch, not just how you deliver.What a CRM actually doesTurn a written procedure into steps the system enforces.More free toolsCalculators and generators for agencies and creators.

Written the SOP but nobody follows it?

Inflowave turns a procedure into an automated sequence so the steps happen whether or not somebody remembers. Want a walkthrough?

1Follow @inflowaveSo we can DM you back — Instagram blocks replies to non-followers.Follow

2DM us the word “{{kw}}”That keyword triggers your free teardown. We reply within 24h.DM “{{kw}}”

Follow + DM “{{kw}}” to @inflowave →

Frequently asked questions

A written set of steps for doing a recurring task the same way every time. The point is consistency and handover: anyone qualified should be able to pick it up and produce the same result without asking the person who normally does it.