SOP vs Process vs Policy vs Procedure

These terms are often mixed together. The easiest way to separate them is by the job each document is supposed to do.

Quick definitions

Policy: what must or must not happen

A policy sets a rule, expectation, or boundary. It normally does not contain detailed instructions.

Example: Customer complaints must receive an acknowledgement within one business day.

The policy defines the requirement. It does not explain who opens the ticket, what message they send, or how the issue is escalated.

Process: how work moves from start to finish

A process describes the major stages that turn an input into an outcome. It is usually broader than a single SOP.

Example: Customer onboarding process

1. Agreement accepted
2. Customer record created
3. Welcome information sent
4. Required information collected
5. Kickoff or first service scheduled
6. Customer handed to the delivery team

Each stage may have its own procedure or SOP.

Procedure: the method for part of the process

A procedure explains how a specific piece of work should be performed. In everyday small-business use, “procedure” and “SOP” are often close in meaning. The practical distinction is that an SOP is the approved, standardized version intended to be followed consistently.

Example: A customer-onboarding process may include a procedure for creating the customer record.

SOP: the repeatable operating instructions

An SOP turns recurring work into a usable operating document. It should identify the trigger, owner, inputs, steps, quality check, completion standard, and exceptions.

Example: Create a new customer record

1. Search the approved system for an existing customer record.
2. If no duplicate exists, create a new record.
3. Enter the required contact and service information.
4. Assign the correct owner.
5. Record the next action and due date.
6. Confirm all required fields are complete.

How they fit together

Think of them as layers:

Small-business example: handling a customer complaint

Policy: All customer complaints are acknowledged within one business day and non-standard refunds require manager approval.

Process: Complaint received → facts verified → resolution selected → approval obtained if needed → customer updated → case closed.

Procedure: The customer-service procedure explains how complaints are reviewed and routed.

SOP: The complaint-intake SOP gives the exact steps for logging the complaint, sending the acknowledgement, verifying the record, assigning ownership, and escalating exceptions.

Which one do you need?

• If people are unclear about a rule, write or clarify the policy.
• If people cannot see how work moves across roles or stages, map the process.
• If a task is performed differently by different people, document the procedure/SOP.
• If the same problem keeps requiring judgment from the owner, define the policy boundary and then write the SOP for the normal path.

Build the SOP

Use the free Small Business SOP Template to document the recurring task, or review practical SOP examples for small businesses.

For a repeatable system for building multiple SOPs, see the Small Business SOP Builder Kit.