Change Management
CG-07Plan, test, and validate each material change within 30 days of go-live
How Leela would run itEvent-driven · each approved material change; validation due 30 days after implementation
From the policy libraryThe requirement
Before an approved change is deployed, the change owner prepares an implementation plan covering scope, affected systems and teams, the testing approach, a rollback plan, a communications plan, and the validation approach, and the Compliance Officer reviews the plan and the testing results before production. Within 30 days after implementation the Compliance Officer validates that the change operates as intended, has no unintended effects, delivered its disclosures and communications, and left compliance controls working, and tracks any remediation to closure.
- Applies
- Tell Leela about your company to see whether this applies.
- Status
- Setup needed
Tell Leela how you handle it today, or hand it over: see what’s next.
The work
Review the implementation plan and the test results before deployment, set the validation date at go-live, complete the five validation checks by that date, and open a remediation item for anything that fails.
What Leela keepsThe evidence this obligation leaves, as the work happens
Listed from the policy libraryContents
- 01Implementation plan and test resultsPlan sections, test cases, outcomes, Compliance Officer sign-off
- 02Post-implementation validation recordFive checks with results, issues found, remediation plan and closure date
Evidence
Implementation plan and test results
Change Management §6, §7
2
of 2 records
The work and the records come from this obligation in the policy library.