Equipment Qualification in Regulated Manufacturing: The Complete Guide to IQ, OQ, PQ, and the Full Lifecycle

A blank Word document. A title that says "Operational Qualification." Below it, the last protocol someone wrote at your site, three years ago, for equipment that has since been replaced. The engineer who wrote it left two jobs ago. You have a deadline. This is how most validation work starts.

The concepts behind equipment qualification are not complicated. What is complicated is knowing what actually belongs in each phase, where most protocols fall apart, and how an auditor will read them. This guide is the canonical hub: it covers the full equipment qualification lifecycle (DQ through PQ and beyond), how IQ, OQ, and PQ fit inside that lifecycle, where PPQ and CSV come in, and how to scope each phase against the regulations that govern it. Each phase links out to a focused deep-dive when you need one.

---

Glossary: The Acronyms You Will Encounter

Before the lifecycle, the vocabulary. Validation documentation lives or dies on terminology precision; mixing these up in front of an auditor is its own kind of finding.

If a term in this guide is not in the glossary, the linked deep-dive defines it where it appears.

---

The Equipment Qualification Lifecycle: One Picture

Equipment qualification is a sequence of phases, each with a distinct purpose, each documented separately, each gated on the prior phase. Together they form the documented evidence that satisfies the qualification and validation expectations under FDA 21 CFR 820 for medical devices, 21 CFR 211 for pharmaceuticals, ISO 13485:2016 for quality management systems, and EU MDR for European medical devices. EU GMP Annex 15 (Qualification and Validation, 2015) is the EU GMP authority on the structure of the qualification lifecycle itself. GAMP 5 (an ISPE guidance, not a regulation) provides the corresponding framework for computerized systems. ICH Q9 (R1) Quality Risk Management governs how scope and formality are decided.

The lifecycle in order:

```

URS -> FS -> Risk Assessment -> DQ -> IQ -> OQ -> PQ -> Release -> Continued Process Verification -> Periodic Review / Revalidation

^

|

VMP defines what goes through this lifecycle, when, and to what depth

```

The applicable regulations expect qualification proportionate to intended use and risk. IQ/OQ/PQ is the framework most commonly used to deliver that evidence, but the depth of each phase, and whether each phase is even required, depends on the equipment's role and the risk it carries. A non-contact utility serving a non-classified area is qualified differently from a sterilizing-grade filter housing on an aseptic fill line. For the scope decision itself, see How to Determine if Equipment Needs IQ Only or Full IQ/OQ/PQ.

---

Pre-Work: The Documents That Make Qualification Possible

You cannot write a meaningful protocol without these. Auditors notice their absence immediately.

Validation Master Plan (VMP)

The VMP defines the site- or system-level approach to validation: which equipment is in scope, the qualification methodology being applied, the responsibilities of each role, the change-control approach, the periodic review schedule, and the regulatory framework it is satisfying. Every protocol you write should reference and conform to it.

A weak or missing VMP creates a recurring audit finding pattern: protocols that reference no master plan, scope decisions that have no documented rationale, and qualification packages that look like they were assembled ad hoc. The VMP exists so that does not happen.

User Requirements Specification (URS)

The URS describes what the business needs the equipment to accomplish, in plain language and outcome-focused. "The chamber must hold material at 2 to 8 degrees Celsius for up to 30 days" is a URS line. "The unit must be a Liebherr LKv 5710" is not.

The URS is the source document the qualification ultimately traces back to. Every test step in OQ and PQ should map to a URS line; every URS line should map forward to at least one test step. Without the URS, the traceability matrix has no anchor.

Functional Specification (FS or FRS)

The FS is the engineering translation of the URS: what functions, parameters, ranges, alarms, interlocks, and control behaviors the equipment will use to satisfy the URS. It is written at the level of detail an engineer needs to design the test plan. "Chamber temperature controlled by PID loop, setpoint adjustable 2 to 30 degrees Celsius, control tolerance plus or minus 0.5 degrees" is FS-level.

Risk Assessment

PFMEA is the most common format. The risk assessment identifies failure modes the equipment can experience, ranks them by severity and detectability, and documents the controls in place. The output drives the CPP list and the qualification scope.

If you are starting an OQ from scratch, How to Write an OQ Protocol From Scratch walks through reading the URS and FS, identifying CPPs, and building the test plan from those inputs.

---

Design Qualification (DQ): Proving It Was the Right Thing to Buy

DQ is the phase most often skipped or compressed, especially for off-the-shelf equipment. It is documented verification that the proposed design satisfies the URS, before money is committed and equipment is delivered.

What goes in a DQ protocol:

URS-to-design traceability. Every URS line is mapped to a feature, parameter, or capability of the proposed equipment. Where the equipment cannot meet a URS line directly, the gap is documented with a justification or a workaround.

Vendor selection rationale. Why this manufacturer, this model. For commercial off-the-shelf equipment, this is often a comparison of two or three vendors against the URS. For bespoke or custom-engineered equipment, this is a design review against the FS.

Risk assessment. A first-pass PFMEA based on the design, identifying the failure modes that the qualification will need to verify control of.

Compliance check. Confirmation that the proposed design supports the regulatory regime the equipment will operate under: Part 11-capable software for electronic records, Annex 1-compatible material finishes for aseptic equipment, accessible serviceable surfaces for cleaning validation, and so on.

When you can collapse DQ:

For low-risk, off-the-shelf equipment with a well-known vendor, DQ is sometimes folded into a combined DQ/IQ document or a brief design review memo. The decision is risk-based and documented in the VMP. Skipping DQ entirely on critical equipment is a common audit finding because it leaves no documented trail for "why this equipment, why this configuration."

Vendor qualification, FAT, and SAT

For custom or configured equipment, the qualification chain often includes vendor-side activities before the equipment ever reaches your site:

• Vendor qualification. Audit or assess the manufacturer or integrator against your supplier qualification program. For critical equipment, an on-site or remote vendor audit is common. The vendor qualification record sits alongside the DQ as part of the "why this vendor" trail.
• Factory Acceptance Testing (FAT). Functional testing of the equipment at the vendor's facility before shipment, typically against the FS. Witnessed FAT (with your engineers present) is common for critical equipment. FAT data can sometimes reduce the scope of OQ at your site if equivalency to your operating conditions is documented.
• Site Acceptance Testing (SAT). Functional testing at your site after installation but before formal IQ/OQ, often verifying that shipping and re-installation did not affect performance.

FAT and SAT records become part of the qualification package. They do not replace IQ/OQ, but a well-executed FAT can streamline the OQ scope through a documented equivalency argument.

---

Installation Qualification (IQ): Proving It Got Here and Got Set Up Right

IQ is the simplest of the qualification phases, but it is also the one people cut corners on most often. The purpose is straightforward: document that the equipment was delivered, installed, and configured according to the manufacturer's specifications and your site requirements.

Think of IQ as a detailed receiving inspection combined with an installation checklist. You are not testing whether the machine works yet. You are confirming it is physically ready to be tested.

What goes in an IQ protocol:

Equipment identification. Manufacturer, model number, serial number, asset tag. An auditor will cross-reference these against the purchase order and the VMP.

Delivery verification. All components, accessories, spare parts, and documentation listed on the packing slip arrived. No shipping damage.

Installation verification. Walk through the manufacturer's installation manual step by step. Confirm utility connections (electrical, pneumatic, water, compressed air), environmental conditions (temperature, humidity, cleanliness class), and physical placement (leveling, clearances, anchoring).

Documentation collection. User manuals, maintenance manuals, engineering drawings, P&IDs, wiring diagrams, certificates of conformity.

Software and firmware verification. Record the software version installed at qualification. This is critical because a software update later may trigger revalidation. For the change-control approach when that update arrives, see How to Handle Validation When Your Equipment Gets a Software Update.

Calibration instrument verification. If the equipment has built-in measurement instruments, verify their calibration status. Record calibration certificate numbers and expiration dates.

Utility verification. Electrical supply voltage, phase, and frequency match equipment requirements.

Common IQ mistakes:

Copying a generic IQ template without tailoring it to the specific equipment.

Failing to record serial numbers for sub-components.

Skipping the environmental check.

Not involving the equipment vendor.

Not capturing the as-installed software version explicitly enough to detect later updates.

---

Operational Qualification (OQ): Proving It Works Across Its Full Range

OQ is where the real engineering starts. The purpose of OQ is to demonstrate that the equipment operates as intended across its specified operating range, including boundary conditions. This is the phase auditors spend the most time in.

The key concept in OQ is worst-case testing. You are not just testing at the nominal setpoint. You are testing at the upper and lower limits of the justified operating range for every Critical Process Parameter.

What goes in an OQ protocol:

Test plan and rationale. Before listing test steps, explain what you are testing and why each test exists.

Operating parameter verification. For each CPP, test at the low limit, nominal setpoint, and high limit of the justified operating range. Record actual measured values, not just pass/fail.

Alarm and interlock testing. Deliberately trigger every alarm and interlock to verify they activate at the correct thresholds and behave as specified.

Safety feature testing. Emergency stops, safety circuits, light curtains, and other safety devices.

Control system verification. HMI screens, operator inputs, recipe management, data logging functions.

Power failure and recovery. Where applicable, simulate a power failure and verify the equipment recovers to a defined state.

Acceptance criteria. Every single test step must have a predefined, measurable acceptance criterion written before testing begins. For the structure that makes acceptance criteria audit-defensible, see How to Write Acceptance Criteria That Won't Get Flagged in an Audit.

Common OQ mistakes:

Testing only at the nominal setpoint.

Vague acceptance criteria.

Not testing alarms.

Skipping power failure recovery.

Not including a traceability matrix.

Conflating equipment design range with the justified operating range. Test at the boundaries you intend to operate within, not at the equipment's design extremes unless your process actually approaches them.

---

Performance Qualification (PQ): Proving It Makes Good Product Consistently

PQ is the phase that connects equipment qualification to actual production. The purpose of PQ is to demonstrate that the equipment can consistently produce product that meets all quality requirements under real-world production conditions.

The critical difference between OQ and PQ: OQ tests the equipment in isolation. PQ tests the equipment as part of your manufacturing process, with your actual materials, your trained operators, and your production environment.

What goes in a PQ protocol:

Production conditions. PQ should be executed using routine production conditions: actual raw materials, the SOPs operators will follow in routine use, and trained personnel. A justified representative substitute may be used in cases where actual product or operator involvement is not possible at this stage, provided the substitution and its rationale are documented.

Batch or run requirements. PQ run count should be justified based on process risk, variability, product impact, and your acceptance strategy. Three consecutive successful runs is a common convention (especially carried over from PPQ practice), but it is not a universal rule. Document the rationale for whatever number you choose.

Sampling plan. How many samples, where they will be collected, what will be tested.

Product quality testing. Test the actual product output against your product specifications, not against the equipment's operating parameters.

Process capability analysis. If capability analysis is part of your acceptance strategy, predefine the threshold and the sampling assumptions and justify them based on characteristic criticality, sample size, and site standards. A Cpk of 1.33 is a common reference point, but the appropriate threshold depends on the process.

Deviation handling. Define in advance how deviations will be handled.

Common PQ mistakes:

Running PQ with engineering staff instead of trained production operators.

Insufficient runs without a documented rationale.

Not monitoring the process during execution.

Treating PQ as a formality.

---

PPQ vs PQ: Don't Confuse the Two

PQ is equipment-focused: a specific piece of equipment performs reliably under production conditions. PPQ (Process Performance Qualification) is process-focused: an entire manufacturing process is reproducible at commercial scale, typically across multiple batches.

PPQ is the second stage of the FDA Process Validation lifecycle (Guidance for Industry, 2011), sitting between Stage 1 Process Design and Stage 3 Continued Process Verification. PPQ batches are commonly executed in sequences of three (the "three batch rule" that frequently leaks into PQ conversations), but the actual number is risk-based and process-specific.

Where PQ asks "does this equipment perform reliably?", PPQ asks "does the entire process reliably produce conforming product at commercial scale?". A site can pass PQ on the equipment and still need PPQ on the manufacturing process. They are not interchangeable, and conflating them in a protocol or report is a recurring audit observation.

---

Software-Heavy Equipment: CSV and CSA

Equipment with significant software (configured SCADA systems, custom-developed applications, complex PLC logic, web-based HMIs) is often qualified under a Computer System Validation (CSV) or Computer Software Assurance (CSA) lifecycle in parallel with or instead of traditional IQ/OQ/PQ.

CSV is the established framework, anchored by GAMP 5 software categories (Category 1 infrastructure software, Category 3 non-configured commercial products, Category 4 configured commercial products, Category 5 custom-developed software). The validation rigor scales with category.

CSA is FDA's guidance for a more risk-based, lighter-touch approach for low-risk software, issued as a draft in 2022 and finalized in September 2025 (revised February 2026 to align with the QMSR). The core idea is that intended-use risk drives test depth, and that automated testing, vendor evidence, and unscripted exploratory testing all count as objective evidence.

Many regulated firms map software qualification to IQ/OQ/PQ-equivalent installation, functional, and performance testing, rather than treating CSV/CSA as fully separate. The structure that fits best is site- and system-specific and should be defined in the VMP. For equipment with embedded firmware that gets vendor-pushed updates, the change-control and impact-assessment workflow matters more than the initial qualification depth.

---

What Ships at the End: Executed Evidence and the Summary Report

A qualification is not complete when the last test step is checked. It is complete when the executed evidence is reviewed, deviations are dispositioned, the summary report is signed, and the equipment is formally released for its intended use.

The package an auditor expects to see at the end includes:

• The executed protocol with every result recorded, performer identified, and timestamp captured
• Raw data attached or referenced (chart recorder traces, calibration certificates, system event logs)
• Each deviation documented with root cause investigation, impact assessment, and disposition
• The final traceability matrix linking every requirement to the evidence that satisfied it
• A summary report stating the objective, what was tested, what passed, what deviated, and the conclusion
• A release statement and signatures matching your site approval procedure

The executed records themselves should satisfy ALCOA+ data integrity expectations: Attributable (who did what), Legible (readable now and in retention), Contemporaneous (recorded at the time of the event), Original (raw data preserved), Accurate (no errors or unjustified amendments), plus the +Complete, Consistent, Enduring, and Available principles regulators added on top. Paper records require contemporaneous corrections (line through the original entry, reason, date, initials); electronic records require a Part 11 / Annex 11 compliant audit trail with documented review.

If any of these are missing, the qualification is incomplete on paper, regardless of whether the equipment is technically running well. For a deeper look at what auditors specifically check in the executed package, see What Auditors Actually Look for in Validation Documentation.

---

End-to-End Worked Example: A Sterilization Autoclave

To make the lifecycle concrete, here is one piece of equipment going through every phase. Equipment: a steam sterilization autoclave for product container sterilization in an aseptic fill line.

URS extract: "The autoclave shall sterilize Type II glass vials and stainless-steel filling components to a Sterility Assurance Level (SAL) of 10 to the negative 6 using saturated steam at 121 degrees Celsius, with cycle times suitable for routine production batches of up to 6,000 vials per cycle, with documented heat penetration evidence in the worst-case load configuration."

FS extract: "Cycle parameters: exposure 121 degrees Celsius for minimum 15 minutes (overkill approach per ISO 17665-1, F0 minimum 12; bioburden-based cycles use F0 derived from product bioburden and target SAL). Steam supply 30 psi minimum at point of use. Thermocouple data logging at 12 distributed positions, sample rate 5 seconds. Door interlock prevents opening above 80 degrees Celsius chamber temperature. Bowie-Dick test cycle for daily air-removal verification."

Risk assessment output (PFMEA, abbreviated): Cold spot in load (high severity, low detectability without mapping), incomplete air removal (high severity, medium detectability), cycle interrupted before sterilization complete (high severity, high detectability via alarm). CPP list: chamber temperature uniformity, exposure time, F0, steam quality.

DQ: Vendor design review against the URS confirms the proposed unit supports the cycle parameters, instrumentation, and load capacity. Compliance check confirms Annex 1 compatible material finishes, Part 11 capable cycle records, and serviceable cleaning access. PFMEA risks mapped to design controls.

IQ: Vendor delivery verified against PO. Steam, water, electrical, and pneumatic utilities connected per drawings. Door seals installed per manual. Software version recorded. Built-in chamber thermocouples calibrated, certificates filed. Bowie-Dick test pack stocked.

OQ: Empty-chamber heat distribution mapping at 121 degrees Celsius across 12 positions, per cycle, three consecutive cycles. Chamber uniformity within plus or minus 1.0 degree of setpoint, per ISO 17665-1 and site SOP. Door interlock challenge above and below 80 degrees Celsius. Cycle parameter verification at low, nominal, and high steam supply pressure within the justified operating range. Alarm activation at every defined threshold. Bowie-Dick cycle daily-test verification.

PQ: Loaded heat penetration mapping with biological indicators at the worst-case load configuration (maximum density, identified cold spots from OQ mapping). Three consecutive successful cycles. F0 minimum 12 demonstrated at every monitored position. All BIs killed. Bioburden challenge studies per the cleaning validation strategy. Routine release cycle defined.

Release: Summary report signed, equipment released for production use. Continued process verification monitoring plan defined: ongoing F0 trending, periodic re-mapping cadence, BI release frequency.

Ongoing: Vendor releases firmware update 14 months later. Change control opens, software-update validation framework applied. Cycle parameter performance unchanged. Updated equipment record. Five-year periodic review confirms continued validated state with no scope changes required.

That is the entire lifecycle for one piece of equipment. Different equipment compresses or expands different phases, but the structure is the same.

---

Revalidation: When You Have to Do It Again

Equipment does not stay in its validated state forever. Revalidation is triggered by:

Significant equipment modification. Hardware change that affects qualified parameters, mechanical rebuild, replacement of critical components.

Software update. Firmware, application, OS, runtime, or vendor-cloud component change. The depth of revalidation is driven by the change classification (documentation update, impact assessment only, targeted testing, partial revalidation, or full revalidation). For the framework, see How to Handle Validation When Your Equipment Gets a Software Update.

Equipment relocation. Move the equipment, requalify the new installation. IQ at minimum; OQ if utility connections changed materially.

Process change. A change to the product, the SOPs, or the production conditions that affects qualified parameters. PQ may need to be revisited even if the equipment itself is unchanged.

Periodic review. Every two to five years, depending on site procedure and equipment risk. The review is documented; the conclusion may be "continued validated state confirmed, no action required."

Continued Process Verification (Stage 3 of the FDA Process Validation lifecycle). Ongoing monitoring data shows the process drifting outside expected variability. Investigate, and revalidate where the data warrants it.

Retirement and decommissioning. Equipment eventually leaves service. The decommissioning record closes the lifecycle: a documented decision to remove the equipment from production use, the rationale (replacement, end-of-life, end-of-product), the disposition of records (retained per record retention SOP, typically minimum 5 to 25 years depending on regulatory framework and product), and any product-impact assessment if the equipment was used for marketed product. Equipment that is "out of use but still in the corner of the room" without a decommissioning record is a recurring audit finding.

The decision in every case is risk-based, governed by your change control SOP, and documented. "We have always done it this way" is not a defensible answer when an auditor asks why.

---

When You Need More Than IQ/OQ/PQ

Some systems require additional or alternative qualification structures:

• DQ for any non-trivial new equipment (already covered above)
• PPQ for the manufacturing process built on the equipment (FDA Process Validation Stage 2)
• CSV / CSA for software systems
• Cleaning validation for product-contact surfaces
• Sterilization validation for terminal sterilization processes (autoclaves, depyrogenation ovens, gamma, ethylene oxide), each with its own ISO/ANSI/AAMI standard
• Aseptic process simulation (media fills) for aseptic manufacturing
• Container closure integrity for sterile drug products
• Stability program qualification for stability chambers

The VMP defines which apply to each system. The qualification scope decision for each is the same risk-based logic that governs IQ/OQ/PQ scope.

---

Documentation Expectations Across the Lifecycle

What an auditor expects to find at any point in the equipment's life:

• A current VMP that includes this equipment
• A current URS, FS, and risk assessment
• An executed DQ (or documented justification for collapsing it)
• An executed IQ with all required attachments
• An executed OQ with all required attachments
• An executed PQ with all required attachments (where applicable)
• A signed summary report and release statement
• Change control records for every modification since release
• Periodic review records on the defined cadence
• Calibration records on every measurement instrument
• Maintenance records per the PM schedule
• Continued process verification data (where Stage 3 applies)

If any of these are missing or thin, that is the audit observation. The depth of the conversation in the audit is set by how complete and coherent this documentation looks, not by how the equipment is actually performing.

---

Getting Started

If you are starting fresh on a piece of equipment:

1. Confirm or update the VMP entry
2. Write or confirm the URS
3. Develop or confirm the FS
4. Run the risk assessment (PFMEA)
5. Decide qualification scope (use How to Determine if Equipment Needs IQ Only or Full IQ/OQ/PQ)
6. DQ if applicable
7. IQ, OQ, PQ in sequence
8. Use How to Write an OQ Protocol From Scratch for the OQ protocol writing process
9. Use How to Write Acceptance Criteria That Won't Get Flagged in an Audit for every test step
10. Release per the summary report
11. Set up periodic review
12. Apply the change control framework when software or hardware changes occur, including the software-update validation workflow

If you are walking into an existing equipment situation that does not have the documentation above, the first job is the gap analysis: what exists, what is missing, what needs to be reconstructed or remediated. That is harder than starting fresh and is its own multi-week project.

---

The Real Problem Nobody Talks About

The concepts in this guide are well documented. The regulatory expectations are clear. The challenge is not understanding what to do. The challenge is actually doing it efficiently.

Most engineers spend weeks writing protocols from scratch, copying and pasting from old documents, reformatting tables, chasing down regulatory references, and manually creating traceability matrices.

That is the gap we built Valiqa to fill. Not another document management tool that stores your protocols after you write them. A platform that generates the actual protocol content: test steps, acceptance criteria, regulatory traceability, all formatted to your company's specific document structure.

Because the hard part was never understanding equipment qualification. The hard part was writing it down at the depth and consistency an audit requires.

If you are ready to go deeper on any phase, the dedicated guides cover what the pillar can only summarize: How to Write an OQ Protocol From Scratch, How to Write Acceptance Criteria That Won't Get Flagged in an Audit, What Auditors Actually Look for in Validation Documentation, How to Determine if Equipment Needs IQ Only or Full IQ/OQ/PQ, and How to Handle Validation When Your Equipment Gets a Software Update.

---

Valiqa is an AI-powered validation lifecycle platform for regulated manufacturing. Learn more at valiqa.io

If you are weighing whether to keep handling protocols by hand or move to a tool, see our category-level guide to choosing validation software for equipment qualification. It walks through the four categories of tools and the seven dimensions that decide which one fits your team.

Qualification is not a one-time event. When changes occur to the equipment, the process, or the inputs, the question of partial vs full requalification comes up. We covered the risk-based framework for that decision in our post on revalidation: when do you actually need to redo IQ/OQ/PQ.

Not sure which category of validation software fits your team? Take the self-scoring evaluation. It walks through the seven dimensions in a few minutes and is honest when the answer is not Valiqa.

The VMP is the document where all of this fits together as a coordinated program. We covered the VMP itself in detail in What is a Validation Master Plan and who owns it.