Lifecycle playbooks
Apply the validation lifecycle to SaaS, AI-enabled applications, and spreadsheets without copying the same document set into every project.
Choose the system type
Each playbook identifies the records normally expected in a CSV package and explains how CSA changes the depth and method of testing.
A practical route from intended use and supplier evidence to release impact, local testing, and maintenance of the validated state for software you cannot freeze.
A controlled path from context of use and human authority to evaluation evidence, release boundaries, monitoring, and stop conditions.
A proportionate method for deciding when a spreadsheet matters and how to control formulas, data, use, change, and retirement.
This crosswalk uses the document names commonly found in validation SOPs. CSA changes how work is scaled and how tests are selected; it does not automatically eliminate familiar CSV deliverables.