CSV vs CSA: Compare Scope, Reasoning and Evidence, Not Slogans
CSV vs CSA is usually framed as old against new. The primary sources support a narrower comparison of computer system validation and computer software assurance: where each term comes from, which software a given text covers, how risk shapes the work and what record is left behind.
Written by CSV/CSA Maturity Editorial TeamPublished 11 min read
On this page10 sections
Computer system validation (CSV) and computer software assurance (CSA) are not rival rulebooks. CSV is industry shorthand for the documented work of showing that a computerized system is fit for its intended use and stays that way through change. Computer software assurance is the name the U.S. Food and Drug Administration (FDA) gives, in final guidance issued in February 2026 [S02], to a risk-based approach for establishing and maintaining confidence that software is fit for its intended use. That guidance gives nonbinding recommendations for software used as part of medical device production or the quality management system. A fair comparison looks at scope, reasoning and evidence, and sets the slogans aside.
This article is for quality, validation, IT and system-owner teams who meet both terms and need to decide what, if anything, to change. It is editorial analysis, not legal or regulatory advice. Where a sentence reports what a primary source says, the link sits beside it. Where we interpret, the sentence starts with "Our reading is". CSV here never means a comma-separated values file.
Where the two terms come from
Neither abbreviation is regulatory vocabulary in the texts cited here. The FDA guidance document [S03] writes "computer software assurance" in full and refers to software validation requirements. It does not use the abbreviations CSV or CSA, and it does not use the phrase "computer system validation". EU GMP Annex 11 [S36], which belongs to the EU guidelines for medicinal products, says the application should be validated and the IT infrastructure qualified. It uses neither abbreviation.
"CSV" is therefore a label practitioners apply to validation work on computerized systems, and what it contains depends on the procedure in front of you. Our working description for the rest of this article is: planned, documented activities that show a system meets the needs of its intended use, with a record that lets another person follow the reasoning.
The FDA guidance describes computer software assurance as a risk-based approach to establish and maintain confidence that software is fit for its intended use. It says the approach keeps software in a state of control through its life cycle, which the document calls the "validated state" (Section V of the guidance [S03]). FDA presents the document as a supplement to its 2002 General Principles of Software Validation [S35] and says it supersedes Section 6 of that earlier guidance (relationship to the 2002 guidance [S03]).
Our reading is that FDA frames computer software assurance as a risk-based way to meet existing validation requirements for the software in scope, not as a separate regime that removes validation.
What the FDA guidance covers and what it leaves out
The document is titled "Computer Software Assurance for Production and Quality Management System Software". It is a final guidance for industry and FDA staff, issued on February 3, 2026 by the Center for Devices and Radiological Health and the Center for Biologics Evaluation and Research, and it is marked as containing nonbinding recommendations (guidance cover and status [S03]). It supersedes a final guidance with a nearly identical title issued on September 24, 2025 (FDA guidance page [S02]). Its history section says the February 2026 revisions include alignment with the amended 21 CFR Part 820, the Quality Management System Regulation (guidance history [S03]).
Four points decide how far the text reaches:
- What it covers. Computers or automated data processing systems "used as part of production or the quality management system for medical devices" (FDA guidance scope [S03]).
- What it excludes. It gives no recommendations for validating device software functions, meaning software that is itself a medical device or part of one (scope exclusions [S03]).
- What it does not address. The document says nothing about pharmaceutical manufacturing, pharmaceutical GMP systems, laboratory systems or clinical systems (full guidance text [S03]).
- What stays mandatory. The recommendations are nonbinding, but the guidance says the underlying regulation requires device manufacturers to validate this software for its intended use (regulatory basis in the guidance [S03]). Our reading is that nothing in it makes validation optional.
Inside that scope, the guidance says general business software such as email or accounting applications is generally outside the validation requirement. It recommends documenting how the manufacturer decided whether a piece of software is used as part of production or the quality management system (Section V.A.1 on intended use [S03]).
For EU medicinal products the reference text is a different one. As of November 12, 2026, the EudraLex Volume 4 index [S04] lists Annex 11 as the January 2011 revision. The European Commission ran a consultation on a revised Annex 11, a revised Chapter 4 and a new Annex 22 [S05] from July 7 to October 7, 2025. The consultation is closed and its page gives no adoption date, so those texts remain consultation drafts.
Our reading is that the reasoning in the FDA guidance can inform teams outside the device sector, but the guidance does not say it applies to them. Whether to use it elsewhere, and how, is a decision for your responsible quality and regulatory specialists.
Comparison matrix: terminology, context, reasoning and evidence
The CSV column describes a common procedural pattern in our own words, because no primary source cited here defines "CSV". The CSA column paraphrases the FDA guidance. Annex 11 references are to the EU GMP text for medicinal products. The last column is editorial.
| Dimension | CSV (industry shorthand) | CSA (FDA's 2026 guidance) | Our reading |
|---|---|---|---|
| Terminology | A practitioner label for validating computerized systems. It appears in neither text cited here. Annex 11 [S36] speaks of validating the application and qualifying the infrastructure. | FDA's own term, written in full and never abbreviated in the guidance [S03]. | The label on a procedure tells you little. Ask which text governs the system in front of you. |
| Applicable context | Used across regulated sectors. The governing text depends on product type and jurisdiction, for example Annex 11 [S36] for EU GMP activities on medicinal products. | Software used as part of medical device production or the quality management system. Device software functions are outside its recommendations (scope [S03]). | A procedure that serves several sectors should say which source applies to which systems. |
| Assurance reasoning | Requirements, risk assessment and testing against intended use. Annex 11 says risk management should be applied throughout the system lifecycle (clause 1 [S36]). | Four steps: identify the intended use, determine the risk-based approach, determine the assurance activities, establish the record (framework [S03]). | Both call for risk-based reasoning. The FDA text is more explicit that function-level risk sets the kind and depth of activity. |
| Evidence expectations | Documented evidence that the system meets its requirements. Annex 11 says evidence of appropriate test methods and scenarios should be shown (clause 4.7 [S36]). | A record of intended use, the risk analysis result, the testing performed, issues found, a conclusion, and who did the work and when, with review and approval when appropriate (Section V.A.6 [S03]). | Neither removes the record. They differ in how openly the amount of evidence is tied to risk. |
How the five working topics are treated
Intended use
The FDA guidance recommends examining the intended use of individual features, functions and operations. It distinguishes software used directly in production or the quality management system from software that supports it (Section V.A.1 [S03]). Annex 11 says user requirements should describe the required functions and be traceable through the life cycle (clause 4.4 [S36]).
Our reading is that both texts start from a description of real use, and that a supplier's feature list is not such a description.
Risk reasoning
The FDA guidance sorts functions into "high process risk" and "not high process risk". A function is high process risk when its failure may cause a quality problem that foreseeably compromises safety. The document adds that risk sits on a spectrum and that the two categories are a way of presenting it (Sections V.A.2 and V.A.4 [S03]). Annex 11 says risk management should be applied throughout the lifecycle of the computerized system (Annex 11, clause 1 [S36]).
Our reading is that the test for a procedure is not whether it contains a risk step. The test is whether the reasoning reaches individual functions and changes what is done afterwards. Our guide to connecting functional risk to a proportionate assurance activity works through a synthetic decision record of that kind.
Activity selection
The guidance describes unscripted testing (scenario testing, error guessing and exploratory testing) and scripted testing. It says more rigor, such as scripted or hybrid testing, may suit high process risk functions, and that its examples are not exclusive to either risk category (Sections V.A.2 and V.A.4 on risk and testing [S03]).
Our reading is that scripts stay in the toolkit and that unscripted work is not reserved for trivial functions. The matching question in our assessment carries this note: "Neither more scripts nor fewer scripts automatically means greater maturity. Unscripted work is not undocumented work."
Evidence
The contents of the record are listed in the matrix above. Two further statements in the guidance matter here. It says the record "need not include more evidence than necessary" for the risk identified. And it recommends digital records such as system logs and audit trails as a less burdensome form than paper printouts, screenshots or duplicated results (the record, Section V.A.6 [S03]).
Our reading is that this is advice on the right amount and form of evidence. It is not permission to leave no record, and it does not prohibit screenshots.
Lifecycle change
The guidance treats assurance as something established and then maintained, so that software stays in a validated state through its life cycle (Section V [S03]). Its section on software changes concerns reporting for devices under premarket approval (PMA) or a humanitarian device exemption (HDE) (Section V.A.3 [S03]). In the EU GMP context, Annex 11 says changes should be made in a controlled manner under a defined procedure and that systems should be periodically evaluated (clauses 10 and 11 [S36]).
Our reading is that the FDA section on changes should not be used as a general change control procedure, and that under either label a change reopens the same three questions: what the intended use is now, what the risk is, and which evidence still holds.
Not a valid conclusion
Each claim below is a tempting shortcut through the comparison. None follows from the sources.
| Claim | Why it does not follow | What the sources support |
|---|---|---|
| "All test scripts are obsolete." | The FDA guidance describes scripted and unscripted testing side by side. | More rigor, such as scripted or hybrid testing, may suit high process risk functions, and the examples are not exclusive to either category (testing approaches described by FDA [S03]). |
| "CSA applies identically everywhere." | The FDA guidance has a defined scope, and other sectors have their own texts. | Medical device production and quality management system software for the FDA guidance (its scope statement [S03]). EU GMP activities on medicinal products for Annex 11 [S36]. |
| "CSA means fewer records, or none." | The guidance lists the contents of the record. | The record need not hold more evidence than the risk warrants. It is still a record (record contents in the guidance [S03]). |
| "FDA replaced CSV with CSA." | FDA uses neither abbreviation and builds on its earlier validation guidance. | The 2026 guidance supplements the 2002 software validation guidance [S35] and supersedes its Section 6 (FDA guidance [S03]). |
| "The guidance makes validation optional." | The recommendations are nonbinding. The validation requirement they address comes from regulation. | The guidance says the underlying regulation requires device manufacturers to validate this software for its intended use (regulatory basis stated by FDA [S03]). |
| "The revised Annex 11 already applies." | The 2025 revision texts are consultation drafts. | As of November 12, 2026, the EudraLex index [S04] lists the January 2011 revision. The consultation [S05] closed on October 7, 2025. |
| "A maturity score confirms compliance." | A score summarizes answers a team selected about itself. Nobody examined the evidence. | The assessment returns a self-reported profile for planning. Its stated limitations say what it cannot establish. |
If you are planning a CSV to CSA transition
None of the sources above tells every organization to switch, and none offers a figure for time or cost saved. If your team decides to change how it works, treat that as a bounded change to your own procedures, made through your own change process.
- Name the scope: which systems, which site or team, and which regulations and guidance govern them.
- Read the current primary text for that scope. Summaries, including this one, go out of date.
- Mark where your procedure already lets function-level risk decide the activity, and where it prescribes one activity for everything.
- Choose one or two systems or functions for a first application, with quality involved from the start.
- Agree what the record will contain, and who reviews it, before the work begins.
- Review the result with the people who own the procedure before widening the change.
Questions to take to your quality team
- Which regulations and guidance apply to each group of systems in our scope, and who made that determination?
- Where does our procedure tie the type and depth of testing to function-level risk?
- Can a reviewer reconstruct, from the record alone, why a given activity was chosen for a given function?
- What does our record contain for testing that was not scripted?
- Which evidence do we keep because the risk calls for it, and which because the template has a box for it?
- When a system or its use changes, what triggers a fresh look at intended use and risk?
- Who would approve a change to the validation procedure, and what would they need to see first?
Where a maturity self-assessment fits
Those questions are about practice, and practice can be described whichever label your procedures carry. The CSV/CSA Maturity Assessment asks 18 questions across seven practice areas and returns a self-reported profile. It does not decide which regulation applies to you, and a score is not evidence of compliance. Our comparison of what a self-assessment and a quality audit can each establish explains why.
The flow is: choose a scope, answer the seven areas, review your answers, give your first name, last name, work email and company, then see the profile and download it as a PDF. To describe how your team works today, start the assessment with one defined scope.
Limitations
- This is editorial analysis by a publication, not legal advice and not a determination of what applies to your organization.
- The CSV column of the matrix is our description of a common pattern. Your procedures may already be more risk-based than it suggests, or less.
- Only the sources listed below were reviewed. We did not review paid industry guides, national guidance outside the EU and the United States, or the full text of FDA's 2002 guidance.
- Section references to the FDA guidance are given to help you find the passage. Read the passage itself before relying on our paraphrase.
- Status statements are dated November 12, 2026 and will age.
Related reading
- Connect functional risk to a proportionate assurance approach: a synthetic decision record that shows the reasoning this comparison describes.
- Self-assessment vs quality audit: what a maturity profile can and cannot tell you before you act on one.
- How to assess CSV/CSA maturity: a scoped, evidence-led way to prepare your answers.
This article describes assessment model csa-maturity-2.0.0.
Sources and references
- S02Computer Software Assurance for Production and Quality Management System Software. U.S. Food and Drug Administration.
Final guidance (nonbinding), dated February 2026; covers software used in medical device production and quality management systems.
- S03Computer Software Assurance for Production and Quality Management System Software: Guidance for Industry and Food and Drug Administration Staff. U.S. Food and Drug Administration.
Final guidance document (PDF), issued February 3, 2026; nonbinding; supersedes the final guidance issued September 24, 2025.
- S04EudraLex - Volume 4 - Good Manufacturing Practice (GMP) guidelines. European Commission.
Official index of EU GMP guidelines; listed Annex 11 as 'Computerised Systems (revision January 2011)' when checked on November 12, 2026.
- S05Stakeholders’ Consultation on EudraLex Volume 4 - Good Manufacturing Practice Guidelines: Chapter 4, Annex 11 and New Annex 22. European Commission, Directorate-General for Health and Food Safety.
Consultation on draft texts, open July 7 to October 7, 2025; status shown as closed. The drafts are not operative guidance.
- S35General Principles of Software Validation. U.S. Food and Drug Administration.
Final guidance (nonbinding), January 2002; FDA's 2026 computer software assurance guidance supersedes its Section 6.
- S36EudraLex Volume 4, Annex 11: Computerised Systems. European Commission.
EU GMP guideline, revision 1, with a stated deadline for coming into operation of June 30, 2011; the version linked from the EudraLex index on November 12, 2026.