Skip to main content
AITE M1.4-Art71 v1.0 Reviewed 2026-04-06 Open Access
M1.4 AI Technology Foundations for Transformation
AITF · Foundations

Template 1 — Transformation Charter

Template 1 — Transformation Charter — Technology Architecture & Infrastructure — Advanced depth — COMPEL Body of Knowledge.

7 min read Article 71 of 48

COMPEL Specialization — AITE-WCT: AI Workforce Transformation Expert Artifact Template 1 of 5


How to use this template

Populate a charter per transformation programme. The charter is the standing reference that anchors the programme against drift through its multi-year horizon. Delete the italicised placeholder text in each field and replace with the programme-specific content. Mark sections “not applicable” only with a one-sentence reason; do not omit them silently.

The charter is a living document. Version it on each stage-gate review (typically every 6–12 months). Keep prior versions for retrospective audit.


Transformation Charter

Charter header

FieldValue
Programme namee.g., Northstar Banking AI Workforce Transformation
Charter version1.0
Charter dateYYYY-MM-DD
Charter authorrole, not individual
Charter approval dateYYYY-MM-DD, by coalition
Next stage-gate reviewYYYY-MM-DD
Programme startYYYY-MM-DD
Programme multi-year horizone.g., 36 months with recommit at 24 months

Section 1 — Sponsor coalition

Primary sponsor

Role (e.g., CEO, COO). The individual who owns the outcome, makes final calls on major decisions, and is visible to board and workforce as the transformation’s sponsor.

Co-sponsor pair

The day-to-day leadership pair — typically CHRO and Head of AI Governance. Share accountability for integration.

Guiding coalition

Seven to ten members by role. Composition meets the criteria in Article 20: CEO/COO, CHRO, Head of AI Governance, CIO/CDO, 2–3 business-unit heads, CLO, optional external voice.

RoleResponsibility on coalitionStanding cadence

Dissenting voice

Named coalition member whose role is to test assumptions and surface risks the other members may be disposed to minimise.

Coalition cadence

Standing meeting rhythm (typical: monthly 90-minute; annual 2-day offsite).

Board relationship

Formal reporting cadence; informal update channel.


Section 2 — Programme scope

Workstreams in Year 1

Named workstreams from the eight-workstream framework of Article 1. Typical Year 1: literacy; talent pipeline; change methodology; manager enablement.

Workstreams added in Year 2

Typical Year 2: role redesign at scale; performance-system redesign; culture investment.

Workstreams added in Year 3 (if any)

Typical Year 3: sustainment infrastructure, or late-addition scope elements.

Explicit out-of-scope

Items the programme is not responsible for, with rationale. Avoids scope creep.

Population in scope

By function, geography, role family. Totals.

Saturation reasoning

Why this scope is feasible against the organisation’s current change-portfolio saturation (Article 22). Cite the portfolio view.


Section 3 — Decision rights

For each decision class, name Responsible / Accountable / Consulted / Informed.

Decision classRACI
Scope and budget of workstreams (Year 1 and multi-year)
Role-redesign decisions at role-family level
Individual role-redesign decisions affecting named employees
Selection criteria for any redundancy programme
Performance-system changes affecting all employees
Curriculum approval for the literacy programme
Works-council consultation material approval
Board reporting content
Methodology choice per workstream
Stage-gate pass/fail decisions

The A column should typically have a single role per decision class. The R can have more than one (delivery is often shared); the A is accountability and should not be split.


Section 4 — Stage gates

GateExpected dateDecision bodyEvidence requiredPossible decisions
Y1 Q2 launch gateYYYY-MMcoalitionreadiness score; initial plan confirmationcontinue / adjust / pause
Y1 year-end reviewKPI tree trajectory; retrospective findings
Y2 mid-programme review
Y3 recommit gatecontinue / rescope / wind down to standing ops

Section 5 — Success criteria

Year-3 outcome targets (Level 1 of KPI tree)

Specific, measurable outcomes the programme commits to deliver by year 3. Balanced across productivity, retention, engagement, and (optionally) capability. Typically 4–6 statements.

  1. e.g., Commercial underwriting decision turnaround reduces by 25% with quality score maintained at or above baseline.
  2. e.g., Literacy completion at 95% across in-scope population with compliance-grade evidence pack delivered.
  3. e.g., Voluntary retention of high-performer segment at or above baseline throughout the programme.
  4. e.g., Engagement score (specific instrument) at or above baseline throughout the programme.
  5. e.g., Readiness score moves from Y1 baseline to target of ≥3.5 on the five-dimension scale by Y3.

Year-1 driver targets (Level 2 of KPI tree)

Shorter-horizon targets that feed the Year-3 outcomes. Typically 6–10 statements.

Measurement commitment

What the programme commits to report, to whom, at what cadence. Links to the KPI tree and readiness-score disciplines.


Section 6 — Methodology selection

Primary methodology

ADKAR / Kotter / Bridges. Justify against the six-criterion framework of Article 18.

Supporting methodologies

Named methodologies that support the primary in specific workstreams.

Combination pattern

Pattern A / B / C from Article 18. Typical at enterprise scale: Pattern A (Kotter programme-level, ADKAR workstream-level, Bridges overlaid on role-change workstreams).

Methodology-specific expert resources

Who holds the methodology expertise, internal and external.


Section 7 — Risk register (initial)

Initial risks identified at charter time. Each risk has an owner and a mitigation approach.

RiskOwnerLikelihood × ImpactMitigation
Saturation breach during Y2
Sponsor loss
Works-council escalation
AI-system change invalidates curriculum
Key-talent attrition

Add programme-specific risks.


Section 8 — Governance and review cadence

Standing governance

Coalition cadence, steering-group cadence, programme-office cadence, board cadence.

Charter review cadence

Annual + event-triggered updates.

Change-log entry on update

How changes to the charter are recorded.


Section 9 — Communication protocol

Internal-communication cadence

All-hands, business-unit, functional.

External-communication protocol

When and what is communicated externally (customers, analysts, regulators, press).

Works-council consultation cadence

Formal consultation windows; information-sharing cadence between formal consultations.


Section 10 — Signatures

RoleName (optional)Signature or confirmationDate
Primary sponsor
CHRO
Head of AI Governance
Coalition members

Appendices

  • A. Programme scope detail by workstream.
  • B. KPI tree (Level 1, 2, 3 from Article 33).
  • C. Readiness assessment (initial) (Article 34).
  • D. Risk register (full).
  • E. Cross-reference matrix to Core Stream and other specialization content.

Quality rubric — self-assessment of template

DimensionSelf-score (of 10)
Completeness (all 10 sections present and operable)10
Clarity (role-not-individual naming; unambiguous RACI)10
Transferability (usable across different organisations)10
Fidelity to credential content (Articles 1, 18, 20, 22, 27, 33, 34)10
Worked example depth (example values provided at appropriate depth)9
Weighted total49 / 50