Difference between GMP and SOP: it is one of the most common questions for anyone entering the pharmaceutical industry, and one of the most expensive confusions for those already working in it. The short answer: GMP (Good Manufacturing Practice) are the manufacturing standards issued by regulatory authorities, defining what a pharmaceutical company must guarantee to produce quality medicines; SOPs (Standard Operating Procedures) are the documents a company writes internally to define how those requirements are met, step by step, in its own real-world context. The former are the regulatory framework, the latter the implementation tool. In this guide we compare the two levels, with the official references and the findings inspectors raise most often when the link between standards and procedures breaks down.
Difference between GMP and SOP: the definitions
GMP are the set of requirements ensuring that medicinal products are consistently produced and controlled to quality standards appropriate to their intended use. Companies do not write them: authorities issue them. In the European Union the reference is EudraLex Volume 4, the European Commission's collection of GMP guidelines, based on Directive 2001/83/EC and Commission Directive (EU) 2017/1572 for human medicines. Volume 4 is structured into Part I (basic requirements for medicinal products, nine chapters from the Pharmaceutical Quality System to Self Inspection), Part II for active substances, Part III with related documents, and a series of topic-specific Annexes. In the United States the equivalent is FDA's CGMP, codified in 21 CFR Parts 210 and 211, while internationally the PIC/S PE 009 guide harmonises requirements across participating inspection authorities.
SOPs, by contrast, are internal documents. EU GMP itself defines them: Chapter 4 "Documentation" lists them among the "instructions" type of documents and describes them as Procedures (otherwise known as Standard Operating Procedures, or SOPs), i.e. documents that give directions for performing certain operations. An SOP is drafted, reviewed and approved by the company through its own quality system; once approved it is binding on anyone performing that activity, and any departure from it must be managed as a deviation.
Standards and procedures compared
The table summarises the differences that really matter in daily practice and during inspections:
| Aspect | GMP | SOP |
|---|---|---|
| Who issues them | Authorities and legislators (European Commission, FDA, PIC/S) | The company, with internal drafting, review and approval |
| Nature | Requirements and principles: they say what to guarantee | Operating instructions: they say how to perform activities |
| Status | Regulatory obligation, a condition for the manufacturing authorisation | Binding internal document: not following it is a deviation |
| Scope | Every company in the regulated sector | The specific site, department or process |
| Language | General, principle-based, expectation-driven | Specific, step-by-step, tied to real roles and systems |
| Updates | Regulatory revisions (new chapters and Annexes) | Internal change control and scheduled periodic review |
| Examples | EudraLex Volume 4, 21 CFR Part 211, PIC/S PE 009 | Deviation management SOP, cleaning SOP, training SOP |
One example clarifies the relationship between the two levels better than any definition. 21 CFR 211.100(a) requires written procedures for production and process control, designed to assure the identity, strength, quality and purity of drug products; 211.100(b) adds that those procedures must be followed and that any deviation must be recorded and justified. The regulation thus mandates that procedures exist and are followed, but says nothing about how they should be written: that is exactly the job of the SOP. GMP creates the obligation, the SOP turns it into practice.
Regulations change, procedures need updating: keeping the two levels aligned is continuous work. With The Pragmatic GMP, GuideGxP's free weekly newsletter, you get the latest GMP regulatory news already translated into concrete actions for your SOPs: subscribe and turn every regulatory revision into a managed update, not a surprise.
How SOPs implement GMP: the document pyramid
In a well-built pharmaceutical quality system, standards and procedures meet inside a documentation hierarchy. The classic scheme, consistent with EU GMP Chapter 4 and the ICH Q10 Pharmaceutical Quality System model, has four levels:
- System documents: the quality manual or PQS description document and the Site Master File, describing how the company interprets GMP requirements in its own context.
- SOPs: the procedures governing recurring, cross-functional processes — deviation management, change control, training, cleaning, supplier qualification.
- Instructions and operational documents: work instructions, manufacturing formulae, processing, packaging and testing instructions, protocols and specifications, which bring the procedure down to the individual product or piece of equipment.
- Records: the evidence that what was planned was actually done — batch records, log books, certificates of analysis, reports.
The principle holding the pyramid together is familiar to every auditor: say what you do, do what you say, and be able to prove it. Every applicable GMP requirement must map to a procedure that implements it; every SOP must be traceable to a requirement or a real process need; every execution must leave a record. When one of these links is missing, that is exactly where the chain breaks during an inspection.
The most common findings when GMP and SOPs get confused
- The copy-paste SOP: copying whole paragraphs of the GMP text without adapting them to the real process produces unusable procedures that nobody follows, because they do not describe the actual work.
- Practice diverging from procedure: the classic finding; if the operator works differently from what is written, either the SOP is wrong or the execution is out of control — and both cases require action.
- SOPs not updated after a regulatory revision: a new Annex or a chapter revision must trigger, through change control, a review of the impacted procedures.
- Treating SOPs as "paperwork": a procedure experienced as a formality will be written for the inspector rather than for the user, and will end up protecting neither the product nor the company.
- Undocumented training: an approved SOP without documented training is, in an inspector's eyes, a procedure that does not exist.
GuideGxP recommendation
Never start from the question "how many SOPs do we need?", but from "which requirements must we implement and which processes do we actually have?". Build a coverage matrix linking every applicable GMP chapter and Annex to your procedures: you will find uncovered requirements and, almost always, duplicated or orphan procedures. Write every SOP for the person executing it, not for the person inspecting it: short sentences, clear roles, explicit decision points. And before approval, have the people who will use it test it on the floor: ten minutes of real-world trial are worth more than three rounds of document review.
If you want to start from a solid base instead of a blank page, browse our catalogue of ready-to-use GxP manuals and templates: operational guides and toolkits already structured around EU GMP requirements, designed to be adapted to your processes.
