Checklist · Fractional CTO leadership

What your board needs to know about your AI: a CTO's checklist for a briefing that leads to decisions

Most boards now ask about AI, and most AI briefings either drown directors in model names or reassure them with demos. Neither helps them govern. A good briefing tells the board where AI is used, what it costs, how it could fail, which rules apply and which decisions are theirs. This is the checklist I use, built on the frameworks regulators and auditors increasingly expect, and it fits on a few pages.

ChecklistSumanta Mukhopadhyay8 min read6 sources
#leadership#governance#ai
CHECKLIST · CHECKLIST · FRACTIONAL CTO LEADERSHIP15 Nov 2026 · 21:20 GST

Why most AI briefings fail

Boards do not need to understand transformers. They need to know whether AI is creating value, what could go wrong, whether management has it under control and what they must decide. Briefings fail when they answer a different question: technical detail directors cannot judge, or optimistic demos that hide risk. The fix is a consistent structure, repeated every time, so directors can see change over time.

Established frameworks help. The NIST AI Risk Management Framework organises the work into governing, mapping, measuring and managing AI risk1, and ISO/IEC 42001 sets out requirements for an AI management system2. You do not need certification to borrow their structure; it gives directors and auditors a vocabulary they will increasingly recognise.

Decide
Board decisionsappetite, investment, red lines
Assure
Risks and controlsIncidents and near missesRules by market
Understand
Inventorywhere AI is usedValue and costSuppliers
Build from understanding to assurance to decisions. Most briefings stop at the bottom layer.

The checklist

1. An inventory of AI in use. One page listing each significant use: what it does, who uses it, whether customers see it, what data it touches and who owns it. Include AI inside bought software, not only what you build. If you cannot produce this page, that is the first finding.

2. Value and cost. For each major use, what it costs (models, infrastructure, people) and what it returns, in the board's terms: revenue, cost avoided, time saved, risk reduced. Show trends, not just a snapshot. Telemetry recording model, tokens and outcome per call makes this possible6.

Dashboard chart of gen_ai.client.token.usage over time with filters for operation, provider, requested model, response model and token type
The raw data behind a board's cost line: usage by model and provider, summarised into cost per use case. Source: OpenTelemetry blog, James Newton-King · CC BY 4.0

3. The top risks and how they are controlled. Five or six risks at most, each with its controls and how you know they work: wrong or harmful outputs, data exposure, agents acting beyond their scope, supplier failure, bias in decisions about people, and cost overruns. Say plainly which are under control and which are not.

4. Supplier dependence. Which model and infrastructure providers you rely on, what you send them, and how quickly you could move. Recent breaches at AI providers, and outages at major platforms, make this a board-level question; see AI inference providers are supply chain.

5. Rules by market. Which laws apply where you operate: the EU AI Act's obligations, including AI literacy for staff4; new national regimes such as Australia's planned rules for frontier developers5; data protection and sector rules. Show what is in force, what is coming and what you are doing about each.

6. Incidents and near misses. What went wrong since the last briefing, including near misses, and what changed as a result. A briefing with no incidents usually means incidents are not being recorded.

7. Principles and red lines. What the company will not do with AI, aligned with widely accepted principles such as the OECD's on transparency, robustness and accountability3. Directors should approve these, not just note them.

8. Decisions for the board. End with specific asks: approve a risk appetite statement, fund a capability, accept or reject a risk, agree a red line. A briefing without a decision is an update, and boards stop reading updates.

A one-page format

SectionWhat goes in itSignal to watch
InventoryUses, owners, data, customer-facing or notNew uses appearing without review
Value and costCost and return per major useCost rising faster than value
RisksTop risks, controls, statusRisks stuck at "not controlled"
SuppliersKey providers, data shared, exit timeSingle points of failure
RulesLaws by market, deadlines, actionsDeadlines without owners
IncidentsWhat happened, what changedNo incidents reported at all
DecisionsSpecific asks of the boardDecisions deferred repeatedly

Boards govern what they can see. Give them the same few pages every time, with trends, red flags and a decision, and they will govern AI as well as they govern anything else.

How to build it the first time

Week 1Inventory
  • Survey teams
  • Check bought software
  • Name owners
Week 2Numbers
  • Costs per use
  • Value evidence
  • Supplier list
Week 3Risks and rules
  • Top risks and controls
  • Laws by market
  • Incident log
Week 4Brief
  • Draft decisions
  • Pre-brief the chair
  • Present and record
About a month of part-time work the first time; much less once the data is routinely collected.

Pre-brief the chair and any director with a technology or risk background before the meeting. It improves the questions you get and avoids surprises. Afterwards, record the decisions and fold them into the next briefing.

CTO take

AI governance is not a separate discipline from running a technology function well; it is the same discipline applied to a fast-moving area. The CTO's job is to make AI legible to the board: what it is, what it is worth, what could go wrong and what they need to decide. Doing that well also forces the inventory, cost tracking and risk controls that the organisation needs anyway. See a fractional CTO's first 90 days, AI literacy under the EU AI Act and the AI governance programme case study.

How I can help

I help leadership teams build AI inventories, risk controls and board reporting that lead to decisions, as part of fractional CTO engagements. I am based in India, the United States and the UAE, working globally. See fractional CTO work, where I work, or analyse your challenge and bring the result to a call.

References
  1. 1
  2. 2
  3. 3
    OECD AI PrinciplesOECD · 2024
  4. 4
  5. 5
    New Australian AI safety and security protectionsPrime Minister of Australia · 10 Nov 2026
  6. 6
FAQ

Common questions

What should a board AI briefing include?

An inventory of where AI is used, what it costs and returns, the main risks and how they are controlled, which suppliers you depend on, which laws apply in your markets, recent incidents, and the specific decisions the board needs to make.

Which frameworks help structure AI governance for a board?

The NIST AI Risk Management Framework and ISO/IEC 42001 for AI management systems are widely used. They give a shared vocabulary for governing, mapping, measuring and managing AI risk.

How often should a board be briefed on AI?

A short update at each regular board meeting and a fuller review once or twice a year is a sensible default, with immediate briefing after any serious AI incident or major change in regulation.

Keep reading

Related

Open to advisory, fractional CTO & select builds

Let's talk about what you're building.

The fastest route is a free 30-minute call. Prefer to write? Send a message and I'll reply personally within two business days.

Start a conversation

How would you like to reach me?

Book a 30-min callFastest. Pick any open slot on my calendar.→ Write in GmailOpens a pre-filled draft in your browser.→ Use my email appOutlook, Apple Mail or your default client.→

I reply personally within two business days. Time zones from the Americas and Europe to the Middle East and Asia-Pacific.