Practical guides · Practical guide

CSV validation reports: bringing evidence together for release

All test results are on file, yet the evidence for a decision is hard to find. A validation report connects those results to a clear conclusion about which use has been demonstrated and under which conditions.

Table of contents

At a glance

What belongs in a CSV validation report?

State the intended use and system version tested, summarise results against the agreed criteria, and assess deviations, changes and evidence gaps. Link requirements to relevant evidence and define operating conditions and limits. The final recommendation and decision should follow from the information in the report.

The report addresses a decision, not a page percentage.

A validation plan describes the intended approach. Test protocols document specific assessments. The validation report consolidates relevant results for evaluation, without reproducing the entire project documentation, but rather clearly presenting the key evidence chain.

For GMP-relevant computerized systems, Annex 11 provides the specific framework. Annex 15, in the context of qualification, addresses among other things result evaluation and documented conclusions. The proposed reporting structure outlined here is a standalone work aid and not a universally mandated official template.

A brief report may be sufficient when clear references are provided. For complex systems, additional explanation may be required. The appropriate length emerges from scope, findings, and decision. A specific page count or a fully green cover page does not establish professional competence.

Sources: [1] [2]

Write Scope and System State so concretely that borders are clear

State the application, version, relevant configuration, location, roles, and interfaces. Describe the intended use in clear, process-based steps. "ERP validated" is overly broad when only a specific quality process with selected data transfers has been demonstrated.

Maintain clear definitions of inclusions and exclusions. An excluded scope must not simultaneously serve as an implicit assumption of approved use. When an external data source is required, its relevant suitability must be established within the overall context, even if not every function of the source is tested within the specific project.

Compare the completed scope with the plan. Changes shall be explained and evaluated for their impact. If a new version was introduced during testing, it must be clearly demonstrable which records correspond to which version and why they remain appropriate for the conclusions.

Sources: [1]

Summarize results against criteria

State the actual required test assertions and their supporting evidence. A simple count of passed test cases can be misleading: many comfort tests do not adequately address an undefined critical data rule. The summary is therefore based on requirements and risks, not merely on a percentage figure.

A traceability overview can link requirements, risks, test results, and findings. It does not need to reference each document repeatedly. What is important is that relevant statements are readily retrievable and that no critical point is omitted from the evaluation without justification.

Supplier documentation received is accompanied by their qualification decision. Additional customer tests and limits remain visible. A foreign report must not be presented as if the own configuration has been fully validated therein.

Own summary of results based on audit statement
RequirementSubstantiating EvidenceAssessment in this example
R-01 · correct batch assignment T-01 Normal case, T-02 incorrect assignment Meets to the extent verified
R-02 · Decision boundary T-03 Limit, T-04 Overstepping Complies, after reviewed correction, K-01
R-03 · Repeat of the handover T-05 Interruption and restart Meets; target object clearly defined
R-04 · Roll Limitation T-06 approved, T-07 rejected action Meets for documented roles
R-05 · required history T-08 Change and Review Compliant; Operating procedure referenced

Sources: [1] [2]

Example of a batch-specific result transfer

A system is considered that transfers validated laboratory results to a quality-related ERP process. Within the scope are assignment, unit, threshold decision, roles, required history, and retry logic following a transmission failure. Professional batch certification is explicitly not part of this technical usage decision.

The report identifies the approved software and configuration state, as well as the validated interface agreement. The five critical requirements are supported by normal, boundary, and error cases. A rounding discrepancy resulted in an incorrect boundary decision (K-01); this was corrected, and the affected cases were re-performed and re-evaluated. The initially ambiguous retry behavior (K-02) was re-examined with a defined target status.

A remaining editorial point concerns the heading of a non-decision-critical support page. Its lack of impact on the assessed requirements is explained. The recommendation specifically references the substantiated application and the required operating conditions. The example illustrates the reporting logic; it does not constitute a release recommendation for your system.

Sources: [1] [2]

Evaluate findings, corrections, and open items in a traceable manner

A finding is summarized with its impact, action taken, and outcome of the investigation. Refer to the full investigation instead of summarizing its content in a way that is unclear. A closed ticket alone does not indicate the effect of the corrective action nor provide evidence of its implementation.

Open points require professional assessment. Not all points carry equal relevance. The absence of a critical justification may preclude the intended use. A well-justified non-critical editorial residual point may be handled differently. This differentiation must arise from content and risk considerations, not from the desired timeline.

Annex 15 addresses conditional transitions to the next qualification level under specific conditions. This does not constitute a blanket authorization for productive go-live despite open findings. The report should not treat such a provision as a general exception waiver.

Own investigation summary with justified impact
FindingEvaluation and HandlingConclusion
K-01 · incorrect boundary decision Root cause assessed, logic corrected, affected cases re-evaluated Final approval statement is documented
K-02 · unclear retry Target status and repetition verified No unexplained dual event in the documented procedure
O-01 · Assistance title No impact on critical functions has been demonstrably justified. Outstanding task and its owner
Example of a blocker Critical history still not comprehensible No unqualified positive recommendation for the intended use.

Sources: [2] [1]

Operational readiness extends beyond passing a test package.

Verify whether the team can operate the documented application under intended conditions. This includes roles, training, defect resolution, change control, recovery, and required review. The report does not need to print all procedures, but should clearly demonstrate the relevant availability and suitability. Annex 11 identifies, among other requirements, qualification and responsibilities (No. 2), controlled changes (No. 10), and appropriate provisions for operational continuity (No. 16).

State dependencies. If a manual check is required, it must be clearly defined who performs it, when, and how its execution remains traceable. The statement "is organizationally ensured" lacks credible substantiation without a specific procedure.

Later operational responsibility will be transferred. A project leader alone is not automatically responsible for all the following changes. The decision should indicate which entities will be responsible for the application, technical components, and quality evaluation.

Sources: [1]

A specific recommendation instead of a general claim of compliance

The conclusion addresses three questions: Which application has been demonstrated? What are the applicable limitations or prerequisites? What decision is recommended based on this? Avoid statements such as "the entire system complies with all regulations" when the supporting evidence pertains to a limited scope.

In the example, the recommendation could pertain to the transfer of results within the designated site and role model under the referenced operating procedures. Functions excluded remain excluded. A subsequent process variant requires an impact assessment rather than relying on the previous overall statement.

The responsible roles determine and document the decision in accordance with the quality system. Reporting, technical assessment, and formal approval may constitute separate responsibilities. A universal list of required signatures would be inappropriate without an organizational and process context.

Sources: [1] [2]

Practical Report Template for Internal Use

Use the following structure as a starting point and adapt it accordingly. First, complete the Scope, key findings, and conclusions. Only then formulate the final recommendation, ensuring it is derived from the evidence presented.

Prior to release, verify the references, versions, and accessibility of the supporting documents. A properly prepared report remains unusable if the referenced test files are not retrievable. The evidence should also be clearly understandable to an auditor who has not participated in the project.

Upon release, the report remains the documented final status. Future amendments will be managed through controlled change processes. A new report is not required for every minor update; however, the existing statement must be maintainable and traceable through appropriate change and operational documentation.

Own structure with fillable guiding questions
SectionIntended contentControl question
1 · Purpose and Scope Process, Roles, In/Out Exclusions Is the statement specifically and clearly defined?
2 · Verified Status Version, Configuration, Interfaces Does all the evidence apply to this version?
3 · Results Requirements, Criteria, Key Evidence Is each critical statement supported by evidence?
4 · Test Results and Modifications Effect, Correction, Retest, Residual Points Is any technical issue still unresolved?
5 · Operation Procedure, training, responsibilities Can the team apply the documented usage?
6 · Recommendation and Decision Justified Scope, Boundaries, Authorization Does the decision follow from the results?

Sources: [1] [2]

Project experience and collaboration

Use the results to document the decision on operational use

We start with the questions your owners need answered before release. For each, we trace the requirement, test and result, including open deviations. A few missing links may need targeted additions to an existing report. If the conclusion cannot be reconstructed from the records, we rebuild the assessment together. We identify operating conditions, limitations and remaining actions explicitly so that an overall status does not obscure them.

Frequently asked questions about The CSV validation report

How long must a CSV validation report be?

There is no universal page limit. The report must clearly link scope, relevant findings, results, and conclusions. Precise references can avoid redundancy. Complex boundaries require greater explanation than a simple, well-supported scope. Assessability determines validity, not length.

Have all the tests been passed?

No, it does not demonstrate whether all required requirements have been appropriately assessed. A critical point may be missing from the test suite. Therefore, link results to requirements, risks, and scope. Consider inherited documentation and relevant operating conditions.

Sources: [1]

Can a report include open items?

Open points must be transparent and professionally assessed. Their significance for the intended use is critical. An unclarified critical justification must not be obfuscated by a general residual point note. A conditional next qualification level does not automatically constitute a productive go-live.

Sources: [2]

Is the report itself equivalent to user authorization?

This depends on the controlled procedure. The report may contain the decision or prepare for a separate release. In either case, responsible roles, scope of review, and rationale must be clearly demonstrable. A document title alone does not establish the decision scope.

Sources: [1] [2]

Who must sign off on the validation report?

The responsible roles are defined within the quality system and the project. Technical responsibility, system responsibility, and appropriate quality oversight must be considered. A company-wide, identical list of signatures cannot be reliably asserted without contextual justification.

Sources: [1] [2]

Must the report be rewritten after each change?

Not at all. Evaluate the change and document necessary tests and decisions in the regulated procedure. In the case of substantial changes, a new summary evaluation may be necessary. The verification chain must indicate which previous statement is still valid and what has been supplemented.

Sources: [1]

Sources and review date

Status: October 14, 2026. Regulatory classification is based on the cited original sources. Examples and test matrices are internal support tools; they are adapted for actual usage purposes.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. European Commission: EU GMP Annex 15, Qualification and Validation (2015)Qualification and validation, supplemented by the specific framework for computerized systems.
  3. EMA / ICH: Q10 Pharmaceutical Quality System, Step 5 (2008)Section 3.2.2: Root Cause Analysis, CAPA, and Effectiveness Evaluation. Specific action plans and exercises provided in the contribution are standalone methodological aids.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →