# Supplier Evidence Review

Version 1.0 | CSVtoCSA practitioner template | Updated 12 September 2026

## Purpose

Document which supplier evidence is accepted, what it supports, its limitations, and the local validation evidence still required.

## When to use

When supplier documents, tests, certifications, or reports are proposed as validation support.

## Instructions

- Define the specific system, service, change, population, and intended use.
- Complete each field from available records and accountable interviews; record unknowns rather than guessing.
- Link conclusions to affected GxP functions, failure scenarios, controls, evidence, and approval.
- Adapt the structure to the organization’s approved procedures and document-control process.

## Blank template

1. Supplier evidence source

   Response: 

2. Version, date, and scope

   Response: 

3. GxP function or risk supported

   Response: 

4. Review performed

   Response: 

5. Credibility and currency

   Response: 

6. Accepted use

   Response: 

7. Limitations

   Response: 

8. Local configuration or process gap

   Response: 

9. Additional evidence required

   Response: 

10. Reviewer conclusion and approval

   Response: 

## Completed fictional example

The example below is teaching material, not an executed or approved validation record.

1. Supplier evidence source

   Fictional supplier regression summary

2. Version, date, and scope

   eQMS 8.5; standard workflow engine; 2 September 2026

3. GxP function or risk supported

   Unchanged standard state-transition processing

4. Review performed

   Scope, environment, acceptance criteria, failures, and defect list reviewed

5. Credibility and currency

   Version specific and approved by supplier Quality

6. Accepted use

   Supports unchanged engine behavior

7. Limitations

   Does not cover local routing, identity mapping, open legacy records, or signed export

8. Local configuration or process gap

   Site/severity rules and Quality approval path

9. Additional evidence required

   Customer branch, unauthorized, state-transition, signature, and recovery tests

10. Reviewer conclusion and approval

   Accept with stated limitations; Quality approval required

## Use and limitations

Adapt this template to the applicable regulation, approved validation procedure, document-control process, risk method, and approval roles. CSVtoCSA does not present this template as a universally required validation record.