Check validation in laboratory instruments and what to verify before use

What check validation means in a laboratory setting

In a laboratory, check validation is the practical review of whether an instrument, analytical method, software-supported workflow, or process has enough documented evidence to support its intended use. It is not a single certificate, a one-time inspection, or a substitute for scientific judgment. A useful validation check asks three questions: what is the intended use, what evidence shows the system can meet that use, and what has changed since the evidence was approved?

For laboratories handling regulated, accredited, or quality-critical work, this distinction matters. A calibration label, vendor service report, or passing system suitability run may support the validation status, but none of them automatically replaces a complete validation or verification decision.

The term is often used informally, so misunderstandings are common. In one laboratory, a technician may say they need to check validation before running samples. In another, a quality reviewer may use the same phrase to mean a formal review of method validation, instrument qualification, and audit-ready records. The safer approach is to treat check validation as a documented decision point, not as a generic quality phrase.

For more articles in this topic area, see the service and validation section.

Validation, verification, qualification, calibration, and routine checks are not the same

A reliable validation review starts by separating related but different activities. If they are treated as interchangeable, the laboratory may overvalidate routine work or rely on weak evidence when a stronger record is required. Public standards and guidance from organizations such as ISO, ICH, USP, and FDA use these terms with specific intent, even when day-to-day laboratory language is less precise.

In practice, a validation check may review all of these records, but it should not treat them as equivalent. A balance, incubator, centrifuge, HPLC system, spectrophotometer, or environmental chamber can be calibrated and still not be qualified for the exact method, range, matrix, load, or workflow in which it is being used.

When full validation is needed and when verification is enough

Full validation is usually appropriate when a laboratory develops a new method, significantly modifies an existing method, applies a method outside its established scope, or uses a non-standard procedure for a regulated decision. Analytical procedure validation normally evaluates characteristics such as specificity or selectivity, accuracy, precision, range, linearity, and detection or quantitation capability when those characteristics are relevant to the purpose of the procedure. ICH Q2(R2), adopted at ICH Step 4 in November 2023 and effective in the European Union from June 14, 2024, is an important modern reference for validation of analytical procedures.

Verification is narrower. For example, USP General Chapter 1226 describes verification of compendial procedures as an assessment of selected analytical performance characteristics in the laboratory that will use the procedure. The purpose is not to repeat the entire validation already established for the official method. It is to generate relevant local evidence that the laboratory, analysts, instruments, reagents, and sample conditions can produce acceptable results.

For many laboratories, the decision can be framed this way:

• Use full validation when the method is new, substantially changed, non-standard, or used outside an established scope.
• Use verification when an established or compendial method is being introduced locally and the laboratory must prove it can perform the procedure acceptably.
• Use qualification when the question is whether an instrument or system is installed and operating according to requirements.
• Use routine checks when the question is whether the system is acceptable for a specific run, day, batch, or sequence.
• Trigger revalidation or re-verification review when changes could affect the original evidence, such as a new detector, software update, method parameter change, new matrix, major repair, relocation, or repeated out-of-trend performance.

A practical workflow for a validation check

A validation check should be simple enough to use routinely and structured enough to withstand internal review, customer questions, accreditation assessment, or regulatory inspection. The following workflow gives laboratories a repeatable way to decide whether an instrument or method is ready for use.

1. Define the intended use. Identify the sample type, measurement range, required decision, acceptance limit, reporting unit, matrix, instrument configuration, software version, and user group. Without an intended use statement, the review becomes a document hunt rather than a scientific assessment.
2. Identify the controlling requirement. Determine whether the work is driven by ISO/IEC 17025, GMP expectations, a pharmacopeial chapter, an internal quality procedure, a customer method, or a regulatory filing. Different requirements may call for different levels of evidence.
3. Select the correct evidence route. Decide whether the question is method validation, method verification, instrument qualification, calibration status, software validation, cleaning validation, process validation, or routine suitability. More than one route may apply.
4. Check protocol approval and acceptance criteria. Acceptance criteria should be approved before testing begins. If criteria are written after the data are known, the evidence is weaker and may be challenged during review.
5. Review raw data and calculations. Summary tables are not enough. The check should confirm that raw data, integration decisions, spreadsheet formulas, instrument printouts, audit trail entries, and calculation logic support the final conclusion.
6. Assess deviations and failed runs. Failed or excluded results need documented scientific justification. A clean final report that ignores failed validation attempts can be more risky than a report that openly explains them.
7. Confirm change control status. Check whether any change occurred after approval: instrument move, repair, software patch, column type change, reagent source change, analyst training change, or sample matrix expansion.
8. Document the conclusion and limits. The final statement should say what is approved, what is not approved, who reviewed it, when it was reviewed, and what condition would trigger another validation check.

This workflow gives the laboratory a defensible answer without treating every instrument check as a full validation study.

Evidence that should be available before approving use

The most useful validation file is not necessarily the largest one. It is the file that connects the requirement, test design, data, review, and conclusion. Before a method or instrument is approved for use, the following evidence should normally be available when relevant to the work:

• Approved protocol or verification plan with scope, responsibilities, acceptance criteria, and required tests.
• Instrument identification, including model, serial number, location, configuration, modules, firmware, and software version where applicable.
• Calibration and maintenance records that cover the validation or verification period.
• Qualification records showing that the instrument or system can operate under the conditions required by the method.
• Reference standards, reagents, media, columns, filters, consumables, and sample preparation materials with lot or traceability details where relevant.
• Analyst training records for the procedure and instrument.
• Raw data, chromatograms, spectra, balance printouts, environmental logs, worksheets, photographs, or other primary records supporting the conclusion.
• Calculation checks, spreadsheet controls, and review of formulas when electronic tools are used.
• Deviation reports, investigations, repeat testing justification, and impact assessment.
• Final report with conclusion, limitations, approval signatures, effective date, and next review or trigger conditions.

For electronic records, the validation check should also consider user access, audit trails, backup practices, data retention, and whether electronic signatures or approvals are controlled according to the applicable quality system. This is especially important when results are created, processed, or reviewed through laboratory information management systems, chromatography data systems, or instrument control software.

Common problems found during validation checks

Many validation gaps are not caused by poor science. They occur because records are scattered, ownership is unclear, or the laboratory treats validation as a one-time event. A careful check often finds one of the following problems. See also: analytical methods.

• The intended use is missing. Records show that a method was tested, but they do not show the matrix, range, specification, or decision that the method supports.
• Acceptance criteria were not predefined. Data may look acceptable, but the report does not prove that the result met an approved requirement.
• Vendor documents were accepted without local review. Vendor qualification can be valuable, but the laboratory still needs to confirm that the configuration and use conditions match the actual workflow.
• Calibration is confused with validation. Calibration may confirm measurement traceability, but it does not by itself prove that a complete analytical method works for a particular sample.
• Changes were not linked to impact assessment. A repaired detector, software update, instrument relocation, new consumable supplier, or method parameter change can affect validation status.
• Failed data disappeared from the story. Validation reports should explain invalid runs, investigations, exclusions, and repeats rather than presenting only successful outcomes.
• Compendial verification was skipped. Even when a method is official, the laboratory should have evidence that it can perform the method acceptably under its own conditions.

These issues are easier to prevent than correct. A short validation status checklist tied to change control can help laboratories avoid last-minute document reconstruction before an audit or customer review.

How recent guidance affects validation checks

Several reference frameworks shape modern validation practice. ISO/IEC 17025:2017 remains the central international standard for testing and calibration laboratories and was confirmed as current by ISO in 2023. It places strong emphasis on method selection, method validation, verification of methods before use, technical competence, impartiality, and reliable results.

For pharmaceutical and related analytical work, ICH Q2(R2) is especially relevant because it reflects updated thinking on validation of analytical procedures and is aligned with ICH Q14 on analytical procedure development. The change does not mean every routine check becomes a full validation. It does reinforce the need to connect validation design with the analytical procedure’s intended purpose and lifecycle.

FDA’s January 2011 process validation guidance also remains influential for manufacturing contexts because it frames process validation as a lifecycle activity: process design, process qualification, and continued process verification. While that guidance focuses on manufacturing processes rather than routine laboratory instrument checks, the lifecycle concept is useful. Validation status should be maintained through monitoring, review, and change control, not frozen at the date of the original report.

The practical conclusion is straightforward: check validation should not be paperwork for its own sake. It is a risk-based review of whether current evidence still supports current use. The more critical the result, the stronger the evidence should be.

Frequently asked questions

What is check validation in a laboratory?

It is a documented review confirming that the available validation, verification, qualification, calibration, and routine performance evidence supports the intended use of an instrument, method, system, or process. The exact scope depends on the work, the risk, and the applicable quality requirement.

Is method verification the same as method validation?

No. Validation demonstrates that a procedure is suitable for its intended purpose, often for a new or modified method. Verification is usually narrower and confirms that an established method can be performed acceptably in a specific laboratory with its own personnel, equipment, reagents, and conditions.

Can a vendor certificate replace laboratory validation records?

Usually not by itself. A vendor certificate, service report, or qualification package can support the file, but the laboratory should still confirm that the instrument configuration, operating range, software setup, method requirements, and local use conditions match the intended application.

How often should validation status be checked?

There is no single interval that fits every laboratory. Validation status should be checked before first use, after significant changes, after major repair or relocation, when performance trends deteriorate, when the method scope changes, and during planned quality review. Critical systems may require more frequent review than low-risk support equipment.

What is the most important document in a validation check?

The final report is important, but it is only convincing when supported by the approved protocol, predefined acceptance criteria, raw data, calculations, deviations, change control records, and a clear conclusion. A short report with traceable evidence is stronger than a large file with unclear scope.