Why a written charter?
Section titled “Why a written charter?”A charter is not a bureaucratic document — it is the formal mandate without which the CCoE has no authority to enforce standards, make decisions or demand resources.
Without a charter: the CCoE recommends, but teams do not follow, because no obligation exists. The CCoE escalates, but the escalation path is unclear. The CCoE blocks deployments, but business units go around it directly to the CIO.
With a charter: the rules of engagement are clear before the conflict arises.
CCoE Charter Template
Section titled “CCoE Charter Template”CLOUD CENTRE OF EXCELLENCE — CHARTER
Section titled “CLOUD CENTRE OF EXCELLENCE — CHARTER”Version: 1.0 Date: [Date] Approved by: [Name], CIO / Cloud Strategy Board Effective from: [Date]
1. Mission
Section titled “1. Mission”The Cloud Centre of Excellence enables [Company] to use cloud technology securely, cost-efficiently and with full sovereignty. It is the central competence and governance authority for all cloud activities and bears responsibility for standards, enablement and transformation progress.
2. Scope
Section titled “2. Scope”This charter applies to:
- All cloud resources on [STACKIT / other platforms]
- All teams and projects using or planning to use cloud infrastructure
- All cloud infrastructure expenditure regardless of cost centre or business unit
3. Mandate and Authorities
Section titled “3. Mandate and Authorities”The CCoE is authorised to:
Set and enforce standards:
- Define cloud architecture standards, naming conventions and tagging standards as binding requirements
- Implement guardrail policies as code and cover all environments
- Conduct compliance reviews for new workloads before production deployment
Decision mandate:
- Technical architecture decisions with platform-wide impact (< [TEUR X] budget impact)
- Workload prioritisation for migration waves
- Onboarding approval for new teams to the cloud platform
- Exceptions to guardrail standards (documentation required)
Escalation right:
- The CCoE may block deployments that violate standards
- The CCoE may escalate to the CIO when teams do not comply with mandates
4. Decision Matrix
Section titled “4. Decision Matrix”| Decision type | CCoE decides | CCoE recommends | Cloud Strategy Board |
|---|---|---|---|
| Technical architecture standards | ✓ | ||
| Workload migration prioritisation | ✓ | ||
| Guardrail exceptions (< 30 days) | ✓ | ||
| Guardrail exceptions (> 30 days) | ✓ | Decides | |
| Provider decisions | ✓ | Decides | |
| Budget > [TEUR Y] | ✓ | Decides | |
| CCoE team personnel decisions | ✓ | Decides |
5. Non-mandate: what the CCoE does not do
Section titled “5. Non-mandate: what the CCoE does not do”The CCoE is not a gatekeeper for daily deployments. The following lies within workload team responsibility:
- Deployment decisions within CCoE standards
- Workload-specific architecture decisions (not platform-wide)
- Operation of own workloads in accordance with CCoE standards
6. Reporting line and governance
Section titled “6. Reporting line and governance”- Reporting line: CCoE Lead reports directly to CIO
- Quarterly report: Quarterly executive summary to Cloud Strategy Board (KPIs, risks, recommendations)
- Monthly status meeting: CCoE Lead + CIO, 30 minutes
- Annual charter review: Charter reviewed annually and adjusted as necessary
7. Resource commitment
Section titled “7. Resource commitment”The organisation commits for the CCoE:
- [N] FTE internal resources (by name or role)
- [TEUR X] annual budget for external support, tools, training
- C-level sponsor availability for escalations
8. Success measurement
Section titled “8. Success measurement”The CCoE is measured quarterly on the following KPIs:
- Guardrail compliance rate (target: >99 %)
- Cloud costs vs. budget (target: ±10 %)
- Migration throughput (target: [N] workloads/quarter)
- Team training completion rate (target: >80 % within 12 months)
- Incident mean time to recovery (target: <30 minutes)
9. Duration and revision
Section titled “9. Duration and revision”This charter is open-ended. It is reviewed annually by the Cloud Strategy Board. Material changes to the mandate require CIO approval.
Signatures:
| Role | Name | Date |
|---|---|---|
| CIO | ||
| CTO | ||
| CFO | ||
| CISO | ||
| CCoE Lead |
Charter introduction: communicating to the organisation
Section titled “Charter introduction: communicating to the organisation”The charter signing is a formal event — and should be communicated as such:
- All-hands communication by CIO: what the CCoE is, what it means for teams, who works in the CCoE
- Department head briefing: specifically on the decision mandate — what the CCoE decides, what teams can decide independently
- Intranet publication: charter accessible to everyone