Change definition
- State scope, business reason and implementation window
- Identify dependencies and impacted services
- Classify risk and required approvals
FinOps Academy · governance guide
Change Governance
Control production change through scope, impact, testing, approval, communication and rollback readiness.
Enterprise control patternEvidence-led review
Execution controls
- Document implementation and validation steps
- Define stop conditions and rollback plan
- Assign technical, business and communication roles
Closure
- Record actual result and deviations
- Confirm monitoring after implementation
- Capture lessons and follow-up actions
Completion evidence
Produce a reviewed artefact for FinOps Academy: named owner, approval date, linked evidence, unresolved risks and the next review trigger.