Board member or executive
You take part in an engagement someone else facilitates: a chair, a director, the CEO, the CRO, the CIO or a member of the AI governance team. The app tells you at each step what is yours to do and refuses anything that is not, which is the point: the record shows who proposed, who decided and who reviewed, and nobody can be said to have done another's part.
What each seat does
| Seat | In AI Board Direction | In AI Risk Appetite and AI Use Assessment |
|---|---|---|
| Director | Completes the B0 briefing (your answers are visible only to you and the facilitator); proposes positions at B2 to B8 | Reads the board view and the board paper |
| Chair | Alone records the resolution at B9 and the board directions in connected mode; decides whether to proceed when directors have not completed the briefing | Receives the board paper: the eight positions in plain words, what changed since last year, what the board is asked to resolve |
| CEO | Confirms the B1 inventory of AI in use (or the technology owner does, where that role is filled); may propose positions | Owns arrangements in the register |
| CRO (regulated mode) | Takes part in B2 to B8 | Proposes the eight appetite decisions; agrees the working appetite within the board's direction (check K11) |
| GC | Alone answers the legal questions raised at any step; agrees the scope; a second approver is needed where the GC also acts as counsel | Answers questions for counsel; sets the privilege position |
| CIO (technology owner) | Confirms each inventory line and each draft measure the AI governance team supplies | Supplies the hand-over of AI in use, evidence and existing assurance; receives scheduled updates; can contest a point on the record |
| AI governance team | Enters and maintains the list of AI in use, what existing policies and thresholds say, and drafts the measures the board will receive | Supplies the hand-over with the technology owner; the same updates and right to contest |
Neither the CIO nor the AI governance team proposes or records a board position, and neither can be the independent reviewer. The CEO seat keeps what it can do today, so an organisation with neither role runs as before.
What to expect
- An invitation by email. Sign-in is a one-time code to your work address; there is no password. Your name, organisation, work email and role are the personal information the app holds about you; it holds no customer, member or client data (see the privacy notice).
- Your actions list. Each app opens on what is waiting for you: a step to complete, a question to answer, a line to confirm, a resolution due. You are reminded by email when something waits.
- The briefing first (directors). B0 is a short briefing built from the matter brief and your sector: AI in plain terms, the obligations in scope, directors' duties as they bear on AI, common failure cases, and a few check questions framed as a check of understanding, not a test. Your completion date is recorded; your answers are not shared with other directors.
- Positions, not policy. At B2 the board records what AI governance should achieve, each goal with an owner and a measure, then its posture by area. The acceptable-use policy, the appetite statement and the action list are generated from those positions; you review the output, you do not draft it.
- Drafts until resolved. Every output says draft until the chair records the resolution. After that, outputs name the version they came from, and a later change starts a new version with the earlier one kept.
Read in this order
- Get started in 10 minutes: Harrow Valley Foods shows the ten steps from a director's side in a quarter of an hour.
- Concepts: roles and separation of duties; modes; versions, drafts and resolutions.
- Frameworks: the method, with its mapping to the AICD/HTI Director's Guide, once published.
- For the CIO and the AI governance team: what they supply and what they read.
If a step refuses something you expected to do, the refusal says why, in the words of the role rules. The facilitator can change roles in set-up; the rules themselves are the method and are the same in every deployment.