IQ / OQ / PQInstallation / Operational / Performance Qualification
IQ, OQ and PQ (installation, operational and performance qualification) are stages for showing that equipment or systems are installed correctly, operate as intended across their ranges, and perform consistently in routine use.
Read the full summary
EU GMP Annex 15 describes them; FDA's process validation guidance covers the same activities within Stage 2.

On this page · 12 sections
- 1What each stage shows
- 2Where the terms come from
- 3Worked example: a new blender
- 4Common failure modes and checks
- 5Why qualification matters on the floor
- 6The lifecycle step by step
- 7What a good protocol contains
- 8Equipment qualification versus software validation
- 9Explain it for your operation
- 10Questions an inspector may ask
- 11Questions to ask a software supplier
- 12Where V5 fits
How does IQ / OQ / PQ apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What each stage shows
| Stage | Question it answers | Typical evidence (Annex 15) |
|---|---|---|
| DQ (design qualification) | Does the design meet the user requirements? | Traceability from URS to design |
| IQ (installation) | Is it installed as designed? | Components against drawings and specifications, calibration of instruments, materials of construction |
| OQ (operational) | Does it operate as intended over its expected range? | Tests of functions and of upper and lower operating limits ('worst case') |
| PQ (performance) | Does it perform consistently in routine use? | Runs with production materials, qualified substitutes or simulated product, over the expected range |
02Where the terms come from
EU GMP Annex 15 uses IQ, OQ and PQ explicitly and says PQ should normally follow successful IQ and OQ, though it may sometimes be performed together with OQ or process validation where justified. FDA's 2011 guidance places equipment and utility qualification within Stage 2 (process qualification) — verifying installation against design and operation across anticipated ranges — without requiring the IQ/OQ/PQ labels. Both are guidance; the underlying obligations come from GMP regulations.
03Worked example: a new blender
- IQ: confirm model, motor rating, product-contact materials and installed utilities against the specification; record instrument calibration.
- OQ: run empty and loaded at minimum and maximum speeds and timer settings; confirm alarms and interlocks.
- PQ: blend representative product at the routine batch size and show uniformity meets the acceptance criteria over several runs.
Each protocol has pre-approved acceptance criteria; deviations are investigated and the final report is approved by people with that authority before routine use.
04Common failure modes and checks
- Acceptance criteria written after testing.
- OQ that never challenges operating limits.
- Supplier FAT/SAT reused without checking it covers what the protocol needs (Annex 15 allows this only where justified).
- No requalification after changes, contrary to change control and periodic review expectations.
05Why qualification matters on the floor
A batch is only as trustworthy as the equipment that made and measured it. If a blender has never been shown to mix uniformly at its maximum load, or a filler has never been challenged at its fastest speed, every batch made at those settings carries a question nobody has answered. Qualification answers that question once, in advance, with recorded evidence, so routine production can rely on the result instead of re-proving it every shift.
It also gives change control something to compare against. When a motor is replaced, a sensor relocated or a recipe pushed to a new speed, the qualified state is the reference point: the team asks whether the change moves the equipment outside what IQ, OQ and PQ already demonstrated, and if so, what needs repeating.
06The lifecycle step by step
- User requirements (URS): write down what the equipment or system must do, in testable terms. Annex 15 treats the URS as the reference point through the whole validation lifecycle.
- Design qualification (DQ): check and document that the proposed design meets the URS before purchase or build.
- Factory and site acceptance testing (FAT/SAT): where used, the supplier tests at the factory and again after delivery. Annex 15 allows this work to be relied on in IQ/OQ when it is shown that function is not affected by transport and installation.
- IQ: verify the installed components, drawings, utilities, materials and instrument calibration against the design.
- OQ: test functions, alarms and interlocks, including upper and lower operating limits and worst-case conditions.
- PQ: show consistent performance with production materials, qualified substitutes or simulated product across the intended operating range.
- Report and release: summarise results and deviations, and have the report formally approved before the equipment enters routine use.
- Maintain the state: keep it under change control, calibration and maintenance, and review periodically whether requalification is needed.
07What a good protocol contains
- Scope: exactly which equipment, serial number, location and configuration is covered.
- Responsibilities: who executes, who reviews and who approves.
- Test steps written so a second person could repeat them and get the same result.
- Acceptance criteria fixed and approved before execution, with the source of each limit (URS, specification or process requirement).
- Instruments used for testing, with their own calibration status recorded.
- How deviations are recorded, investigated and resolved, and whether a failed test can be repeated.
- Space for raw data, signatures and dates, or the electronic equivalent with audit trail.
08Equipment qualification versus software validation
The same three-stage idea is often applied to computerised systems: installation checks that the software, versions and configuration are in place; operational testing exercises functions and security; performance testing shows the system supports the real business process with real users. The vocabulary overlaps, but the risks differ. Software rarely wears out; its risks come from configuration, data and change. That is why many teams scale software testing by risk rather than copying an equipment protocol line by line.
For laboratory instruments, many labs follow a separate analytical instrument qualification approach. That is outside the sources reviewed for this page, so check the applicable chapter or guideline for your lab before adopting its terms.
09Explain it for your operation
- Food or supplement plant: a new metal detector is installed (IQ), challenged with test pieces at line speed and reject timing confirmed (OQ), then run with real product to show consistent detection without excessive false rejects (PQ).
- Pharmaceutical site: a tablet press is qualified across its compression force and speed range before process validation batches are made on it.
- Device assembly: a heat sealer is qualified at its temperature, pressure and dwell limits before seal strength is relied on for product release.
- Warehouse: a temperature-controlled room is installed with mapped sensor positions, alarm functions are tested, and performance is shown across seasonal loads.
10Questions an inspector may ask
- Show me the URS this equipment was qualified against.
- When were the acceptance criteria approved relative to the test dates?
- How did OQ challenge the operating limits you actually use in production?
- Which deviations occurred and how were they closed?
- What has changed since qualification, and how did you decide whether to requalify?
11Questions to ask a software supplier
- What installation and operational testing documentation do you provide, and on which plans?
- How are releases tested, and what change information do you share before an update?
- Which parts of validation remain the customer's responsibility?
- Can equipment qualification status be recorded and shown before the equipment is used?
12Where V5 fits
For software, Enterprise may include IQ/OQ documentation and validation support for V5. V5 does not supply or perform your PQ: you plan it, run it with your processes and data, and approve the result. V5's calibration and asset records can also hold qualification status for equipment, but protocol approval and release decisions remain with your people.
Frequently asked questions
Q.Is IQ/OQ/PQ required by law?+
The terms come from guidance such as EU GMP Annex 15. Regulations require equipment and processes to be suitable and validated; IQ/OQ/PQ is the common way to show that.
Q.Must PQ follow OQ?+
Annex 15 says normally yes, but PQ may sometimes be combined with OQ or process validation where justified.
Q.Does V5 provide PQ?+
No. Enterprise may include IQ/OQ documentation and validation support; the customer plans and runs PQ.
Q.Does FDA use the term PQ?+
FDA's 2011 guidance uses process performance qualification (PPQ) for the process; equipment qualification sits within Stage 2.
Q.Can supplier FAT/SAT replace IQ/OQ?+
Annex 15 allows FAT/SAT results to be relied on where justified and where transport and installation do not affect function. They support qualification rather than replacing your approval.
Q.When is requalification needed?+
After changes that could affect the qualified state, and when periodic review shows it is needed. Change control decides the scope.
Primary sources
Further reading
Explore this topic
IQ / OQ / PQ sits inside 4 overlapping topic clusters in our glossary. Every neighbour is one click away.
Electronic records, signatures, audit trail and ALCOA+ data-integrity principles.
ICH Q8/Q11/Q12 toolkit — Quality by Design, design space, control strategy, CPV and lifecycle management.
URS-through-PQ lifecycle, GAMP 5 categorisation and CSA's modern alternative.
Want to see how IQ / OQ / PQ could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
