Templates › AI CoE RACI
AI CoE RACI
Template id: coe-raci
Responsible skill: ai-centre-of-excellence:coe-raci.
How to use this template: rename the role columns to your organisation's role titles (never personal names), add or remove rows, then fill each cell with R (responsible), A (accountable), C (consulted) or I (informed). Every row has exactly one A. Reviewers are C or hold a gate, never A for what they review. Champions are never A for approval or release. Mark roles that do not yet exist [To confirm: role to be appointed].
Summary RACI (one page for the sponsor)
A typical starting allocation for a business-owned CoE, where the CoE lead sits in the business unit that benefits. Challenge it locally; do not adopt it unchanged. Each row has exactly one A.
| Activity | Executive sponsor | CoE lead | Champions | Central AI enablement |
|---|---|---|---|---|
| Prioritisation | A | R | C | C |
| Funding | A | C | I | I |
| Delivery | I | A | R | C |
| Knowledge management | I | A | R | C |
| Governance | C | C | I | A |
| Adoption | C | A | R | C |
| [To confirm: any further summary row] |
Agreed summary allocations: [To confirm: changes made and why]. The detailed matrix below still gives each solution's business owner the A for its benefit and each knowledge owner the A for their content.
Roles
| Column | Role title in this organisation | Filled or vacant |
|---|---|---|
| SP | Executive sponsor - [To confirm: role title] | [To confirm] |
| CL | CoE or working-group lead - [To confirm] | [To confirm] |
| BO | Business owner (of the opportunity or solution) | [To confirm] |
| KO | Knowledge owner | [To confirm] |
| MK | Maker or delivery team (internal or partner) | [To confirm] |
| PL | Platform or IT lead | [To confirm] |
| IS | Information security (gate holder) | [To confirm] |
| DP | Data protection (gate holder) | [To confirm] |
| AL | Adoption lead | [To confirm] |
| CH | Champions (knowledge, process, adoption and AI champion roles) | [To confirm] |
The central AI enablement function (advisor, coach, governance and technical specialist support) usually supplies the PL, IS and DP roles, or works beside them: [To confirm: how it maps to these columns].
Opportunity lifecycle
| Activity | SP | CL | BO | KO | MK | PL | IS | DP | AL | CH |
|---|---|---|---|---|---|---|---|---|---|---|
| Identify: spot and submit an idea | I | I | A | C | R | |||||
| Assess: frame the problem and outcome | C | A | C | |||||||
| Assess: decide whether AI is suitable | A | R | C | C | ||||||
| Assess: classify the initial risk tier | A | R | C | C | C | |||||
| Prioritise: rank opportunities in the backlog | C | R | A | |||||||
| Build: design and build the solution | C | A | C | R | C | |||||
| Build: prepare knowledge sources | C | A | R | |||||||
| Deploy: test against the acceptance threshold | C | A | C | R | ||||||
| Deploy: launch and enable users | A | C | R | R | ||||||
| Measure: report adoption and benefit against baseline | I | C | A | R | ||||||
| Improve: decide scale, change or stop | C | R | A | C |
These sample allocations are a starting point to challenge, not a recommendation for your organisation: [To confirm: agreed allocations].
Governance decisions
| Activity | SP | CL | BO | KO | MK | PL | IS | DP | AL | CH |
|---|---|---|---|---|---|---|---|---|---|---|
| Maintain the acceptable-use starter and approved tools list | I | A | C | R | C | C | C | I | ||
| Register a tier 1 solution | I | A | R | |||||||
| Approve release of a tier 2 solution | I | A | R | C | C | C | C | C | ||
| Approve release of a tier 3 solution | A | R | R | C | C | C | C | C | ||
| Accept residual risk for a tier 4 solution | A | R | C | C | C | C | ||||
| Grant an exception to policy | [To confirm] |
Knowledge, platform and register
| Activity | SP | CL | BO | KO | MK | PL | IS | DP | AL | CH |
|---|---|---|---|---|---|---|---|---|---|---|
| Keep a knowledge source accurate and reviewed | C | A | ||||||||
| Maintain the solution register | A | C | R | R | ||||||
| Configure environments and data policies | C | A | C | |||||||
| Review and retire unowned or unused solutions | A | R | C | R |
Adoption, Champions and value
| Activity | SP | CL | BO | KO | MK | PL | IS | DP | AL | CH |
|---|---|---|---|---|---|---|---|---|---|---|
| Run the adoption programme | C | C | A | R | ||||||
| Provide first-line peer guidance | A | R | ||||||||
| Publish the scorecard | I | A | C | R | I | |||||
| Own and report a solution's benefit | I | C | A |
Checks before agreement
- [ ] Every row has exactly one A.
- [ ] Business owners are A for outcomes, priorities, knowledge content, team adoption and benefits.
- [ ] No reviewer is A for something it reviews.
- [ ] Champions are never A for approvals or release.
- [ ] Every role is a role title, not a person.
- [ ] Tested against two or three real cases: [To confirm: cases used].
Agreed by: [To confirm: forum and date]. Next review: [To confirm: date].
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.