Assay validation parameters are the documented performance characteristics you must demonstrate to prove an analytical method is fit for purpose, and the first practical step is to define the analytical target profile, or ATP, before any experiment begins. The core set includes specificity, accuracy, precision, linearity, range, detection limit, quantitation limit and robustness, with system suitability testing as the routine check that keeps the method in control. ICH Q2(R2), ICH Q14 and the Eurachem fitness-for-purpose guide are the three references worth keeping open while you plan.
TL;DR:
- Validation parameters like specificity, accuracy, and precision are essential mainly for quantitative methods, while qualitative identity tests require fewer parameters.
- Establishing the analytical target profile first ensures validation efforts are proportionate and aligned with the intended decision-making process.
- Robustness studies should use design of experiments to define the method operable design region, allowing flexible adjustments within validated ranges.
- System suitability testing should be planned early, with criteria based on validation data to continuously monitor the method’s routine performance.
- Proper documentation of validation experiments, criteria, and uncertainty is crucial for regulatory approval and ongoing lifecycle management.
Table of Contents
- Core validation parameters and how they map to your assay
- Designing accuracy, precision, linearity and range studies
- Proving specificity and managing matrix interference
- Robustness, PAR and MODR: turning development data into validated ranges
- Building a control strategy and setting system suitability criteria
- Writing the validation protocol and report
- Lifecycle management and what ICH Q14 changes for post-approval work
- A practical checklist from ATP to validation report
- Where ABMIUM fits into validation work
- A practitioner’s perspective on avoidable validation mistakes
- ABMIUM resources for your next validation project
- FAQ
- Sources
Core validation parameters and how they map to your assay
Every validation parameter answers a specific question about method performance, and not every assay needs all of them. A quantitative chromatographic method typically requires the full set; a qualitative identity test needs far less.
- Specificity or selectivity: the ability to measure the analyte without interference from related substances or matrix components.
- Accuracy (trueness): how close measured results sit to the true or accepted reference value.
- Precision: the spread of results across repeatability, intermediate precision and reproducibility conditions.
- Linearity: whether response is proportional to analyte concentration across a defined interval.
- Range: the interval between the lowest and highest concentrations shown to give acceptable accuracy and precision.
- Detection limit (LOD): the lowest amount of analyte that can be reliably detected, not necessarily quantified.
- Quantitation limit (LOQ): the lowest amount that can be quantified with acceptable accuracy and precision.
- Robustness: the method’s resilience to small, deliberate variations in operating conditions.
- System suitability testing (SST): routine checks confirming the system performs as validated on the day of use.
ICH Q2(R2) positions these characteristics as the standard reference for quantitative methods in clinical and nonclinical work, while bioanalytical methods governed by frameworks such as ICH M10 add matrix-specific requirements including calibration curve design and defined upper and lower quantitation limits. Stability-indicating assays lean heavily on specificity and forced-degradation data, since their job is to detect change over time rather than simply confirm identity.
The ATP should drive every one of these decisions. If the assay supports a release decision with a tight specification, precision and accuracy demands tighten accordingly; if it supports an exploratory screen, the acceptance criteria can reasonably widen. Defining the ATP first, as Eurachem recommends, keeps the validation plan proportionate to the decision it serves rather than defaulting to the most exhaustive protocol available.
Designing accuracy, precision, linearity and range studies
These four parameters are usually assessed together because they share experimental infrastructure: a calibration curve, a set of spiked or reference samples, and a statistical analysis plan agreed before data collection starts.
- Prepare calibration standards across at least five concentration levels spanning the intended range, consistent with the minimal experiment numbers Eurachem’s method validation leaflet sets out for linearity studies.
- Run accuracy and precision studies at a minimum of three concentration levels, typically low, medium and high within the range, each with multiple replicates on the same day to establish repeatability.
- Repeat the same design across different days, analysts or instruments to capture intermediate precision, and pool results with ANOVA to separate within-run from between-run variance.
- Back-calculate concentrations from the regression equation and compare them against nominal values to express accuracy as percentage recovery.
- Report precision as percentage coefficient of variation (%CV) at each level, and check that residuals from the regression are randomly distributed rather than showing curvature.
One of the most widely applied acceptance benchmarks comes from FDA bioanalytical guidance, which describes accuracy and precision within ±15% of nominal for most quality control levels and ±20% at the lower limit of quantitation. These figures are not universal law; they are the FDA’s own numerical expectation for bioanalytical and chromatographic methods, and a laboratory working to a different ATP can justify tighter or looser limits provided the rationale is documented in the validation plan.
Range is derived rather than tested in isolation: once linearity, accuracy and precision are all acceptable at the extremes of your tested interval, that interval becomes your validated range. Extending the range later means repeating the boundary experiments, not simply assuming the method still performs.
Regression analysis deserves its own line of scrutiny. A correlation coefficient close to 1 is necessary but not sufficient; plot the residuals, check for heteroscedasticity, and consider a weighted regression if variance increases with concentration, a pattern common in ligand-binding assays. FDA guidance also expects calibration curves to include a blank, a zero and enough non-zero levels to define the curve shape reliably, a point echoed in ICH M10 for ligand-binding and chromatographic bioanalytical methods specifically.
Where replicate numbers are constrained by sample cost or instrument time, document the statistical power you can achieve with the available replicates rather than silently reducing rigour. A smaller n with a transparent justification in the validation plan is defensible; an unexplained departure from the plan is not.
Proving specificity and managing matrix interference
Specificity and selectivity are often used loosely, but they answer different questions. Specificity asks whether the method responds to the target analyte alone; selectivity asks how well it distinguishes the analyte from other components likely to be present, including structurally related substances, degradation products or matrix constituents.
- Interference testing: analyse samples spiked with potential interferents at realistic concentrations and confirm the signal attributable to the analyte remains unaffected.
- Forced-degradation studies: expose the analyte to stress conditions such as heat, light or oxidation and confirm the method separates parent compound from degradation products.
- Matrix-matched controls: prepare calibration standards and quality controls in the same matrix as the test samples, rather than in a simplified buffer, to capture any matrix-driven bias.
- Blank and double-blank samples: run matrix without analyte and matrix without analyte or internal standard to confirm no false positive signal arises.
Matrix effects are a particular concern in bioanalytical and immunoassay work, where plasma, serum or tissue lysates can suppress or enhance signal unpredictably. A standard mitigation is to run post-extraction spiked samples alongside neat standards and compare recovery; a consistent offset points to matrix suppression that calibration against a matrix-matched curve can correct. ICH M10 treats matrix-matched calibration as a baseline expectation for chromatographic and ligand-binding bioanalytical methods rather than an optional refinement.
For forced-degradation work, choosing realistic stress conditions matters more than exhaustive ones. A method intended to monitor a protein therapeutic’s stability gains little from exposing it to conditions it will never encounter in storage or transport, and the resulting data can obscure rather than clarify genuine degradation pathways.
Robustness, PAR and MODR: turning development data into validated ranges
Robustness, proven acceptable ranges (PARs) and method operable design regions (MODRs) describe increasingly ambitious ways of understanding how a method behaves across its operating space, and the distinction matters for how much flexibility regulators will grant later.
- Robustness is a univariate check: vary one parameter at a time, such as mobile phase pH or column temperature, and confirm the method still meets acceptance criteria.
- PAR extends this to a documented range for a single parameter within which performance stays acceptable, based on either univariate or multivariate data.
- MODR is a multidimensional region, usually built from design of experiments (DoE), describing combinations of parameters that together keep the method within its ATP.
ICH Q14 recommends a lifecycle, risk-based development approach: use risk assessment and prior knowledge to decide which parameters warrant full DoE investigation, then design factorial or response-surface experiments that probe interactions rather than testing one factor at a time. A MODR built this way captures interaction effects that univariate robustness testing simply cannot see, which is precisely why regulators treat a well-justified MODR as grounds for allowing movement within that region without prior notification.
Pro Tip: Run a small screening DoE before committing to a full robustness study. It identifies which factors actually interact, so the confirmatory experiments focus effort where it changes the outcome.
The regulatory position under ICH Q14 is that development data can substitute for some formal validation testing when it is generated with equivalent rigour and documented transparently. Critical parameters identified through risk assessment still need dedicated validation evidence; non-critical parameters that development data already covers adequately do not need to be re-tested purely to satisfy a checklist. This is the practical payoff of enhanced development: it shortens the formal validation campaign for the parameters that genuinely carry risk.
Building a control strategy and setting system suitability criteria
A method’s analytical procedure control strategy translates validation results into the checks that run every single time the method is used. Defining this strategy before validation starts, rather than retrofitting it afterwards, keeps the two activities aligned and avoids SST criteria that are either too loose to catch drift or so tight they fail good runs.
- Decide the control strategy early: identify which performance characteristics need a routine check versus which are adequately controlled by equipment qualification alone.
- Chromatography SST examples: resolution between critical peak pairs, tailing factor, retention time reproducibility and signal-to-noise ratio at the LOQ.
- Ligand-binding assay SST examples: standard curve back-calculated accuracy, replicate %CV on controls, and minimum signal window between negative and positive controls.
- Set criteria from validation data: use the precision and accuracy ranges observed during validation to anchor SST limits, rather than adopting generic defaults from another method.
- Review periodically: trend SST outcomes over time to confirm the limits still reflect real-world performance rather than theoretical best cases.
A control strategy built this way does double duty. It protects routine testing from undetected drift, and it gives a documented, data-backed justification if a regulator later asks why a particular SST limit was chosen rather than a tighter or looser one. ICH Q14 treats a well-designed control strategy, including SSTs, as one of the more effective ways to manage routine method risk without repeating full validation at every use.
Writing the validation protocol and report
A validation plan and report are not paperwork laid on top of the science; they are where the ATP, the experiments and the acceptance criteria are tied together into a single, auditable argument for fitness for purpose. Eurachem’s method validation guide sets out the structure that most laboratory SOPs now follow.
- State the objective and the ATP: what decision does this method support, and what performance does that decision require.
- List the parameters to be validated and the rationale for including or excluding each one, tied back to the ATP.
- Describe each experiment: sample preparation, number of levels, replicates, instruments and analysts involved.
- Define acceptance criteria before data collection, including any statistical tests to be applied, so the plan cannot be adjusted after seeing the results.
- Report results as tables of raw and calculated values, with calculations shown rather than only final figures.
- Include an uncertainty statement, even a simple one, since Eurachem treats measurement uncertainty as the concept that ties bias and precision together into a single fitness-for-purpose judgement.
- Conclude explicitly: state whether the method meets its ATP and acceptance criteria, rather than leaving the reader to infer it from the tables.
Common reporting traps include checking normality assumptions only after a test has already been run, applying a transformation without stating why, and presenting %CV without the underlying replicate count, which makes the figure impossible to interpret statistically. A report that lets a reviewer reconstruct every calculation from the raw data is a report that survives an audit.
Lifecycle management and what ICH Q14 changes for post-approval work
Established conditions, or ECs, are the specific elements of a method, such as performance criteria, SST parameters or particular set-points, that a regulator approves and that subsequently require formal notification to change. ICH Q14 lets a sponsor propose which elements become ECs and which remain more flexible, provided the proposal is backed by development data.
- ECs can include performance criteria, SST acceptance limits, and specific operating set-points, chosen deliberately rather than by default.
- Enhanced development earns flexibility: a MODR built on solid DoE evidence can justify narrower ECs, leaving more of the operating space open for adjustment without a new submission.
- Validation must still cover routine set-points: however the MODR is defined, the conditions the method will actually run under in routine use need direct validation evidence, not only extrapolation from the edges of the design space.
- Trend review sustains the strategy: ongoing monitoring of SST outcomes and performance data over the method’s life confirms the original ECs remain appropriate, and flags when revalidation is warranted.
This lifecycle view is the real shift ICH Q14 brings to method validation: rather than treating validation as a single event, it frames validation, control strategy and ongoing monitoring as one continuous programme, with development data at the front end reducing the burden carried by formal validation later.
A practical checklist from ATP to validation report
A compact, repeatable sequence keeps a validation project on track and makes gaps obvious before they become findings in an audit.
- Define the ATP and the decision it supports.
- Identify which parameters are critical to that decision through a brief risk assessment.
- Draft the validation protocol with acceptance criteria fixed in advance.
- Run specificity, accuracy, precision, linearity and range experiments as planned.
- Use DoE to probe robustness and, where justified, define a MODR.
- Translate validation results into an analytical control strategy and SST limits.
- Write the validation report with an explicit fitness-for-purpose conclusion.
- Implement SSTs in routine use and schedule periodic trend review.
| Protocol field | What it captures |
|---|---|
| Sample preparation | Matrix, dilution scheme, extraction method |
| Calibration design | Number of levels, concentration range, curve model |
| Replicates | Levels per run, runs per day, days per study |
| Acceptance criteria | Accuracy, precision and linearity limits tied to the ATP |
A small validation campaign built around this sequence, with a handful of concentration levels and a modest number of analysts, is often enough to satisfy an ATP focused on a research or screening decision. A method supporting regulatory release typically needs more replicates, more analysts and a longer timeline to generate the intermediate precision and reproducibility data regulators expect.
Where ABMIUM fits into validation work
ABMIUM supports several points in this lifecycle without replacing the scientific judgement the protocol demands. Its catalogue and services are built around the same provenance and evidence questions that validation planning raises.
- ABMIUM MATCH connects researchers to reagents suited to a specific experimental requirement, which helps when selecting antibodies or kits for specificity and matrix-effect studies.
- Product Validation Service gives an independent check on reagent performance, useful when a validation plan needs external confirmation of a critical input.
- Custom Antibody Service, Custom ELISA Development and Custom PCR / qPCR Assay Development support bespoke assay work where no catalogue reagent meets the ATP.
- Calibrated protein markers, such as the calibrated colour prestained protein marker (10 to 250 kDa), provide defined molecular-weight controls useful in biochemical assay validation.
- Native mass spectrometry and spatial validation offer additional characterisation routes for laboratories validating complex biologics or multiplexed assays.
These services sit alongside, not instead of, a laboratory’s own validation protocol, and are most useful when a specific reagent or independent check is the missing piece in an existing plan.
A practitioner’s perspective on avoidable validation mistakes
The most frequent failure is not a flawed statistical test; it is skipping the ATP and writing acceptance criteria after the data already exist. Loose criteria and thin statistics usually trace back to that same shortcut. Fix it by fixing the ATP first, pre-registering acceptance limits, and running the replicate numbers the plan actually calls for.
— Veron
ABMIUM resources for your next validation project
Sourcing well-characterised reagents matters as much as the statistics once you reach the experimental stage, and ABMIUM’s catalogue of primary antibodies and ELISA kits gives researchers documented provenance to build matrix-matched controls and calibration standards around.
When you contact ABMIUM about a specific product, ask about lot-to-lot consistency data and any available validation evidence so it can be weighed against your own acceptance criteria before purchase.
FAQ
How do you validate an assay?
You define the ATP and acceptance criteria first, then run experiments for the parameters your assay type requires, typically specificity, accuracy, precision, linearity, range and robustness. Results are compared against the pre-set criteria in a formal report, following structures set out by ICH Q2(R2) and Eurachem.
What are the most common parameters used in analytical method validation?
The parameters most consistently referenced across guidance documents are specificity/selectivity, accuracy, precision (repeatability, intermediate precision and reproducibility), linearity, range, detection limit, quantitation limit and robustness, with system suitability testing as the routine companion check. Eurachem’s leaflet lists this same core set for single-laboratory validation.
What are the ICH guidelines for method validation?
ICH Q2(R2) defines the validation characteristics themselves, while ICH Q14 describes a lifecycle, risk-based development approach that uses DoE to establish parameter ranges such as PARs and MODRs. Together they cover both what to test and how development data can reduce the formal validation burden.
What are the typical steps of method validation?
A typical sequence runs from defining the ATP and risk-assessing which parameters are critical, through drafting a protocol with pre-set acceptance criteria, running the specificity, accuracy, precision, linearity and robustness experiments, to writing a report with an explicit fitness-for-purpose conclusion and implementing SSTs for routine use. The exact number of discrete steps varies by laboratory SOP, so definitions differ.
Sources
- ICH Q2(R2) Guideline
- Eurachem: The fitness for purpose of analytical methods
- FDA: Analytical procedures and methods validation for drugs and biologics