Regulations and compliance · Practical guide

GAMP 5 vs FDA CSA: approach and scope

GAMP 5 and CSA can contribute to the same project. First establish the requirements for the specific process and the evidence needed for intended use. Then decide where each approach helps. This comparison gives QA and IT a worked alternative to replacing one method wholesale with the other.

Table of contents

At a glance

Does FDA CSA replace our GAMP approach, or do they address different questions?

GAMP 5 provides an industry approach for computerised systems used in GxP. FDA’s February 2026 CSA guidance makes recommendations for software used in medical device production and quality management systems. Your team can combine suitable elements of both approaches, guided by the requirements that apply and the intended use. CSA does not replace GAMP 5 across the board or remove the need for validation.

  • First, define the product, process, and applicable control range.
  • A method selection does not alter any underlying requirement.
  • Rationale for test method and detection limit based on specific error risk.
  • Evaluate supplier evidence based on actual coverage.

Three Levels Prevent a False Conflict

Separate the regulatory framework, the selected industry methodology, and your operational workflow. A legal or record-keeping requirement addresses a different question than a guideline for execution. Your SOP ultimately describes how the organization makes decisions and documents them.

A clean project kickoff explicitly establishes this assignment. Thus, "We are now doing CSA" becomes a verifiable statement defining which software function is under consideration, which regulatory domain is affected, and which traceability concept the team employs.

Sources: [1] [2]

Read the FDA CSA 2026 in its actual area of application

The current FDA Guidance, issued on February 3, 2026, addresses production and QMS software used in medical device manufacturing. Its scope distinguishes software functions that are themselves classified as medical devices from those that serve as part of a broader system. As a result, the pharmaceutical manufacturer does not receive a blanket waiver of its GMP requirements.

For example, a single document platform may support different purposes: a medical device quality management system (QMS) process, a human medicinal product GMP process, or purely organizational collaboration. The platform's brand does not determine this assignment. For linked workflows, relevant dependencies must also be considered.

Sources: [2] [3]

What you should actually compare

The following overview compares roles and associated responsibilities. It is not a ranking of the most effective method. A row-by-row alignment of terms may obscure differences; therefore, any assignment should always be accompanied by an explanation of the specific decision it supports.

Align GAMP 5 and CSA within the project scope
QuestionGAMP 5 PerspectiveFDA-CSA-Perspective
What role does the source play? Industry guideline as a methodological framework. FDA recommendation within the designated medical device scope.
What is being evaluated? Intended GxP use throughout the lifecycle. Function or operation in production/QMS and its failure consequences.
What evidence counts? Appropriate evidence for the intended use. Appropriate objective assurance evidence.
What determines the application? Relevance, risk, and existing knowledge. Intended Use and Process Risk within the Guidance Scope.

Sources: [1] [2]

Further reading:

Assess the consequence of failure for the process

Propose a potential decision error in the process. "The QMS is critical" is too broad. A more precise statement would be: A modified specification could reach manufacturing prior to its technical approval. From this, affected data, protection mechanisms, and required monitoring activities can be derived.

Do not treat a GAMP category as a substitute for this documentation. Terms such as "Low Code," "standard software," or the size of a change package alone provide little insight into the potential impact of a failure. The team should be able to demonstrate that the intended validation evidence actually reduces the associated uncertainty.

Sources: [3] [4]

Example: A specification workflow

A medical device manufacturer uses an electronic specification. Prior to review, it is defined that only the approved revision may be selected for a production order. A draft remains locked, and an already issued order must not lose its documented revision assignment without notice. This constitutes a specific required condition, not a test of the software provider.

For this example, the provider test is intended to cover the general version display. Whether it also proves its own role rule and job connection is only decided on the basis of its content. The following matrix shows possible complementary tests; it does not claim a universal test list.

Expected results for use of the specification
Starting pointActionExpected prior behavior
Revision A is approved, B is in draft. Production selects a revision. A is usable; B is not selectable as an approved production instruction.
Order refers to A B will be approved later. The existing instruction maintains its traceable assignment; any change follows the established procedure.
Role without approval permission User attempts to approve B. Unauthorized transfers are prevented and the attempt is appropriately addressed.
Evidence from supplier environment QA assesses its transferability. Version, configuration, and verified rule are compatible or the gap is explicitly stated.

Sources: [2]

Assign the test method to the objective of knowledge acquisition

A comparison against predefined expected results suits a precise revision rule. Exploratory testing may uncover other ways around the rule. Automation can cover repeatable checks when the method and its evaluation are suitable. Justify the method for the particular test objective.

A rigid rule "high risk always scripted, low risk always unscripted" short-circuits the decision-making process. Instead, describe why the combination of assessment, existing evidence, and process control appropriately addresses the specific risk. Unexpected findings require a transparent evaluation and, if necessary, additional work.

Sources: [2] [3]

The actual delivered package is materially significant

A supplier may provide general platform testing, configuration-specific evaluations, or customer-specific validations. The term "validation package" does not indicate which of your requirements are included therein. Similarly, it must not be assumed a priori that the package covers only standard functions.

The subject matter, status, result and transmission conditions should be recognisable for each statement taken. Missing interface, role or error cases are specifically supplemented. The effort follows the open questions; they are not calculated from the number of documents delivered or a flat-rate repetition rate.

Sources: [2] [3]

A small team requires a shared decision-making foundation

QA defines requirements and acceptable evidence. Subject-matter experts describe the consequences of a system failure. IT and the supplier explain configuration and data flows. A joint case review at an existing process is often more effective than an abstract training session involving two competing conceptual worlds.

Before widespread implementation, it should be clear how the new working practice integrates with existing procedures. If the current SOP specifies certain validation requirements, it will be reviewed and adjusted as necessary or continued as is. A new heading in the project plan does not automatically alter internal policies.

  • Scope and specific functions to be documented.
  • Describe the sequence of failures and existing control effectiveness.
  • Compare supplier documentation against own requirements.
  • Test method and remaining uncertainty justify.
  • Maintain traceability of findings, final release decision, and subsequent change evaluations.

Sources: [3] [2]

Project experience and collaboration

Apply the common methods while respecting the scope of each framework

We start by identifying the regulatory framework for the intended use with your quality team. We compare your current activities with relevant GAMP and CSA methods. FDA guidance may apply directly in medical devices. For a pharmaceutical GMP process, the method must be assessed against the requirements applicable there. We help document the choice and integrate it into your procedures. Renaming a method alone changes neither the evidence needed nor responsibility for use.

Frequently asked questions about GAMP 5 and FDA CSA

Does CSA GAMP 5 replace?

No. GAMP 5 provides a sector-wide framework, while the FDA-CSA Guidance addresses a specific application area. Determine which requirements apply and which methodological elements support your work. A change in terminology does not replace a professional assessment.

Sources: [1] [2]

Does FDA CSA apply to every pharmaceutical manufacturer?

The Guidance 2026 applies to software used in medical device production and within the quality management system (QMS) of such production. This does not automatically classify a human medicinal product GMP process as a CSA (Computer System Validation) application case. Useful methodologies may be adopted without expanding the scope of the source document.

Sources: [2] [3]

Is CSA equivalent to unscripted testing?

No. The selection of a test form is part of the assurance decision. Describe the property or failure mode being assessed and the appropriate evidence for it. This can integrate targeted, exploratory, and automated components.

Sources: [2]

Are GAMP categories still useful?

Classifying software components can help understand existing customization and development efforts. However, it does not alone address the risk associated with your process. Therefore, do not derive a fixed test volume from a single category.

Sources: [1] [3]

Can we perform fewer tests with CSA?

A reduced test volume is not an independent objective. Appropriate existing evidence can limit additional testing. A newly identified gap may require enhanced safeguards. Ultimately, justified assurance of the expected behavior in the specific application remains essential.

Sources: [2]

Does a supplier certificate constitute sufficient evidence?

Verify what the certificate or audit actually covers. It may contain relevant information, but it does not necessarily address your specific functional question. Supplement only where your own requirement or transferability has not been adequately substantiated.

Sources: [2] [3]

Does the method require its own document series?

No, an additional document series is not required solely due to the method designation. The CSA Guidance outlines the content of a record and permits other documentation formats, provided applicable requirements are met (V.A.(6)). An integrated register may be appropriate when usage, risks, testing, results, and approvals are clearly interrelated. When considering this, also take into account your own quality management procedure.

Sources: [3] [2]

Who decides on acceptance?

This determines the responsibilities of your quality system. The department, IT and QA should contribute the decision-relevant information. A supplier can provide evidence; the responsibility for the use in its own process will not become invisible.

Sources: [3]

How do we begin with limited capacity?

Select a manageable real function sequence and first evaluate existing evidence. Test the new decision documentation. Effort drivers are unclear requirements, missing data paths and hard-to-transfer documents, not the chosen abbreviation.

Sources: [2] [3]

Which version of the FDA Guidance is pertinent?

The final guidance used here is from February 3, 2026. It replaces the version from September 2025. Older presentations and SOPs should therefore be checked for the current title, scope and source status.

Sources: [2]

Sources and review date

Source date: October 6, 2026. Scope and document status are distinguished within the text. Examples and work aids are proposed suggestions; they do not replace assessment of your specific process.

  1. ISPE: GAMP 5 Guide, Second EditionJuly 2022; Public Product Description; Published; Maintaining Principles; Service Providers; Iterative/Incremental Methods; Critical Thinking
  2. FDA: Computer Software Assurance for Production and Quality Management System SoftwareFinal, 03.02.2026; III Scope; V.A(1)–(6); in particular Intended Use, Risk, Evidence, and Supplier Documentation
  3. European Commission: EU GMP Annex 11, Computerised SystemsRevision January 2011; Principle; §§ 1–4, 7, 9–13, 17
  4. EMA: ICH Q9(R1), Quality Risk ManagementR1, Correction 2 dated 23.01.2025; Sections 3–5; Formalities, Uncertainty, Subjectivity, and Risk-Based Decisions

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify the specific decision jointly

We support your team in linking the applicable requirement to the actual data workflow and a traceable validation evidence. Starting point are your existing documentation and the open technical question.

  • GAMP 5 consulting →

    Understand how GAMP 5, EU GMP Annex 11 and 21 CFR Part 11 apply to your systems. We translate the relevant requirements into proportionate validation work and evidence your team can defend in an audit.

Send a project enquiry Customer testimonials →