IQ, OQ and PQ: what they mean and how to plan effective qualification

IQ, OQ and PQ: what they mean and how to plan effective qualification

IQ, OQ and PQ are stages used to show, with documented evidence, that equipment, systems, or facilities are installed correctly, operate within expected ranges, and perform consistently in their intended environment. Testing without a clear strategy can produce large files but little confidence.

What do IQ, OQ and PQ mean?

  • IQ — Installation Qualification: verifies installation, critical components, construction materials, utilities, manuals, initial calibration, and alignment with approved specifications.
  • OQ — Operational Qualification: demonstrates that the system operates as intended across defined ranges, including relevant alarms, controls, and challenge conditions.
  • PQ — Performance Qualification: provides evidence of consistent performance under routine conditions with representative operators, materials, and procedures.

Before these stages, design qualification may be used to demonstrate that the proposed design meets user requirements and intended use. The exact sequence depends on the system and applicable regulatory framework.

How to plan IQ, OQ and PQ

1. Start with intended use and risk

User requirements should state what the system must do, which attributes may affect quality, and which data or alarms are critical. Risk assessment focuses testing on functions that can affect product, safety, identity, strength, purity, quality, or data integrity.

2. Define acceptance criteria before execution

Each protocol needs an objective, scope, responsibilities, prerequisites, instruments, steps, expected results, and acceptance criteria. Criteria should not be selected after results are known. The protocol should also explain how corrections, repeats, and deviations will be handled.

3. Maintain traceability

A traceability matrix connects requirements, risks, and tests. It shows that every critical requirement was evaluated and that each test has a purpose. The matrix later supports change assessment and helps identify which functions require requalification.

4. Manage deviations with discipline

An unexpected result should not be erased or repeated without explanation. Evaluate impact, cause, correction, and the validity of the test. Open CAPA when appropriate and verify the effectiveness of completed actions.

5. Approve a final report

The report summarizes results, deviations, open evidence, restrictions, and the qualification conclusion. Approval should occur before routine release unless a controlled and justified exception is authorized.

Qualification continues after PQ

Calibration, maintenance, software changes, relocation, repairs, and performance trends can affect qualified status. Change control should assess impact and define return-to-service testing. Periodic review confirms that documents and operations remain aligned.

FDA’s Process Validation: General Principles and Practices describes a lifecycle and science- and risk-based approach. Its scope focuses on drugs and biological products; other sectors must use their applicable requirements.

Evidence should tell one complete story

Effective qualification follows a logical line: requirement, risk, test, result, deviation, and approval. That story is more useful than a long protocol disconnected from actual use.

Need URS documents, protocols, traceability matrices, or requalification plans? Talk with Professional Aid Partners. We tailor documentation to the system and applicable risk.