Verifying Compendial Analytical Methods: How Much Is Enough?

Any lab that runs pharmacopeial chemistry methods eventually ends up in the same debate. You have a USP assay or related substances method, you know it has to be “verified” before routine use, and the questions start: which validation parameters do we repeat? Is accuracy enough, or do we need linearity too? Are we accidentally revalidating the whole method?

USP <1226> Verification of Compendial Procedures does not settle the argument, partly by design. This guide explains why verification is required, why the guidance is deliberately general, and a practical way to decide what to test: think about what an auditor will ask for, and work backwards.

Why Verify a Method That Is Already Validated?

Compendial methods are validated by USP or the method sponsor, but not on your product, in your lab, with your instruments and analysts. Several things can change how a method performs:

• Matrix. Excipients, antioxidants, buffers, coatings or container extractables can co-elute with the analyte, suppress recovery or create new peaks.
• Material source. Impurity profiles differ between suppliers, and a different synthetic route can produce impurities the monograph never anticipated.
• Lab conditions. Instruments, columns, reagents, water quality and environment vary from site to site.
• People. Analyst training and experience affect how reliably a complex method runs.

US drug regulations make the expectation explicit: 21 CFR 211.194(a)(2) states that the “suitability of all testing methods used shall be verified under actual conditions of use.” USP <1226> was written to explain how to meet that requirement for compendial methods. Other pharmacopoeias have followed: Ph. Eur. general chapter 5.26 Implementation of Pharmacopoeial Procedures, in force since January 2023, sets out a two-step approach of first assessing the factors that could affect performance in your lab, then verifying experimentally where needed.

Regulators do follow up. FDA warning letters cite labs for failing to establish the accuracy, specificity, sensitivity and reproducibility of their test methods (21 CFR 211.165(e)), including labs using in-house versions of compendial methods without showing equivalence.

“Verification isn’t about proving the method works. USP already did that. It’s about proving it works here.”

The Challenge: <1226> Is General by Design

Compare <1226> with its sister chapter, <1225> Validation of Compendial Procedures, which sets out the performance characteristics (accuracy, precision, specificity, detection and quantitation limits, linearity, range and robustness) and which apply to each category of method. <1226> takes a lighter touch. It says that:

• Full revalidation is not required; verification should assess selected characteristics.
• The extent of verification depends on the complexity of the procedure and the material, and on the lab’s training and experience.
• For chromatographic methods, specificity is key and may be shown partly by meeting the monograph’s system suitability requirements; impurity methods may also call for detection or quantitation limits and precision.
• Basic tests such as loss on drying, residue on ignition, acid value and pH generally don’t need verification unless there is reason to doubt their suitability for the article.

What it does not say is exactly which experiments to run, how many replicates, or what acceptance criteria to use. As one industry review put it, there is no absolute guidance for verification requirements, so each company sets its own approach (Schniepp and Lynn, 2022).

That flexibility is intentional. No single recipe could cover both a simple titration of a pure active and a gradient HPLC impurity method for a multi-component tablet. The cost of that flexibility is debate: QC, QA, clients and contract labs often disagree on where “verification” ends and “revalidation” begins.

A Risk-Based, Case-by-Case Assessment

The way through is to treat verification as a documented risk assessment rather than a checklist. For each method, ask:

• How complex is the method? A gradient HPLC with multiple impurities carries more risk than a UV assay or a titration.
• How complex is the sample? A pure active ingredient is low risk; a multi-ingredient tablet, cream or botanical supplement is high risk.
• What could interfere? Excipients, degradants, impurities from a new supplier, preservatives, colourants and other actives.
• What decision does the result support? Release and stability results on critical quality attributes deserve more scrutiny than information-only tests.
• What do we already know? Prior verification on a similar formulation, method transfer data, or the lab’s experience with the technique.

The answers determine which <1225> characteristics are worth testing experimentally and which can be justified on paper. In most chromatographic methods, specificity in your matrix is the central question, with accuracy, precision and sensitivity added as the risk warrants. And “simple” methods are not always simple: a Karl Fischer water determination, for example, can be thrown off by sample components that react with the reagent or will not dissolve.

Strategies and Approaches

• Start with a gap assessment. Compare the monograph, your product and your lab set-up. Document what differs from the conditions the method was validated under, and why each difference does or does not matter.
• Write a protocol with predefined acceptance criteria. Criteria chosen after the data are in are the first thing an auditor will question. Base them on <1225> conventions, the monograph’s system suitability and the product specification.
• Scale effort with risk. A tiered approach keeps low-risk methods light and focuses experimental work on complex methods and difficult matrices.
• Use what you already know. Prior verifications on similar formulations, method transfer data and supplier information can reduce new work, as long as the link is justified in writing.
• Group similar products. Where formulations share a matrix and concentration range, one well-designed verification can sometimes cover several products.
• Know when to reassess. Monograph revisions, a new ingredient supplier, formulation or process changes, or a move to a new site should all trigger a fresh look. Ph. Eur. 5.26 explicitly expects re-evaluation when a monograph changes.
• Think lifecycle. USP <1220> Analytical Procedure Life Cycle and ICH Q2(R2) and Q14 frame verification as one stage in managing a method over time, followed by ongoing monitoring of performance.

Work Backwards From the Audit

The most practical test of a verification plan is to picture an inspector reading it. Auditors typically ask:

• Is this the current official method, and how do you track monograph revisions?
• Where is your rationale? Why did you test these characteristics and not others?
• Were acceptance criteria set in advance, in an approved protocol?
• Does the data show the method works in your matrix? Show me the blank or placebo, the specificity data and the recovery.
• Who ran it? Were they trained, and were the instruments qualified and calibrated?
• What happened to deviations or failed runs?
• If you changed anything from the monograph, how did you show it is equivalent or better?

If your verification package answers each of those questions clearly, you have done enough. If it cannot answer one of them, no number of extra experiments will make up for the gap. That is also the best way to end the internal debate: the question is not “how many parameters did USP say?” but “can we defend this decision to an inspector?”

What This Means for Your Lab

Compendial method verification is required, but it is meant to be proportionate. Treat it as a risk-based, documented assessment, focus experimental work on what could go wrong in your matrix and lab, and justify the rest in writing. That avoids both extremes: revalidating methods USP has already validated, and doing so little that an auditor cannot follow your reasoning.

For the microbiology side of the same question, see our guide to microbiology method suitability studies. Terraforme Biosciences helps manufacturers and contract labs build defensible analytical quality systems, including verification and transfer strategies, protocols and SOPs, and audit readiness. Learn more about our quality management services.