← Research
Research

How to run a board away day on AI

Half a day or a full day, and four things written down at the end.

Last reviewed: 4 October 2026 · Next review due: 4 October 2027

A board away day on AI works when the board spends most of the day deciding and little of it being presented to. Read and survey before the day, open with one short argument, then work through four lists in order: the decisions machines may make, who can stop each system, what counts as an AI incident, and what management reports each meeting. Put a name and a date against every line before anyone leaves.

A board away day on AI earns its time when the board spends most of the day deciding and the least of it being presented to. The measure of the day is what is written down at the end, and who owns each line.

The answer, in one line

Half a day is enough to produce the four written lists: the decisions machines may make, who can stop each system, what counts as an AI incident, and what management reports each meeting.

Share as a card

Definition#

A board away day on AI is a half or full day, away from the boardroom, in which a board works through the decisions it owns about AI and leaves with them written down: what machines may decide, who can stop each system, what counts as an incident, and what management reports each meeting.

Share this definition as a card

Before the day: reading, a survey and one question#

Most of the value is set up beforehand. Agree the purpose with the chair and the company secretary, then read whatever management has already produced on AI: the policy, the inventory of tools if one exists, the last risk report. Gaps in those papers usually tell you where the day should spend its time.

Send a short anonymous survey to the executive team, one layer below the board. Ask what they can no longer do unaided, who would notice if a system were wrong, how often anyone has overridden one, and what they could still do if it stopped. A board that starts from its own people's answers argues about the business in front of it rather than about AI in general.

Then set one question in the invitation, so that directors arrive having thought about it. A good one names a decision the board owns, such as which decisions in this company a machine should never make.

A running order for half a day#

  1. The argument, twenty minutes. One short case, no product tour: AI reaches judgement before it reaches jobs, and an organisation either designs where human judgement stays or drifts into handing it over.
  2. The decision list, an hour. Which decisions do the company's systems already make or shape, and who approved each one? Most boards find decisions on the list that nobody remembers approving.
  3. A break. Longer than feels necessary. The useful corridor conversation happens here.
  4. The stop list, forty-five minutes. For each system that matters, who can stop it, how long a stop takes, and when it was last rehearsed.
  5. The incident definition, thirty minutes. What counts as an AI incident here, written before there is one, and who is told within what time.
  6. What the board sees, thirty minutes. What management puts in front of the board each meeting from now on, so the other three lists survive past the day.
  7. Owners and dates, fifteen minutes. A name and a date against every line, read back to the room before anyone leaves.

A full day adds two sessions in the afternoon. One reads the survey results in full. The other turns from risk to capability: what the organisation must remain able to do on its own, the record this site calls custody.

The four things the board leaves with#

Short enough to fit on two pages. A record that runs to twenty gets filed and forgotten.

Where away days on AI go wrong#

Too much presentation. A board that listens for four hours leaves informed and undecided. Keep the talking from the front to the first twenty minutes and the read-backs.

A vendor in the room. A demonstration of a product the company might buy turns a governance day into a sales meeting, and directors stop saying what they think.

The introductory talk, again. Most boards have heard what a large language model is. Spending the morning on it pushes the decisions into the last hour, when people are tired.

No owner for the output. If nobody is named against each list, the day produces a pleasant memory and nothing the board can hold management to.

Who should chair it#

The chair of the board can run the day, and some do it well. The difficulty is that the chair also has a view, and the room knows it. An outside chair with no stake in the answer, who sells no software and builds nothing, makes it easier for directors to say the uncomfortable thing. Either way, the person in the chair should be chairing rather than presenting for most of the day.

The away day, designed and chaired. Half a day or a full day, the survey before it, and the four lists written up after. Board away days and briefings.

The dinner the night before. Three courses and one question, so the formal day starts with the argument already had. The board dinner.

Essay · SS-2026-406

Cite this page

Hirji, R. (2026). How to run a board away day on AI. The SuperSkills evidence base, SS-2026-406. https://thesuperskills.com/research/how-to-run-a-board-away-day-on-ai. Last reviewed 4 October 2026.

An evidence review by Rahim Hirji, not peer-reviewed research. For a material claim, cite the underlying study as well; every study here carries its own permanent link.

How citations and IDs work
Questions answered on this page

How long should a board away day on AI be?

Half a day is enough to produce the four written lists: the decisions machines may make, who can stop each system, what counts as an AI incident, and what management reports each meeting. A full day adds time to read an executive survey in full and to turn from risk to capability.

What should a board prepare before an AI away day?

Read what management has already produced on AI, survey the executive team anonymously about what they can no longer do unaided and how often systems are overridden, and set one question in the invitation so directors arrive having thought about it.

What should a board leave an AI away day with?

Four things in writing: the decisions machines may make and who approved each; who can stop each system and how long a stop takes; a definition of an AI incident; and what management reports to the board each meeting. Each line should carry an owner and a date.

Who should chair a board away day on AI?

The board chair can, but an outside chair with no stake in the answer, who sells no software, often makes it easier for directors to say the uncomfortable thing. Whoever chairs should spend most of the day chairing rather than presenting.

What are the common mistakes in a board AI away day?

Too much presentation, a vendor demonstration in the room, repeating the introductory talk the board has already heard, and leaving without an owner against each output.

In this hub

Judgement, oversight and accountability

Who decides, who checks, and who is answerable when the machine was involved.

Ask the evidence
What does the evidence actually show?What should our board be asking about this?Where does Rahim disagree with the consensus?
Bring this into your organisation

If this describes something happening in your teams, say so.

Keynotes, board sessions and advisory work, drawing on research across more than 200 organisations in 30 countries. Tell me the room, the date and the shift you need. A reply within 24 hours.

Start a conversation

Topics and audiences  ·  All research

This argument is one a board usually meets for the first time in the room. There is AI keynote for boards and leadership offsites, and the full range of topics and audiences.

Running a session on this for your board? See what a board briefing on AI should cover and questions for a board dinner on AI.

Box of Amazing

Rahim’s free weekly letter on AI and human capability

If this was useful, the weekly letter is where the thinking happens first. Most of what ends up on this site starts there. Weekly essays on AI, capability and the future of work. Read by 25,000 people, every week since 2017. Free, and one click to stop.

Opens Substack to confirm. No pitch in it, unsubscribe in one click, and nobody follows up because you read something.