AI Playbook for Board AI Literacy Briefing
A publicly traded company's board has asked for a 45-minute AI governance briefing before the next quarterly meeting. The board includes two directors with technology backgrounds and four without. The company uses AI in 7 business functions. The board has never formally reviewed AI risk.
When to use this playbook
- Use this playbook when the decision looks like the situation above: A publicly traded company's board has asked for a 45-minute AI governance briefing before the next quarterly meeting.
- It is a fit when you have source files in hand and need a structured, reviewable analysis — not a generic chat answer about "Board AI Literacy Briefing".
- Do not use it as a substitute for licensed, legal, clinical, or authorized official judgment in the domain.
What you'll need
- The company's current AI deployment register (7 functions)
- SEC cybersecurity disclosure rules (applicable to AI risk disclosure)
- Peer company AI risk disclosures in recent 10-K filings
- Recent AI-related regulatory enforcement actions (past 12 months)
- Board meeting agenda and available time: 45 minutes
Attachments: Spreadsheets (Spreadsheets)
The Prompt
You are an AI governance specialist preparing a board AI literacy briefing for a publicly traded company. I am attaching: Work only from the attached source files. If a conclusion is not supported, say so. Produce: 1. Draft the 6-slide briefing structure: what the board needs to understand about AI risk at the company level, not the technology level. 2. Translate each of the 7 AI deployments into plain-language risk statements the board can act on: "If this model fails, here is what happens and who is liable." 3. Identify the AI risk disclosures the company should be making in its 10-K based on peer company precedents and SEC guidance. 4. Define the board's oversight role: what decisions require board approval, what gets delegated to management, and what triggers board notification. 5. Recommend the governance structure: AI oversight committee composition, reporting cadence, and escalation criteria. Call out where independent models are likely to disagree, and list follow-up documents a reviewer should request.
What to expect
- 6-slide board briefing structure with talking points
- Plain-language risk statement for each AI deployment
- 10-K disclosure recommendations
- Board oversight role definition
- Governance structure recommendation
Review before you act
- Validate this output against source files before relying on it: Draft the 6-slide briefing structure: what the board needs to understand about AI risk at the company level, not the technology level.
- Validate this output against source files before relying on it: Translate each of the 7 AI deployments into plain-language risk statements the board can act on: "If this model fails, here is what happens and who is liable.".
- Validate this output against source files before relying on it: Identify the AI risk disclosures the company should be making in its 10-K based on peer company precedents and SEC guidance.
- Validate this output against source files before relying on it: Define the board's oversight role: what decisions require board approval, what gets delegated to management, and what triggers board notification.
- Confirm every cited figure, date, counterparty, or requirement against the attached originals — models compress and can drop a qualifier.
- Treat disagreement between models as a review item, especially on classification, materiality, and recommended next action.
- Do not authorize an operational, clinical, legal, credit, or enforcement action solely because the models agree.
Why compare models on this
For Board AI Literacy Briefing, running the same attachments across independent models is useful because the hard part is classification and completeness, not fluency. The workflow is already designed to surface 6-slide board briefing structure with talking points; plain-language risk statement for each ai deployment; 10-k disclosure recommendations; board oversight role definition. Those are comparison artifacts — they only exist if more than one model runs. Risk-tier assignments and 'high-risk system' calls vary with how a model reads a use-case description. Comparison exposes those classification fights before they reach an exam.
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

