> For the complete documentation index, see [llms.txt](https://help.cubelet.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cubelet.ai/the-review-board.md).

# The Review Board

*Put a real document in front of a panel of AI reviewers, get a written record of where they agree and disagree, then meet them out loud.*

The Review Board is different from everything else in this Help Center. Everywhere else, you practise against a fictional Case. Here you bring **your own document** — a policy, a contract, an AI system description — and a panel reads it and files positions on it.

You are not the learner in this room. You are the **convener**: the person who called the meeting. The panel addresses you by name and waits for you to run it.

![One issue from a finished dossier: the panel is split, three reviewers oppose and one raises concerns, each quoting the passage of the document they are reacting to.](https://pub-b341f5dd338c47ffa088178d54291c95.r2.dev/help-center/v2/review-board-dossier.png)

## What happens, in order

1. **Convene.** Upload the document, choose who sits on the panel, and click **Convene the board**.
2. **Prep runs.** Every reviewer reads the document and files a position on each issue it raises. This takes a few minutes.
3. **Read the dossier.** A written record of every issue: who supports it, who objects, and the exact passage each reviewer is reacting to.
4. **Share the link.** Once prep finishes you get a meeting link you can send to anyone.
5. **Meet.** Join a live voice meeting with the panel. Afterwards the minutes stay on the board.

## Who sits on the panel

Two seats are **always** filled, whatever else you choose:

* **Conrad** — the chair. He synthesises across frameworks, gives a plain-language read of what the document does, and keeps the meeting moving.
* **Ms. Morgan** — a CISO and Chief AI Officer who has watched frameworks fail in practice. Her register is: "That's the textbook answer — what happens in practice?"

Then you add **jurisdiction counsel** — reviewers who read your document through one specific rulebook. Four are built in, and all four cover AI governance.

| Counsel              | Reads your document as                                                                                                  | Weighs what this person would care about                                                  |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Henry Reyes**      | TRAIGA — Texas AI governance obligations for developers and deployers of high-risk AI systems, effective 1 January 2026 | A General Counsel facing $200K per violation                                              |
| **Eden Roos**        | The EU AI Act — risk-tiered obligations for organizations deploying AI in the EU                                        | A Chief Compliance Officer facing €30M / 6%-of-revenue fines and loss of EU market access |
| **Clarkson Okonkwo** | The NIST AI Risk Management Framework — GOVERN, MAP, MEASURE and MANAGE                                                 | A Chief Risk Officer accountable for organizational AI trust                              |
| **Clive Lloyd**      | ISO/IEC 42001 — Annex A/B controls and clauses 4–10                                                                     | A board pursuing ISO 42001 certification                                                  |

If you need a seat these four don't cover, you can [build your own](/the-review-board/build-your-own-panelist.md).

## The one rule every reviewer follows

**Cite the document, or say nothing.** Every panelist — built-in or one you built — is instructed to quote the passage it is reacting to. If a point can't be tied to something actually written in your document, the panelist drops the point rather than asserting it.

That is why a dossier sometimes comes back shorter than you expected. A short dossier means your document gave the panel little to hold onto, not that the panel was lazy.

{% hint style="info" %}
**Access.** The Review Board is an Experiments feature. If your account has experimental access you'll see **The Review Board** in the left sidebar under **Experiments** — that means the internal experiments flag, or a paid plan at Consulting Partner or above. Without it, the page sends you back to Home. See **Plans & upgrades**.
{% endhint %}

## In this section

* [Convene a board](/the-review-board/convene-a-board.md) — upload a document and choose the panel.
* [Reading the dossier](/the-review-board/reading-the-dossier.md) — stances, severity, citations, and what "the panel is split" means.
* [Holding the meeting](/the-review-board/holding-the-meeting.md) — the share link, the lobby, the call, and the minutes.
* [Build your own panelist](/the-review-board/build-your-own-panelist.md) — the bench: your own reviewer, bound to one domain.