SOP Scope and Purpose: Start With a Clear Policy Definition

Most SOPs that fail do not fail on the steps. They fail on the two short sections at the top: the purpose, which says why the procedure exists, and the scope, which says who it covers, where it applies and where it stops. And both of those sections depend on something that sits above the SOP altogether: the policy it supports.

This is part two of our seven-part series on the SOP lifecycle. It starts with a plain policy definition, shows how a policy shapes an SOP’s purpose, and then walks through a practical method for defining purpose and scope before you write a single step. If you want the full picture first, read our complete SOP lifecycle guide.

Policy definition: what is a policy?

Merriam-Webster defines a policy as “a definite course or method of action selected from among alternatives and in light of given conditions to guide and determine present and future decisions.” The US Centers for Disease Control and Prevention (CDC) uses a broader public health definition: “Policy is a law, regulation, procedure, administrative action, incentive, or voluntary practice of governments and other institutions.”

Inside an organization, the working definition is narrower. A workplace policy is a documented rule or guiding principle, approved by the organization, that states what is required of people, what is allowed or not allowed, and why. It sets the direction. It does not describe every step of how the work gets done.

A good policy usually has these features:

It is formal. It is written down, approved by someone with authority and published in one controlled place.
It states requirements, not tasks. It says what must happen and why, and leaves the how to procedures.
It has a defined audience. It names who it applies to, whether that is the whole organization or one department, role or site.
It has an owner. One named role is responsible for keeping it accurate and reviewing it.
It changes slowly. It is usually revised when a law, regulation, risk or strategy changes, not every time a system or form changes.

For example, an expenses policy might say: “Employees are reimbursed for reasonable business expenses that are approved by their line manager and supported by a receipt.” That is the rule. How a claim is submitted, checked, approved and paid belongs in an SOP.

For a fuller explanation, with the sections every policy should include and the most common types, see our guide on what a workplace policy is and why it matters. If you are still building your set of policies, this list of essential policies for your organization is a good place to start.

How a policy shapes an SOP’s purpose

Every SOP should trace back to a policy, a regulation or a clear business need. The policy defines the requirement. The SOP’s purpose explains how this particular procedure helps meet it.

	Policy	SOP
Answers	What is required, and why?	How is this task done, by whom, and in what order?
Audience	Everyone the rule applies to	The named roles who carry out the task
Level of detail	High level and principle based	Step by step, for a specific context
Example	Approved business expenses with a receipt are reimbursed.	How expense claims are submitted, checked, approved and paid.

When you can name the policy behind an SOP, writing the purpose becomes much easier, and reviewers can check that the procedure actually delivers what the policy requires. To see how policies, processes and procedures fit together as layers, read our guide to the differences between policies, processes and procedures.

Why purpose and scope come first

Settling purpose and scope before you write the steps pays off in four practical ways:

Consistency. Everyone who performs the task works to the same outcome and the same boundaries.
Quality and compliance. Reviewers and auditors can see what the procedure is meant to achieve and check it against the policy or regulation behind it.
Faster onboarding. New employees can tell in a few seconds whether a procedure applies to them.
Safety. Where hazards are involved, a clear scope shows exactly which people, sites and equipment the controls cover.

Purpose vs scope: what is the difference?

	Purpose	Scope
Answers	Why the procedure exists and what a correct outcome looks like	Who follows it, where and when it applies, and where it starts and stops
Length	One to three sentences	Two to five sentences, including exclusions
Written in terms of	Outcomes and obligations	Roles, sites, systems, timing and boundaries

How to define purpose and scope in six steps

Name the task and the outcome. Describe the result the procedure produces in one line.
Write a focused purpose statement. In one to three sentences, say what the procedure achieves and which policy, regulation or obligation it supports.
Identify the roles it applies to. Use role titles, not individual names, so the SOP does not go out of date when people move on.
Set the start and end points. Name the event that triggers the procedure and the event that closes it.
State the exclusions. Name what the procedure does not cover, and point to the document that does.
Check the steps against the scope. Before approval, confirm that every step sits inside the scope and that nothing inside the scope is missing a step.

Five questions your scope should answer

Who? Which roles must follow the procedure.
Where? Which sites, departments or systems it covers.
When? Which shifts, conditions or circumstances it applies to.
From what to what? The trigger that starts it and the point at which it ends.
What is excluded? What it deliberately does not cover, with a reference to the document that does.

Weak vs strong: an example

	Weak	Strong
Purpose	“To outline the process for handling expense claims.”	“This SOP sets out how expense claims are checked and approved, so that claims are reimbursed in the correct pay run and every approved claim has a receipt and a named approver on file. It supports the Expenses Policy.”
Scope	“This SOP applies to all employees.”	“This SOP applies to employees who submit expense claims, the line managers who approve them and the accounts payable team who pay them. It covers each claim from submission to payment. It does not cover corporate card transactions or travel booking, which are covered by separate procedures.”

The strong version tells the reader what success looks like, which policy it serves, who is involved, where the procedure starts and stops, and what to read instead if their situation is out of scope.

What a clear scope looks like in practice

Manufacturing: Two sites write separate procedures for the same machine because neither SOP says which equipment it covers. Naming the equipment models and sites in the scope shows that one procedure is enough.
Multi-site retail: A single store-opening SOP does not fit both large stores and small-format stores. Scoping by store format produces two short procedures that staff actually follow.
IT service desk: A triage SOP with a purpose written around the outcome, such as routing each ticket to the right team on first contact, gives analysts a clear test for every decision.

Common mistakes to avoid

Using “all employees” as the default scope. It is rarely true, and it hides who is actually accountable.
Writing the purpose only for auditors. The purpose should make sense to the person doing the task, not just to a reviewer.
Leaving out exclusions. Without them, readers guess where the procedure stops, and different people guess differently.
Changing the scope without a new version. A scope change is a material change. Record it in the revision history and tell the people affected.
Naming individuals instead of roles. The SOP goes out of date the day someone changes job.
Not testing the boundaries. Ask someone to check real cases against the scope before you publish.
Not naming the policy behind the SOP. Without it, reviewers cannot tell whether the procedure meets the requirement it exists to support.

Many of these issues show up later as common problems with implementing SOPs, so it is worth getting them right now.

Keep purpose and scope current

When a policy changes, check the purpose and scope of every SOP that supports it. Use version control so you can show which version was in force on a given date, and use a consistent layout so readers always find the purpose and scope in the same place. Our free policy and procedure template in Word gives you a standard layout, and these best practices for managing policy changes in SharePoint cover versioning and approval.

When a policy or SOP is updated, the people in scope need to know. DocRead for Microsoft 365 and SharePoint Online lets you assign the updated document to the roles, departments, locations or groups it applies to, ask them to read and acknowledge it, send automated reminders and report on who has and has not done so.

Frequently asked questions

What is the definition of a policy?

In general use, a policy is a definite course or method of action chosen to guide present and future decisions. In the workplace, a policy is a documented, approved rule or guiding principle that states what is required of people and why.

What is the difference between a policy and an SOP?

A policy states what the organization requires and why. An SOP explains, step by step, how named roles carry out a task in a specific context so that the policy’s requirements are met.

What is the purpose of an SOP?

The purpose section explains why the procedure exists and what a correct outcome looks like. It is usually one to three sentences and often names the policy or regulation the SOP supports.

What is the scope of an SOP?

The scope says who must follow the procedure, where and when it applies, where it starts and stops, and what it does not cover.

Does a policy have a scope too?

Yes. A policy’s scope states which employees, departments, locations, systems and activities the rule applies to. It is usually broader than the scope of the SOPs that support it.

How long should a purpose and scope be?

Short. One to three sentences for the purpose and two to five sentences for the scope is enough for most procedures.

Next in the series

With the purpose and scope defined, the next stage is identifying the audience and authors for your SOP, followed by choosing the SOP format and writing style. You can also download the free standard operating procedures manual to have the whole lifecycle in one place.