SOP: Analytical Instrument Qualification and Classification Program

This is a ready-to-use SOP that governs an analytical instrument qualification (AIQ) program end to end: how instruments are classified into Groups A, B, and C, how each qualification phase is owned and executed, what puts an instrument back into requalification, and how the qualified state is tracked. Replace every <<FILL: ...>> placeholder with your own specifics, set your document numbers and dates, and route it through your normal document control, review, and approval. It sits above the per-phase protocols (DQ, IQ, OQ, PQ) rather than replacing them. A worked filled specimen follows the template. Verify each cited regulation against the current source before you rely on it. This is educational reference content, not legal or regulatory advice.

Document control header

1. Purpose

Define how analytical instruments are qualified and kept in a qualified state so that data generated on them is suitable for its intended use. The program scales qualification effort to instrument complexity, integrates software qualification for instruments whose results depend on software, and keeps a demonstrable record that every instrument generating GxP data is qualified, calibrated, and current.

2. Scope

Applies to all analytical instruments used to generate, acquire, process, or store data supporting GxP decisions (release, stability, in-process control, method validation, clinical sample analysis) at the sites named above. Covers laboratory instruments across Groups A, B, and C as classified under USP General Chapter <1058>. Excludes process equipment qualified under the manufacturing equipment program and standalone computerized systems qualified under the computer system validation program, except where an instrument’s control software is qualified as an integrated part of the instrument.

3. Responsibilities

4. Definitions

• Analytical Instrument Qualification (AIQ): documented evidence that an instrument is suitable for its intended use.
• Group A / B / C: the USP <1058> classification of instruments by measurement and software complexity (standard equipment with no measurement; measuring instruments with no significant software control; instruments whose results depend on software).
• DQ / IQ / OQ / PQ: design, installation, operational, and performance qualification.
• Qualified state: the condition in which nothing (repair, relocation, software change, or method change beyond the qualified range) has invalidated the qualification.
• Intended use: the specific measurements and methods the instrument is qualified to support.

5. Procedure

5.1 Classification

1. On acquisition, or when intended use changes, the instrument owner classifies the instrument as Group A, B, or C against its intended use, using the classification determination record (<<FILL: form number>>).
2. Base the decision on whether the instrument measures a result that feeds a GxP decision, and whether software acquires, processes, or stores that result such that it would be needed to reproduce or defend the result.
3. Record the rationale. Classification is a documented decision, not an opinion, and QA reviews it. Where the same hardware is used two ways (for example a plate reader used both for a fixed endpoint read and for a software-driven kinetic read), classify against the more demanding intended use in use.

5.2 Design Qualification (DQ)

4. Before purchase or before first use, document the intended use, the user and data requirements, the environment and utility needs, and confirmation that the selected model meets them. For a routine commercial instrument, DQ can be short; for a configured system, DQ ties to the user requirements specification.

5.3 Installation Qualification (IQ)

5. Verify and record the as-installed configuration: model and serial/asset numbers, software and firmware versions, utilities, environment, network and server connection, manuals, and calibration certificates present. Confirm calibration is current before OQ acceptance criteria are judged.

5.4 Operational Qualification (OQ)

6. Test each function against pre-approved acceptance criteria across the operating range. For Group C, include software function and security tests, audit trail verification (configured, enabled, cannot be disabled by an analyst), and access control.
7. Acceptance criteria come from the manufacturer specification and the methods in use, not a generic template.

5.5 Performance Qualification (PQ)

8. Demonstrate the instrument performs for the methods actually run, against the tightest applicable method criterion. PQ is system-level and distinct from per-run system suitability. Record the intended use PQ covers.

5.6 Requalification and periodic review

9. Assess for requalification on any of these triggers: a repair to a measuring component; relocation; a software update or patch to the control or data system; a method change that pushes requirements beyond the qualified range; or a defined periodic interval (<<FILL: e.g. annual for Group C, biennial for Group B>>).
10. Scale the requalification to the change (abbreviated IQ and a PQ run for a same-room relocation; the relevant OQ plus PQ for a detector replacement; software requalification and regression testing for a major version upgrade). Route software changes through change control with an impact assessment.

5.7 Inventory and qualified-state tracking

11. Maintain a central inventory listing each instrument with its group, qualification status, responsible analyst, and next requalification and calibration dates. Review the inventory <<FILL: frequency>> and act on anything drifting out of the qualified state.

6. Acceptance criteria

• Every instrument generating GxP data has a documented classification with rationale, and a current qualification appropriate to its group.
• Calibration is current and cross-referenced in the qualification record.
• For Group C, the audit trail configuration is verified and captured as evidence, access is individual and role-based, and raw data is retained and restorable.
• The inventory can answer, for any instrument, “is it qualified and when is it next due.”

7. Records generated

Classification determination records; DQ/IQ/OQ/PQ protocols and reports; requalification impact assessments; the instrument inventory; calibration certificates referenced in qualification records.

8. References

• USP General Chapter <1058>, Analytical Instrument Qualification (describe by title; do not reproduce chapter text)
• USP General Chapter <621>, Chromatography (for system suitability, where applicable)
• 21 CFR Part 11; EU Annex 11 (electronic records and signatures)
• EU Annex 15 (qualification and validation)
• FDA guidance, Computer Software Assurance for Production and Quality Management System Software (issued 3 February 2026, superseding the 24 September 2025 final), for risk-scaled test effort

9. Revision history

10. Approvals

Filled specimen

A worked example for one instrument moving through the program. Illustrative only; your values come from your instruments and methods.

Instrument: UPLC with networked chromatography data system, asset LAB-0142, assay and related-substances laboratory.

Classification: Group C. Rationale: the CDS acquires, integrates, and stores the chromatogram; removing the software would prevent reproduction or defence of the result. Classified against the related-substances method (the tighter intended use). QA reviewed and approved 2026-02-28.

DQ: Intended use recorded as reversed-phase gradient separations for assay and impurities; user requirements include audit trail that cannot be disabled by an analyst and individual user accounts; selected model confirmed to meet them.

IQ: Pump, autosampler, column oven, detector installed and recorded; CDS version and server connection documented; audit trail confirmed enabled; calibration certificates present and current.

OQ: Flow accuracy, gradient accuracy, injector precision, detector linearity and wavelength accuracy, oven temperature accuracy all passed against method-derived criteria; audit trail generated an entry on a processing-method change showing old value, new value, user, timestamp; a low-privilege user could not delete data.

PQ: Related-substances method run; peak area RSD 0.6% (limit 2.0%), critical-pair resolution 2.1 (limit 1.5), S/N at reporting threshold 28 (limit 10). Qualified for both assay and related-substances methods because it cleared the tighter criteria.

Qualified state: Next periodic requalification 2027-03-10; calibration due 2026-12-01. A CDS patch in June triggered a change-control impact assessment; scope limited to a focused regression check of integration and audit trail behaviour, which passed.

Inventory row: