Practitioner template

SaaS Release Assessment Template

Determine whether a supplier release affects approved GxP functions and what evidence or monitoring is required.

Author
CSVtoCSA editorial
Published
12 September 2026
Last reviewed
2026-09-12
Version
1.0
Content type
Template
Primary references
Apply the sources and approved procedures relevant to the system
Download Template

Blank template

  1. Release and date
  2. Authoritative change information
  3. Affected GxP functions
  4. Configuration and interface exposure
  5. Potential failure and impact
  6. Supplier evidence
  7. Customer evidence needed
  8. Decision and rationale
  9. Post-release monitoring
  10. Reassessment criteria and approval

Completed fictional example

Fictional teaching example: This is not an executed or approved validation record.

Release and date
Fictional eQMS 8.4; 15 September 2026
Authoritative change information
Dashboard color, routing engine, and export signature block
Affected GxP functions
CAPA route and exported signed record
Configuration and interface exposure
Local site/severity conditions and open legacy records
Potential failure and impact
Approval bypass or incorrect signature association
Supplier evidence
Release note, defect list, standard workflow regression summary
Customer evidence needed
Targeted routing, open-state transition, signature export, and role challenge
Decision and rationale
Approve only after mapping correction and retest; broad platform regression is not justified
Post-release monitoring
Routing exceptions, audit-trail discrepancies, and export complaints for seven days
Reassessment criteria and approval
Critical incident, workflow or identity change, or threshold breach; Quality approval required