TemplateCoE Charter
Charter for your internal AI Center of Excellence, covering mandate, people, governance board, builder community, intake and the handover from the Clone team.
#What this is for
The goal of the engagement is that your organization runs its agentic program without us. The Center of Excellence (CoE) is how that happens: an internal AI governance board plus a builder community that owns intake, standards, skills, governance and enablement. This charter gives the CoE a clear mandate, named people, real decision rights and a transition plan, so self-sufficiency is planned rather than assumed.
#When to use it
Draft it in Month 8 and approve it before Month 9. The CoE then shadows the Clone team in Months 9–10, co-leads in Month 11 and leads in Month 12. Review the charter annually.
#Who's involved
- Executive sponsor charters the CoE and signs.
- CoE lead owns it day to day.
- Governance board: InfoSec lead, IT lead, a business owner rotation, legal or compliance, HR.
- Builder community: org admins, Champions and power users who build in SkillForge.
- Solutions Partner and Change & Enablement Lead coach the transition.
#How to fill it in
- Write the mission in two sentences (section 1).
- Agree scope: what the CoE owns, and what it does not (section 2).
- Name the people and protected time (section 3).
- Set decision rights and forums (sections 4–5). Reuse the Agentic Operating Model RACI.
- Define the intake process (section 6).
- Set measures (section 7) and the transition plan (section 8).
#The template
#1. Mission
Example: The Northgate AI Center of Excellence helps every team put AI teammates to work safely. We own the standards, the intake and the governance so departments can move fast without creating risk.
#2. Scope
| The CoE owns | The CoE does not own |
|---|
| Intake and prioritization of new Clone and AI requests | Day-to-day accountability for a Clone's work (business owner) |
| Standards: design, naming, knowledge, prompts, testing | Final security approval (InfoSec lead) |
| Skill change control and the builder community | Budget decisions outside the AI program |
| Autonomy promotion process (runs it; does not sign) | HR decisions on roles |
| Enablement: training, Champions, how-to library | |
| Monitoring rhythm and optimization reviews | |
| Governance of adjacent AI tools under the AI Use Policy | |
#3. People
| Role | Name | Department | Time commitment | Responsibilities |
|---|
| CoE lead | | | 50–100% | Runs the CoE; chairs intake; owns the operating model |
| Governance board: InfoSec | | | 2 hrs/month | Security approvals; incident review |
| Governance board: IT | | | 2 hrs/month | Systems, connections, change control |
| Governance board: business owner (rotating) | | | 2 hrs/month | Business priority and value |
| Governance board: legal / compliance | | | 1 hr/month | Policy and regulatory input (not legal advice from Clone) |
| Lead builder | | | 40% | SkillForge standards; code review; test packs |
| Builders (certified) | | | 10–20% | Build and maintain skills |
| Champions network | | | Per charter | Adoption in departments |
#4. Decision rights
| Decision | Decided by | Input from | Forum |
|---|
| Approve a new Clone or skill request | CoE lead | Governance board | Intake review |
| Approve a new connection | InfoSec lead | IT lead, CoE | InfoSec sync |
| Autonomy promotion | InfoSec lead AND business owner | CoE (prepares evidence) | Promotion review |
| Skill version to production | Lead builder | Business owner | Change review |
| Standards and policy updates | Governance board | Champions | Monthly board |
| Pause a Clone in an emergency | InfoSec lead or business owner | – | Any time |
#5. Forums and cadence
| Forum | Cadence | Attendees | Output |
|---|
| Intake review | Weekly | CoE lead, lead builder | Scored and prioritized requests |
| Governance board | Monthly | Board | Decisions, policy changes, risk review |
| Builder community | Bi-weekly | Builders | Shared patterns, code review, demos |
| Champions council | Bi-weekly | Champions, CoE lead | Adoption issues, wins |
| Quarterly business review | Quarterly | Sponsor, steering, CoE | Roadmap, promotions, results |
#6. Intake process
- Request submitted (problem, department, volume, systems, data)
- Scored with the opportunity rubric (value, feasibility, risk, data readiness)
- Route: Marketplace template / configuration / custom skill / non-Clone tool / decline
- Design spec and InfoSec review for anything touching new data or connections
- Build, test, pilot, go-live using the department rollout cycle
| Request | Department | Score | Route | Decision | Target date |
|---|
| Vendor onboarding intake | Procurement | 3.9 | Marketplace template + 1 custom skill | Approved | Month 11 |
#7. Measures
| Measure | Target |
|---|
| Requests triaged within 5 business days | 90% |
| Skills built by client builders (vs. Clone team) by Month 12 | Majority of new skills |
| Workflows at Execute with approval or higher | |
| Governance incidents above agreed severity | 0 |
| Champion coverage in live departments | 100% |
| Clones reviewed for Power Rating and usage each quarter | 100% |
#8. Transition plan
| Capability | Months 9–10 (shadow) | Month 11 (co-lead) | Month 12 (lead) | Ready? |
|---|
| Intake and prioritization | Clone team leads; CoE attends | CoE leads; Clone team reviews | CoE alone | |
| Skill building (SkillForge) | Builders pair with Skill Engineers | Builders lead; review by Clone team | Builders alone | |
| Promotion evidence packs | Observe | Assemble | Own | |
| Audit log reviews | Observe | Co-run | Own | |
| Training and Champions council | Co-run | Lead | Own | |
| Optimization reviews | Observe | Co-run | Own | |
#Good looks like
- The CoE lead has real time, ideally a dedicated role, not a side project.
- InfoSec sits on the board and keeps its approvals. The CoE runs the process; it does not replace the signatures.
- Intake is visible and scored. Requests do not disappear into a queue.
- Builders ship real skills before Month 12. Certification without production work is not readiness.
- The transition plan has a "ready?" check per capability, agreed by both sides.
- Common mistake: chartering a committee that only meets. The CoE should do work: intake, builds, reviews.
#How Clone helps
The Project Clone drafts the charter from the Agentic Operating Model and tracks the transition plan in the portal, capability by capability. The Enablement Clone runs builder and Champion training and maintains the how-to library the CoE inherits. The GRC Clone hands over the risk register, evidence routines and audit log review checklist. The Solutions Architect Clone trains the CoE on the opportunity rubric for intake.
#Sign-off
| Role | Name | Date | Decision |
|---|
| Executive sponsor | | | CoE chartered |
| CoE lead | | | Accepted |
| InfoSec lead | | | Approved |
| Solutions Partner | | | Transition plan agreed |