Table of contents
At a glance
What do IQ, OQ and PQ mean for computerised systems?
IQ is installation qualification, OQ is operational qualification and PQ is performance qualification. They assess correct installation, specified functions and fitness for the intended workflow. For computerised systems, align those objectives with actual use and Annex 11. The abbreviations do not imply three separate documents or a general three-batch rule. Select evidence that fits the system version and risks.
- Assign each piece of evidence a specific statement regarding the system.
- Do not transfer software audits without proper review.
- Evaluate supplier documentation against your intended use and system configuration.
- Link partial inspections to the complete operational process flow.
1. Integrate facility qualification and computerized system validation.
This guide looks at computer systems in the human medicine GMP environment. At the source level 6 October 2026, the European Commission is conducting Annex 11 in the revision of January 2011 and Annex 15 in the revision that has been in force since October 2015. Both are GMP guidelines; draft consultations do not constitute an additional obligation here.
Annex 15 outlines qualification and validation, primarily for facilities, equipment, supply systems, and processes. For computerized systems, the guidance refers to Annex 11, where application validation and IT infrastructure qualification are distinguished. Therefore, a software project cannot be meaningfully assessed through merely renaming an existing facility blueprint.
Use IQ, OQ, and PQ as an ordering framework for different validation questions. The tables and example below are internal work aids for this transition. Whether your organization uses these terms or other appropriate terminology should align with a consistent approach. An alternative heading does not eliminate a technical validation gap.
2. Three questions to clarify prior to documenting the structure
Begin with the intended workflow and the information upon which a decision is based. Then inquire which assumptions regarding installation, functionality, and usage must hold true for this workflow to be valid. This will reveal whether a record provides necessary prerequisites, supports a single function, or validates the interaction of functions during operation.
The matrix serves as a framework for a computerized system and is not a binding assignment of each check point. A permission test, for example, may simultaneously verify the assigned role and its functional impact. Describe both statements and their underlying conditions, rather than repeating the same test under multiple headings.
| Testing objective | Appropriate justification within the software project | What remains solely open-ended |
|---|---|---|
| IQ: defined station established | Alignment of application version, configuration, required services, and endpoints with the intended baseline | Whether professional guidelines function correctly |
| OQ: specific function operates effectively | Performed test of an authorized action and relevant error scenarios with pre-defined expected outcome | Whether the complete routine procedure operates under its actual conditions |
| PQ: intended procedure appropriate | Seamless process with appropriate roles, data, interfaces, and work instructions | Variants not considered, operational checks, or subsequent modifications |
3. IQ: Verify the installed system is operable
A viable installation basis describes what was actually provided. For your scope, for example, capture application version, released configuration state, required runtime environment, interface address, and assignment to the test environment. What matters most is not the most comprehensive inventory list, but the traceability of the prerequisites for subsequent testing.
In addition, assess whether a deviation would be detectable. A screenshot of the homepage may provide visible version information. However, it does not necessarily indicate which background service or printer assignment is currently active. Select the evidence based on the specific question; technical logs, controlled configuration extracts, or supplier certifications may contribute different elements.
With a cloud service, physical infrastructure is often not under your direct control. Therefore, clarify which statements the provider makes regarding its environment and which tenant, access, or integration configurations you are responsible for verifying. An inaccessible server neither justifies fabricated local audit logs nor the omission of relevant prerequisites.
Hold the line: A correctly installed application may still contain incorrect functional settings. Therefore, an installation qualification does not replace testing of these settings.
4. OQ: Check functions with conclusive cases
Before execution, define the behaviour that meets the requirement. For an otherwise permitted posting, decide what should happen if mandatory data are missing, the user role is not authorised or communication is interrupted. For computerised systems, Annex 11 section 4.7 explicitly addresses limits and error handling.
Derate the data from the considered risk. If a digit swap could lead to an incorrect quantity, a test with a single arbitrary value is insufficient as justification for your selection. Conversely, you do not need to perform a mechanical check of every conceivable combination, if you can clearly demonstrate that the relevant effects are covered.
A test can appear to be meaningful due to a hidden requirement. Therefore, check user role, initial status and previous data. Whoever performs a blocking function with an administrator may check a different process than intended. The actual state belongs in the execution documents.
Separate the intended use from the actual outcome. Acceptance criteria cannot be defined after the run has been completed, as this undermines the basis for comparison. Professionally justified changes may still be made, but must be evaluated as changes.
5. Performance qualification covers the full intended use
For practical implementation in software, the central question is: Does the intended workflow function with the required personnel, data, and information transfers? A successfully tested button does not guarantee that the subsequent work station receives the correct information or that an employee can appropriately manage a failure situation.
Select a representative process and justify the selection. A site with a different printer control or an interface using a different data format may represent an additional variant. Ten identical runs may provide limited insight compared to a deliberately different procedure.
The MHRA explains in section 6.19 of its data integrity guidelines the link between validation and the actual intended use. Supplier testing conducted independently of user configuration and process is insufficient for this purpose. The UK regulatory perspective complements the EU-GMP framework; it does not render all supplier verification efforts obsolete.
For software-driven manufacturing systems, standalone process and facility justifications may also be required. Clearly distinguish the purpose of each. A complete IT workflow does not substitute for the necessary evaluation of the manufacturing process.
6. Combine appropriate documentation and strategically utilize supplier invoices
Annex 15 provides appropriate combinations of qualification documents. The public ISPE description of the GAMP approach also supports iterative and incremental specification and verification. Consequently, for planning, there is no requirement to divide each project into three strictly separated document blocks.
A common protocol can initially verify the established system status and subsequently evaluate subsequent functions. Indicate the dependency: if the required configuration does not match, the conclusion of the following test remains limited. A shared filename does not render this prerequisite unnecessary.
Supplier results should be able to address the specific question. Compare the verified version, configuration, data, acceptance criteria, and outcome against your requirements. A fully aligned justification can prevent unnecessary repetition. A gap should trigger targeted supplementation, not automatic rejection of the entire package.
Document the decision in a location where it can be readily retrieved. For SMEs, a brief assignment helps: statement, existing evidence, scope, remaining local review. The actual transfer assessment should be included in the designated process.
7. Example: From Order to Verified Label
The following case does not describe an executed product test. A labeling application generates labels for internal container materials. The example requirement is: Order M-204 may only be printed using approved template version V3 and the exact associated material identifier. In the event of a communication failure, the system must not treat an unconfirmed print as completed.
The intended setup shall include Application A2, Configuration K4, Interface Profile S1, and Printer P1. The local roles are designated as Preparation and Printing. These names, versions, and rules apply solely to this example and are neither manufacturer functions nor general GMP guidelines.
The validation procedure begins with a controlled order dataset, proceeds through document selection and handover to the printer, and concludes with a comparison of readable content, machine-readable identifier, and order status. In the event of a failure, the connection is interrupted at a pre-defined point. Evaluation includes the defined behavior, such as retry capability, not merely a visible error message.
| Step and statement | Specific implementation | Requirement and Assessment |
|---|---|---|
| Setup, IQ reference | Compare A2/K4/S1 together with assigned P1 and compare against intended baseline | Consistency demonstrates the prerequisite; a different profile precludes the intended statement |
| Effectiveness, OQ Reference | For M-204, select V2 first, then V3. | V2 is locked in the example; V3 contains the defined material identifier |
| Error handling, OQ reference | Controlled transfer interrupted | Unconfirmed pressure remains open; no false closing message |
| Routine workflow, PQ reference | Prepare and operate the M-204 press according to work instruction | The order, readable text, checked identifier and completion status agree |
| Retrospective, cross-cutting | After interruption, complete the planned resumption route | Actual pressure condition is verified; no uncontrolled additional pressure. |
8. Track deviations and altered prerequisites
Conduct a failed run with its original result. Describe the expected and actual behavior, affected versions, suspected scope, and the next investigation. A subsequent successful attempt does not, by itself, explain why the initial run failed.
In the example, a correction from K4 to K5 could change the status treatment. Then, not only check the termination again. Also, evaluate whether normal completion, resumption or double processing can be affected. The scope follows the change and its effect, not only the previous label IQ, OQ or PQ.
Annex 15 Section 2.10 addresses an authorized transition to the next qualification or validation stage. This does not constitute general approval for go-live with critical open items. Therefore, please identify which subsequent activity a reviewed intermediate status can actually support.
9. Plan participation and resource requirements based on open statements
The effort increases significantly with variations, interfaces, unclear prerequisites, and lack of transferable evidence. A comprehensive documentation package can be quickly completed yet still overlook local handovers. Therefore, plan the required technical contributions prior to estimating page numbers or test case volumes.
The following knowledge is required: process, system configuration, and appropriate testing. The individual responsible for execution, evaluation, or authorization must possess qualification and authorized access. The combination of the three acronyms does not establish a fixed assignment between supplier, IT, functional area, and QA.
Provide test data, representative access points, and reachable contacts. Additionally, schedule time for report review. A tight timeline does not substitute for active involvement; rather, a clearly defined and bounded scope enables concrete planning.
10. Checklist prior to execution and completion
Use the following checklist when reviewing your inspection plan. Respond to each point with a specific reference or a named open task. A general confirmation such as "IQ/OQ/PQ available" obscures differences between planned, executed, and professionally evaluated.
Upon completion, the consolidated results must support the requested intended use. The subsequent decision on usage shall also take into account the required operational readiness. Changes in later operation will be re-evaluated based on their impact.
- Process, system boundary, and considered release are clearly defined.
- For each inspection, the statement to be supported by evidence is specified.
- Required installation and configuration have been confirmed prior to the dependent execution.
- Acceptance criteria and target values are defined prior to run initiation.
- Supplier invoices are assessed for their actual scope.
- Normal operating procedures, relevant boundaries, and failure scenarios are justified and selected.
- At least the required technical transfers are considered in combination.
- Deviations, corrections, and implications for other validations remain traceable.
- The responsible personnel and decision-makers possess the appropriate qualifications and authorizations.
- The closure signifies the documented status and remaining limitations.
Project experience and collaboration
Link the questions addressed by IQ, OQ and PQ
What is installed, do the required processes work, and is the intended use adequately demonstrated? With QA, IT and process owners, we match existing results to those questions. We can supplement usable evidence with targeted tests. Where handovers are unclear, we develop an integrated plan. Prerequisites, approvals and deviations remain visible through IQ, OQ and PQ, reducing duplication and helping identify missing evidence.
Frequently asked questions about IQ, OQ and PQ
Do we need to prepare three separate IQ, OQ, and PQ documents for each computerized system?
No. The key factors are the required evidence and a clear, traceable relationship. Annex 15 permits appropriate combinations of qualification documents. You must clearly define where the equipment, function, and intended workflow are supported. A combined protocol may be appropriate, provided that the assumptions, results, and evaluations remain clearly identifiable. Organizational requirements of your quality system must be taken into account.
What distinguishes OQ and PQ in a software-driven process?
For practical planning, OQ verifies whether specified functions operate under the considered conditions. PQ focuses on the intended operational workflow. Correct functioning of template selection does not necessarily confirm proper handover to the printing work station. Individual tests can support both questions; describe their scope and unaddressed variants.
Does a software PQ inherently require three batches?
From the IQ, OQ, and PQ checks, a universal three-batch approach for computerized systems cannot be derived. Annex 15 also addresses manufacturing processes and equipment; the specific requirements for such processes and equipment must not be generalized to all applications. Define required procedures and repetitions based on intended use. If the system is part of a process validation, its specific applicable framework must also be considered.
Can we accept the IQ/OQ results provided by the supplier?
Yes, if their statement aligns with your current status and requirements. Specifically review version, configuration, criteria, execution, and results. Adoption may be complete, partial, or with additional amendments. A manufacturer package without relevance to the local application purpose does not automatically address your outstanding questions. Similarly, it would be impractical to generate appropriate documentation solely based on its origin.
What does IQ mean for a cloud-based application without own servers?
Clarify which infrastructure and provisioning responsibilities the service provider carries and which local prerequisites remain. This may include tenant status, active configuration, roles, or integration endpoints. The selection is usage-dependent. Do not request fabricated local installation proofs for externally operated servers; evaluate appropriate supplier documentation and the unrecorded aspects of the provider’s own settings.
Who is responsible for performing and releasing the IQ, OQ, and PQ?
Personnel with the requisite technical and professional competence may perform the activities. Authorization and approval shall be granted to individuals designated within the quality system; this assignment is described in Annex 15, Section 2.2. For documentation provided by an external validation service provider, appropriate on-site personnel must verify suitability and alignment with internal procedures prior to approval (Section 2.6). Clear responsibilities for execution, evaluation, release, and acting in place within the project must be formally defined.
Can a completed PQ run resolve an open OQ deviation?
Not merely by its existence. Verify whether the PQ run actually captured the error and was executed under comparable conditions. In the labeling example, a successful normal pressure does not indicate anything about a wrong final status message following a stop. Explicitly assess the finding, its scope, and required corrections. A later positive result does not replace this investigation.
Must the entire IQ/OQ/PQ be reperformed after each update?
Not automatically complete. Assess which prerequisites and statements are affected by the update. A new interface version may impact different validation evidence compared to a editorial assistance change. Derive confirmations, repetitions, and additional checks accordingly. The validation evidence must align with the continued use version; even a full test exemption requires a justified evaluation.
Are screenshots sufficient as the sole evidence?
A screenshot alone is sufficient only to support a statement that is actually substantiated with the required context. A screenshot may illustrate a visible status, but it does not automatically verify the data source or system behavior following a connection loss. When necessary, combine observable results, technical records, and professional reconciliation. Clearly label execution, date, and context to ensure the evidence remains understandable. The number of screenshots is not indicative of the level of assurance achieved.
Sources: [2]
Is the system automatically released for production following completion of IQ/OQ/PQ?
No. The results form a basis for decision-making regarding the specific intended use. Open findings, operating procedures, training, and responsibilities must also be appropriately assessed. Annex 15, Section 2.10, describes a transition phase within the qualification and validation process, not a blanket product release. Therefore, document the requested scope of use and the actual conditions met for that use.
Sources and review date
Source date: 6 October 2026. Focus: Human medicinal product-GMP. Tables, checklists, and labeling scenarios are standalone reference tools. The MHRA guidance serves as supplementary UK regulatory orientation. The public version of the GAMP publication was reviewed; the paid full text was not accessed.
- European Commission: EudraLex Volume 4
- European Commission: EU GMP Annex 11 – Computerised Systems
- European Commission: EU GMP Annex 15 – Qualification and Validation
- ISPE: GAMP 5 Guide, 2nd Edition – Public Publisher Overview
- MHRA: GxP Data Integrity Guidance and Definitions
- ICH Q9(R1): Quality Risk Management – official EU version
Sources checked: .
Plan validation evidence for your system status
We help you link existing documentation and outstanding review objectives to a traceable evidence strategy. We consider the actual workflow, its prerequisites, and the required level of involvement.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

