Templates › AI Centre of Excellence charter
AI Centre of Excellence charter
Template id: coe-charter
Responsible skill: ai-centre-of-excellence:coe-charter. The cadence section is completed with ai-centre-of-excellence:coe-cadence, and the structure and launch roadmap sections with ai-centre-of-excellence:coe-operating-model.
How to use this template: complete every section in your own words. Replace each [To confirm: ...] marker only with a fact your organisation has agreed. Use roles, never personal names. For a Starter organisation, complete the sections marked "Starter" as the terms of reference for an AI working group and leave the rest out.
1. Document control
| Field | Value |
|---|---|
| Organisation | [To confirm: organisation name or alias] |
| Form | [To confirm: AI working group (Starter) / business-owned CoE (Scale) / hub and spoke (Enterprise)] |
| Owning business unit (the unit that benefits) | [To confirm: business unit] |
| Executive sponsor (role) | [To confirm: sponsor role] |
| CoE or working-group lead (role) | [To confirm: lead role] |
| Version and date | [To confirm: version, date] |
| Status | Draft / Agreed by sponsor on [To confirm: date] |
| Next review | [To confirm: review date] |
2. Purpose (Starter)
One sentence a department head would recognise.
[To confirm: purpose statement, for example "Help every department use AI safely to improve outcomes it already owns."]
3. Outcomes the CoE serves (Starter)
| Outcome | Business owner (role) | Baseline | Target and date |
|---|---|---|---|
| [To confirm: outcome 1] | [To confirm: role] | [To confirm: baseline or "to be captured by" date] | [To confirm: target] |
| [To confirm: outcome 2] | [To confirm: role] | [To confirm] | [To confirm] |
4. Who owns what (Starter)
| Party | Owns or leads | What that means here |
|---|---|---|
| The business | Priorities, knowledge, outcomes, adoption, return on investment | [To confirm] |
| AI and IT enablement | Governance, architecture, security, technical delivery, support | [To confirm] |
| Executive sponsor | Funding, decisions, resource allocation, adoption support | [To confirm] |
5. Scope across the six pillars
Govern once, repeat everywhere: a control or pattern agreed in one pillar for one team is reused by the next.
| Pillar | Status now | What the CoE does in this pillar | Deferred until |
|---|---|---|---|
| Opportunity management | Active / Deferred | [To confirm] | [To confirm] |
| Knowledge management | Active / Deferred | [To confirm] | [To confirm] |
| Agent development | Active / Deferred | [To confirm] | [To confirm] |
| Automation | Active / Deferred | [To confirm] | [To confirm] |
| Adoption and change | Active / Deferred | [To confirm] | [To confirm] |
| Governance | Active / Deferred | [To confirm] | [To confirm] |
6. Principles and what they mean here (Starter)
| Principle | Consequence in this organisation |
|---|---|
| Business-owned | [To confirm: for example, every opportunity has a named business owner before delivery; benefits are reported by the business] |
| AI-enabled | [To confirm] |
| Outcome-focused | [To confirm] |
| Govern once | [To confirm] |
| Repeat everywhere | [To confirm] |
7. Sponsorship (Starter)
The sponsor is an active decision maker, not a recipient of reports. Tick what the sponsor has agreed to do.
| Commitment | Agreed |
|---|---|
| Attend steering (or send a named delegate with authority to decide) | [To confirm] |
| Make priority decisions between competing opportunities | [To confirm] |
| Remove blockers the CoE cannot clear itself | [To confirm] |
| Secure resources (people, time, funding) | [To confirm] |
| Drive adoption visibly in the business | [To confirm] |
| Resolve conflicts between teams | [To confirm] |
| Accept residual risk at tier 4 | [To confirm] |
8. Decision rights
| Decision | CoE decides | CoE recommends, other body decides | Never the CoE's decision |
|---|---|---|---|
| Approved tools list | |||
| Intake criteria and routing | |||
| Risk tier classification | |||
| Release of tier 1 and 2 solutions | |||
| Release of tier 3 and 4 solutions | |||
| Investment and funding | |||
| Priorities within a department |
Mark each row with the deciding role: [To confirm].
9. Interfaces with existing forums
| Existing forum or function (role) | What passes between it and the CoE |
|---|---|
| [To confirm: for example, information security function] | [To confirm] |
| [To confirm: for example, data protection officer] | [To confirm] |
| [To confirm: for example, architecture board or IT leadership] | [To confirm] |
10. What the CoE is and is not (Starter)
The CoE is:
- a business transformation capability, owned by the business unit that benefits;
- a structured delivery function with one backlog;
- a governance framework applied in proportion to risk;
- the home of opportunity management and knowledge management;
- the place where value and return are measured against baselines.
The CoE is not:
- an IT project: the business owns priorities, knowledge, adoption and benefits;
- a monthly reporting group: forums exist to take decisions;
- a technology experiment: work starts from a business outcome;
- a queue of requests for the central AI team: ideas arrive with an owner and a framed problem; the CoE provides method, assurance and patterns.
11. Structure and membership (Starter)
Sizes are typical starting points; record real time, not aspirations.
| Role | From (function) | Time commitment | Responsibilities |
|---|---|---|---|
| Executive sponsor | [To confirm: business executive role] | [To confirm] | Funding, decisions, resources, adoption support |
| CoE lead | [To confirm: role in the owning business unit] | [To confirm: days per month] | Backlog, cadence, scorecard |
| Core team member (often three to five in total) | [To confirm] | [To confirm] | [To confirm] |
| Knowledge champion | [To confirm] | [To confirm] | Keeps documentation owned, current and of good quality |
| Process champion | [To confirm] | [To confirm] | Spots opportunities and measures benefits |
| Adoption champion | [To confirm] | [To confirm] | Promotes use and shares success stories |
| AI champion | [To confirm] | [To confirm] | Supports agent testing and experimentation |
| Central AI enablement (support, not owner) | [To confirm: function] | [To confirm] | Advisor, coach, governance and technical specialist support |
12. Cadence and terms of reference
Completed with ai-centre-of-excellence:coe-cadence. One column per forum. Lengths and frequencies shown are typical starting points; a Starter working group may merge the first two columns.
| Field | Working group | Steering committee | Strategy review | Community |
|---|---|---|---|---|
| Purpose | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Decisions taken | [To confirm: triage, routing, tier, delegated release] | [To confirm: priorities, funding, risk acceptance, escalations] | [To confirm: roadmap, scale-or-stop] | None (sharing forum) |
| Chair (role) | [To confirm] | [To confirm: executive sponsor] | [To confirm] | [To confirm] |
| Members (roles) | [To confirm] | [To confirm: sponsor mandatory] | [To confirm] | Open |
| Quorum | [To confirm] | [To confirm: sponsor or named delegate who can decide] | [To confirm] | Not applicable |
| Frequency and length | [To confirm: typically weekly, 30 minutes] | [To confirm: typically monthly, 60 minutes] | [To confirm: typically quarterly, 90 minutes] | [To confirm] |
| Inputs and deadline | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
| Outputs and where published | [To confirm] | [To confirm] | [To confirm] | [To confirm] |
Standing agendas:
- Working group: new opportunities; delivery updates by exception; risks; knowledge gaps.
- Steering committee: return achieved against baseline; priority decisions; funding requests; new opportunities above delegated limits; escalations.
- Strategy review: roadmap; adoption; value delivered; future priorities.
Decision log
| Ref | Date | Forum | Decision | Options considered | Rationale | Deciding role | Conditions | Review date |
|---|---|---|---|---|---|---|---|---|
| [To confirm] |
13. Collaboration space
Completed with ai-centre-of-excellence:coe-operating-model. Use tools the organisation already runs.
| Area | Used for | Tool or list in this area | Owner (role) |
|---|---|---|---|
| General | Announcements and updates | Gallery of live agents and automations | [To confirm] |
| Opportunities | Ideas and prioritisation | Backlog board | [To confirm] |
| Knowledge management | Documentation and ownership | Knowledge asset register | [To confirm] |
| Agent development | Agent design and testing | [To confirm] | [To confirm] |
| Automation | Workflow and automation discussion | [To confirm] | [To confirm] |
| Governance | Policies and compliance | [To confirm] | [To confirm] |
| Success stories | Sharing value and outcomes | [To confirm] | [To confirm] |
14. Launch roadmap
Completed with ai-centre-of-excellence:coe-operating-model. Timings are typical; move on when exit items are met.
| Phase | Typical timing | Exit items | Planned dates |
|---|---|---|---|
| Establish | Month 1 | Sponsor confirmed; lead and core team named; collaboration space set up | [To confirm] |
| Foundation | Month 2 | Backlog live; knowledge asset register started; first opportunities framed | [To confirm] |
| Deliver | Months 3-4 | Quick wins live; first agents or automations deployed; value measured against baseline | [To confirm] |
| Scale | Month 5 onwards | Reusable assets; wider rollout; adoption growing | [To confirm] |
15. Launch commitments (Starter)
| Commitment | What it means here | Agreed by (role) |
|---|---|---|
| Active sponsorship | [To confirm] | [To confirm] |
| Champion participation | [To confirm: time agreed with managers] | [To confirm] |
| Knowledge ownership | [To confirm] | [To confirm] |
| Opportunity prioritisation through one backlog | [To confirm] | [To confirm] |
| Return measured against baselines | [To confirm] | [To confirm] |
| Continuous improvement | [To confirm] | [To confirm] |
Commitment principle: the goal is not to build AI; it is to build business capability supported by AI and automation.
16. Changing this charter
[To confirm: who may propose changes, which forum agrees them, and how often the charter is reviewed.]
17. Sign-off
| Role | Decision | Date |
|---|---|---|
| [To confirm: executive sponsor role] | Agreed / Agreed with conditions | [To confirm] |
Credit: Template from CopilotForge by Simon Foote (https://github.com/SimonFoote-greensparx/CopilotForge), licensed under CC BY 4.0. Keep this credit when you share or adapt the template; in your own completed document you may keep it as a footer or remove it.