Difference Between SOPs v Work Instructions v Procedures

How can you tell if a document is a SOP, Procedure, or Work Instruction? Also, what are the connections between each of these documents? Is one more important than the other? Do you need to write an SOP before the Work Instruction… or should it be the other way round?

Download Work Instruction Templates for only 7.99!

Download Template

Learn more about this template

In this tutorial, we look at:

  • How to document SOPs, Work Instructions and Procedures
  • How to structure the documents in the correct sequence

Difference between Work Instructions and Procedures

Work Instructions – tell you how to do something. They are very specific instructions, for example, how to complete a form.

Procedures – tell you who does what when. In other words, it identifies who completes the form and when this should occur.

In simple terms:

  • Procedures tell you Who, What and When
  • Work Instructions tell you How

SOP, Work Instruction, & Procedures: How to structure

If you look at the documents like a pyramid, then

  • Standard Operating Procedures are the top layer. These are often shared with customer  and rarely hold confidential data.
  • Procedures (second tier) describe the process. They are more detailed and often contain both a narrative (i.e. text description of the steps) and visuals, usually in the form of use cases and workflow diagrams. These documents will be examined during audits.
  • Work instructions (third tier) describe the work to be performed. These provide the lowest possible level of detail. As the name implies they are instructions to perform a specific piece of work. Some are less than one page. Just a list of bullet points.

Download Template

Learn more about this template

ISO: Documenting SOPs, Work Instructions, & Procedures

If you’re documenting ISO processes, then you can approach them based on levels. Again, this is similar to the idea of a pyramid or tiered structure.

  • Level 1 = Quality Assurance Manual – these are mandatory documents for ISO and must be maintained as the project evolves. This is the starting point for document-related goals, objectives and accountability.
  • Level 2 = Procedures – Document interection between departments/business units in terms of input/outputs.
  • Level 3 = Work Instructions – Any document that defines how work objectives are achieved.
  • Level 4 = Records – evidence of conformance.

To be clear: Level 3 documents are sometimes referred to as SOPs, Process Instructions, or Procedures.

Does it make a difference?

Yes, in that if you chop and change terminology, you’ll confuse the readers (and possibly the writers) and also raise concerns with the auditors.

No, if you use a consistent document convention and apply the same guidelines across all documents.

In other words, if ISO did not exist, would you still use the same document naming conventions?

To recap:

  • Work Instructions are 3rd level documents
  • Procedures are 2nd level documents and
  • Quality Manual is the 1st level document

In the next tutorial, we’ll look at how to write more effective work instructions.

Download these templates to start

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan