The misunderstanding that generates “free” findings

“It is an official method, so it works.”
In an audit, that sentence is an invitation to a finding. The guide highlights that the absence of method verification is one of the most frequent observations (“compendial methods not verified”), because a method — even if compendial — may behave differently in your laboratory (equipment, reagents, matrix, analysts, environmental conditions).

Verification vs Validation: how to explain it in 30 seconds (without getting stuck)

In an audit, you need a clear distinction (practical, not academic):

• Method validation: you demonstrate that a method (often developed internally or significantly modified) is suitable for its intended use.
• Method verification (compendial): you demonstrate that the adopted compendial method is executable and performs adequately in your real context (product/matrix, equipment, set-up).

When verification is practically “non-negotiable”

From an inspection perspective, the need for verification increases when:

• the matrix is complex (oily, high excipient content, etc.);
• you change equipment/column/kit compared with the typical context;
• the method is critical for release (assay, impurities, dissolution, microbiology);
• you have made even small operational changes (that still affect critical parameters).

Structure of an “audit-proof” dossier: what it must contain

If you want the verification to close the inspector’s question, build it as a standardized mini-dossier:

1) Cover page + purpose + references

Product/material, test, compendial reference (chapter/monograph), applied version.
Statement of intent: “To verify the suitability of the compendial method under the laboratory conditions.”

2) Gap assessment versus the compendium

• What you apply as is.
• What differs (even just equivalent column, different reagent, software).
• Technical rationale + risk statement.

This point is essential because the guide identifies undocumented deviations and generic SOPs as red flags.

3) Experimental design (risk-based)

The guide suggests a lean approach: repeat key studies such as precision/specificity and, where relevant, linearity.

Example of a minimum set (to be adapted to the test):

• Precision (repeatability): replicates on real sample (and/or spiked standard).
• Specificity: matrix interferences/known impurities where applicable.
• Linearity/range: if the method is quantitative and the risk requires it (e.g. assay).
• System suitability: demonstrate that the compendial criteria are met and recorded (SST records always available).

4) “Defensible” acceptance criteria

Golden rule: define criteria before performing the study, not afterwards.
If the inspector hears “we looked at it and it seemed okay”, the probability of a finding increases.

5) Execution + raw data + deviations

• Complete raw data (chromatograms, integrations, calculations, instrument logs).
• Deviation management (if something happens during the study, it must be traceable).

6) Report + conclusion + approvals

• Clear conclusion: “Method suitable / suitable with limitations / not suitable”.
• QA approval.
• Analyst training and go-live date.

The 5 red flags that trigger follow-up questions

From the guide, the most common are:

• Undocumented deviations (“we changed the mobile phase/column because it works better this way”).
• Outdated pharmacopoeial version.
• SST not recorded or not archived.
• SOP too generic (not reproducible).
• Untrained personnel (unable to explain differences and rationale).

“We had to adapt the method”: how to say it without scoring an own goal

If you changed something, the guide is clear: without justification and comparative data, this is a typical finding.

In an audit, the safest formula is:

• I declare the difference (transparency).
• I show the rationale (scientific).
• I show the data (comparability/verification/validation).
• I show QA governance (change control + approvals).
• I show that regulatory impact has been managed (if applicable).

Mini-script: inspection questions and “good” answers

Q: “Where is the verification of the USP/Ph. Eur. method?”
A: “We have a verification dossier for each critical compendial method: here are the protocol, raw data, and QA-approved report. We verified the highest-risk parameters in our context.”

Q: “Why are you using a different column?”
A: “It is an equivalent column; we documented the assessment and demonstrated that SST and performance are comparable. Here are the comparative data and the change control.”

Quick checklist (to post in the laboratory)

• I have identified the correct and current compendial version
• I have performed a gap assessment and documented differences
• I defined acceptance criteria before execution
• I archived raw data + SST + calculations
• QA approved the report and go-live
• Training completed and recorded

If you want ready-to-use support for building defensible dossiers (structure, checklists, and inspection logic), the full guide includes the roadmap and practical examples for preparing for multi-region inspections.