SOP vs Work Instruction vs Process Map vs Policy

By Nikhil Gupta

SOP vs Work Instruction vs Process Map vs Policy

Short answer:

• A policy says what must happen and why.

• A process map shows how work flows across people and decisions.

• An SOP describes the steps of a process in order, with roles.

• A work instruction explains exactly how to do one task, often at click-by-click level.

They form a hierarchy, from rules down to detail, and good documentation links them together.

The documentation hierarchy

POLICY            "Invoices over $5,000 require Director approval."      WHY / WHAT
   ↓
PROCESS MAP       Invoice received → match → approve → pay (roles, decisions)  FLOW
   ↓
SOP               Step 1 AP logs invoice … Step 3 route by amount …       STEPS
   ↓
WORK INSTRUCTION  "In the ERP, click Invoices → New → enter PO number…"   HOW (one task)

Side-by-side comparison

When you need each

• Policy: when a rule must apply everywhere, such as approval limits, data handling, or compliance requirements.

• Process map: whenever a process crosses roles or teams, has decisions, or you plan to improve or automate it.

• SOP: for any recurring process where consistency matters, including onboarding, closing the books, and handling claims.

• Work instruction: for tasks where getting the details wrong causes errors, like system entries, equipment operation, and quality checks.

Common mistakes

1. Writing SOPs at work-instruction detail. They become huge and break every time a screen changes. Keep system clicks in linked work instructions.

2. SOPs without a process map. Text hides missing decisions and hand-offs.

3. Policies disguised as procedures. "Invoices must be approved" is a rule. How they get approved is the SOP.

4. Documents that don't link to each other. The SOP should reference its policy, its map, and its work instructions.

How the pieces fit in Vevos

In Vevos, the process map (BPMN 2.0) is the source. The SOP-style documentation is generated from it, so the steps always match the map. Link out to work instructions captured in tools like Scribe or Tango, and reference the governing policy in the documentation. When the process changes, you update the map once and regenerate the documentation.

FAQ

Is an SOP the same as a process?

No. The process is the work itself. The SOP is the written description of how to do it.

Do I need both a process map and an SOP?

For anything beyond a simple, single-person task, yes. The map shows the flow, and the SOP gives the detail. Generating one from the other keeps them consistent.

Where do checklists fit?

A checklist is a condensed SOP for running the process. It's useful for recurring execution, but it isn't a replacement for documenting the decision logic.

Start with the map: describe a process in Vevos and generate its documentation.