# SaaS change-impact worksheet

Version 2.0 · Updated 2026-09-21 · Operations

Assess changed functions, local evidence needs and the conditions for continued use.

Adapt this template to your intended use, applicable requirements, and approved procedures.

## When to use it

Use before documenting the corresponding assessment or decision.

## Information needed before starting

- Supplier release notes and deployment date
- Current configuration, integrations and open-record states
- Relevant supplier evidence and local risk/test records

## Field instructions

- **Release:** Identify the supplier release/version and planned deployment date, including the authoritative release-information reference.
- **Changed component:** Describe what changed and which shared component, workflow, rule or export could be affected.
- **Local use:** Explain how the changed function is configured and used locally, including the decisions and records that rely on it.
- **Dependencies:** List interfaces, shared rules, roles, data states and other functions whose behavior could change indirectly.
- **Supplier evidence:** Reference the exact evidence, version, date and assessed conditions. Explain the claim it supports, how it was reviewed and what remains unproven locally.
- **Local checks:** Select checks for the uncovered local risks. Define representative conditions, expected results and the evidence to retain.
- **Operational preparation:** Identify required procedure, training, access, support and monitoring updates and who confirms readiness.
- **Deployment condition:** State what must be demonstrated or resolved before the specified use can continue; define any restriction and accountable decision owner.
- **Recovery:** Explain rollback or containment, record reconciliation and restoration checks if deployment causes an unacceptable result.
- **Monitoring:** State what will be compared or monitored, against which baseline, by whom and how often. Define discrepancy thresholds and the response.

Does the assessment include indirect effects and records already in progress?

## Blank template

System / record ID: ____________________

Prepared by / date: ____________________

Required review / approval under local procedure: ____________________

| Field | Your entry |
| --- | --- |
| Release | ____________________ |
| Changed component | ____________________ |
| Local use | ____________________ |
| Dependencies | ____________________ |
| Supplier evidence | ____________________ |
| Local checks | ____________________ |
| Operational preparation | ____________________ |
| Deployment condition | ____________________ |
| Recovery | ____________________ |
| Monitoring | ____________________ |

## Related guidance

- [Review the SaaS release example](https://csvtocsa.com/case-studies/saas-eqms-weekly-releases)

- [Plan periodic review](https://csvtocsa.com/learn/guidance/periodic-review)

- [Open the saas release assessment template](https://csvtocsa.com/templates/saas-release-assessment)

Canonical page: https://csvtocsa.com/worksheets/saas-change-impact