Your AI Risk Register Is Furniture. Boards Read Dollars, Not Threats.

Most enterprise AI risk registers are dead documents. Created during an annual compliance cycle, padded with vague threats like "model bias" and "data leakage," scored on a 1-5 matrix nobody calibrated, filed in a SharePoint folder the board will never open.

The gap is not awareness. It is language. Technical teams write for technical audiences. Boards want three answers: what could break, what it would cost, what we are doing about it. A register that does not answer those three in financial terms becomes furniture — present in the room, ignored by everyone at the table.

This is the rebuild. A register that scores AI risk in the language a board operates in, maps it to regulatory obligations that actually apply to your systems, and draws a hard line between security theater and operational risk management.

What we got wrong the first time: completeness. We catalogued 41 entries across 18 systems before we ever brought it to leadership. The board spent 45 minutes debating whether "hallucination risk" and "model accuracy degradation" were distinct, then walked out without approving a dollar of mitigation budget. Version two had five entries. Each one carried a dollar range and a named executive. The next meeting ran 20 minutes and produced three budget decisions.

Roughly 72% of board members report feeling inadequately informed about AI-specific risks — even at organizations that maintain formal registers.^[5] The disconnect is structural. The information exists. It is unreadable to the audience that has to act on it.

Technical teams document risks as attack vectors, model architectures, and failure modes. Boards think in revenue impact, regulatory fines, reputational damage, competitive position. "Adversarial prompt injection may cause unintended model outputs" registers as noise. "A prompt injection on our customer chatbot exposes 200,000 customer records, triggers GDPR Article 83 fines up to 4% of global turnover, and an estimated 15% churn in the affected segment" registers as a decision the board has to make this quarter.

The second failure is granularity. Engineering wants every risk for every model. The board wants the top five things that could materially move the business. A register with forty equally-weighted line items guarantees none of them get attention. Volume is the enemy of action.

The ubiquitous 5x5 likelihood-by-impact grid was built for workplace injuries and supply chain disruptions. Discrete events, observable frequencies, calibrated actuarial data. AI fails all three. Risks compound across systems, depend on context the model cannot see, and stay invisible until the cascade hits production.

Four scoring dimensions map to what boards actually allocate against. Each scores 0-10. Composite is a weighted average and the weights are configurable per organization based on risk appetite and regulatory exposure. The point of the four dimensions is not precision. It is that each one carries a verb the board can act on: write a check, change a vendor, escalate to legal, halt a deployment.

An internal summarization tool and a credit decisioning model do not deserve the same review depth. Treating them the same is how risk programs collapse — engineers route around heavy controls on lightweight tools, and the high-stakes systems hide inside the same checklist as the low-stakes ones.

The EU AI Act codifies this into law: unacceptable, high, limited, minimal.^[4] Even outside EU jurisdiction, the same tiering pattern works. It catches the two failure modes that kill governance programs: over-governing low-risk tools until teams stop using them, and under-governing high-risk systems because nothing flagged them on the way in.

The regulatory landscape moved from advisory to operational. EU AI Act high-risk system requirements became enforceable in August 2025. Full compliance for general-purpose AI systems lands in August 2026.^[4] Organizations selling into the EU cannot treat this as planning material.

The EU is not the only jurisdiction. NIST AI RMF 1.0 is voluntary in the United States but increasingly referenced in procurement and litigation.^[3] ISO/IEC 42001 sets AI management system requirements. Sector regulation layers on top: HIPAA for healthcare AI, SR 11-7 for banking model risk, FDA guidance for AI medical devices.

The register maps each system to the obligations that actually apply to it. Not every system triggers every regulation — and the mapping prevents two expensive mistakes: pouring compliance budget into low-risk systems that do not need it, and missing obligations on high-risk systems until a regulator asks for documentation that does not exist.

Security theater is risk management optimized for the appearance of control instead of the reduction of harm. AI governance is full of it. The field is new, the threats are abstract, most programs are built under regulatory pressure rather than operational scar tissue. Decoration accumulates faster than enforcement.

The test is a single question. Would this activity change the outcome of a real incident? A comprehensive AI ethics policy that nobody reads before deploying a model would not. A bias audit conducted once during development and never repeated after the data distribution shifted would not. A register that catalogues forty risks and triggers zero operational changes would not. All decoration.

Real risk management is boring, repetitive, and specific. Specific metrics for specific systems. Specific tests on specific schedules. Specific actions when specific thresholds breach. It looks worse in a slide deck and runs better in a crisis.

The single most effective lever for board communication is financial translation. Every score maps to an estimated annual loss exposure denominated in the currency the board allocates. The FAIR (Factor Analysis of Information Risk) model decomposes each risk into loss event frequency and loss magnitude and expresses the result as a dollar range.^[6]

A composite score of 7.2 is a number with no frame of reference. The same system expressed as $1.8M-$3.2M in annual loss exposure from bias-related regulatory action, with a 15-25% probability of occurrence in the next 12 months, sits next to every other capital allocation decision the board is making. They are illustrative ranges — calibrate them against your incident history and regulatory context, not industry averages.

The second lever is trend. A single score is a snapshot. Boards allocate against direction. Is the risk increasing or decreasing? Is the mitigation budget actually moving the number? Present scores as time series with quarter-over-quarter deltas. A 6.5 declining from 8.2 over three quarters is a different story than a 6.5 climbing from 4.1. Same number, opposite decision.

The schema is not theoretical. Each field is there because a board member or a regulator will ask for it.

owner forces accountability — without a named executive, nobody escalates. annualLossExposure is a range because risk quantification is probabilistic, and false precision destroys credibility faster than honest uncertainty. trend is the temporal context that turns a static score into a signal worth a meeting.

Populating the register takes about six weeks for a mid-size enterprise. Week one is inventory — every system in production and development. Weeks two and three are tier classification and scoring workshops with engineering, legal, and business in the same room (this is the friction step; remote workshops do not produce calibrated scores). Week four is regulatory mapping with outside counsel where it matters. Weeks five and six are financial translation, where loss estimates get pressure-tested against industry benchmarks and your own incident history. Skip the pressure-test and the numbers fall apart the first time the board asks where they came from.

Dead registers create a dangerous illusion of control. They let leadership believe governance exists because the document exists. The fix is a quarterly cadence with enforced accountability — and the enforcement matters more than the cadence.

Every quarter, each owner presents a five-minute update on their risks to the AI governance committee. Three questions, no slides longer than that: Has the score moved and why? Are mitigations on track? Does this need a board escalation? Any risk above 7.0 with the third answer at yes goes on the next board agenda automatically — the political negotiation about whether something is "important enough" to surface gets removed by the rule.

Between reviews, automated feeds update two fields continuously: incident count touching the system, and performance drift on accuracy or fairness metrics. Either crosses a trigger and an ad-hoc review fires outside the quarterly cycle. The register is a system, not a document.

Board presentations on AI risk follow a strict format. Limited time. Competing priorities. Zero tolerance for transformer architecture explainers. The goal is decision enablement.

Four sections, twenty minutes or less, every time. Anything longer gets cut short or skipped — and a skipped slide is a risk that never made it onto the agenda.

The gap between organizations with real AI governance and those running theater will widen sharply over the next 18 months. Regulators are moving from guidance to enforcement. Boards are moving from curiosity to accountability. The organizations that built real registers — scored in dollars, mapped to regulations, reviewed on cadence, owned by named individuals — will navigate the transition without scrambling.

Start with the five highest-exposure systems. Score them this week. Translate the scores to dollars next week. Present to your governance committee the week after. A rough register that drives decisions beats a perfect register that sits in SharePoint. The board is ready to read it. The question is whether the team is ready to write it in their language.