IQ OQ PQ stands for Installation Qualification, Operational Qualification, and Performance Qualification — the three stages used to validate that equipment, a process, or a software system is installed correctly, operates as intended, and performs consistently in real-world use. It’s a cornerstone of validation in regulated industries, and the documented evidence auditors expect to see. This guide explains what each stage means, why IQ OQ PQ matters, how the process works, and how it applies to validating QMS software.

What is IQ OQ PQ?

IQ OQ PQ is a structured, three-part approach to proving that something does what it’s supposed to do — with documented evidence rather than assumption. Each stage answers a different question, and they build on each other: you confirm it’s set up right (IQ), then that it works right (OQ), then that it keeps working right under real conditions (PQ). Together they make up the heart of a validation effort for equipment, manufacturing processes, and computerized systems.

Installation Qualification (IQ)

IQ verifies that the equipment or system is installed correctly and according to specifications. It confirms the right version, components, utilities, settings, and environment are in place, and that installation followed the manufacturer’s requirements. The question IQ answers: “Is it set up the way it’s supposed to be?” Typical IQ evidence includes installation checklists, component and version verification, calibration status, and documentation that the correct configuration is in place.

Operational Qualification (OQ)

OQ verifies that the equipment or system operates as intended across its full specified range. It tests functions, controls, alarms, and limits to confirm the system behaves correctly, including at the edges of its operating parameters. The question OQ answers: “Does it work the way it’s supposed to?” OQ is usually the most test-heavy stage, challenging the system against its functional requirements under defined conditions.

Performance Qualification (PQ)

PQ verifies that the equipment or process performs consistently under actual, real-world operating conditions, typically over multiple runs. Where OQ tests capability, PQ demonstrates sustained, reproducible performance with real inputs, real people, and real workloads. The question PQ answers: “Does it consistently produce the right result in normal use?” PQ is often the final confirmation that a process is ready for routine production.

Why IQ OQ PQ matters

In regulated industries — pharmaceuticals, medical devices, food, and others under FDA, cGMP, or ISO 13485 expectations — validation isn’t optional. IQ OQ PQ provides the documented, objective evidence that your equipment, processes, and systems are fit for their intended use, which auditors and regulators expect to see. Beyond compliance, it reduces risk: catching installation and operational problems before they affect product quality is far cheaper than discovering them in production or a recall. Validation is also increasingly expected for the software that runs or records quality-critical activities.

How the IQ OQ PQ process works

A validation effort generally follows this arc:

• Plan and specify. Define requirements (often a user requirement specification) and a validation plan. Some programs add Design Qualification (DQ) up front to confirm the design meets requirements before installation.
• Write protocols. Document the IQ, OQ, and PQ protocols — what you’ll test, acceptance criteria, and how you’ll record results.
• Execute and record. Run each qualification in sequence, capturing evidence and any deviations.
• Resolve and report. Address deviations, then summarize results in a validation report that concludes whether the system is qualified for use.

A risk-based approach — focusing effort where the impact to quality is greatest — keeps validation proportionate rather than testing everything equally.

IQ OQ PQ for QMS software

When the “system” is your quality software itself, IQ OQ PQ becomes computer system validation (CSV): evidence that the software is installed correctly, functions as intended, and performs reliably for its intended use. Modern, risk-based approaches (such as the FDA’s Computer Software Assurance thinking) focus validation effort on the features that matter most to quality, rather than exhaustively testing everything. A good QMS vendor supports this — providing documentation and a guided, risk-based path so you can validate efficiently rather than from scratch. That’s how TLM approaches it for small-to-mid regulated teams: an eQMS designed to be validated proportionately, with support that makes qualification manageable. To see how validation and the rest of your quality system fit together, book a demo.

Frequently asked questions

What does IQ OQ PQ stand for?

IQ OQ PQ stands for Installation Qualification, Operational Qualification, and Performance Qualification. They are the three stages of validation that confirm equipment, a process, or a software system is installed correctly (IQ), operates as intended across its specified range (OQ), and performs consistently under real-world conditions (PQ).

What is the difference between IQ, OQ, and PQ?

IQ confirms the system is installed and configured correctly (“is it set up right?”). OQ confirms it operates correctly across its full specified range, including limits and alarms (“does it work right?”). PQ confirms it performs consistently under actual operating conditions over multiple runs (“does it reliably produce the right result in normal use?”). They run in that order and build on each other.

Is IQ OQ PQ required by the FDA?

Validation is an expectation in FDA-regulated industries (pharmaceuticals, medical devices, food) and under cGMP and ISO 13485. IQ OQ PQ is the widely used framework for providing the documented, objective evidence that equipment, processes, and systems are fit for their intended use. Regulators expect that evidence, though modern guidance encourages a risk-based approach that focuses effort where quality impact is greatest.

What is DQ in validation?

DQ is Design Qualification — an optional stage performed before installation that confirms the proposed design or selection meets the user and functional requirements. When used, the sequence becomes DQ, then IQ, OQ, and PQ.

How does IQ OQ PQ apply to software?

When the system is software, IQ OQ PQ becomes computer system validation (CSV): evidence that the software is installed correctly, functions as intended, and performs reliably for its intended use. Risk-based approaches such as the FDA’s Computer Software Assurance focus validation on the features most critical to quality rather than testing everything equally. A good QMS vendor provides documentation and a guided path to make this efficient.