Template: Generic SOP (the SOP for writing SOPs)

This is the master template every author copies to start a new standard operating procedure. Replace each <<FILL: ...>> placeholder, write the procedure body to the conventions described in the notes, then route it through your normal document control, review, and approval. A worked filled specimen follows the template so you can see how a completed procedure reads. Italic lines marked “Author note” are guidance for you, the author, and are deleted before the SOP is issued.

The structure below is typical and inspection-friendly. It is not a regulation in itself. Your own document control SOP defines the binding template and numbering scheme; if it differs from this layout, follow yours and use this as a content checklist.

Document control header

Author note: the header (or footer) must appear on every page and must carry document number, version, effective date, and “page x of y”. The “of y” matters: without it, a missing page goes undetected.

1. Purpose

<<FILL: one or two sentences on what this procedure achieves and why it exists.>> State the outcome the procedure assures, not a restatement of the title.

Author note: good purpose, “This procedure defines how deviations from approved procedures, specifications, and conditions are recorded, assessed, investigated, and closed, so that product quality and data integrity are protected and recurrence is prevented.” Weak purpose, “The purpose of this SOP is deviation management.”

2. Scope

This procedure applies to <<FILL: the activities, areas, products, systems, and roles covered>>. It does not cover <<FILL: the explicit exclusions and what governs them instead, e.g. "supplier quality events, which are governed by SOP-QA-030">>.

Author note: state both what is in and what is out. Silent boundaries are how two SOPs overlap or a gap opens between them. Inspectors find these by cross-reading.

3. Responsibilities

Author note: name roles, not people. Every role listed here must appear in the procedure steps, and every actor in the steps must appear here. No orphan roles, no unnamed actors.

4. Definitions and abbreviations

• <<FILL: term>>: <<FILL: definition as used in this procedure>>.
• <<FILL: abbreviation>>: <<FILL: expansion>>.

Author note: define only terms that are load-bearing or could be read two ways. Do not define obvious words. Do not leave a critical acronym undefined. Pick one term for one thing and use it identically throughout.

5. References

Author note: only list references the procedure actually uses. Dead references to superseded documents are a common finding. Confirm each cited regulation against its current published version before issue.

6. Materials and equipment

<<FILL: list what the user needs before starting, e.g. calibrated balance, controlled form SOP-QA-021-F1, validated system access. State "None" if genuinely none.>>

Author note: if the user has to stop mid-task to hunt for a part, a form, or system access, this section was incomplete. List it here so they gather everything first.

7. Safety and environmental controls

<<FILL: hazards specific to this task and the controls, e.g. handle solvent X in the fume hood; wear nitrile gloves. State "Not applicable" only if truly none.>>

Author note: keep this specific to the actual steps. Generic boilerplate disconnected from the task is ignored and adds length without value.

8. Procedure

Author note: this section is where the SOP lives or dies. Write it first, then build the framing sections around it. Conventions:

• One step, one actor, one action, active voice. “8.3 The analyst records the reading,” not “the reading is recorded.”
• Put the acceptance criterion (value, range, condition) inside the step.
• Write decisions as explicit if/then branches with a defined path for every outcome, including the failure path.
• Number steps so they can be cited (“repeat 8.3 to 8.5”).
• Tie every recording action to the time of performance.

8.1 <<FILL: first action. The {role} {does what} {to what}, and records {what} in {which form} at the time of performance.>>

8.2 <<FILL: next action, with its acceptance criterion stated in the step.>>

8.3 If <<FILL: condition>>, the <<FILL: role>> <<FILL: action and where it continues>>. If <<FILL: alternate condition>>, the <<FILL: role>> stops, <<FILL: defined failure path, e.g. initiates a deviation per SOP-QA-021 and notifies the supervisor>> before proceeding.

8.4 <<FILL: continue the numbered steps to completion>>

8.x <<FILL: final step, including the handoff or close-out and the record signed at the time of performance>>

9. Acceptance criteria

The activity is performed correctly when all of the following are true:

• <<FILL: the values, ranges, or conditions that must hold, drawn from the steps above>>
• The required records are complete, legible, attributable, and recorded at the time of performance.
• Any out-of-criteria result was handled by the defined failure path and routed per the deviation procedure.

Author note: this section restates the in-step criteria as a single pass/fail summary. A reviewer or auditor reads it to know what “good” looks like without re-deriving it from the steps.

10. Records generated

Author note: state what the procedure generates, where it goes, and how long it is kept. A procedure that creates a record but never says where it lives or how long to keep it leaves an undocumented gap.

11. Attachments

• <<FILL: attachment ID and title, e.g. SOP-QA-021-F1 Deviation Record>>
• <<FILL: decision tree, diagram, or labeled photo if used>>

Author note: every form, template, or diagram referenced must be a controlled attachment or a controlled standalone document. Uncontrolled forms are a data integrity exposure.

12. Revision history

Author note: “Updated for clarity” fails the test. Describe what changed and why, traceable to a change control record, so someone can reconstruct what the procedure required at any past date.

13. Approvals

Author note: approvals must be controlled, signed, dated, and traceable to this version, wet ink or compliant electronic signature. For electronic signatures, the controls in 21 CFR Part 11 and EU GMP Annex 11 apply.

References

21 CFR 211.100(a) and 211.100(b) (production and process control procedures shall be followed and documented at the time of performance). 21 CFR 211.22(d) (the quality unit’s procedures shall be in writing). 21 CFR Part 11 (electronic records and electronic signatures). EU GMP (EudraLex Volume 4) Chapter 4, Documentation. EU GMP Annex 11 (computerised systems), where the procedure governs a computerized activity. ICH Q10, Pharmaceutical Quality System; ICH Q7, GMP for active pharmaceutical ingredients. 21 CFR Part 820 / the medical device Quality Management System Regulation, for device quality system procedures.

Confirm the current version and clause numbers of each reference before issue.

Filled specimen

The following shows the template completed for an example procedure, the receipt and quarantine of an incoming raw material sample, so you can see the level of detail an inspector expects. The company, document numbers, roles, and values are illustrative; replace them with your own. Only the header and the procedure body are shown filled; the remaining sections follow the same pattern.

Document control header (specimen)

8. Procedure (specimen)

8.1 The receiving analyst confirms the delivered container matches the purchase order for material name, lot number, and quantity. If any attribute does not match, the analyst quarantines the container, applies a “HOLD” label, and notifies QA before proceeding. The analyst does not test material that does not match the order.

8.2 The receiving analyst inspects the container for damage, leakage, or tampering. If damage is present, the analyst initiates a deviation per SOP-QA-021 and places the container on hold.

8.3 The receiving analyst assigns the next sequential sample ID from the Sample Receipt Log (SOP-QC-014-F1) and records the material name, lot number, supplier, and receipt date in the log at the time of receipt, with initials.

8.4 The receiving analyst measures the container surface temperature with a calibrated thermometer. The acceptance range is 2 C to 8 C. The analyst records the reading in the Sample Receipt Log.

8.5 If the temperature is within 2 C to 8 C, the analyst proceeds to 8.6. If the temperature is outside 2 C to 8 C, the analyst stops, retains the container in the quarantine cooler, initiates a temperature excursion deviation per SOP-QA-021, and notifies the supervisor and QA before any further handling.

8.6 The receiving analyst transfers the container to the quarantine cooler, confirms the cooler display reads within 2 C to 8 C, and records the storage location and time in the Sample Receipt Log.

8.7 The receiving analyst notifies the QC laboratory that the sample is available for testing by completing the handoff field in the log and signing.

Records generated (specimen)

In this specimen every step has one actor, one action, an acceptance criterion where one is needed, and a defined failure path. The form ID is named so the record is under document control. Each recording action is tied to the time of performance. That is the bar a completed SOP should clear.

Common inspection findings this template prevents

• Procedures with no version, effective date, or “page x of y”, so a missing page or an out-of-date copy goes undetected.
• Passive-voice steps with no named actor, so each role assumes someone else performs the step.
• Acceptance values buried in an appendix or absent entirely, leaving steps unauditable.
• Decision points with no defined failure path, so operators improvise and deviations follow.
• Forms referenced by the SOP that are uncontrolled or unversioned.
• Records sections that omit storage location or retention period.
• Revision history entries like “updated for clarity” that prevent reconstruction of past requirements.
• Responsibilities listing roles that never appear in the steps.

How to adapt this template

1. Copy this file, set your document number, owner, author, and effective date in the header to match your numbering scheme.
2. Delete every italic “Author note” line before issue; they are guidance, not procedure text.
3. Write section 8 first to the conventions in the author notes, then complete sections 1 to 7 and 9 to 13 around it.
4. Replace the specimen entirely; it is an illustration, not a starting point for content.
5. Point every cross-reference (deviation, change control, retention schedule) at your real procedure IDs.
6. Run the draft past a real user who did not write it before approval; every hesitation is a defect to fix.
7. Confirm every regulation in the References block against its current published version before issue.