What is the difference between a process, an SOP, and a work instruction?

These terms get used interchangeably, which is how teams end up with a "procedure" that is really a flowchart, or an "SOP" that is really a list of clicks. The difference is level: each one zooms in further than the last.

What does each term mean?

• ✓Policy: a rule the organization commits to, and why. It says what must be true, not how to make it true.
• ✓Process: the sequence of activities, often across roles and systems, that turns an input into an output. It says what happens and who is involved.
• ✓SOP (standard operating procedure): the written, step-by-step way one team performs one recurring task within a process, including the decisions and exceptions. It says how we do this task here.
• ✓Work instruction: the detailed instructions for one step or one screen inside an SOP. It says exactly how to do this step.
• ✓Checklist: a short list of items to confirm. It says what must be done, not how.

For a fuller definition of the SOP itself, including its parts and a worked example, see what an SOP is and what makes one usable.

How does one task look at every level?

Here is a single request traced through all five levels: an insurance agency adding a driver to a client's personal auto policy.

Policy. "Coverage changes are made only at the request of a named insured, confirmed in writing, and documented in the client record the same business day." It does not mention screens, forms, or carriers. It applies to every kind of change, not just drivers.

Process. The policy change process runs from request to documented result:

1. 1A request comes in by phone, email, or client portal.
2. 2A customer service representative confirms who is asking and what they want.
3. 3The change is submitted to the carrier, or referred to underwriting.
4. 4The premium change is explained to the client.
5. 5Updated documents go out, and the file is noted.

The process crosses roles (customer service, account manager, carrier, client). It shows handoffs. It does not tell anyone how to add a driver.

SOP. "Add a driver to a personal auto policy" is one task inside that process. It has a trigger (a request to add a driver), an owner (the personal lines lead), and steps. Most importantly, it has the decisions:

• ✓Is the requester a named insured? If not, get confirmation from one before doing anything.
• ✓Is the new driver a household member the carrier requires to be listed, or someone the client wants excluded? Follow the carrier's rules for either.
• ✓Does the driver's history fit the carrier's guidelines, or does it need an underwriting referral?
• ✓Can the agency make the change directly in the carrier's system, or must it be submitted for approval?

It ends with a completion check: request saved, change confirmed by the carrier, client informed of the premium change, new ID cards sent, activity noted.

Work instruction. "Enter a new driver in the carrier portal" covers one step of the SOP at screen level: "On the Drivers page, click Add driver. Enter the license number exactly as printed, without spaces. Select the relationship to the named insured from the list. Click Save, then confirm the driver appears in the list with a status of Pending." Every carrier's screen is different, so an agency may keep one work instruction per carrier for the same SOP step.

Checklist. The completion check, pulled out as a list an experienced person can run in seconds:

• ✓Written request saved to the client record
• ✓Driver entered and change confirmed by the carrier
• ✓Any underwriting questions answered
• ✓Premium change explained to the client
• ✓New ID cards sent
• ✓Activity note added

When do you need each one?

Not every task needs all five. Use each where it earns its place.

• ✓Write a policy when a rule carries legal, financial, or client consequences and applies across many tasks.
• ✓Map a process when work falls through the cracks at handoffs, or when you are changing systems and need to see everything that touches the old one.
• ✓Write an SOP for any recurring task that more than one person does, or that only one person can do today.
• ✓Write a work instruction when a single step is fiddly, error-prone, done rarely, or different across systems, like one screen per carrier or payer.
• ✓Use a checklist when the reader already knows how to do the task and the risk is skipping something.

The same pattern holds in other offices. At an accounting firm, month-end close is the process, "reconcile the operating account" is an SOP, "download the statement from the bank portal" is a work instruction, and the close checklist confirms every account was reconciled. At a medical office, patient intake is the process, "verify insurance eligibility" is the SOP, and "search a member in a specific payer portal" is the work instruction.

For most small teams, the SOP does the heavy lifting. The step-by-step method for writing an SOP covers capture, decisions, testing, and upkeep, and the free SOP template has fields for the trigger, decision points, exceptions, and completion check.

Tools that record a task, SopWow included, produce SOP-level documents: one task, with its decisions written out. The policy and the process map are still yours to write.

Where do people get confused?

• ✓Calling a process map an SOP. A flowchart of stages and handoffs is useful, but a new hire cannot do the task from it.
• ✓Calling a work instruction an SOP. A list of clicks for one screen, with no trigger, owner, or decisions, only covers one path. When the next request is different, the reader is stuck.
• ✓Burying policy inside SOP steps. If the only place a rule is written is step 7 of one SOP, nobody finds it when a different task needs the same rule. State it once as policy and reference it.
• ✓Using a checklist to train. A checklist reminds; it does not teach. "Premium change explained" means nothing to someone who does not know how to explain it.
• ✓Treating process and procedure as synonyms. A process is what happens; a procedure (SOP) is how one part of it gets done.

Quality management systems and some regulated industries define these terms formally. If your organization has its own definitions, use them.

Frequently asked questions

view as markdown · /guides/sop-vs-process-vs-work-instruction.md