Product

Product overview Agents Automations Apps Code (Beta) Integrations Governed Runtime Security

Where Renly runs

Windows app Android app Inside other AI apps

Solutions

Finance Sales Operations People and HR Marketing Enterprise

Resources

Pricing Docs Academy Blog Compare Support

AI governance and capability

AI governance framework AI governance assessment AI capability maturity AI maturity assessment
Book a demo Sign in

AI Capability Maturity Assessment · Part IV. From findings to roadmap

Findings, strategy and governance reports

37 minute read · Version 1.0.0

In this chapter

The three documents an assessment produces, the Findings Report, the AI Strategy and Roadmap, and the Governance and Operating Model recommendations, with each blueprint’s audience, outline, content rules, and every section’s data sources, writing rules and a worked example.

  1. Three reports
  2. AI Capability Maturity Assessment: Findings Report
  3. AI Strategy and Roadmap
  4. AI Governance and Operating Model: Recommendations

Three reports

An assessment produces three documents for three audiences. Each follows a blueprint: an outline, content rules and, for every section, its purpose, the data it draws on, the rules that write it and a worked example. The assessment generates all three in Word from your results, following these blueprints.

ReportForPurpose
AI Capability Maturity Assessment: Findings ReportExecutive committee and board (sections 1 and 6 to 7); Chief AI Officer, technology, risk and business leaders (all sections).Set out, with evidence, where the organisation stands on AI capability, what is exposed, and how far it is from the target it has chosen.
AI Strategy and RoadmapBoard and executive committee (endorsement); Chief AI Officer and initiative owners (delivery); all staff (summary of vision and principles).Set the direction for AI and the sequenced, owned plan that takes the organisation from its assessed baseline to its target.
AI Governance and Operating Model: RecommendationsExecutive committee (endorsement); Chief AI Officer, committee members, owners and specialist functions (operation).Recommend the roles, forums, decision rights, lifecycle and assurance lines that will run AI governance at the target level, sized to the organisation.

AI Capability Maturity Assessment: Findings Report

Set out, with evidence, where the organisation stands on AI capability, what is exposed, and how far it is from the target it has chosen.

Audience
Executive committee and board (sections 1 and 6 to 7); Chief AI Officer, technology, risk and business leaders (all sections).

Outline

  1. Executive summary
  2. Method and scope
  3. Maturity profile
  4. Findings by domain
  5. Cross-cutting themes
  6. Risk exposure
  7. Target state and gap analysis
  8. Appendices: criterion scores and evidence, survey results, AI estate, responsible AI overlay, governance crosswalk

Content rules

  • Lead with the answer: the overall band, the foundation flag, the three findings that matter most and the obligations due.
  • Each domain finding has four parts in this order: strengths, gaps, evidence state, risk.
  • Name the pass test that was not met for every gap; this is what makes the finding actionable and defensible.
  • Keep recommendations short in this report and point to the AI Strategy and Roadmap for the plan.

Sections

Executive summary

Give leaders the result, why it matters and what to decide, on one page.

Draws on
overall; domains; overall.foundationFlag; obligations; survey.flags; biggestGaps; profile.aiInUse; targets

How it is written

  • Paragraph 1: the overall band phrase for the overall score, plus the approaching suffix where it applies, then the shape sentence: ‘Capability is {{overall.shape}}: domain scores range from {{min}} to {{max}}.’
  • If foundationFlag is true, paragraph 2 must open with: ‘The foundations are not yet in place.’ and name the foundation criteria below 2.0 in plain words.
  • Paragraph 3: the strongest two and weakest two domains with scores.
  • Paragraph 4: obligations that are overdue or due within 12 months, each with its date and the criterion it depends on. Omit if none.
  • Paragraph 5: the AI estate in one sentence (uses found, how many were on the register), then the most material survey flag.
  • Close with a ‘Decisions sought’ list of three to five items drawn from the first horizon of the roadmap and the target-setting decisions.
  • Length: 350 to 500 words.

Worked example

Paragraphs
  • Wattlegrove Group is at an early stage of AI capability (1.7, Initial). AI is being used, but the organisation cannot yet see, own or steer that use. It is approaching Repeatable. Capability is balanced: domain scores range from 1.4 to 2.1, so no single area is holding the rest back; the whole organisation needs to move together.
  • The foundations are not yet in place. There is no AI risk appetite, the list of AI in use is incomplete, impact assessments are not done, and AI incidents are not recognised or recorded. Every other improvement depends on these four.
  • The strongest domains are Platform, architecture and security (2.1), built on an assessed cloud landing zone, and People, capability and culture (2.0), where the Copilot pilot has a change plan and champions. The weakest are Risk, assurance and transparency (1.4) and Use-case delivery and value (1.4): nothing is tiered or gated, and no pilot has a decision date.
  • Three obligations need action now. The EU AI Act’s AI literacy duty has applied since 2 February 2025 and its transparency duty for AI that talks to people since 2 August 2026; the EU website’s chat assistant does not tell customers they are talking to AI. From 10 December 2026 the Privacy Act requires the privacy policy to explain automated decisions that use personal information and significantly affect people; the recruitment platform’s candidate ranking is one such decision and is not disclosed.
  • The assessment found eight AI uses, of which five were on Wattlegrove’s list. Three were found during the assessment, including the candidate ranking feature, which the vendor switched on in 2025 and which nobody owns. In the staff survey (214 responses), 41 percent had used an AI tool for work without being sure it was approved, and 33 percent sometimes rely on AI output without checking it.
Decisions sought
  • Endorse the target of a defined practice (Level 3) in every domain within 24 months, with oversight and testing of AI that affects people at Level 4.
  • Fund the dedicated uplift team that sets the roadmap’s capacity.
  • Appoint the Chief AI Officer with written authority, including to pause AI use, and establish the AI governance committee within 90 days.
  • Direct the privacy, people and customer teams to meet the EU AI Act and Privacy Act obligations in the first 90 days.
  • Set the first re-assessment for October 2027, with a light re-score in April 2027.
Method and scope

Show that the result is evidence-based and repeatable, and what it covers.

Draws on
assessment.mode; assessment.scope; assessment.edition; assessment.period; assessment.method; survey; scoring.criterionScoring; scoring.domainAggregation

How it is written

  • State the scope, edition, mode and period in the first sentence.
  • List the evidence base: documents and records reviewed, interviews, focus groups, workshops, survey responses and response rate, and whether the survey met the validity threshold.
  • Explain scoring in three sentences taken from the model: pass tests decide levels; asserted evidence is capped at 2; domain scores are capped means.
  • State the evidence confidence across the 40 criteria (counts of evidenced, asserted and not known) and any criteria not assessed and why.
  • In self or team mode, add the mode’s limitation sentence from scoring.modes.

Worked example

Paragraphs
  • This assessment covered the whole of Wattlegrove Group (600 staff, including the Netherlands sales subsidiary) using the organisation edition of the AI Capability Maturity Assessment. It was assessor-led by two UHS Logic assessors with an independent quality reviewer, and ran from 17 August to 9 October 2026.
  • The evidence base comprised 63 documents, records and system configurations; 19 interviews across nine roles; two frontline focus groups; five workshops; and an anonymous staff survey that received 214 responses (36 percent of staff, above the validity threshold of 90).
  • Each of the 40 criteria was scored at the highest level whose pass test was met, in half-level steps where substantial parts of the next level were in place. Scores that rest on assertion alone are capped at Level 2. A domain’s score is the average of its five criteria, capped at one level above its weakest criterion, so that a missing foundation cannot be averaged away.
  • Of the 40 criteria, 39 were scored on evidence seen and one on assertion: executives described quarterly board briefings on AI, but no papers were provided, so Executive evidence rhythm (1.5) is capped at Level 2. All scores were played back to the people who provided the evidence before this report was drafted.
Maturity profile

Show the result at a glance: overall, by domain, by criterion and against target.

Draws on
overall; domains; criteria; layers; rai; biggestGaps

How it is written

  • Show the radar (current against target), then the domain table: domain, score, band, uncapped mean where different, target and gap.
  • Show the 40-criteria heat map, then one paragraph reading it: how many criteria are at each level, which are at Level 3 or above, and which are at Level 1.
  • Report the layer scores in one sentence and the responsible AI overlay scores in a short table with the weakest dimension named.
  • Where a domain was capped, say which criterion capped it and by how much.

Worked example

Paragraphs
  • Wattlegrove’s overall score is 1.7 (Initial, approaching Repeatable). The foundations layer averages 1.8, ways of working 1.4 and practice 1.9: the organisation is weakest at the everyday disciplines of assessing, gating and delivering use cases.
  • Of the 40 criteria, one is at Level 3 (Assessed AI platform), three are at 2.5, seventeen at Level 2, twelve at 1.5 and seven at Level 1. The seven at Level 1 are risk appetite and tiers, three lines of assurance, risk tiering, incident and near-miss management, decision records, lifecycle execution, and reuse. No domain was capped: each domain’s average is within one level of its weakest criterion.
  • Read through the responsible AI overlay, impact and risk is weakest (1.1) and transparency and records next (1.3), while development and operation and people and culture both reach 2.0. Wattlegrove is better at building and running AI than at understanding and explaining its effects on people.
Table
Headers
  • Domain
  • Score
  • Band
  • Target (24 months)
  • Gap
Rows
D1 Strategy and leadership1.7Initial, approaching Repeatable3.01.3
D2 Governance and operating model1.6Initial3.01.4
D3 Risk, assurance and transparency1.4Initial3.42.0
D4 Data, knowledge and semantics1.8Initial, approaching Repeatable3.01.2
D5 Platform, architecture and security2.1Repeatable3.00.9
D6 Design and engineering practice1.9Initial, approaching Repeatable3.51.6
D7 Use-case delivery and value1.4Initial3.01.6
D8 People, capability and culture2.0Repeatable3.01.0
Findings by domain

Explain each domain’s score so that owners can act on it: what is working, what is missing, how sure we are, and what it exposes.

Draws on
domains; criteria (scores, confidence, evidence, findings); model.domains[].risksWhenWeak; model.criteria[].passTests; model.criteria[].editions[edition]; survey.signals

How it is written

  • One subsection per domain, in domain order, opening with the domain band phrase.
  • Strengths: criteria at or above the domain score, highest first, each with the practice that earned it (from the assessor’s finding). If no criterion exceeds 2.0, say what partial practice exists instead.
  • Gaps: criteria below the target, lowest first. For each, quote the next level’s pass test that is not met, in plain words, and the red flag observed if any.
  • Evidence state: counts of evidenced, asserted and not-known criteria; any caps applied and why; survey signals that corroborate or contradict.
  • Risk: the two or three risksWhenWeak most relevant to the gaps found, made specific to the organisation’s AI uses. Mention edition obligations that touch the domain.
  • Close with one line pointing to the initiatives that address the gaps (ids and titles).

Worked example

Domain
D3 Risk, assurance and transparency (score 1.4, target 3.4)
Paragraphs
  • Risk, assurance and transparency is at an early stage (1.4, Initial): practice depends on individuals, nobody owns the outcome and little is written down.
  • Strengths. The organisation has the beginnings of two practices. IT project gates exist and every system passes them before release (Lifecycle and gates, 2.0), and a privacy impact assessment was completed for the recruitment platform in 2024 (Impact assessments, 1.5). The Australian chat assistant tells customers it is automated.
  • Gaps. Incident and near-miss management (1.0, target 3): AI problems are logged as IT tickets and no near misses are recorded. To reach Level 3, Wattlegrove needs an AI incident definition, a severity scale and a runbook naming who may halt a system, a register of incidents and near misses, and one rehearsal. Risk tiering (1.0, target 3): no use case is tiered, so the candidate ranking feature, which affects job applicants, receives the same attention as a meeting summary tool. Impact assessments (1.5, target 3): the 2024 assessment predates the ranking feature and no AI method exists; Level 3 needs a standard method applied to every in-scope use before deployment. Transparency and contestability (1.5, target 3): there is no statement of AI use and no inventory of decisions about people, the EU chat assistant gives no notice, and the privacy policy does not explain automated decisions. Lifecycle and gates (2.0, target 3): the IT gates test nothing AI-specific; the chat assistant went live without an AI review.
  • Evidence state. All five criteria were scored on evidence seen. The survey corroborates the gaps: 36 percent of staff know how to report an AI problem, 21 percent believe reported problems lead to change, and 41 percent do not know when they must tell a customer that AI was involved.
  • Risk. Harmful or unfair outcomes from the candidate ranking could go unnoticed, could not be explained to an applicant, and would not be recognised as an AI incident. Wattlegrove is already outside the EU AI Act’s transparency obligation for its EU chat assistant, and has two months to meet the Privacy Act’s automated-decision disclosure. Repeated chat assistant errors are being fixed as tickets without anyone looking for the pattern.
  • Initiatives: I-307 and I-308 (inventory, privacy policy, statement and review paths), I-310 (incident runbook), I-301 and I-302 (impact assessments), I-305 (tiering), I-303 (lifecycle and gates).
Second example
Domain
D5 Platform, architecture and security (score 2.1, target 3.0)
Paragraphs
  • Platform, architecture and security is emerging (2.1, Repeatable): good practice exists in places, but it depends on people rather than standards and is not yet followed everywhere.
  • Strengths. Assessed AI platform (3.0): Azure AI services run inside a landing zone assessed by an external party in 2025, with residency documented for each service. This is Wattlegrove’s only criterion at Level 3 and the reason sensitive work can safely move onto approved AI.
  • Gaps. Third-party and embedded AI (1.5, target 3): contracts carry no AI clauses and the recruitment vendor switched on candidate ranking without a decision by Wattlegrove. AI security controls (2.0, target 3): content filters are on, but there is no AI threat model and the chat assistant has never been tested for prompt injection. Approved tools (2.0, target 3): Copilot is approved, but no list is published, and 41 percent of surveyed staff had used a tool they were unsure was approved; this survey result also caps the criterion at Level 3 until detection works. Observability, halt and rollback (2.0, target 3): uptime is monitored, behaviour is not, and no halt procedure is written down.
  • Evidence state. All five criteria were scored on evidence seen.
  • Risk. Customer and employee information may be reaching public AI tools; vendor model changes can alter the chat assistant’s behaviour without notice; and the SmartFlow feature, which adjusts irrigation schedules within limits, has no documented way to be halted if it misbehaves.
  • Initiatives: I-503 (approved tool list), I-507 (procurement checklist and clauses), I-509 (threat model and testing), I-505 (logging and behaviour monitoring), then I-506 (halt rehearsal).
Cross-cutting themes

Name the few patterns that explain most of the findings, so leaders address causes rather than symptoms.

Draws on
criteria; domains; survey; profile.aiInUse; obligations; context

How it is written

  • Detect themes with these rules and include every theme that fires, most material first (maximum five):
  • Use is wider than the register: criterion 2.3 below 3 and (survey S08 concern 25 percent or more, or AI uses found that were not on the register).
  • Decisions about people without oversight: context decisionsAboutPeople is true and (3.4 below 3 or 6.2 below 3).
  • Obligations arriving without owners: any obligation overdue or due within 12 months whose criterion is below the minimum level.
  • Willing staff without rules or tools: survey S12 agreement 70 percent or more, and 8.3 or 5.3 below 3.
  • Technology ahead of governance: D5 or D6 more than 1.0 above D2 or D3.
  • Controls that exist but are not run: three or more criteria at 2.0 to 2.5 whose next pass test fails only for want of operating records.
  • Pilots without decisions: 7.3 below 2.5 and at least one pilot older than six months.
  • Each theme: a one-line title, two to four sentences of evidence across domains, and the initiatives that address it.

Worked example

Paragraphs
  • 1. AI use is wider than anyone can see. Eight AI uses were found, five of which were on Wattlegrove’s list. The candidate ranking feature and meeting summaries arrived through vendor updates, and 41 percent of staff had used a tool they were not sure was approved. Until the register is complete, no other control can be applied consistently. (I-203, I-503, I-507)
  • 2. AI is shaping decisions about people without designed oversight. The recruitment platform ranks candidates, recruiters are told to ‘use judgment’, nothing records what they review, and applicants are not told AI is involved. One third of staff say they sometimes rely on AI output without checking it. (I-307, I-308, I-605, I-302, I-404)
  • 3. Obligations are arriving without owners. The EU AI Act’s literacy and transparency duties already apply to Wattlegrove as a provider in the EU, and the Privacy Act’s automated-decision disclosure starts on 10 December 2026. No one has been asked to meet them. (I-801, I-307, I-308)
  • 4. A sound platform without the governance to use it. The assessed landing zone is Wattlegrove’s strongest asset, but there is no appetite, committee, tiering or lifecycle to decide what should run on it. The platform can safely carry far more than the organisation can currently govern. (I-102, I-103, I-202, I-303)
Risk exposure

Translate gaps into the risks leaders carry today, rated consistently.

Draws on
criteria (score, weight); model.domains[].risksWhenWeak; obligations; context; profile.aiInUse

How it is written

  • Exposure score for each criterion = max(0, 3 minus score) x importance weight. Rate High at 4.5 or more, Medium at 2.0 to 4.4, Low below 2.0.
  • List the High exposures first, each as a risk statement: cause (the gap), event (what could happen with this organisation’s actual AI uses), consequence (to people, the organisation, compliance).
  • Add every overdue or due obligation as its own compliance risk with the date.
  • Group the rest as Medium and Low counts with the criteria named.
  • Do not invent likelihoods or financial values; the rating comes from the rule.

Worked example

Paragraphs
  • Ten criteria rate High: risk appetite, the register, impact assessments, risk tiering, transparency, incident management, classification and handling, decision records, third-party AI and oversight design. Twenty rate Medium and ten Low. The three most material risks, with Wattlegrove’s own uses, and the three compliance exposures:
Table
Headers
  • Risk
  • Criteria
  • Exposure
Rows
Because AI incidents are not defined or recorded, a pattern of wrong or harmful chat assistant answers, or a biased ranking of candidates, could continue for months without anyone recognising it, damaging customers and applicants and exposing Wattlegrove to complaints it cannot answer.3.5 (1.0), 3.2 (1.0)High
Because the candidate ranking is not assessed, overseen or recorded, an applicant who is unfairly screened out could not be given an explanation or a human review, creating discrimination and privacy exposure.3.1 (1.5), 6.2 (1.5), 4.4 (1.0)High
Because there is no published tool list or enforced ceiling, customer and employee information may already be in public AI tools used by 41 percent of staff, outside any contract or retention control.5.3 (2.0), 4.3 (2.0)High
EU AI Act transparency (Article 50) for the EU chat assistant: obligation has applied since 2 August 2026.3.4 (1.5)Compliance: overdue
EU AI Act AI literacy (Article 4): measures to support literacy expected since 2 February 2025; 34 percent of staff have done the optional module.8.1 (2.0)Compliance: overdue
Privacy Act automated-decision transparency: privacy policy must explain qualifying automated decisions from 10 December 2026.3.4 (1.5)Compliance: due in 62 days
Target state and gap analysis

Show the chosen targets, the gaps, the biggest gaps by priority and what closes each.

Draws on
targets; domains (target, gap); criteria (target, gap, weight); biggestGaps; roadmap

How it is written

  • State the ambition preset, time frame and any overrides with their reasons, from the workshop notes.
  • Show the domain gap table and the biggest gaps chart.
  • For each of the ten biggest gaps: current to target, priority score, and the next initiative with its horizon.
  • State the overall gap and the share of first-horizon initiatives that are must-dos or quick wins.
  • Close by pointing to the AI Strategy and Roadmap.

Worked example

Paragraphs
  • Leaders chose the Balanced ambition over 24 months: a defined practice (Level 3) in every domain, with Risk, assurance and transparency and Design and engineering practice lifted to 3.5 because AI contributes to recruitment decisions. Risk, assurance and transparency is held to 3.4 by the pace rule, which allows one level of improvement per year. Platform, architecture and security was set to 3.0 because no supervised autonomy is planned within 24 months. The overall gap is 1.4 levels.
  • The ten biggest gaps by priority are: 3.5 Incident and near-miss management, 1.0 to 3 (priority 27), next I-310 in the first 90 days; 6.2 Autonomy and human oversight design, 1.5 to 4 (22.5), next I-605 in the first 90 days; 3.1 Impact assessments, 1.5 to 3 (20.25), next I-301 in the first 90 days; 1.2 Risk appetite and tiers, 1.0 to 3 (18), next I-102 in the first 90 days; 3.2 Risk tiering in practice, 1.0 to 3 (18), next I-102; 2.3 Use-case register, 1.5 to 3 (13.5), next I-203 in the first 90 days; 3.4 Transparency and contestability, 1.5 to 3 (13.5), next I-307 in the first 90 days; 5.4 Third-party and embedded AI, 1.5 to 3 (13.5), next I-507 in months 3 to 6; 4.3 Classification and handling, 2.0 to 3 (13.5), next I-406 in the first 90 days; 6.3 Testing, evaluation and simulation, 2.0 to 4 (12), next I-603 in months 6 to 12.
  • All twelve first-horizon initiatives are must-dos or quick wins. The AI Strategy and Roadmap sets out the full plan.

AI Strategy and Roadmap

Set the direction for AI and the sequenced, owned plan that takes the organisation from its assessed baseline to its target.

Audience
Board and executive committee (endorsement); Chief AI Officer and initiative owners (delivery); all staff (summary of vision and principles).

Outline

  1. Vision and ambition
  2. Guiding principles
  3. Strategic priorities
  4. Target operating model
  5. Prioritised initiative portfolio
  6. Roadmap by horizon
  7. Investment and capacity
  8. Benefits and measures
  9. Risks and dependencies
  10. Governance of the roadmap
  11. The first 90 days

Content rules

  • The strategy is short and decisive: it says what AI is for, how far and how fast, what is out of bounds, and what happens first.
  • Every priority traces to findings and every initiative to a criterion gap.
  • Vendor-neutral throughout; ‘Where Renly helps’ only in a separate box per workstream if included.
  • Dates come from the roadmap horizons counted from the endorsement date, and obligation dates from the references.

Sections

Vision and ambition

Say what AI is for in this organisation and how far it will go in the time frame.

Draws on
profile; targets; domains (target); context

How it is written

  • Purpose statement: one sentence linking AI to the organisation’s own mission and naming human accountability.
  • Vision statement: what will be true at the end of the time frame, in three or four observable clauses drawn from the Level 3 descriptors of the target domains.
  • Ambition: the preset, time frame and target band, and the autonomy ceiling: the highest autonomy rung the organisation will allow in the period, which may not exceed rung 2 unless D5 and D6 targets are 3.5 or more.
  • Boundaries: three to five things AI will not be used for, drawn from the risk appetite or proposed for it.

Worked example

Paragraphs
  • Purpose. Wattlegrove uses AI to help farmers and councils use water well, to serve customers faster and to free our people for the work only they can do, with a named person accountable for every use.
  • Vision. By October 2028, Wattlegrove will know every AI system it uses and who owns it; will assess and gate every use before it goes live, in proportion to its risk; will tell customers and applicants when AI is involved and give them a human to talk to; and will measure what each AI investment delivers.
  • Ambition. A defined practice in every domain within 24 months, with oversight and testing of AI that affects people at Level 4. In this period AI may assist and draft (rungs 1 and 2). The SmartFlow feature continues to act within its fixed limits under the product’s existing safety design, but no new AI will act without per-action approval until halt and rollback have been rehearsed.
  • Boundaries. Wattlegrove will not use AI to make hiring, discipline or credit decisions without a person deciding; will not put customer, employee or commercial-in-confidence information into tools not approved for it; and will not deploy AI to EU customers without the notices EU law requires.
Guiding principles

Give every AI decision a short, shared test.

Draws on
edition; rai (overlay); model.ethicsPrinciples; context

How it is written

  • Six to eight principles, each a short imperative and one sentence of meaning in practice.
  • Always include: human accountability; proportionate to risk; evidence over assertion; transparent and contestable; secure and private by default.
  • Add a principle for the weakest responsible AI dimension, worded as a commitment.
  • Map each principle to the Australian AI Ethics Principles it serves.

Worked example

Paragraphs
  • A named person answers for every use. AI never owns a decision; an accountable owner does. (Accountability.)
  • Proportionate to risk. Light rules for assistants, full assurance for AI that affects people. (Wellbeing; reliability and safety.)
  • Tell people when AI is involved, and give them a person. Customers, applicants and staff know when AI contributed and can ask a human to review it. (Transparency and explainability; contestability.)
  • Understand the impact before go-live. No AI that affects people goes live without an impact assessment. This principle answers our weakest responsible AI dimension. (Fairness; human-centred values.)
  • Approved tools, within their limits. Use the tools on the list, and only with the information each is approved for. (Privacy protection and security.)
  • Evidence over assertion. We report what we can show, and we measure what AI delivers. (Accountability.)
Strategic priorities

Turn the findings into three to five priorities that organise the roadmap.

Draws on
themes (F5); obligations; domains (gap); playbooks

How it is written

  • Priority 1 is always ‘Meet the obligations now due’ if any obligation is overdue or due within 12 months.
  • Priority 2 is ‘Build the foundations’ if foundationFlag is true; otherwise the largest-gap layer.
  • Further priorities come from the cross-cutting themes, one each, worded as outcomes.
  • For each: the outcome, the domains and workstreams it draws on, and two measures.

Worked example

Paragraphs
  • 1. Meet the obligations now due. EU AI Act literacy and transparency, and Privacy Act automated-decision disclosure. Workstreams: Governance and assurance; People and adoption. Measures: EU notice live on the chat assistant within 30 days; privacy policy updated before 10 December 2026.
  • 2. Build the foundations. Appetite and tiers, a Chief AI Officer with authority, a committee that decides, a complete register and a short acceptable-use policy. Workstreams: Strategy and leadership; Operating model; Governance and assurance. Measures: all eight AI uses with an owner and a tier within six months; committee decision log in use.
  • 3. Govern AI that affects people. Impact assessment, oversight design and decision records for the recruitment ranking first, then for any future people-affecting use. Workstreams: Governance and assurance; Engineering practice; Data and knowledge. Measures: ranking feature assessed and its review recorded within six months; zero people-affecting uses without an assessment.
  • 4. Give staff approved tools and the skills to use them well. Workstreams: Platform and security; People and adoption. Measures: staff unsure whether a tool was approved below 15 percent at the next survey; training completion above 80 percent.
  • 5. Make value measurable. Charters for pilots, an intake and a benefits register. Workstream: Use-case portfolio and value. Measures: every pilot with a decision date; every funded use case with a baseline.
Target operating model

Describe who will do what when the target is reached, summarised from the Governance and Operating Model.

Draws on
governanceModel sections; playbooks.WS-OPM; context.staff

How it is written

  • Four layers in one table: strategic (board and executive), governance (committee), operational (owners and the enabling team), system (technology, security, data, privacy, records).
  • Size the enabling team: fewer than 250 staff, a part-time AI lead; 250 to 999, an AI lead plus one to three; 1,000 or more, a team of four or more.
  • Say which forums are created, which are reused and which are retired.

Worked example

Paragraphs
  • Strategic: the board’s Risk and Audit Committee oversees AI risk; the executive committee owns the strategy, appetite and investment; the Chief Operating Officer is executive sponsor. Governance: an AI governance committee chaired by the Chief AI Officer (the CTO, with a written delegation) replaces the informal working group. Operational: a named owner for each AI use, supported by a three-person AI centre of excellence. System: IT runs the platform and logging; the security lead owns AI controls and the tool list; legal and privacy own assessments and disclosure; records management owns retention.
  • The full model is in the Governance and Operating Model recommendations.
Prioritised initiative portfolio

List every selected initiative by workstream with its priority, so owners see their part.

Draws on
roadmap.horizons; initiatives; playbooks

How it is written

  • Group initiatives by workstream (playbook order). For each: id, title, class (must-do, foundation, value), effort, owner role, horizon, criteria lifted.
  • Mark quick wins.
  • Under each workstream add two lines from its playbook: the first recommendation and the main pitfall.
  • List any ‘beyond 24 months’ initiatives and any criteria with no library initiative at the end.

Worked example

Paragraphs
  • Forty-six initiatives were selected across the eight workstreams: twelve start in the first 90 days, ten in months 3 to 6, thirteen in months 6 to 12 and ten in months 12 to 24. One (I-606, enforcing autonomy in the platform) falls beyond 24 months because it depends on halt and rollback being rehearsed first.
  • Governance and assurance (10 initiatives) carries the must-dos and most foundations: I-307 and I-308 (transparency and the privacy policy), I-310 (incident runbook), I-203 (register and discovery), I-301 and I-302 (impact assessment), I-202 (committee), I-305 (tiering), I-303 (lifecycle and gates). Start with the register; avoid a committee that never refuses anything.
Table
Headers
  • Workstream
  • Initiatives (horizon)
Rows
Strategy and leadershipI-102 (H1), I-103 (H1), I-101 (H2), I-105 (H3), I-104 (H4)
Governance and assuranceI-307 (H1), I-308 (H1), I-310 (H1), I-203 (H1), I-301 (H1), I-202 (H1), I-302 (H2), I-305 (H2), I-205 (H3), I-303 (H3)
Operating modelI-201 (H2), I-209 (H2), I-207 (H2)
Use-case portfolio and valueI-701 (H3), I-702 (H3), I-706 (H4), I-710 (H4), I-704 (H4), I-708 (H4)
Data and knowledgeI-406 (H1), I-404 (H3), I-408 (H3), I-403 (H4), I-401 (H4)
Platform and securityI-503 (H1), I-507 (H2), I-509 (H3), I-505 (H3), I-506 (H4)
Engineering practiceI-605 (H1), I-609 (H2), I-603 (H3), I-601 (H3), I-607 (H4), I-604 (H4); I-606 beyond 24 months
People and adoptionI-801 (H1), I-803 (H2), I-809 (H2), I-805 (H3), I-807 (H3)
Roadmap by horizon

Show what starts when, and why in that order.

Draws on
roadmap; roadmapLogic.horizons; obligations

How it is written

  • One paragraph per horizon: its focus (from roadmapLogic), the initiatives starting in it, capacity used against capacity, and any flags (over capacity, obligation overdue, deadline at risk).
  • Explain the ordering in one sentence: must-dos first, quick wins in the first 90 days, dependencies respected, capacity limits per horizon.
  • Show the roadmap figure.

Worked example

Paragraphs
  • The roadmap puts obligations and foundations first, fits quick wins into the first 90 days, respects dependencies and keeps each horizon within the capacity leaders funded.
  • Mobilise (0 to 90 days). Twelve initiatives using 18 of 18 capacity points: the three must-dos (I-307, I-308, I-801), then appetite and tiers (I-102), the incident runbook (I-310), the register and discovery sweep (I-203), the impact assessment method (I-301), tool ceilings (I-406), the Chief AI Officer’s authority (I-103), the committee (I-202), the approved tool list (I-503) and autonomy rules for each system (I-605). The two EU obligations are already overdue and are flagged as such.
  • Establish (3 to 6 months). Ten initiatives using 18 of 18 points: owners for every use (I-201), the acceptable-use policy (I-803), the strategy (I-101), impact assessments for every in-scope use (I-302), the centre of excellence (I-209), procurement clauses (I-507), the RACI (I-207), independent tiering (I-305), design review (I-609) and the concern channel (I-809).
  • Embed (6 to 12 months). Thirteen initiatives using 29 of 30 points, including intake (I-701), decision records (I-404), the executive review (I-105), the assurance map (I-205), pilot charters (I-702), the AI threat model (I-509), evaluation suites (I-603), logging and behaviour monitoring (I-505), champions (I-807) and the lifecycle and gates (I-303).
  • Scale (12 to 24 months). Ten initiatives using 31 of 40 points, including the reference use case governed end to end (I-710), automated evaluation (I-604), the benefits register (I-704), data quality baselines (I-401) and halt and rollback rehearsal (I-506).
Investment and capacity

Show the effort the roadmap needs and the resourcing behind it.

Draws on
roadmap.capacity; roadmap.used; initiatives (effort); roadmapLogic.effortDefinitions

How it is written

  • Show effort points per horizon against capacity, and the count of S, M and L initiatives.
  • Convert to indicative people effort with the standard ranges: S about 1 to 1.5 person-months, M about 3 to 5, L about 9 to 15. Present as a range, never a single figure, and state that it excludes licences and platform costs.
  • Name what the organisation must fund (enabling team, partner support, platform work) and what it must free up (owners’ time, specialist reviewers).
  • If capacity was overridden, state the reason from the workshop notes.

Worked example

Paragraphs
  • The roadmap needs 96 effort points over 24 months: 22 small, 22 medium and one large initiative, about 97 to 158 person-months of effort excluding licences and platform costs. That is more than Wattlegrove could absorb from existing roles, which is why leaders funded a dedicated uplift team (an AI lead, two analysts and partner support) for 24 months and set capacity above the mid-size default.
  • The largest single item is the reference use case (I-710), 6 to 9 months of work by the recruitment owner, HR systems and the centre of excellence. Business owners must free time to own their uses and present at gates; legal and privacy carry an early peak in the first 90 days.
Benefits and measures

Say how success will be measured, with baselines from this assessment.

Draws on
domains; criteria; survey; initiatives (kpis); targets

How it is written

  • Four groups of measures: maturity (overall and domain scores against target), governance (coverage and gate measures), people (survey and training measures) and value (benefits register measures).
  • Each measure has a baseline from this assessment and a target with a date. Use survey items as baselines where they exist.
  • Include one leading indicator of healthy reporting (near misses reported) and say that a rising count at first is good news.

Worked example

Table
Headers
  • Measure
  • Baseline (October 2026)
  • Target
Rows
Overall maturity1.73.0 or more by October 2028
AI uses on the register with owner and tier5 of 8 (owner); 0 tiered100 percent by April 2027
In-scope uses with a current impact assessment0100 percent by October 2027
Staff who have completed AI training34 percent80 percent by April 2027; 95 percent by October 2028
Staff unsure whether an AI tool they used was approved41 percentBelow 15 percent at the October 2027 survey
Staff who know how to report an AI problem36 percent70 percent at the October 2027 survey
Near misses reported per quarter0Rising during 2027, then stable
Funded AI use cases with a benefit baseline1 of 5100 percent by October 2027
Paragraphs
  • A rising count of reported near misses in 2027 will mean the reporting culture is working, not that AI has become less safe.
Risks and dependencies

Name what could stop the roadmap and how it is handled.

Draws on
roadmap (flags, beyond); initiatives (prerequisites); playbooks (pitfalls); context

How it is written

  • Always include: capacity (from flags or overrides), owner engagement, the dependency chain with the longest path, and any obligation flagged ‘deadline at risk’ or ‘overdue’.
  • Add the main pitfall of each of the two largest workstreams.
  • Each risk has a mitigation and an owner role.

Worked example

Table
Headers
  • Risk
  • Mitigation
  • Owner
Rows
The EU obligations are already overdue and the Privacy Act date is 62 days away.Treat I-307, I-308 and I-801 as must-dos with weekly reporting to the executive sponsor until complete; put the EU chat notice live first.Executive sponsor
The uplift team is funded but not yet recruited.Use partner support for the first 90 days; recruit the AI lead before month 3.Chief AI Officer
Owners named but not engaged, so the centre of excellence ends up owning use cases.Owners present their own gate submissions; ownership written into position descriptions in year 2.Executive sponsor
Longest dependency chain: register, then owners, then impact assessments, then the lifecycle and the reference use case.Start the register in week 1; do not let the sweep exceed 10 weeks.AI lead
A committee that discusses but never decides.Terms of reference with decision rights from the first meeting; decision log reported quarterly.Chief AI Officer
Governance of the roadmap

Say how progress is tracked and when the plan is changed.

Draws on
roadmapLogic.governanceCadence; reassessment

How it is written

  • Reproduce the cadence table (monthly committee, quarterly executive, six-monthly re-score, annual re-assessment) with the organisation’s forum names.
  • List the realignment triggers in plain words and say who convenes the realignment review.
  • Give the dates of the first light re-score and the first full re-assessment.

Worked example

Paragraphs
  • Monthly, the AI governance committee reviews initiative status, blockers and decisions needed. Quarterly, the executive committee checks progress against planned uplift, reviews the dashboard and confirms and funds the next horizon. In April 2027 the centre of excellence re-scores the criteria targeted so far and re-runs four survey items; in October 2027 a full re-assessment sets the new baseline.
  • The Chief AI Officer convenes a realignment review within 30 days if a domain achieves less than half its planned uplift at two consecutive quarterly checks, if any domain falls by half a level, if an obligation changes, after a serious AI incident, if Wattlegrove starts using AI that acts without per-action approval or makes decisions about people in a new area, or if a domain reaches its target three months early.
The first 90 days

Give the executive a week-by-week start that can be approved on the day.

Draws on
roadmap.horizons.H1; initiatives (duration, owner); obligations

How it is written

  • List every first-horizon initiative with owner role and the week it starts and finishes, scheduled so that must-dos with the earliest dates start in week 1 and dependent items follow their prerequisites.
  • Add three fixed milestones: committee’s first meeting (by week 4), register complete (by week 10), executive review of the first 90 days (week 13).
  • Close with the decisions needed now to start.

Worked example

Table
Headers
  • Weeks
  • Initiative
  • Owner
Rows
1 to 2EU chat notice live (part of I-308); I-103 Chief AI Officer’s written authorityHead of Customer Service; Board
1 to 6I-307 Inventory of decisions about people and privacy policy updateLegal and privacy lead
1 to 10I-203 Register and discovery sweepAI lead
1 to 12I-801 Mandatory foundational AI trainingPeople and capability
2 to 4I-202 AI governance committee (first meeting by week 4)Executive sponsor
2 to 6I-102 Risk appetite and tier criteriaExecutive sponsor
3 to 6I-503 Approved tool list; I-406 Tool ceilingsSecurity lead
3 to 8I-310 Incident runbook, register and rehearsalSecurity lead
5 to 10I-301 Impact assessment method and intake screeningLegal and privacy lead
6 to 12I-605 Autonomy and approval rules, starting with the candidate rankingRecruitment owner
6 to 13I-308 Transparency statement and human review pathsLegal and privacy lead
13Executive review of the first 90 daysExecutive committee
Paragraphs
  • Decisions needed now: endorse the targets, fund the uplift team, sign the Chief AI Officer’s delegation and name the members of the AI governance committee.

AI Governance and Operating Model: Recommendations

Recommend the roles, forums, decision rights, lifecycle and assurance lines that will run AI governance at the target level, sized to the organisation.

Audience
Executive committee (endorsement); Chief AI Officer, committee members, owners and specialist functions (operation).

Outline

  1. Roles and accountabilities
  2. Forums
  3. Decision rights
  4. Lifecycle and gates
  5. Assurance lines
  6. Implementation and the ask

Content rules

  • Minimum viable: recommend the lightest model that meets the target and the obligations, and say what it grows into.
  • One accountable role per decision; never a committee or a vendor.
  • Reuse existing forums where they can carry the work; create new ones only where decision rights are missing.
  • Size by organisation: fewer than 250 staff, combine roles; 250 to 999, a small enabling team; 1,000 or more, a full enabling team and specialist reviewers.

Sections

Roles and accountabilities

Name who is accountable for what.

Draws on
criteria 1.3, 2.1, 2.2, 8.2 (scores and findings); playbooks.WS-OPM; context.staff; edition

How it is written

  • Table of roles: board or accountable authority, executive sponsor, Chief AI Officer or AI lead, AI governance committee, enabling team, use-case owners, technology, security, privacy and legal, data, records, internal audit, champions, all staff.
  • For each: accountabilities in one line, and whether the role exists today (from findings), needs a change, or is new.
  • Government edition: map to accountable officials and accountable use-case owners under Policy v2.0 and the Chief AI Officer under the APS AI Plan.

Worked example

Table
Headers
  • Role
  • Accountabilities
  • Today
Rows
Board Risk and Audit CommitteeOversees AI risk; receives an AI report twice a year.Change: AI not yet on its agenda
Executive sponsor (Chief Operating Officer)Owns AI outcomes for the executive; chairs the quarterly executive AI review.New
Chief AI Officer (CTO, with written delegation)Runs the register, lifecycle and tool list; chairs the committee; can pause any AI use.Change: named by email, no authority
AI governance committeeDecides use cases, tiers, gates, approved tools and exceptions.New: replaces the working group
AI centre of excellence (three people)Runs intake, register and lifecycle; supports owners; reports the dashboard.New
Use-case ownersAnswer for each AI use; present gate submissions; attest annually.Change: five of eight named informally, none acknowledged
Security leadAI controls, threat model, tool ceilings, incident runbook.Change
Legal and privacyImpact assessment review, automated-decision disclosure, review paths, EU obligations.Change
Records managerRetention of AI content; legal holds.Change
Internal auditIndependent assurance of AI governance from 2027.Change
ChampionsHelp colleagues and feed back problems; two hours a week.Change: six informal champions
Paragraphs
  • Wattlegrove’s model is deliberately small: a three-person enabling team under the CTO and a monthly committee, growing only if the portfolio grows.
Forums

Say which bodies meet, how often, and what each decides.

Draws on
criteria 1.5, 2.2; workshops; roadmapLogic.governanceCadence

How it is written

  • Table of forums: name, chair, members, cadence, decides, escalates to.
  • Use existing forums where possible (executive committee, risk committee) and say what changes in their terms of reference.
  • Include the review calendar: weekly triage, monthly committee, quarterly executive, annual re-assessment and runbook rehearsal.

Worked example

Table
Headers
  • Forum
  • Chair
  • Cadence
  • Decides
  • Escalates to
Rows
Board Risk and Audit CommitteeCommittee chairTwice a year on AIOversight of AI risk and appetiteBoard
Executive committee AI reviewExecutive sponsorQuarterlyStrategy, appetite, investment, out-of-appetite usesBoard
AI governance committeeChief AI OfficerMonthly, with out-of-cycle gate decisionsUse cases, tiers, gates, approved tools, exceptions within appetiteExecutive committee
Intake triageAI centre of excellence leadWeeklyStandard decisions under delegation; routingAI governance committee
Paragraphs
  • The AI working group is retired once the committee has met three times; its members join the committee or the champion network.
Decision rights

Make clear who decides each AI matter, and how fast.

Draws on
criterion 2.5; playbooks.WS-OPM; edition

How it is written

  • RACI table for at least: set strategy and appetite; approve a use case and its tier; decide at a gate; approve a tool or model; approve an exception; complete an impact assessment; publish the transparency statement; respond to an AI incident; pause or stop an AI use.
  • One A per row. Columns: board, executive sponsor, Chief AI Officer, committee, owner, enabling team, technology, security, privacy and legal, internal audit.
  • Decision categories with turnaround: standard (days), use case (next meeting), platform and tool (next meeting), strategic (executive cycle). Add two worked examples from the organisation’s own AI uses.

Worked example

Table
Headers
  • Decision
  • Accountable
  • Responsible
  • Consulted
Rows
Set AI strategy and risk appetiteExecutive committeeChief AI OfficerCommittee, security, privacy and legal
Approve a use case and its tierAI governance committeeUse-case ownerSecurity, privacy and legal, centre of excellence
Decide at a gateAI governance committeeUse-case ownerSecurity, privacy and legal
Approve an AI tool or modelAI governance committeeSecurity leadIT, privacy and legal
Pause or stop an AI useChief AI OfficerITUse-case owner
Respond to an AI incidentUse-case ownerSecurity leadPrivacy and legal, Chief AI Officer
Publish the transparency statementChief AI OfficerLegal and privacyOwners
Paragraphs
  • Worked example: the recruitment vendor switches on a new AI feature. Platform and tool decision: the vendor must disclose it under the new contract clause; security assesses it; the committee decides at its next meeting whether and how it may be used; the register is updated.
  • Worked example: a team wants Copilot to summarise customer complaints. Standard decision: registered under the Copilot entry by the centre of excellence within days, within the tool’s ceiling; no committee decision needed.
Lifecycle and gates

Define the path every use case travels and the gates it must pass, scaled by tier.

Draws on
criteria 3.1 to 3.3, 6.1 to 6.3; tier criteria (1.2); edition references

How it is written

  • Stages: intake, impact assessment, design, testing or simulation, shadow, operating, retired.
  • Gates with question and pass condition: G1 design complete, G2 simulation or testing passed, G3 governance validated, G4 shadow proven, G5 organisationally ready.
  • Tier table: which gates apply at low, medium and high tier.
  • Government edition: align stages to the AI technical standard’s Discover, Operate and Retire phases and name the DTA impact assessment tool at G3.

Worked example

Table
Headers
  • Tier
  • Indicative criteria
  • Gates
Rows
LowAssistive; no decisions about people; information within the tool’s ceiling; easily reversedG3 and G5; register entry; standard monitoring
MediumDrafts or analysis a person approves; customer-facing; moderate sensitivityG1, G3, G4 and G5; evaluation suite; quality sampling
HighContributes to decisions about people (for example recruitment); acts within bounds on physical systems; sensitive informationAll five gates; decision records; human review path; executive sign-off
Paragraphs
  • At Wattlegrove the candidate ranking and the SmartFlow scheduling feature are high tier; the chat assistant and forecasting model are medium; Copilot and the coding assistant are low. The candidate ranking goes through the full lifecycle first, as the reference use case.
Assurance lines

Make sure controls are operated, overseen and independently assured.

Draws on
criterion 2.4; criterion 1.5; reassessment

How it is written

  • Three-line table: who, what they do for AI, evidence they produce.
  • Name the first internal audit of AI with its quarter and criteria (the auditors’ published criteria for the edition).
  • Name the health measures the committee watches monthly.

Worked example

Table
Headers
  • Line
  • Who
  • What they do for AI
  • Evidence
Rows
FirstUse-case owners, ITOperate controls: assessments, approvals, logging, haltGate records, approval logs, monitoring
SecondSecurity, privacy and legal, riskSet standards and test that first-line controls operateQuarterly control tests, assessment quality samples
ThirdInternal auditIndependent assurance of the whole modelFirst AI audit in the third quarter of 2027
Paragraphs
  • The committee watches five health measures monthly: register coverage, assessments current, gate decisions recorded before go-live, incidents and near misses reported, and training completion.
Implementation and the ask

Say what must be decided to stand the model up.

Draws on
roadmap.horizons.H1; playbooks.WS-OPM; playbooks.WS-GOV

How it is written

  • Numbered decisions sought, each tied to a first-horizon initiative.
  • Name what the model grows into at Level 4: decision rights in tooling, generated dashboards, internal audit of AI each year.

Worked example

Paragraphs
  • 1. Sign the Chief AI Officer’s delegation, including authority to pause any AI use (I-103).
  • 2. Establish the AI governance committee with the terms of reference attached and retire the working group (I-202).
  • 3. Fund the three-person AI centre of excellence (I-209).
  • 4. Endorse the risk appetite and tier criteria (I-102) and the lifecycle and gates (I-303).
  • 5. Ask the Board Risk and Audit Committee to add AI to its agenda twice a year and to the internal audit plan (I-205).
  • At Level 4 the model grows into approval routing built into tools, a dashboard generated from the register and monitoring, and an internal audit of AI each year.

This assessment is not legal advice and is not a certification. Obligations and dates were checked against official sources on 15 October 2026; confirm them against the source instruments, which can change.