Process vs. Procedure vs. Policy vs. SOP

By Lisa González, Certified EOS Implementer® and co-author of Process! (The EOS Mastery Series). Updated June 10, 2026.

The short version: a policy is the why, a process is the what, a procedure is the how, and an SOP is a procedure written down in standard form. Most teams use these words interchangeably, and the confusion is one reason documentation efforts die. Here are the working definitions, with examples.

I'm Lisa González, Certified EOS Implementer® and co-author of Process! How Discipline and Consistency Will Set You and Your Business Free. After hundreds of leadership sessions on documentation, I can tell you the vocabulary debate is not academic. Teams that agree on terms document faster and argue less.

What is a policy?

A policy is a rule or guiding principle. It states the company's position and the boundaries for decisions. It does not tell anyone how to do anything.

Example: "We respond to every customer complaint within one business day."

What is a process?

A process is an end-to-end flow of work: the major steps that turn an input into a result, usually crossing several people or departments. A company runs on six to ten core processes.

Example: The complaint-handling process: receive, log, assign, resolve, follow up.

What is a procedure?

A procedure is the step-by-step instruction for one task inside a process. It is written for the person doing the work, at the level of clicks and actions.

Example: How to log a complaint in the CRM: which fields, which tags, which queue.

What is an SOP?

SOP stands for standard operating procedure. It is a procedure documented in a standard format so anyone qualified can follow it. In practice, "SOP" has become shorthand for any documented process or procedure. That blurring is mostly harmless, with one warning: if you document everything at procedure-level detail, you will create binders nobody reads. Document processes at the 20/80 level first. Save full SOPs for tasks where the cost of error is high.

How they stack

1. Policy sets the boundary: respond within one day.
2. Process defines the flow: receive, log, assign, resolve, follow up.
3. Procedure / SOP details one step: how to log the complaint, exactly.

Policies are owned by leadership. Each process has one owner. Procedures are owned by the people who do the work. When you know which layer you're writing, you know how much detail it needs and who should write it.

Why this matters for execution

Most documentation failures are layer mistakes. A policy written like a procedure becomes micromanagement. A process documented like a procedure becomes a 40-page manual nobody opens. A procedure treated like a policy never gets specific enough to train from. Match the detail to the layer and documentation gets dramatically easier. Then the real work begins: getting it followed.

Frequently asked questions

What is the difference between a process and a procedure?

A process is the end-to-end flow of major steps, often across departments. A procedure is the detailed instruction for one task inside that flow.

Is an SOP the same as a process?

No. An SOP is a documented procedure in standard form. A process is the larger flow the procedure lives inside. Casually, many teams call all documentation "SOPs."

Which should I document first?

Processes. Identify your six to ten core processes and document each at a high level, one to three pages. Add detailed procedures only where errors are costly.

Who should own each layer?

Leadership owns policies. Each core process has a single owner. Procedures belong to the people who perform them, with the process owner approving changes.

Ready to document without drowning in detail? Book a discovery call.