Demystifying GAMP 5 Classification from Category 1 to 5 | Valkit.ai
Demystifying GAMP 5 Classification from Category 1 to 5
Master GAMP 5 software categorization from Category 1 to 5 with this guide to risk-based validation, categories, and compliance.
Steve Ferrell·
Why GAMP 5 Software Categorization Is the Foundation of Compliant Validation
GAMP 5 software categorization is the structured method regulated life sciences companies use to classify computerized systems by complexity and risk — and it directly determines how much validation work each system requires.
Here is a quick reference for the four active GAMP 5 software categories:
Note: Category 2 (firmware) was removed in GAMP 5 and no longer applies. Modern firmware is now classified under Categories 3, 4, or 5 depending on its function.
Getting this classification wrong is costly. Misclassify a system too low and you face regulatory findings. Over-classify it and you burn validation budget on unnecessary documentation. Neither outcome is acceptable when patient safety and data integrity are on the line.
The good news: GAMP 5 is not a rigid checklist. It is a risk-based framework designed to scale validation effort to actual risk — meaning you can do less work where it is safe to do so, and concentrate effort where it truly matters.
I'm Stephen Ferrell, Chief Product Officer at Valkit.ai and a contributing author to the GAMP 5 Second Edition, with over two decades of hands-on experience guiding organizations through gamp 5 software categorization and computerized system validation. In this guide, I'll walk you through every category, the common mistakes teams make, and how to apply GAMP 5 practically in today's regulatory environment.
The Core Framework of GAMP 5 Software Categorization
To build a solid CSV computerized system validation strategy, we must first understand the core framework of GAMP 5 software categories. GAMP 5 (Good Automated Manufacturing Practice, Fifth Edition) is not a set of laws, but rather an internationally recognized guideline published by the ISPE (International Society for Pharmaceutical Engineering). It provides a structured lifecycle approach to ensure computerized systems are fit for their intended use.
The GAMP 5 V model serves as the primary visualization tool for this lifecycle, mapping user requirements to corresponding verification activities.
Infrastructure software represents the foundational layer of our IT environment. It includes operating systems (e.g., Windows, Linux), database engines (e.g., SQL Server, Oracle), networking software, virtualization platforms, firewalls, and antivirus solutions.
Risk Level: Lowest.
Validation Strategy: We do not perform full validation on the operating system itself. Instead, we document the software name, version, patch level, and installation location. We manage these systems under standard IT infrastructure controls, applying patch management and change control procedures to ensure a qualified environment.
Category 3: Nonconfigured Products
Category 3 software refers to standard commercial off-the-shelf (COTS) software that is used as-is, without any configuration or custom code. These are systems where the user cannot alter the core functionality or database structure. Examples include standard lab instrument software (e.g., a simple pH meter interface), standard office tools, or statistical software used without custom scripts.
Risk Level: Low-to-Moderate.
Validation Strategy: The validation effort focuses on establishing a clear User Requirements Specification (URS) to confirm the software fits our business process. We perform Installation Qualification (IQ) and Operational Qualification (OQ) to verify that the system runs correctly in our environment. Testing is typically limited to verifying critical default functions.
Category 4: Configured Products
This is the most common category in pharmaceutical manufacturing and clinical environments. GAMP 5 Category 4 covers commercial software packages that are configured to match specific business processes. Configuration refers to assigning values to specific software variables, setting up user roles, defining approval workflows, and building custom reports without modifying the underlying source code. Examples include Laboratory Information Management Systems (LIMS), Enterprise Resource Planning (ERP) systems, and SCADA applications.
Risk Level: Moderate.
Validation Strategy: We focus our testing on the configuration itself rather than the base platform. This requires a detailed URS, a Configuration Specification, and a functional risk assessment. We conduct supplier assessments to leverage the vendor's software development lifecycle (SDLC) documentation, followed by targeted IQ, OQ, and Process Qualification (PQ) testing of the configured elements.
Category 5: Custom Applications
Category 5 represents custom or bespoke software developed specifically for our organization. This includes entirely custom-written applications, custom-built interfaces between systems, and custom scripts or macros (such as complex VBA code in Excel or custom Python scripts) that process GxP data.
Risk Level: Highest.
Validation Strategy: Category 5 systems require the most rigorous validation effort. We must apply a full software development lifecycle (SDLC), which includes creating detailed design specifications, conducting code reviews, performing unit testing, and executing extensive functional and integration testing.
To learn more about how these classifications apply to your systems, you can explore our dedicated resources on the GAMP 5 Category and the broader GAMP 5 Categories frameworks.
The Mystery of the Missing Category 2: Why Firmware Evolved
One of the first questions validation newcomers ask is: "What happened to Category 2?"
In GAMP 4, Category 2 was designated for firmware and hard-coded software. However, as microprocessor technology advanced, the line between hardware, firmware, and software blurred. Modern firmware is no longer just simple hard-coded instructions; it often contains complex operating systems, configurable parameters, and web-based user interfaces.
Because of this technological shift, Category 2 was officially retired in GAMP 5. Today, we classify firmware under the remaining active categories:
Category 3: If the firmware is non-configurable and used as-is (e.g., a basic laboratory scale or a fixed-function temperature transmitter).
Category 4: If the firmware allows users to configure custom parameters, alarm limits, and multi-step profiles (e.g., a configurable smart sensor or a programmable incubator controller).
Category 5: If we write custom code or scripts to modify the firmware's behavior.
By removing Category 2, the ISPE simplified the classification process, allowing us to focus on the software's functional complexity rather than where the code is physically stored.
Risk-Based Validation and the GAMP 5 Second Edition Paradigm Shift
In July 2022, the ISPE released the GAMP 5 Second Edition, marking the most significant update to the guidelines in 14 years. This update did not change the core software categories, but it fundamentally changed how we are expected to apply them.
The Second Edition explicitly moves away from rigid, checklist-based classification. Instead, it urges us to view gamp 5 software categorization as a continuum rather than a set of isolated, rigid boxes. A system rarely fits perfectly into a single category. For example, a modern chromatography data system might run on a Category 1 operating system, use a Category 3 standard database, utilize Category 4 configured signature workflows, and execute Category 5 custom calculations.
This continuum approach is deeply aligned with the CSV risk-based approach and the principles of Quality Risk Management (QRM) defined in ICH Q9. The new guidance emphasizes that we must use critical thinking instead of relying solely on a system's category to determine our validation effort.
Product Risk: How does the system affect patient safety, product quality, and data integrity?
System Complexity: What GAMP categories are active within the system?
Supplier Capability: How robust is the vendor's Quality Management System (QMS)?
By combining these factors, we can significantly optimize our testing. Applying a true risk-based reduction can lower validation effort by 30% to 50% without compromising quality, allowing us to focus our resources on the areas of highest risk. For a deeper dive into these concepts, refer to the official GAMP 5 Guidance.
Transitioning from Legacy CSV to Modern GAMP 5 Software Categorization
Historically, Computer System Validation (CSV) was notorious for generating mountains of paper. Validation teams spent weeks writing highly detailed, step-by-step test scripts and taking thousands of screenshots to prove that standard commercial software worked as intended.
To address this inefficiency, the FDA finalized its Computer Software Assurance (CSA) guidance in September 2025, officially superseding Section 6 of the older General Principles of Software Validation (GPSV) guidance from 2002. This represents a massive paradigm shift.
While CSV focuses heavily on documentation and generating "records of testing," CSA focuses on assurance and critical thinking.
Under the CSA framework, we scale our testing methods based on the GAMP category and risk level:
Unscripted Testing: For low-risk, standard functions (such as Category 3 features or standard Category 4 base platforms), we can use unscripted or ad-hoc testing. We do not need to write detailed, step-by-step scripts or capture endless screenshots. A simple "Pass" or "Fail" record with the tester's name, date, and a brief description of what was tested is sufficient.
Scripted Testing: We reserve robust, step-by-step scripted testing for high-risk, custom-configured (Category 4) or custom-developed (Category 5) functions that directly affect product quality or patient safety.
Exception-Based Reporting: GAMP 5 and CSA promote exception-based reporting, where we only document deviations or failures in detail, eliminating redundant paperwork for successful tests.
This transition allows us to leverage vendor test evidence for the underlying software platform, focusing our efforts entirely on our unique configuration and custom elements. You can read more about this modern approach in our guide on CSA for Pharma.
Practical Application: Handling Multi-Category Systems and Spreadsheets
In the real world, computerized systems are rarely simple. Most enterprise applications are hybrid systems made up of components from multiple GAMP categories.
When validating a multi-category system, we should not default to validating the entire system as Category 5 (the highest risk). Instead, we deconstruct the system and apply a scalable validation strategy to each component:
Isolate the Core Platform: Treat the vendor's base software as Category 3 or Category 4. Rely heavily on the vendor's validation package and standard OQ testing.
Focus on the Configurations: Identify and document all Category 4 configurations (e.g., custom user roles, security settings, and workflows) in a Configuration Specification, and test them thoroughly.
Target the Customizations: Isolate any custom interfaces, bespoke code, or custom scripts, and validate them as Category 5. Perform code reviews and detailed unit testing on these specific components.
Best Practices for Applying GAMP 5 Software Categorization to Spreadsheets
Spreadsheets (such as Microsoft Excel) are a classic source of confusion in regulated environments. We often hear the question: "What GAMP category is Microsoft Excel?"
The answer is: It depends entirely on how you use it. Excel itself is a standard commercial tool, but its GAMP classification shifts dynamically based on its application:
If we use Excel to calculate critical GxP data (such as specification limits, batch yields, or release decisions), we must validate it. Here are our best practices for managing spreadsheets under GAMP 5:
Treat Custom Macros as Category 5: Any custom VBA macro or script that processes GxP data — even a short 20-line macro — must be validated as Category 5 custom software. This requires a code review, version control, and functional testing.
Secure the Spreadsheet: Protect formulas from accidental modification by locking cells and enabling password protection.
Maintain Version Control: Store validated spreadsheet templates in a secure, read-only directory with strict access controls.
Verify Calculations: Perform independent manual calculations to verify that the formulas and macros yield correct results under normal and boundary conditions.
Hardware vs. Software: Key Differences in GAMP 5 Classification
While software classification is based on complexity and customization, hardware classification is much simpler. GAMP 5 divides hardware into two distinct types:
Hardware Type Description Examples Validation/Qualification Requirements Type 1 Standard Hardware Standard servers, computers, network switches, standard lab instruments Record manufacturer, model, serial number, and verify compatibility. No custom testing required. Type 2 Custom Hardware Custom-built control panels, bespoke automated machinery, custom robotic arms Requires detailed design specifications, custom engineering drawings, and full hardware qualification (IQ/OQ).
For most systems, hardware qualification is performed alongside software validation. For example, when validating an automated packaging line, we qualify the physical sensors and motors (Type 2 hardware) while validating the underlying PLC code (Category 4 or 5 software). You can explore how hardware and software integrate under GMP controls in our guide on GMP Computerized Systems.
The 10 Deadly Sins of GAMP 5 Implementation
Over our years of validating systems in Scotland and Indiana, we have seen organizations make the same mistakes repeatedly. Here are the 10 "deadly sins" of GAMP 5 implementation to avoid:
Using GAMP Categories as a Rigid Checklist: Relying on categories to dictate your testing without applying critical thinking or assessing product risk.
Falling for Vendor "Prevalidation" Claims: Believing a vendor's claim that their software is "prevalidated." Validation must always be based on your unique intended use and configuration.
Failing to Maintain a Traceability Matrix: Not linking your user requirements (URS) to your functional specifications and test cases, leaving gaps in your validation coverage.
Over-Classifying Systems: Defaulting to Category 5 validation for standard, configurable Category 4 applications, wasting massive amounts of time and budget.
Ignoring Supplier Assessments: Failing to audit or assess your software vendors, preventing you from safely leveraging their testing documentation.
Treating All Excel Spreadsheets as Low-Risk: Allowing unvalidated, macro-enabled spreadsheets to calculate critical GxP data without version control or security.
Bypassing Change Control: Applying software patches, upgrades, or configuration changes to validated systems without documenting them under formal change control.
Maintaining Separate GxP and Non-GxP SOPs: Having separate validation procedures for GxP and non-GxP systems, which increases operational complexity and leads to human error.
Failing to Validate Procedural Controls: Focusing solely on technical software controls while ignoring the standard operating procedures (SOPs) and training required to run the system safely.
Writing Test Scripts Before the URS is Finalized: Attempting to write validation protocols before your user requirements are clearly defined and approved.
To help your team stay on track, we recommend utilizing a structured GAMP 5 Checklist to guide your validation planning.
Frequently Asked Questions about GAMP 5 Categorization
Can a software vendor prevalidate their system for a GxP environment?
No. Regulators like the FDA and MHRA explicitly state that validation is the sole responsibility of the regulated organization. A vendor cannot prevalidate their software because they cannot predict your unique business processes, network environment, user access levels, or configuration choices.
However, a high-quality software vendor can provide a robust "validation accelerator package" containing their internal testing records, functional specifications, and IQ/OQ templates. You can assess and leverage this documentation to significantly reduce your own testing workload, but you must still perform validation activities to prove the system is fit for its intended use in your specific environment.
How do GAMP 5 categories align with FDA 21 CFR Part 11 and EU Annex 11?
GAMP 5 categories and regulatory requirements are highly complementary. GAMP 5 provides the methodology (how to classify and validate), while FDA 21 CFR Part 11 and EU GMP Annex 11 provide the regulatory requirements (what the system must achieve to protect electronic records and signatures).
Regardless of whether a system is Category 3, 4, or 5, if it handles GxP data, it must comply with Part 11 and Annex 11 requirements, including:
Audit Trails: Recording who created, modified, or deleted data, along with timestamps and reasons for changes.
Security Controls: Implementing role-based access control, unique user IDs, and password aging.
Data Integrity: Ensuring all data meets the ALCOA+ principles (Attributable, Legible, Contemporaneous, Original, Accurate, Complete, Consistent, Enduring, and Available).
We use GAMP categories to scale our testing of these critical compliance features. For example, we might perform standard functional testing on a Category 3 system's default audit trail, while executing complex, custom boundary testing on a Category 5 custom audit trail.
What is the difference between GAMP 5 software categories and risk priority?
A common mistake is assuming that a system's GAMP category automatically determines its risk priority. This is incorrect.
GAMP Category describes the complexity and customization of the software.
Risk Priority is a combination of three factors:
Severity of Harm: How severely would a failure affect patient safety or product quality?
Probability of Occurrence: How likely is the failure to occur (which is influenced by software complexity/category)?
Likelihood of Detection: How likely are we to detect the failure before it affects the patient?
A simple Category 3 software used in high-risk oncology drug manufacturing will have a very high risk priority, requiring rigorous validation. Conversely, a complex Category 5 custom software used in low-risk vitamin manufacturing may have a lower risk priority, allowing us to scale down our validation activities.
Conclusion
Correctly applying gamp 5 software categorization is the key to building an efficient, compliant, and modern computerized system validation program. By moving away from rigid checklists and embracing the "continuum" approach of GAMP 5 Second Edition, your team can focus its effort where it matters most: protecting patient safety, product quality, and data integrity.
At Valkit.ai, we are redefining how life sciences companies approach validation. Our AI-powered digital validation platform is designed specifically for pharmaceutical, biotech, and medical device organizations. By automating the classification, risk assessment, and test generation processes, Valkit.ai reduces validation costs by up to 80% and slashes execution times from weeks to hours through smart automations, cloning, and compliance tools.
Ready to eliminate validation bottlenecks and streamline your GAMP 5 compliance? Book a demo with Valkit.ai today and discover how our platform can transform your validation process.