CM-21 Change Management

Go-Live / Implementation Approval

Systems go live only when ready.

Domain: Change Management
Control type: Preventive
Automated / manual: Manual
Frequency: Per project
Framework reference: COBIT BAI07.05

What good looks like

Go-live requires formal approval confirming readiness (testing, training, support, fallback).

Risk if it fails

Premature/unready deployment.

How Tess tests it

2 tests — each concludes only on cited evidence.

Go-live readiness checklist & approval gate

Design

Procedure: Inspect the checklist/gate.
Expected: Defined.
Sample: 1 (design inspection)
Evidence: Go-live approval, readiness checklist.

Readiness criteria met & approved

Operating

Procedure: Sample a go-live.
Expected: Approved on meeting criteria.
Sample: Judgmental, by population (e.g. 10–25)
Evidence: Go-live approval, readiness checklist.

Evidence Tess looks for

Go-live approval, readiness checklist.

More in Change Management

CM-01 Change Management Policy CM-02 Change Request & Documentation CM-03 Change Authorisation CM-04 Testing / UAT Before Production

Want Tess to test CM-21 against your evidence?