Process Validation: IQ, OQ, PQ Explained

IQ, OQ, and PQ are the three qualification stages of process validation: Installation Qualification proves the equipment is installed correctly, Operational Qualification proves it works across its full operating range, and Performance Qualification proves the whole process makes acceptable product consistently under real production conditions. Each stage is a documented gate that must pass before the next begins.

In FDA-regulated manufacturing, you cannot simply assert that a process works. You have to prove it with evidence, in a fixed order, and keep the records. IQ, OQ, and PQ are how that proof is built and structured. This guide covers what each stage proves, the deliverables it produces, why the order cannot be shuffled, and how the three fit inside the modern lifecycle approach to validation.

What is process validation?

Process validation is the documented collection and evaluation of data, from process design through commercial production, that establishes scientific evidence a process can consistently deliver quality product. It is not one test at the end; it is a body of evidence built up as a process moves from design into routine manufacturing. IQ, OQ, and PQ are the qualification core of that body of evidence, the part where installed equipment and a defined process are put through their paces and the results are recorded against pre-approved acceptance criteria.

The order matters because each stage rests on the one before it. There is no point testing a machine's operating range before you have confirmed it was installed correctly, and no point running production batches before you know the equipment holds its parameters across that range. The stages are a staircase, not a menu.

What does Installation Qualification (IQ) prove?

IQ documents that equipment, utilities, instrumentation, and supporting systems are installed and configured according to the manufacturer's specifications and the design intent. It is the "is it built and set up right?" stage. Typical IQ evidence includes verification of the correct model and serial numbers, confirmation that utilities such as power, air, and water meet spec, calibration status of instruments, installed software versions, spare-parts and manual documentation, and that the installation matches approved drawings. IQ does not run product; it confirms the box is the right box, wired the right way, in the right place.

What does Operational Qualification (OQ) prove?

OQ documents that the equipment operates as intended across its full specified operating range, including at the edges. It is the "does it do what it should, everywhere it should?" stage. OQ deliberately pushes to the limits: it establishes process control limits, tests worst-case conditions and action levels, and challenges failure modes, so the safe operating window is proven rather than assumed. Alarms, interlocks, and control loops are exercised. OQ is where you learn the boundaries of the process before any product depends on them.

What does Performance Qualification (PQ) prove?

PQ documents that the complete process, running under normal production conditions with trained operators and production materials, consistently produces product that meets all requirements. It is the "does the whole thing make good product, repeatably, for real?" stage. PQ is typically run over multiple consecutive batches or runs to demonstrate reproducibility, not a single lucky lot. Where IQ and OQ qualify the equipment, PQ qualifies the process as a whole, which is why it comes last and why capability thinking, the same logic as a process capability study belongs here.

How do you run process validation, step by step?

The mechanics are consistent across regulated industries: plan it, write protocols with acceptance criteria set in advance, execute in order, and report. Deviations get investigated, not quietly edited.

1. Write a validation plan. Define the scope, the systems and process covered, the responsibilities, and the acceptance strategy before any protocol is executed.
2. Draft and approve the IQ protocol. Specify exactly what installation evidence will be checked and the acceptance criteria, and get it approved before execution.
3. Execute IQ and resolve findings. Verify the installation against the protocol, document results, and close out any discrepancies before moving on.
4. Draft, approve, and execute OQ. Challenge the operating range, worst-case conditions, and control limits against pre-approved criteria, and record the proven operating window.
5. Draft, approve, and execute PQ. Run multiple consecutive production batches under normal conditions and demonstrate the process consistently meets all product and process acceptance criteria.
6. Compile the validation report. Summarize the results of all three stages against the plan, document any deviations and their resolution, and formally release the process for routine production.
7. Move into continued verification. Monitor the validated process in routine production to confirm it stays in control, and re-validate when a change warrants it.

How do IQ, OQ, and PQ fit the FDA lifecycle approach?

IQ, OQ, and PQ are the traditional qualification sequence, and they live inside a broader three-stage lifecycle in the FDA's current thinking. The FDA's 2011 guidance, Process Validation: General Principles and Practices frames validation as Stage 1 Process Design, Stage 2 Process Qualification, and Stage 3 Continued Process Verification. The familiar IQ/OQ/PQ work sits inside Stage 2, and Stage 3 replaces the old "validate once and forget" habit with ongoing monitoring for the life of the process.

What deliverables does validation produce?

Each stage produces approved protocols and executed reports, and the whole effort is tied together by a validation plan and a final report. The records are the point: in an FDA inspection, an unvalidated or poorly documented process is treated as a process you cannot prove works. Because so much of this evidence is now electronic, it falls under electronic-records expectations covered by 21 CFR Part 11 and it sits inside the broader GMP compliance system that governs how regulated product is made. In practice, validation is where pharmaceutical manufacturing operations turn a promising process into a licensed one.

Why acceptance criteria come before execution

The rule that separates real validation from theater is simple: acceptance criteria are written and approved in the protocol before the stage is executed. You decide what "pass" looks like first, then run the test, then compare. Setting criteria after seeing the data is how a failing run gets quietly reasoned into a passing one, and it is one of the fastest ways to earn an inspection finding. A protocol that says "the fill weight shall stay within 495 to 505 grams across all runs" is a commitment made in advance; a report that backfills the limits to match whatever happened is not.

Deviations are handled the same disciplined way. When a run misses a criterion, you investigate the cause, document it, and decide whether the deviation is acceptable with justification or whether the stage must be repeated. You do not erase the result. A single documented, investigated deviation with a sound rationale is far stronger evidence than a suspiciously clean record with no deviations at all, because inspectors know real processes produce surprises.

What can go wrong in validation?

The recurring failures are familiar across regulated plants:

• Running stages out of order or starting PQ before OQ has proven the operating window, so the process runs on an unverified foundation.
• Vague acceptance criteria that cannot actually pass or fail, which turns the report into an opinion.
• Treating validation as one-and-done and never re-validating after a change to equipment, materials, or method.
• Weak documentation that cannot reconstruct what was tested, when, by whom, and against what limit.

The regulations behind IQ, OQ, PQ

Process validation is a regulatory expectation, not an internal nicety, and the primary guidance is public.

• The FDA's current guidance defines the three-stage lifecycle that contains IQ/OQ/PQ and defines process validation as evidence that a process consistently delivers quality product (FDA, Process Validation: General Principles and Practices).
• For medical devices, the widely referenced GHTF (now IMDRF) process validation guidance provides the decision framework for when validation is required and detailed IQ/OQ/PQ protocol guidance (GHTF/IMDRF final documents).

Why validated processes drift out of their evidence

A process is validated against the conditions in the PQ runs, but production keeps moving. Operators change, a component supplier swaps, a parameter creeps, and none of it necessarily triggers the re-validation it should. The gap between "the process we validated" and "the process we run today" is where regulatory findings and quality escapes live. When production parameters, deviations, and line checks are captured digitally at the point of work instead of on paper, the validated state stays visible: a drift away from the qualified operating window shows up as it happens, not at the next audit. That continuous verification, the spirit of Stage 3, is what Harmony's quality intelligence and paperwork digitization supports on the floor, keeping the running process honest against the process that was qualified. See it in a real plant in our CLS case study.