GAMP 5 categorises software by how much it is configured or customised, and that simple idea is the fastest way to decide how much validation a computerised system genuinely needs.
Why categories exist
The ISPE GAMP 5 guide, with its Second Edition published in 2022, promotes a risk-based, lifecycle approach to computerised systems in regulated environments. Software categories give a starting point: the more a system is configured or custom built, the more of the lifecycle activity sits with you rather than with the supplier.
The categories in practice
- Infrastructure software: operating systems and databases, generally qualified through the infrastructure rather than validated individually.
- Non-configured products (Category 3): used as supplied, so validation concentrates on confirming fitness for intended use and on version control.
- Configured products (Category 4): the typical laboratory, quality and ERP system. Configuration decisions are documented and tested, and the supplier’s quality system is assessed.
- Custom applications (Category 5): bespoke code where the full development lifecycle, including code review, falls to you or your developer.
Using categories wisely
Category is a guide to effort, not a substitute for risk assessment. A simple configured system that releases batches carries more risk than a complex one that tracks meeting rooms. Many real systems are hybrids: a configured platform with custom reports or interfaces, in which case each element should be handled according to its own category and risk.
Leveraging the supplier
Supplier documentation can reduce your own testing if the supplier has been assessed and its testing is relevant to your intended use. Annex 11 expects a formal agreement defining responsibilities where a third party provides services. Reliance has limits: configuration, interfaces and your own data still need to be verified in your environment.
Moving from validation to assurance
The Second Edition emphasises critical thinking and proportionate effort, in line with the wider shift toward assurance-based approaches. Regulators do not ask for more paper, they ask for evidence that the system fits its use and that the risks are controlled.
Related reading
- Computerised System Validation: A Risk-Based Lifecycle That Survives Inspection
- Writing a User Requirements Specification That Validation Can Actually Test
- Validating Cloud and SaaS GxP Systems: Supplier Oversight and Shared Responsibility
How PQRA helps
PQRA classifies systems, defines proportionate validation plans, assesses suppliers and prepares the documentation that shows reviewers how effort was matched to risk.
Ready to talk it through? Contact the PQRA team.


No responses yet