Installation, operational and performance qualification are a familiar framework, but applying them to software requires care: each stage answers a different question, and merging them without thinking leaves gaps.
The three questions
- Installation qualification: is the system installed correctly, in the intended environment, at the intended version and configuration?
- Operational qualification: does it operate as specified across its intended ranges, including limits and error conditions?
- Performance qualification: does it perform reliably in the real process, with trained users, procedures and representative data?
Annex 11 does not prescribe a fixed IQ/OQ/PQ document set. What it requires is that validation is demonstrated and justified, so the framework is a convenient structure rather than a legal mandate.
Writing meaningful protocols
Installation checks should record versions, hardware or cloud environment details, security settings and the configuration baseline. Operational tests should be derived from requirements and risk, not from a vendor manual alone, and should cover limits and error handling as Annex 11 expects. Performance testing is where the business process, user roles and procedures come together, ideally with a realistic data set.
Adapting the model
For cloud and configurable products, the supplier may carry out much of the installation and base functionality testing. You can leverage that evidence if you have assessed the supplier and can show it is relevant to your configuration. The user organisation remains responsible for testing what it configured and how it uses the system. Newer thinking, including GAMP 5 second edition, accepts that risk-based records can replace rigid three-stage documents where they provide equal assurance.
Execution discipline
- Approve protocols before execution.
- Record actual results, with screenshots or output where they add value.
- Raise a deviation whenever actual and expected results differ, and assess its impact before continuing.
- Use contemporaneous, attributable entries consistent with ALCOA principles.
Documenting results so they can be reviewed
Reviewers need to be able to see what was done without re-performing it. Use clear step-by-step instructions where risk requires them, define the expected result in advance, and capture evidence in proportion to the risk. Reviewers should check not only the pass or fail outcome but also completeness, dates, signatures and consistency with the approved protocol. Any deviation from the protocol, even a minor one, should be recorded and justified before the summary report is written.
How PQRA helps
PQRA can design right-sized qualification protocols, review supplier evidence for reuse, and support execution oversight so that results stand up to audit and inspection.
Contact PQRA to discuss how we can support your computerised system validation programme.


No responses yet