Muhammad Raheel
Sr. Manager Validation Abbott, Pakistan
Introduction
Every pharmaceutical product is judged by the results of analytical tests. Assay, related substances, dissolution, content uniformity, and identification tests decide whether a batch is released, whether a stability study supports a shelf life, and whether a generic product is equivalent to its reference. If the method behind a result is not reliable, the result is not reliable either.
Analytical method validation is the process of demonstrating, through documented laboratory studies, that a method is suitable for its intended purpose. It is a regulatory expectation under GMP, and it is also good science. A validated method protects patients, protects the company from costly out-of-specification investigations, and gives analysts confidence in what they report.
This article walks through validation step by step, from defining the purpose of the method to maintaining it over its lifecycle, and explains what each validation parameter means and how it is tested in practice.
What Is Analytical Method Validation?
Validation answers one question: is this method fit for its intended use? The answer is never “yes” or “no” in the abstract. It depends on what the method is for. A method to quantify the active ingredient in a tablet needs different performance characteristics than a method to detect a trace impurity at 0.05%.
Three related terms are often confused:
- Method development is where the procedure is designed and optimised: choosing the column, mobile phase, wavelength, sample preparation, and so on.
- Method validation is the formal demonstration that the finished method meets predefined criteria.
- Method verification applies to a compendial or already validated method used for the first time in a new laboratory. The lab confirms that the method performs as expected under its own conditions, without repeating the whole validation.
A fourth term, method transfer, describes the documented process of qualifying a receiving laboratory to use a validated method from another site.
Modern guidance, especially ICH Q14 and the revised ICH Q2(R2), treats these as connected stages of one analytical procedure lifecycle, not isolated events. Validation is a key milestone, but it is not the end of the story.
When Is Validation Required?
Validation is expected for methods used to release and monitor drug substances and drug products. It is typically required:
- Before a new method is used for routine GMP testing
- When a method is changed beyond its approved range, for example a new column type, a different detection principle, or a change in the sample matrix
- When the product formulation or manufacturing process changes in a way that could affect the method
- When a compendial method is used outside its stated scope
Which parameters you validate depends on the type of method. ICH categorises analytical procedures broadly as:
- Identification tests
- Quantitative tests for impurities
- Limit tests for impurities
- Assay, including dissolution (measurement only) and content or potency
An identification test needs mainly specificity. An assay needs accuracy, precision, linearity, range, and specificity. A quantitative impurity method needs all of these plus a limit of quantitation.
Step 1: Define the Purpose and Performance Requirements
Validation starts before any experiment. The first step is to write down clearly what the method must achieve. ICH Q14 calls this the Analytical Target Profile (ATP): a statement of what is to be measured, over what range, and with what required quality of result.
A simple ATP might read: “Quantify drug X in 250 mg tablets over 80–120% of the label claim, with accuracy within ±2% and precision of not more than 2% RSD, in the presence of excipients and known degradation products.”
Defining this up front has two benefits. It guides method development toward the right design, and it gives you objective acceptance criteria, so you are not deciding after the fact whether the data “look good enough.”
Questions to settle at this stage:
- What is the analyte, and in what matrix?
- What concentration range must be covered?
- Is the method for release, stability, cleaning verification, or in-process control?
- What are the specification limits, and how tight must the method be to make sound decisions against them?
Step 2: Develop and Optimise the Method
A method that is poorly developed will struggle in validation. Good development includes understanding how the method behaves before you commit to formal studies. This usually means:
- Selecting the technique (HPLC, GC, UV, dissolution, titration, and so on) on the basis of the analyte’s properties
- Optimising chromatographic conditions, sample preparation, and detection
- Running forced degradation (stress) studies to generate degradants and confirm the method can separate them from the main peak
- Evaluating the robustness of key parameters early, for example pH, column temperature, and flow rate, using structured experiments (design of experiments) where appropriate
- Defining system suitability criteria that will confirm the system works correctly on each day of analysis
Documenting the development work matters. Inspectors often ask how the final conditions were chosen, and a well-written development report is the best answer. It also supports later changes within an established range.
Step 3: Conduct a Risk Assessment
Before writing the protocol, consider which parts of the method are most likely to affect the result. A simple risk assessment, using a fishbone diagram or an FMEA, can identify critical variables such as sample preparation, extraction time, filter type, standard stability, or column batch.
Risk assessment helps in two ways. It shows which robustness factors deserve testing, and it helps define appropriate controls in the final method. The depth of validation should reflect the risk: a stability-indicating impurity method for a potent drug deserves more rigor than a simple identification test.
Step 4: Write the Validation Protocol
A validation protocol is an approved document, written and signed before experiments begin. It is the plan against which results will be judged. A good protocol includes:
- Title, objective, and scope, and the method being validated
- The analytical procedure, with reference to the approved version
- The responsibilities of the people involved
- Materials: reference standards (with purity and potency), reagents, samples, and placebo
- Instruments and equipment, with confirmation they are qualified and calibrated
- The validation parameters to be tested, the design of each experiment, and the predefined acceptance criteria
- How deviations will be handled
- How results will be calculated and reported, including any statistical tools
Setting acceptance criteria before you see the data is essential. Criteria written afterwards, to fit the results, are a serious data integrity concern. If a criterion must change, it should be done through a documented protocol amendment with justification.
Step 5: Confirm Equipment Readiness and System Suitability
Before generating validation data, confirm that all instruments are qualified and calibrated, that analysts are trained, and that reference standards and reagents are in date. Validation data generated on uncontrolled equipment has no value.
System suitability testing (SST) is performed at the start of each analytical run, including every validation experiment, to confirm the whole system works on that day. Typical SST parameters for HPLC include:
- Resolution between critical peaks, often ≥ 2.0
- Tailing factor, often ≤ 2.0
- Theoretical plates (column efficiency)
- Repeatability of replicate standard injections, often RSD ≤ 2.0% for assay
SST is not a substitute for validation, but it proves that the validated conditions are working when the method is used.
Step 6: Execute the Validation Parameters
This is the core of validation. The following parameters are defined in ICH Q2 and widely followed by regulators, including the USP and WHO. Not every parameter applies to every method, and the protocol should state which are included and why.
6.1 Specificity (Selectivity)
Specificity is the ability to measure the analyte unequivocally in the presence of other components that may be present: impurities, degradation products, excipients, and matrix.
How it is tested:
- Inject blank, placebo, standard, and sample, and show no interference at the analyte’s retention time
- Spike the sample with known impurities and degradants and show adequate resolution
- For stability-indicating methods, analyse stressed samples (acid, base, oxidation, heat, light) and demonstrate peak purity using a photodiode array or mass spectrometry detector
- Check that the analyte peak is pure and that mass balance is reasonable
If a method is not specific, none of the other parameters mean much, so this is usually evaluated first.
6.2 Linearity and Range
Linearity is the ability to obtain results that are directly proportional to the analyte concentration. The range is the interval between the lowest and highest concentration for which the method has suitable accuracy, precision, and linearity.
How it is tested:
- Prepare at least five concentration levels across the intended range
- Plot response against concentration and calculate the regression line: slope, intercept, and correlation coefficient (r or R²)
- Examine the residual plot, not just the correlation coefficient, since a high r can hide curvature
Typical ranges, which should be justified for the specific method:
- Assay of drug substance or product: 80–120% of the test concentration
- Content uniformity: 70–130% of the test concentration
- Dissolution: ±20% over the specified range of the profile
- Impurities: from the reporting level to 120% of the specification limit
A common acceptance criterion for linearity is r ≥ 0.999 for assay, with y-intercept not significantly different from zero. Criteria should match the method’s purpose.
6.3 Accuracy
Accuracy is the closeness of the measured value to the true value, or to an accepted reference value.
How it is tested:
- For drug products, spike placebo with known amounts of the active ingredient at three levels (for example 80%, 100%, and 120%), with three replicates at each level, for at least nine determinations
- For impurities, spike the sample with known amounts of the impurity across the range
- Calculate the percentage recovery and its confidence interval
For an assay, recovery within 98.0–102.0% is a common expectation. For impurities at low levels, wider limits are acceptable and should be justified. Where a placebo cannot be prepared, comparison with a second well-characterised method may be used.
6.4 Precision
Precision is the closeness of agreement among a series of measurements from the same homogeneous sample. It has three levels:
- Repeatability (intra-assay precision): same analyst, same instrument, same day. Usually six determinations at 100% of the test concentration, or nine determinations across the range.
- Intermediate precision: variation within a laboratory, such as different days, analysts, and instruments. This shows the method stays consistent in normal routine use.
- Reproducibility: precision between laboratories, typically assessed during method transfer or collaborative studies.
Results are expressed as relative standard deviation (% RSD). For drug product assay, an RSD of not more than 2.0% is a common benchmark, while impurity methods at low levels may allow higher variability.
6.5 Detection Limit (LOD) and Quantitation Limit (LOQ)
The limit of detection is the lowest amount of analyte that can be detected but not necessarily quantified. The limit of quantitation is the lowest amount that can be measured with acceptable accuracy and precision.
These apply mainly to impurity and trace-level methods. Common approaches include:
- Signal-to-noise ratio: typically about 3:1 for LOD and 10:1 for LOQ
- Standard deviation of the response and the slope: LOD = 3.3σ/S and LOQ = 10σ/S
Whichever approach is used, confirm the LOQ experimentally by analysing samples at that concentration and showing acceptable accuracy and precision. The LOQ must also sit at or below the reporting threshold for the impurity.
6.6 Robustness
Robustness measures the method’s capacity to remain unaffected by small, deliberate variations in method parameters. It gives an indication of reliability during normal use.
Examples for HPLC: mobile phase pH (±0.2 units), organic composition (±2%), flow rate (±10%), column temperature (±5 °C), detection wavelength (±2 nm), and different column lots or brands.
Robustness is best studied during development, but it should be documented in the validation package. The results support setting meaningful SST limits and define which parameters the analyst must control carefully.
6.7 Solution Stability
A parameter that is easy to forget but often causes problems in routine testing is the stability of standard and sample solutions. Test solutions at intervals, such as 0, 12, 24, and 48 hours, under defined storage conditions, and confirm the results stay within an acceptable range of the initial value. This determines how long prepared solutions can safely be held, and it prevents invalid results caused by degradation on the autosampler.
Step 7: Evaluate Data and Apply Acceptance Criteria
When experiments are complete, compare every result against the criteria in the protocol. Good practice includes:
- Using validated calculations or software, and validated, locked spreadsheets where used
- Reviewing raw data and audit trails, not just summary tables
- Reporting all results, including any invalid runs, with justification
- Investigating any failure or unexpected result through a documented deviation
If a criterion is not met, the method may need to be modified and revalidated, or the criterion may need scientific re-evaluation through a formal amendment. Repeating experiments until a pass is obtained, without explanation, is unacceptable and is a classic data integrity failure.
Step 8: Write the Validation Report
The validation report summarises the work and concludes whether the method is suitable for its intended use. It should include:
- Reference to the protocol and the method version
- A summary of each parameter, with the results, acceptance criteria, and conclusion
- Representative chromatograms, spectra, and calibration plots
- Any deviations, and how they were resolved
- The final validated conditions, SST criteria, and the validated range
- Approval signatures from the analyst, reviewer, and quality assurance
A clear, accurate report is the document inspectors will review first. The raw data, notebooks, and electronic records must be retained and readily available to support every number in the report.
Step 9: Implement the Method under Change Control
Once validated and approved, the method is released for use through the quality system. Analysts are trained, the method becomes an effective controlled document, and any future change follows change control. Even a small change, such as a new column supplier or modified diluent, should be assessed to decide whether it needs partial or full revalidation.
For products that are filed with regulatory authorities, changes to the registered method may also need notification or approval.
Step 10: Manage the Method over Its Lifecycle
Validation is not a one-off. Over time, instruments age, reagents change, and products evolve. A good lifecycle approach includes:
- Ongoing performance monitoring: trending SST results, control sample results, and out-of-specification or out-of-trend investigations that point to method weakness
- Method transfer to other sites or laboratories, with a pre-approved protocol and comparative testing
- Verification of compendial methods in the user’s laboratory
- Revalidation when changes occur, or periodically where warranted by risk
ICH Q14 introduces the idea of an established condition and a structured approach to post-approval changes, which can make managing change more predictable when well-developed knowledge is documented.
Common Pitfalls in Method Validation
Even experienced laboratories encounter recurring problems:
- Starting validation before development is complete. A method that keeps changing during validation wastes effort and creates confusion.
- Vague acceptance criteria, or criteria defined after data are generated.
- Inadequate specificity studies, particularly missing forced degradation or peak purity for stability-indicating methods.
- Using the correlation coefficient alone to judge linearity.
- Ignoring solution stability, which later leads to unexplained variability in routine testing.
- Poorly characterised reference standards or expired materials.
- Unvalidated spreadsheets or uncontrolled processing of chromatographic data, including undocumented manual integration.
- Weak documentation, such as unsigned protocols, missing raw data, or inconsistent records.
- Treating validation as a paperwork exercise rather than understanding what the method can and cannot do.
Most of these can be avoided by planning carefully, involving experienced reviewers early, and applying data integrity principles throughout.
Practical Tips for a Smooth Validation
- Invest time in development. An hour of optimisation often saves days of failed validation.
- Write the protocol with the end in mind. Think about how each experiment will be executed and calculated, and let another analyst review the plan.
- Use a single, well-characterised batch of reference standard and samples where possible, to avoid unnecessary variability.
- Randomise and organise the run sequence so that days, analysts, and instruments are documented clearly for intermediate precision.
- Record everything contemporaneously, and retain all raw data, including failed runs.
- Review as you go. Checking results after each parameter allows issues to be fixed early, through documented deviations and not last-minute surprises.
- Keep the method simple enough to be routine. A method that only works in the hands of its developer is not a validated method in any practical sense.
Conclusion
Analytical method validation is the foundation for trustworthy pharmaceutical data. By following a structured approach, defining the purpose, developing a sound method, assessing risk, writing a protocol with predefined criteria, testing each relevant parameter, evaluating results honestly, reporting clearly, and managing the method through its lifecycle, laboratories can be confident that their results are accurate, reproducible, and defensible.
The regulatory landscape continues to evolve, with ICH Q2(R2) and Q14 placing more emphasis on scientific understanding, risk-based decisions, and lifecycle management. The underlying goal is unchanged: to show that a method does what it is meant to do, every time it is used. A well-validated method is an investment that pays back through fewer investigations, smoother inspections, and, most importantly, reliable assurance of medicine quality for patients.
Guideline References
- ICH. Q2(R2): Validation of Analytical Procedures. International Council for Harmonisation, adopted November 2023.
- ICH. Q14: Analytical Procedure Development. International Council for Harmonisation, adopted November 2023.
- ICH. Q2(R1): Validation of Analytical Procedures: Text and Methodology. November 2005 (superseded by Q2(R2) as it is implemented).
- U.S. FDA. Analytical Procedures and Methods Validation for Drugs and Biologics: Guidance for Industry. July 2015.
- USP. General Chapter <1225> Validation of Compendial Procedures; <1226> Verification of Compendial Procedures; and <621> Chromatography. United States Pharmacopeia.
- WHO. Guidelines on Validation, Appendix 4: Analytical Method Validation. WHO Technical Report Series No. 1019, Annex 3, 2019.
- European Commission. EudraLex Volume 4, EU GMP Guidelines, Annex 15: Qualification and Validation.
- EMA. ICH Guideline Q2(R2) on Validation of Analytical Procedures: Scientific Guideline. European Medicines Agency.
- U.S. FDA. Data Integrity and Compliance With Drug CGMP: Questions and Answers. December 2018.