Regulations and compliance · Practical guide

FDA CSA: documenting assurance evidence and conclusions

An FDA CSA assurance record explains why a software function has sufficient assurance for its intended use. Link the use to the activities performed, results, findings and decision. This makes the record meaningful for production and quality management system software in medical device manufacturing, whether the supporting report is short or extensive.

Table of contents

At a glance

Which findings and decisions should our assurance record make traceable?

Document intended use, the risk assessment outcome, assurance activities, significant results and identified problems. Explain whether the function is acceptable for that use and how findings were resolved or otherwise justified. Link evidence to the people involved, date and tested version. FDA does not recommend one universal report type. Suitable digital evidence can form part of the record.

  • The record contains a justified decision, not merely a test count.
  • Open findings and their handling must be visible in the conclusion.
  • Link existing digital evidence purposefully instead of unnecessarily duplicating documentation.

1. Write for a specific usage decision

The starting point is a clear statement defining what the function is intended to achieve. "The system was tested" is too general. For example, specify that an authorized user should be able to capture a complaint with specific mandatory fields and route it to the responsible handler. Boundaries should include: which decisions does the application not make?

The FDA-CSA Guidance dated February 3, 2026, addresses production and QMS software in the medical device sector. Its recommendations regarding documentation support compliance with applicable requirements; it is not a standalone law and does not constitute a comprehensive compliance checklist. A record must align with actual use, not merely fulfill a prescribed form in full.

Sources: [1] [2]

2. Link the key information elements

Section V.A.6 of the Guidance outlines the information that should be included in a traceable assurance record. This includes intended use, risk assessment, activities performed, identified issues, conclusions, and details on execution. A predefined review and approval should be considered, where appropriate in the specific context.

Our matrix translates these elements into practical questions. It is not a prescribed FDA template. The information may be distributed across multiple controlled, linked objects. What is essential is that a subsequent reader can understand the statement without prior knowledge of the project and that the necessary detailed evidence is available.

Own work aid for a compelling Assurance Record
ElementQuestion to askTypical weak peak entry
Purpose of use Which function under what conditions? Standard software validated
Risk What consequence of failure justifies this level of evidence? Low risk without justification
Activity What was investigated using which basis? Test successfully completed
Findings What was identified and how was it addressed? No critical points identified without clinical finding reference
Conclusion What usage is acceptable on this basis? Released without scope
Assignment Who, when, which version, and what evidence? Link to a shared folder whose contents were overwritten

Sources: [1]

3. Make the verified state identifiable

A result must have a clearly demonstrable basis. Depending on the intended use, version, configuration, interface status, and data used may be relevant. If a test could only be performed in a deviating environment, identify that deviation and its significance. An identical product name alone does not establish identical conditions.

In addition, link accepted supplier documentation to the specific statement it supports. It is not necessary to fully copy every document. However, it must be clearly established which evidence has been evaluated and what limitations remain. A simple link to a general supplier portal is often insufficient, particularly when the portal's content is subject to ongoing changes.

Sources: [1]

4. Example: a record for a mandatory field verification

In the example, the manufacturer includes a mandatory field for the affected product identifier in its complaint management application. The function shall ensure that incomplete cases are not treated as fully processed and forwarded further. In the assumed process, the safety-related assessment is conducted separately; this requirement is explicitly stated as part of the risk justification.

The following internal draft note illustrates how a finding is linked to a conclusion. For the example, it is assumed that an initial inspection identifies a bypass through import, and a subsequent correction is supported by appropriate documentation.

Example: completed Assurance Record
FieldExample contentComment on the statement
Purpose and Scope Product identity required upon manual entry and import; no automatic safety decision. Both input paths are in scope
Risk Incomplete assignment delays processing; separate safety evaluation remains valid Demonstration of control acceptance in an actual project setting
Activities Verify complete and incomplete datasets via both pathways The inspection focuses on the actual regulation.
Finding Manual data entry prevents onward transmission; import initially bypasses mandatory fields No overall success assessment
treatment Import rules corrected; affected cases re-evaluated; results assigned Link the correction to its evidence
Conclusion Use of the described mandatory field function in the corrected version is acceptable if the aforementioned evidence is available. No release of all other complaint functions

Sources: [1]

5. Reason the treatment of open points

Not every finding carries the same significance. Describe which function is affected, what potential consequences may arise, and whether an appropriate correction or control is in place. The record should indicate why the remaining usage remains acceptable or why the decision is being deferred.

A general statement such as "no critical errors" is weak when the criteria or associated findings are absent. In the example, the import pathway would be part of the requirement and could not simply disappear from the conclusion without proper justification. If the use of this pathway is initially excluded, such exclusion must be effectively implemented and explicitly stated in the conclusion.

Sources: [1]

6. Use digital evidence with sufficient context

The Guidance encourages the use of appropriate digital records, logs, and existing system information. This can avoid unnecessary manual repetitions. Critical factors are credibility and traceability, not the medium alone. An automatically generated file is not inherently complete or correct.

Check whether the evidence can still be properly linked to the correct batch and date. Consider required result details, deviations, and the significance of status values. A summary report may reference these information points. A screenshot is useful when it substantiates a relevant point; a universal requirement for screenshots cannot be inferred.

Sources: [1]

7. Match the review and responsibilities to the process

A traceable conclusion requires the professional authority and competence of the involved personnel. The roles responsible for review or approval are determined by applicable requirements and the established procedure. The CSA guidance does not establish a universal QA signature for each individual test run.

During review, particularly assess alignment of purpose, risk, scope, and decision. Have relevant findings been considered? Does the accepted evidence truly support the conclusion? A purely formal completeness check may overlook such inconsistencies. For small teams, a concise and well-integrated record may be significantly easier to evaluate than multiple disjointed reports.

Sources: [1] [2]

8. Checklist for Record Closure

End the recording with a clear usage limit. The limit should neither be more restrictive than the actual decision made nor extend beyond the existing evidence. A demonstration of a mandatory field function does not constitute complete validation evidence for the entire complaint management platform.

Our checklist supports the final consolidation phase. It can be integrated into existing workflows. Crucially, the documented conclusion must remain understandable even after personnel or version changes, and the required validation evidence must remain accessible.

  • Use and not covered functions clearly described.
  • Risk assessment linked to actual control acceptances.
  • Activities and verified basis traceable.
  • Findings including their handling are visible.
  • Required digital traceability records assigned.
  • The conclusion aligns with the achieved coverage.
  • Execution, responsibility, and appropriate review documented.

Sources: [1]

Project experience and collaboration

Use test results to document the decision on intended use

With your team, we assemble an assurance record covering intended use, risk, test activity, results and open deviations. An extra screenshot rarely resolves a missing link to the version tested. Existing evidence can support well-understood standard functions. A configuration that the evidence does not cover needs additional testing. Within the specified medical device context, we help you document the decision and its risk at an appropriate level of detail.

Frequently asked questions about Reaching a conclusion from FDA CSA evidence

Is there a prescribed FDA-CSA form?

The Guidance outlines appropriate information elements and examples, but does not specify a universal report format. Use a form that clearly links purpose, activities, results, and conclusions in a logical and traceable manner. An existing electronic tool may be suitable if the required evidence remains intact.

Sources: [1]

Must every test step be documented in detail?

This depends on the method and the intended conclusion. For exploratory testing, objectives, relevant activities, results, and findings may be documented without a predefined sequence of clicks. For other types of validation questions, more detailed expectations are appropriate. The documentation must support the conclusion.

Sources: [1]

Does a summary of all completed tests exist?

Not solely when purpose, basis, or findings are missing. A summary can be helpful but must highlight the key details. Even unperformed tests and issues can be highly relevant to the decision and must not be obscured by a success rate.

Sources: [1]

How are open findings documented?

Describe the impact, treatment, and remaining significance for the intended use. A justified limitation may be part of the decision. The record must not omit an open point solely because remediation is planned in a subsequent ticket.

Sources: [1]

Do we need to fully re-write supplier assessments?

No. Appropriate existing evidence can be utilized with traceable attribution. Assess its quality and coverage for your specific application. It must remain evident which statements are adopted and which additional configurations or process conditions require further investigation.

Sources: [1]

Are screenshots always required?

The guidance does not state a general obligation. Use appropriate digital records, logs, or other evidence that demonstrates the relevant behavior. A screenshot may supplement but does not replace invisible data or processing information when such information is essential to the assertion.

Sources: [1]

Must QA sign off on each Assurance Record?

Not mandatory. The FDA Guidance calls for review and approval, as appropriate, potentially with the signature and date of an authorized individual (V.A.(6)). It does not require the signature of a specific QA role for every record. The procedure must specify who is authorized to professionally evaluate the results and approve the corresponding decision.

Sources: [1] [2]

Is an electronic approval automatically a Part 11 signature?

No. The record scope, meaning of the action, and actual implementation must be considered. A status change is not solely justified by its name being an electronic signature. Conversely, an electronic approval within the appropriate context may trigger corresponding requirements; the specific function must be verified.

Sources: [1]

Can a record consolidate multiple software functions?

Yes, if the use, risk, and evidence for each remains sufficiently distinguishable. A joint report may be appropriate, but it must not create the impression that successful testing of one function automatically validates the suitability of all other functions on the same platform.

Sources: [1]

What is the most critical closing question?

Can a qualified reader identify why this specific functionality is acceptable for this exact application? If the answer relies solely on additional oral expertise, clear linkages or a definitive conclusion are often missing. Specifically address this gap.

Sources: [1]

Sources and review date

Source date: 7 October 2026. Regulatory requirements, guidelines, and industry practices must be categorized separately. Tables, figures, and case examples are to be considered standalone reference materials; they do not constitute completed product testing.

  1. FDA: Computer Software Assurance for Production and Quality Management System SoftwareFinal guidance of 3 February 2026. Non-binding recommendations for production and quality management system software in the medical device sector.
  2. 21 CFR Part 820 – Quality Management System RegulationQMSR, effective since 2 February 2026: §§ 820.1, 820.7 and 820.10. The CSA-Guidance refers for software validation to the included ISO-13485:2016 subsections 4.1.6, 7.5.6 and 7.6 as well as for records on 4.2.5; § 820.35 contains additional recording requirements. The ISO-Verweiseen are documented here via the FDA-Guidance, no independent full text comparison of the ISO standard.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Jointly develop the specific evidence process

We support your team in consolidating existing results and open findings into a traceable assurance justification.

  • 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 →