Standard Operating Procedure format

Almost every well-written SOP — whether for an FDA-regulated lab, a coffee shop, or a SaaS support team — uses the same seven sections. Following the format makes your SOPs easier to read, audit, and update.

1. 01

   Purpose

   One or two sentences explaining why the procedure exists. State the outcome it produces and who benefits.

2. 02

   Scope

   When the SOP applies, where it applies, and who is bound by it. Call out anything explicitly out of scope.

3. 03

   Responsibilities

   Each role involved, by job title or team, with the specific actions they own. Avoid naming individuals — roles outlast people.

4. 04

   Materials & systems

   Tools, software, forms, equipment, and access required to execute. List version numbers and account names where it matters.

5. 05

   Procedure

   Numbered, imperative steps. One action per step. Include decision points ("if X, then Y") inline rather than in separate flowcharts.

6. 06

   Quality checks

   How to verify the work was done correctly. Inspections, sign-offs, automated checks, or sampling rules go here.

7. 07

   References & revision

   Linked policies, regulatory citations, prior SOP versions, and the revision date plus owner. Required for any audited environment.

A minimal SOP skeleton

Title: <Process name>
Owner: <Role>     Version: 1.0     Last reviewed: YYYY-MM-DD

1. Purpose
2. Scope
3. Responsibilities
4. Materials & systems
5. Procedure
   5.1 ...
   5.2 ...
6. Quality checks
7. References & revision history