Compendial Methods: GMP Obligations and Verification
Share

Compendial analytical methods: what that really means, and how to make them GMP-proof
“It’s in the pharmacopoeia, so we’re covered.”
This is one of the most dangerous statements in a QC laboratory, because it confuses three different concepts: regulatory status, original compendial validation, and suitability at your own site. The GuideGxP guide makes this point clearly: a compendial method is validated at origin, but the user must verify its suitability and transfer it correctly under actual conditions of use.
An analytical method is “compendial” when it is described in an official recognized compendium, such as USP, Ph. Eur., JP, and others. It is often mandatory if there is a monograph applicable to your product and market. It does not require full revalidation, but it does require method verification, line-by-line aligned SOPs, control of deviations, and management of pharmacopoeial updates.
Contents
- Definition: what makes a method “compendial”
- When it is mandatory, and what happens in multi-market scenarios
- “Already validated” does not mean “blindly adoptable”: method verification
- When you can deviate: flexibility versus regulatory approval
- Roles and responsibilities: QC, QA, and QP, and why inspectors separate them
- How to build a pharmacopoeial management system: update → change → training
- Multi-pharmacopoeia strategy: one method or two-track approach
- Audit-ready documentation package: what to prepare before you are asked
- FAQ
1) What makes a method “compendial”
A method is compendial when it is described in:
- a monograph, for substance or product
- or an official general chapter,
- in a compendium recognized by authorities, such as USP or Ph. Eur.
Critical point: because it is official, it has a special regulatory status. Authorities expect you either to apply it correctly or to have a justified and, where required, authorized alternative.
2) When it is mandatory, and what happens in multi-market scenarios
In practice, it is mandatory when:
- your product is covered by an applicable monograph in the destination market
- and that compendium is legally recognized as the standard, such as Ph. Eur. in the EU or USP in the US, especially where the label claims compliance
Multi-market: the complexity multiplier
If you release batches for EU + US, you may need to demonstrate compliance with more than one compendial requirement. In some cases, that results in different methods for the same parameter, for example dissolution, if the monographs are not aligned.
3) “Already validated” does not mean “blindly adoptable”: method verification
Pharmacopoeias state that methods are validated according to accepted practices. At the same time, they explicitly require the user to confirm suitability under real conditions. The guide strongly emphasizes this user responsibility and the need to transfer the procedure correctly.
What robust verification should include, without turning it into a full validation
For a compendial method, a pragmatic and defensible verification often includes:
- system suitability, where applicable, and confirmation of instrument performance
- specificity and interference assessment, including excipients, colorants, and degradants
- precision, such as repeatability on the same lot and same day
- critical execution aspects, such as filter, degassing, and sample stability
- line-by-line comparison between the internal SOP and the compendial text, to avoid gaps introduced during internal procedure writing
Audit rule: if you cannot show a rationale and minimum evidence of verification, the inspector’s question, “How do you know this works here?”, remains unanswered.
4) When you can deviate from the official method, and when you cannot
The guide defines a boundary that is often non-negotiable during audits:
Deviations or alternatives are acceptable only with solid scientific justification and, where required, regulatory approval through the dossier or variation process.
“Small” deviations that have high audit impact
Typical examples include a different filter, a sinker, or small operational adjustments. Even these must be managed through:
- change control
- impact assessment
- comparative data, where needed
- QA and QP approval, and RA alignment where registered content is affected
5) Roles and responsibilities: QC, QA, and QP
One of the fastest ways to lose credibility during inspection is to have inconsistent answers across functions. The guide distinguishes these roles operationally:
QC, Quality Control
- performs the tests and must have SOPs that faithfully reflect the compendium
- trains analysts on the critical method
- conducts the first part of the investigation in case of OOS or anomaly, often called Phase I, together with QA
QA, Quality Assurance
- governs the system, including procedure approval, control of pharmacopoeial updates, and data integrity review
- oversees deviations and OOS and authorizes justified retesting where applicable
QP, Qualified Person, EU context
- certifies that the batch meets legal requirements and marketing authorization commitments
- in multi-market situations, must clearly understand how compliance with multiple standards is ensured, for example one stricter harmonized method or dual testing, and must be able to demonstrate it
6) Pharmacopoeial management system: update → change → training
Inspectors often ask: “How do you manage USP or Ph. Eur. updates?”
A GMP-proof system includes:
- update monitoring, usually by QA or a dedicated function
- impact assessment by product and method
- opening a change control if the SOP or method must be updated
- documented training before operational implementation
- evidence of effectiveness, for example focused internal audit or review of batch records
7) Multi-pharmacopoeia strategy: one method or a two-track approach
The guide describes two defensible models:
A) Two-track approach, maximum formal compliance
You perform distinct tests for distinct requirements.
Pros: hard to challenge formally, because you have done everything separately
Cons: higher complexity, more operational risk, and possible discordant results that must be explained
B) One harmonized method, efficiency plus strong governance
You choose conditions that cover both requirements, often by taking a worst-case approach supported by comparative data and risk assessment, using ICH Q9 and Q4B as the framework.
Pros: fewer operational errors, better global standardization
Cons: requires excellent documentation and strong RA alignment
8) Audit-ready documentation package, QA checklist
If you want to reduce findings, prepare these before anyone asks for them:
- signed and approved comparison between internal method and compendium
- method verification report
- change control records for modifications and updates
- matrix of products × markets × applicable compendia
- training records for analysts
- examples of well-executed batches with traceable raw data
FAQ
If a monograph exists, can I use an internal method?
Yes, but only if justified and, where required, authorized in the dossier. You cannot ignore the official standard without governance.
Who should own the pharmacopoeial update process?
Typically, QA governs the system, QC implements it in the laboratory, RA evaluates dossier impact, and QP confirms that release remains compliant.
If you want a complete operational framework for implementing compendial methods without gray zones, including verification, management of USP versus Ph. Eur. differences, audit-ready checklists, and a risk-based setup, the guide “Guide to Pharmacopoeias: Dissolution Testing and Compendial Methods” is available on guidegxp.com.
