
GAMP 5 Categories Guide
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
ExploreThe industry framework regulators and QA teams use to scope computerized system validation.
GAMP 5 is the shared vocabulary of computerized system validation — when a vendor says 'Category 4' or an auditor asks for your lifecycle approach, this is the framework behind the words.

GAMP 5 — A Risk-Based Approach to Compliant GxP Computerized Systems — is the industry guide published by ISPE (International Society for Pharmaceutical Engineering) that defines how regulated companies specify, validate, and maintain computerized systems. The current version is the second edition, published in July 2022.
Its core ideas: scale validation effort to risk, complexity, and novelty; leverage supplier activities and documentation instead of repeating them; apply critical thinking rather than templated test volume; and manage systems across their whole lifecycle — concept, project, operation, retirement — not just at go-live.
Its best-known tool is the software category classification: Category 1 (infrastructure software), Category 3 (non-configured products), Category 4 (configured products), and Category 5 (custom applications). The category signals how much specification and verification work the regulated company owes on top of what the supplier already did. A configured multi-tenant eQMS is typically assessed as Category 4.
GAMP 5 is not a regulation — no authority enforces it directly. It is the industry's consensus method for meeting the validation expectations that ARE law (21 CFR Part 11 §11.10(a), EU GMP Annex 11). Auditors use its vocabulary because everyone else does.
When a quality team qualifies an eQMS, LIMS, or MES supplier, the assessment is almost always GAMP-shaped: what category is the system, what does the supplier's quality system cover, which lifecycle deliverables exist (URS, risk assessment, configuration specification, test evidence, traceability), and what residual work belongs to the regulated company.
The second edition (2022) matters because it modernized the framework for how software is actually built and run now: it embraces agile and incremental delivery, cloud services and SaaS, automated testing and tool-supported traceability, and aligns with the critical-thinking direction FDA later formalized in its Computer Software Assurance guidance. Validation positions written against the 2008 first edition tend to over-document and under-think — exactly what the second edition argues against.
GAMP 5 is the how behind several regulatory whats:
The practical failure mode with GAMP 5 is treating it as a template library: generating maximum documentation for every system regardless of risk. The framework itself says the opposite — a Category 4 configured product with a qualified supplier should lean on supplier evidence, focus testing on the regulated company's configuration and intended use, and document decisions rather than boilerplate.
A workable pattern: classify the system honestly, assess the supplier once and deeply (quality system, lifecycle deliverables, change and release discipline), write a URS that reflects your intended use rather than the vendor's feature list, risk-assess per requirement, and let the risk tier drive test depth.
Complere is assessed as a GAMP 5 Category 4 configured product and ships the lifecycle deliverables a GAMP-shaped supplier assessment asks for — VMP, URS, risk assessment, traceability matrix, IQ/OQ/PQ protocols, Part 11 checklist, and audit trail specification — per module, generated against the customer tenant. Validation depth is scoped per requirement risk in line with FDA's CSA guidance. The artifact list and clause mapping are public on the validation pack page; the methodology is described in the validation approach, and the category model in the GAMP 5 categories guide.
Common questions about GAMP 5 sourced from regulatory references and inspection patterns.
No — GAMP 5 is industry guidance from ISPE, not a regulation. What is mandatory is validation itself (21 CFR Part 11 §11.10(a), EU GMP Annex 11). GAMP 5 is the consensus method most regulated companies and auditors use to meet those requirements, which is why supplier assessments speak its vocabulary.
A configured commercial eQMS is typically Category 4 (configured products): the supplier builds and tests the product, and the regulated company specifies, configures, and verifies its own intended use on top. Custom-developed extensions would be assessed as Category 5.
The 2022 second edition modernized the framework for current software practice: agile and incremental delivery, cloud and SaaS, automated testing and tool-based traceability, stronger emphasis on critical thinking over document volume, and closer alignment with the risk-based direction FDA formalized in its Computer Software Assurance guidance.
They point the same way. GAMP 5 (second edition) and FDA's CSA Final Guidance (February 3, 2026) both argue for scaling assurance effort to risk and intended use rather than generating uniform documentation. GAMP 5 covers the full lifecycle method; CSA is FDA's position on assurance for production and quality system software.
Walk through the modules and workflows that address this area inside a controlled, validation-ready quality system.
Explore related topics, modules, and compliance resources for a deeper understanding of your quality system.

Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore
Explore this topic in more depth to build a complete picture of your quality and compliance operations.
Explore