top of page

How to Write IQ, OQ and PQ Protocols: Required Content and Acceptance Criteria

Nov 5
5 min read

Updated: Nov 10

Reviewed by Aaron Lyon, President of A.P. Lyon and former Director of Quality Assurance and International Regulatory, with more than 30 years in medical device quality. Last reviewed November 10, 2026.


An IQ, OQ or PQ protocol is one of the most closely read documents in a medical device audit. Auditors open it to see whether the acceptance criteria were set before testing, whether the sample sizes have a rationale, and whether every deviation was closed before someone signed "validated." A protocol that is vague on any of these points is a common source of audit findings, even when the process itself works well.


This guide covers what a qualification protocol needs to contain, where the requirements come from, and how to keep the protocol, the executed data and the final report connected. It applies to companies working under ISO 13485:2016, FDA's Quality Management System Regulation (QMSR), or both, and to dual-standard systems that also follow ISO 9001:2026.


Where the requirements come from


ISO 13485:2016 clause 7.5.6 requires validation of any production or service process "where the resulting output cannot be or is not verified by subsequent monitoring or measurement." Validation has to demonstrate that the process can achieve planned results consistently. The clause also requires documented procedures for validation that include:


  • defined criteria for review and approval of the processes

  • equipment qualification and qualification of personnel

  • use of specific methods, procedures and acceptance criteria

  • as appropriate, statistical techniques with rationale for sample sizes

  • requirements for records

  • revalidation, including criteria for revalidation

  • approval of changes to the processes


Clause 7.5.6 also requires that records of the results, the conclusion and any necessary actions from validation be maintained.


In the United States, the QMSR took effect on 2 February 2026 and incorporates ISO 13485:2016 by reference, so the same clause now applies to FDA-regulated device manufacturers. Note that ISO 13485 asks for procedures, not a fixed protocol format. Your validation procedure defines what a protocol must contain, and the protocol shows you followed it.


IQ, OQ and PQ: what each protocol has to prove


The terms most companies use come from GHTF/SG3/N99-10:2004 (Edition 2), Quality Management Systems – Process Validation Guidance. Its definitions are a useful anchor for the objective of each protocol:


  • Installation qualification (IQ): objective evidence that key aspects of the equipment and ancillary system installation meet the approved specification and that the supplier's recommendations are suitably considered. In the guidance's own words, "is it installed correctly?"

  • Operational qualification (OQ): objective evidence of process control limits and action levels that result in product meeting all predetermined requirements. OQ is where the parameters are challenged, including worst-case conditions.

  • Performance qualification (PQ): objective evidence that the process, under anticipated conditions, consistently produces product that meets all predetermined requirements. PQ is run under normal operating conditions.


Keeping these objectives separate matters. A common finding is an OQ that only runs at nominal settings, which does not show that the operating window works, or a PQ that runs at the edges of the window, which does not show routine production performance.


What to put in the protocol


The GHTF guidance lists the elements a process validation protocol should include. Organized into the sections most quality teams use, they look like this.


Scope and identification


  • the process to be validated and the devices made with it

  • the equipment, utilities and the required quality of those utilities

  • shifts, operators and the operator qualifications required

  • a complete description of the process and the relevant product, component and material specifications


Test method and controls


  • the process parameters to be monitored and how they are controlled and monitored

  • the product characteristics to be measured and the method used for each

  • any special controls on preceding processes during the study

  • consideration of maintenance and repairs of the equipment during the study


Acceptance criteria and statistics


  • objective and measurable criteria for a successful validation

  • any subjective criteria, such as visual inspection standards, and how they are applied

  • a definition of nonconformance for both measurable and subjective criteria

  • the statistical methods for data collection and analysis, with the rationale for each sample size

  • the length and duration of the study


Revalidation


  • the criteria that will trigger revalidation, such as equipment changes, relocation, material changes or adverse trends


Five protocol problems auditors find


  • Criteria written after the data. Acceptance criteria must be approved before execution. Changing them afterward without a documented, approved deviation undermines the study.

  • Sample sizes with no rationale. "n = 30" is not a rationale. State the confidence and reliability, or the statistical basis, and connect it to the risk of the characteristic.

  • Uncalibrated or unqualified inputs. Measuring equipment out of calibration, untrained operators or unreleased materials can invalidate results. List the prerequisite checks in the protocol and record them.

  • Open deviations. Every deviation needs a description, an impact assessment and a disposition before the report concludes.

  • No revalidation triggers. Without defined criteria, changes slip through change control without anyone asking whether the validated state still holds.


The final report closes the loop


The GHTF guidance says the final report should summarize and reference all protocols and results, draw conclusions about the validation status of the process, and be reviewed and approved by the validation team and appropriate management. In practice, a good report:


  • states each acceptance criterion next to the actual result and a pass or fail

  • lists every deviation and its disposition

  • states the conclusion and any limits, such as the validated parameter ranges and product families

  • references the raw data, which should be attached or traceable


If you run validation in an eQMS, keep the approved protocol, the executed data and the report linked in the same record so the chain is easy to show. The eQMS guide explains how to adapt A.P. Lyon procedures to an electronic workflow.


A.P. Lyon documents for validation protocols


A.P. Lyon documents are editable Word and Excel files that work on paper or in an eQMS. They were written by founder Aaron Lyon, who has 30+ years in product design, development and global manufacturing and is a former Director of Quality Assurance and International Regulatory. Relevant documents include:



Each document must be adapted to your processes, products and acceptance criteria. Qualification depends on your approved study and results.


Next steps


Browse the full validation protocols category or the Dual-Standard QMS range. Buying several procedures from the same family earns a discount of 20% off 5–9 procedures, 35% off 10–19, 50% off 20–39 and 60% off 40 or more, and Build Your QMS helps you choose and price a set. For help planning a validation program or reviewing a protocol, see A.P. Lyon consulting.


Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.


Just getting started? The free Startup Quality Plan shows which procedures you need now, which can wait, and how long they take to put in place.

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page