IQ/OQ/PQ (Installation, Operational, and Performance Qualification)

IQ/OQ/PQ is the three-stage documented qualification sequence — Installation Qualification, Operational Qualification, and Performance Qualification — used to prove that a piece of equipment, instrument, utility, or system was installed correctly, functions correctly across its specified operating range, and performs consistently under the lab’s actual conditions of use before it is relied on to produce results. It is the standard vocabulary for equipment commissioning in regulated laboratory environments (GxP, pharmaceutical, clinical, and any ISO/IEC 17025-accredited testing lab), and it governs new-equipment procurement as much as it governs ongoing compliance: a lab that buys a freezer, autoclave, HPLC, or biosafety cabinet without an IQ/OQ/PQ plan has no documented basis for trusting the data or product that equipment produces.

The same three-letter sequence is also used for computer systems and software (LIMS, ELN, chromatography data systems) under GAMP 5 — that application is covered in depth in CASRAI’s guide to Computer System Validation (CSV). This entry covers the broader, original usage: physical equipment, instruments, and facility systems.

The Qualification Sequence: DQ, IQ, OQ, PQ

Each stage answers a different question, is executed after the one before it, and produces its own signed documentary evidence. Some qualification programs add a Design Qualification (DQ) stage ahead of the three below, particularly for custom-built or high-risk systems, to confirm the proposed design and specifications meet the lab’s documented user requirements before the equipment is even ordered.

Stage	Question it answers	Typical evidence produced
DQ — Design Qualification (optional, risk-based)	Does the proposed equipment design/specification meet the documented user requirements?	User Requirements Specification (URS), vendor design review, signed DQ report
IQ — Installation Qualification	Was the equipment installed correctly, in the right environment, matching the specified configuration?	Installation checklist, model/serial number and firmware/software version record, utility connection verification, calibration status at install, signed IQ report
OQ — Operational Qualification	Does the equipment operate as intended across its full specified operating range, including boundary conditions and alarms?	Executed test scripts with expected-versus-actual results, challenge tests at operating limits, alarm/interlock verification, signed OQ report
PQ — Performance Qualification	Does the equipment perform consistently and correctly under the lab’s actual, real-world conditions of use over a defined period?	PQ protocol executed against representative loads/workflows, extended monitoring data, signed PQ report and validation summary sign-off

The distinction between OQ and PQ is where qualification programs most often go wrong: OQ proves a function works when tested in isolation against a written script; PQ proves the equipment works the way the lab actually uses it — typical sample loads, typical run lengths, typical ambient conditions — sustained over time. A freezer can pass every OQ temperature-set-point test and still fail in practice because nobody ran PQ against the door-opening frequency and rack density the lab actually uses.

Worked Examples

• -80°C ultra-low freezer: IQ confirms it was sited correctly, connected to facility power and to the alarm/monitoring system, and matches the purchase order specification. OQ confirms it reaches and holds -80°C ± the specified tolerance across an empty-chamber test, including alarm activation at excursion thresholds. PQ confirms it maintains that setpoint over an extended period (commonly weeks) under actual lab loading — racks, inventory density, and normal door-opening frequency — before any sample is stored in it long-term.
• Autoclave: IQ verifies correct installation, steam/water/drain connections, and chamber specification match. OQ verifies the cycle reaches and holds the specified temperature and pressure for the specified dwell time across programmed cycles, empty. PQ verifies sterility/kill efficacy is achieved with representative loads (e.g., biological indicators placed in the densest, hardest-to-penetrate load configuration the lab actually runs).
• HPLC or other analytical instrument: IQ verifies the instrument, modules, and software version match the order and vendor specification. OQ verifies each module (pump flow accuracy, detector wavelength accuracy, autosampler precision) performs to specification, typically using the vendor’s OQ protocol. PQ verifies the complete system produces accurate, precise, reproducible results running the lab’s actual methods and typical sample matrices.
• Biosafety cabinet: IQ verifies correct installation and airflow ducting. OQ verifies airflow velocity, HEPA filter integrity, and containment performance meet the certification standard (e.g., NSF/ANSI 49). PQ, where a program includes it, confirms sustained performance under routine operational use between certification intervals.

What IQ/OQ/PQ Is Not

Three adjacent activities are commonly confused with qualification, and the difference matters for what a lab can actually claim in an audit:

• Calibration is not PQ. Calibration verifies a single measurement’s accuracy against a traceable reference standard at a point in time (see CASRAI’s guide to calibration certificates and metrological traceability). PQ verifies the equipment’s overall performance under actual conditions of use over a defined period. Calibration is usually an input to OQ/PQ, not a substitute for either.
• Preventive maintenance (PM) is not OQ. PM is scheduled, routine servicing (filter changes, lubrication, part replacement) intended to keep equipment functioning; it does not, by itself, generate documented proof that the equipment meets its specified operating range.
• Vendor Factory Acceptance Testing (FAT) and Site Acceptance Testing (SAT) are not a substitute for the lab’s own IQ/OQ/PQ. FAT/SAT confirm the equipment worked at the vendor’s site or immediately on delivery; they speak to the equipment as shipped, not to whether it was installed correctly and performs correctly in this lab’s specific environment, with this lab’s utilities, software configuration, and actual use pattern. Vendor qualification documentation can be leveraged as supporting evidence, but it does not, on its own, satisfy the lab’s IQ/OQ/PQ obligation.

When Requalification Is Triggered

IQ/OQ/PQ is not a one-time event. A documented, risk-based change-control procedure should trigger full or partial requalification when equipment is relocated or moved between rooms; after a major repair or component replacement; after a firmware, software, or control-system update; following a calibration or performance failure; or on a scheduled periodic interval defined by the lab’s own risk assessment or an applicable accreditation standard.

IQ/OQ/PQ in Equipment Procurement

Because qualification depends on documented requirements defined before equipment is ordered, IQ/OQ/PQ planning belongs in the procurement process itself, not bolted on after delivery. A User Requirements Specification (URS) written and approved before purchase gives the lab something concrete to qualify against, lets a DQ step confirm the vendor’s proposed equipment actually meets those requirements, and lets the lab negotiate vendor-supplied IQ/OQ support (increasingly common for complex analytical instruments and computer-controlled systems) as part of the purchase agreement rather than as an unplanned post-delivery cost.

Standards and Frameworks

IQ/OQ/PQ terminology is not itself a single regulation; it is the shared vocabulary of several overlapping frameworks. ASTM International’s E2500 guide (specification, design, and verification of pharmaceutical and biopharmaceutical manufacturing systems and equipment) promotes a science- and risk-based approach to commissioning and qualification as an alternative to exhaustive, one-size-fits-all IQ/OQ/PQ paperwork. ISPE’s Baseline Guide on Commissioning and Qualification covers the same territory from an engineering-project perspective. In GxP-regulated labs, qualification sits alongside Good Manufacturing Practice (GMP) and broader GxP compliance expectations; in accredited testing/calibration labs, equipment qualification is part of what an ISO/IEC 17025 assessor reviews as evidence of a lab’s technical competence. Where the “equipment” is a computer system rather than a physical instrument — a LIMS, ELN, or chromatography data system — the same IQ/OQ/PQ sequence is executed under GAMP 5 and is closely tied to 21 CFR Part 11 controls; see CASRAI’s Computer System Validation (CSV) guide for that application in full.

Frequently Asked Questions

What is the difference between OQ and PQ?

OQ proves the equipment’s individual functions work correctly when tested in isolation against a written script, including at the boundaries of its specified operating range. PQ proves the equipment performs consistently and correctly under the lab’s actual conditions of use — real sample loads, real workflows, real duration — not just a scripted test.

Is Design Qualification (DQ) always required?

No. DQ is most common for custom-built, high-complexity, or high-risk equipment and computer systems, where confirming the proposed design meets requirements before the equipment is built or purchased materially reduces risk. Off-the-shelf, lower-risk equipment often moves straight to IQ.

Who performs IQ/OQ/PQ — the vendor or the lab?

Either, or both, depending on the agreement. Vendors frequently offer IQ/OQ (sometimes IQ/OQ/PQ) as a paid service at installation, particularly for complex analytical instruments. Responsibility for the equipment being fit for the lab’s specific, actual use — which is what PQ demonstrates — ultimately rests with the lab, whether or not a vendor participates in executing the protocol.

How often does equipment need requalification?

There is no single universal interval; it is set by the lab’s own risk assessment, applicable accreditation standard, or regulatory expectation, and is separately triggered by relocation, major repair, a control-system or software update, or a calibration/performance failure, regardless of the scheduled interval.