Gate C — Execution Gate.
Gate C approves go-live. It sits at the end of Generate, after cutover readiness completes. Past Gate C, the program enters Embed — hypercare, KPI/QBA reviews, and benefit verification.
Purpose
Gate C is the last decision before production. It confirms that UAT has actually been run, that training materials exist and have been delivered, that a rollout plan is in place, and that rollback and monitoring plans are written down — not improvised at 2 a.m. during an incident.
Entry criteria
- Gate B is approved (FD Part B signed).
- All delivery sprints closed with demo evidence and release notes.
- UAT completed with signed acceptance.
- Training materials delivered; affected population trained.
- Rollout plan signed off.
- Rollback and monitoring plan written down and reviewed.
Exit criteria
- Execution Gate approval metadata and go-live artifacts recorded.
- Go-live change approval issued (the real one, not a process checkbox).
- Hypercare plan active — on-call rotation, triage path, exit-report template ready.
Outputs
Production cutover proceeds. Program transitions to E Embed, which starts with hypercare and ends with benefit realization verification against the claim in WS04 Business Objective.
Who approves
The change authority for the target environment — typically the PMO lead with technical lead sign-off. For regulated systems, the formal change advisory board owns this gate.