How to Write a Manufacturing SOP (With a Real Example)

What a manufacturing SOP needs to contain

An SOP that survives an audit contains seven elements. Remove any one of them and the document has a gap an auditor will find. These are not optional sections you can fill in later. They need to be present, complete, and accurate before the procedure is issued for use.

The seven required components are: a defined scope, a materials and equipment list with specifications, process parameters with tolerances, a numbered step sequence, sign-off requirements by role, a deviation routing procedure, and a revision history table.

The scope tells the auditor exactly what this document covers and what it does not cover. Without it, there is no boundary on the procedure's authority. The materials list with specifications tells operators which items are required and at what standard. A materials list that says "cleaning solvent" without specifying the solvent type, grade, and concentration is not a materials list. It is a suggestion.

Process parameters with tolerances are the difference between an SOP and a narrative. Every temperature, pressure, speed, time, and force value needs a tolerance. The sign-off requirements define who authorized the process and who witnessed it. Deviation routing explains what an operator must do when a step cannot be completed as written. Without it, operators make judgment calls that never get documented. The revision history creates the chain of evidence that the document reflects the current process.

The section structure that passes audits

The header section of an SOP carries the document's identity. It must include the document number, document title, revision number, effective date, and approval signatures. The document number and revision number together create the version identifier. An auditor checking your SOP will look at the effective date and compare it to your batch records to confirm you were using the right revision at the time of production.

The purpose section is one or two sentences. It states what the procedure covers and why it exists. "This procedure defines the heat treatment process for batch annealing of austenitic stainless steel tubing to achieve specified mechanical properties." That is a purpose statement. "This document describes our process" is not.

The scope section is where you draw the line. State what is in scope in concrete terms: which product families, which equipment, which production area. Then state what is explicitly out of scope. Auditors appreciate explicit exclusions because they show you have thought about the procedure's boundaries, not just its contents.

The materials and equipment section needs part numbers, calibration requirements, and acceptable substitutes if any exist. If you specify thermocouple TC-001, that means TC-001. If TC-003 is an acceptable substitute during maintenance, say so explicitly. If it is not, say that too.

Procedure steps must be numbered and must contain one action per step. Steps that bundle two actions are a finding waiting to happen. The operator completes step one but misses the embedded second action, and there is no record of the omission because it was never a separate step.

Acceptance criteria must be measurable and objective. "Parts should look acceptable" will fail every audit. "Surface finish Ra less than or equal to 1.6 micrometers measured per ASME B46.1" is an acceptance criterion.

The deviation and non-conformance section defines the path when a step fails or cannot be completed. Who gets notified? What forms get filled out? Where does the affected material go? If this section is absent, non-conformances default to operator judgment, which is not a controlled process.

The revision history table closes the document. It records every change, the reason for each change, and who approved it. A procedure with no revision history looks like it has never been updated, which to an auditor is indistinguishable from a procedure that has never been maintained.

How to write the procedure steps, with real examples

The procedure section is where most SOPs fail. Engineers write steps at a level of abstraction that made sense to them during drafting but leaves operators without enough information to perform the task correctly.

Consider a bad step: "Heat parts to temperature." This step fails on every dimension. Which temperature? What tolerance? Which heating equipment? How long? Who confirms it was achieved? There is no way to perform this step consistently across operators or shifts, and no way to verify it was done correctly afterward.

A good step for the same operation: "Set furnace F-003 setpoint to 730 degrees C. Allow furnace to reach setpoint temperature, confirmed by calibrated thermocouple TC-001 reading between 716 degrees C and 744 degrees C. Load parts per arrangement drawing DWG-HT-014-A. Hold at temperature for 45 minutes, plus or minus 5 minutes. Record start time, end time, and thermocouple reading at 30-minute mark in heat treatment log F-HT-002."

That step contains a temperature with a tolerance of plus or minus 14 degrees C, a named instrument, a specific hold time with a tolerance of plus or minus 5 minutes, a named record, and specific data fields to capture. An operator following that step correctly is performing a controlled, documented process. An operator following "heat parts to temperature" is performing an uncontrolled operation.

You can see this level of specificity applied throughout the batch annealing SOP example (SOP-HT-014) on this site. That document shows how the header, materials section, step sequence, and deviation routing work together in a single complete procedure.

Two rules hold for every step. Every measurement needs a value and a tolerance. Every action needs to name the specific tool, instrument, or form involved. If either is missing, the step is incomplete.

Five SOP mistakes that fail audits

These are the five most common findings on manufacturing SOPs during external audits under ISO 13485, FDA 21 CFR Part 820, and similar regulated frameworks.

Missing tolerances on process parameters. Any numeric value in a procedure without a tolerance is an incomplete specification. This includes temperature, pressure, speed, time, force, and torque. Auditors read every number looking for tolerances. A single unqualified value is a finding.

Passive voice in operator steps. "Parts are heated to 730 degrees C" does not assign responsibility. Who heats them? On which equipment? Operator steps must use active voice and name the actor. "Operator A heats parts in furnace F-003 to 730 plus or minus 14 degrees C" is a step that can be signed off against.

No defined deviation path. When step 7 cannot be completed as written, what does the operator do? If the SOP does not say, operators improvise. Improvisation in a controlled process is a non-conformance that never gets recorded. Every SOP needs a deviation routing section that tells operators exactly what to do when the process goes off-script.

Incomplete sign-off matrix. The approval block must identify who approves, who witnesses, and what role each person holds. An approval block that shows only a name and date is not traceable to a role or function. When the approver leaves the company, there is no way to confirm they had the authority to approve that class of procedure.

No revision history. Auditors check revision history to confirm the current procedure reflects the current process. A document on revision A that has been in use for four years, through two equipment changes and a process revalidation, has a revision history problem. Every change to the process must be reflected in a new revision of the SOP, with the change described, dated, and approved.

SOP format and what goes in the document header

The document header carries all information needed to uniquely identify and trace the procedure. Required fields are: document number, document title, revision number, effective date, department, author, reviewer, approver, and page number (typically formatted as "Page X of Y").

Section numbering follows the 1.0, 1.1, 1.2 convention for major and minor sections. This makes it straightforward for auditors to reference specific sections in observations or findings, and makes it easier to update a single subsection without renumbering the entire document.

Page layout should be consistent: fixed margins, clear section breaks, and a table of contents for procedures longer than four pages. Consistent formatting is not a cosmetic concern. It signals that the document system is maintained and controlled. A procedure that changes fonts between sections, or has inconsistent heading styles, looks like it was assembled from parts rather than authored as a controlled document.

The best template is the one your QMS has already approved. If your QMS is certified to ISO 13485:2016, your document control procedure defines what the SOP template must contain and what approval authority is required. Write to that template, not to a generic one from the internet. If you do not have an approved template, the first step is creating one through your document control process, not writing individual SOPs in whatever format seems right.

When to write it yourself vs bring in help

Write it yourself when you have all three of the following: a subject matter expert who can describe the process step by step, time to write and review the document before the deadline, and a QMS-approved template that defines the required format and approval workflow. If you have all three, an experienced engineer can produce a solid SOP in a day or two per procedure.

Bring in help when any of those three conditions are missing. The most common situations: the audit is scheduled and the backlog is 15 SOPs with two weeks available. The subject matter expert left the company and took the process knowledge with them. The procedures need to conform to a QMS format your team has not written in before. The team is running production and cannot pull engineers off the line to write documents.

The cost of a poorly written SOP is not just the audit finding. It is the batch rejection, the corrective action, the revalidation run, and the rescheduled audit. A procedure written correctly the first time is almost always cheaper than one written under time pressure and revised after a finding.

If you have a backlog of procedures that need to be written or updated before an upcoming audit, Aptibot's documentation service handles exactly that. You provide access to the process, the equipment, and the subject matter expert. The output is an audit-ready procedure set in your QMS format.

For the distinction between an SOP and a work instruction, which is a separate document type with different scope and authority, see the guide on SOP vs work instruction. Using the wrong document type is itself a finding in a QMS audit.

If FDA process validation requirements are relevant to your procedures, the agency publishes guidance at FDA process validation: general principles and practices. That guidance describes what the agency expects to see in a validated process, including the role of written procedures in maintaining process control.