A well-built SOP format for the pharmaceutical industry is the difference between a procedure that actually drives operations and a document nobody reads but everybody signs. In GMP, a standard operating procedure is not a formality: it is how a company demonstrates that every critical activity is performed the same way, every time, by trained people, with reconstructable evidence. This article walks through the reference structure of a pharmaceutical SOP — section by section — the regulatory requirements the format must satisfy, and the most common mistakes inspectors spot at first glance.
What regulations require from a pharmaceutical SOP format
The European reference is Chapter 4 (Documentation) of EudraLex Volume 4, mirrored almost identically in the PIC/S PE 009 guide. Procedures are defined there as instructions giving directions for performing certain operations, and the chapter sets the requirements every template must guarantee:
- documents containing instructions must be approved, signed and dated by appropriate, authorised persons (§4.3);
- content must be unambiguous, with title, nature and purpose clearly stated and a defined effective date (§4.3);
- SOPs, work instructions and methods must be written in an imperative mandatory style, with short, checkable steps (§4.4);
- §4.29 lists the activities for which procedures must exist: validation, calibration, maintenance, cleaning, training, environmental monitoring, complaints, recalls, change control, deviation management, self-inspections and supplier audits.
On the FDA side, 21 CFR 211.100 requires written procedures for production and process control, drafted, reviewed and approved by the relevant organisational units including the quality unit; any departure from a procedure must be recorded and justified in writing. The format, in other words, is not an aesthetic choice: header, signatures, revision control and writing style all flow directly from these requirements.
The reference structure: the sections of an SOP template
No regulation imposes a single format, but established pharmaceutical industry practice converges on a structure that covers all Chapter 4 requirements. The table summarises the typical sections of an SOP template and the function of each.
| Section | Content | Typical mistake |
|---|---|---|
| 1. Purpose | Why the procedure exists and what outcome it guarantees | Generic purpose copied from other SOPs |
| 2. Scope | Areas, departments, products and stated exclusions | Undeclared exclusions: the SOP "applies to everything" |
| 3. Responsibilities | Who performs, who checks, who approves (roles, not names) | Personal names instead of roles: obsolete at the first turnover |
| 4. Definitions and abbreviations | Technical terms and acronyms used in the text | Unexplained acronyms, inconsistent across SOPs |
| 5. Materials and related documents | Equipment, forms, SOPs and regulatory references cited | References to withdrawn or never-issued documents |
| 6. Procedure (body) | Numbered steps, imperative style, in order of execution | Descriptive paragraphs instead of verifiable instructions |
| 7. Handling of deviations | What to do when a step cannot be executed as written | No link to the deviation procedure |
| 8. Records and attachments | Forms to complete, where they are filed, for how long | Attachments not version-controlled with the SOP |
| 9. Revision history | Version, date, nature of the change, author | "General revision" with no description of what changed |
The template should be scaled to the complexity of each procedure: a balance calibration SOP does not need the same depth as a deviation management SOP. What is non-negotiable is consistency: the same sections, the same order and the same terminology across the entire document system, so that anyone moving from one procedure to another always knows where to find responsibilities, acceptance criteria and associated records. It is also the simplest way to make training effective: you teach the format only once.
Want weekly, hands-on content like this — templates, checklists and mistakes to avoid on GMP documentation? Subscribe to The Pragmatic GMP, GuideGxP's free weekly newsletter.
Header and document control
The header is the SOP's identity card and must appear on every page. The minimum elements are the company logo or name, the document title, the unique identification code from the company numbering system, the version number, the effective date and "page X of Y" numbering. The signature block — who drafted, who reviewed, who approved, with dates — puts the §4.3 requirement into practice: without signatures from authorised persons, the document is simply not an SOP; it is a draft.
The template must then live inside a document control system: controlled distribution of copies, systematic retrieval of superseded versions, a defined review period (typically every 2-3 years, or following change control) and traceability of who received and read the document. An SOP that is perfect on paper but found on the shop floor in a superseded version is a finding ready for the inspection report.
How to write the body of the procedure
Chapter 4, §4.4 calls for an imperative, easily checkable style — and this is where most templates fail. Some practical rules:
- One step, one action: "Weigh 100 g of sample", not "the sample is weighed and subsequently transferred".
- Number the steps in the real order of execution, verified on the floor with the people who actually use the procedure.
- State explicit acceptance criteria wherever a decision is needed: limits, ranges, tolerances.
- Avoid chained cross-references ("as described in SOP X, which refers to SOP Y"): every reference is a breaking point.
- Plan for failure: what the operator does if a result is out of criteria or a piece of equipment does not respond.
Finally, the principle of 211.100(b) applies: the procedure must be documented at the time of performance. If the template does not include record forms that can be completed in real time, the SOP will systematically generate backdated records — one of the most frequent data integrity findings.
GuideGxP recommendation
Before writing any new SOP, define your company template once — header, sections, style, signature block — and make it binding with an "SOP on SOPs" that mandates its use. Then test every new procedure in the field: have it executed by an operator who did not write it, time the ambiguous steps and correct them before issue. An SOP that requires interpretation is a deviation waiting to happen. And remember that inspectors judge a documentation system by its consistency: ten SOPs in ten different formats tell the story of a quality system that does not govern its own documents.
If you need a concrete starting point, the GuideGxP catalogue includes professional SOPs already structured to this format and ready to adapt to your quality system — for example the SOP CAPA GMP | Corrective and Preventive Action, complete with forms and an audit-ready workflow.
