Concern 923 · Working draft · editorial review in progress

Reporting lines for AI risk

Unclear AI risk reporting lines allow important problems to fall between teams or remain unresolved because nobody knows who can decide.

Understanding the concern

Security may examine attacks, privacy staff may examine personal data and operational teams may examine service quality. A single AI incident can involve all three. If each team assumes another is responsible, the organization can delay action or give conflicting instructions.

NIST's governance framework calls for clear roles and communication. Think of a leaking pipe between two departments: an organization chart is useful only if someone can authorize the repair. Teams need a shared escalation route and a named decision-maker for cross-cutting issues. The right arrangement can vary, but responsibility should be understandable to the person who first notices a problem.

An example

Staff report an AI data leak to several teams, and each redirects it without anyone taking ownership.

Illustrative unless identified as a documented case.

Words in plain English

AI
Software that learns patterns from examples or uses rules to perform tasks such as recognizing images or generating text. It can make mistakes and does not understand every situation as a person would.

Evidence and its limits

The framework supports clear accountability. It does not prescribe whether every organization must place AI risk under a CIO, risk officer or another named role.

Explore these sources in the library →
Broader frameworks and background

These resources provide context. They do not establish every claim in this concern.

A question to discuss

Who coordinates this issue across teams, and who has authority to make the final decision?

Keep track of different views, what needs checking, and any next step in your own discussion notes.

Open discussion notes →
Principles for the conversation

Before you finish · reflect together

Virtues and principles to consider

Virtues are qualities we practice in how we treat people and make choices. They are not scores for judging someone. Use these ideas to explore what a thoughtful response could look like.

Trustworthiness

Trustworthiness means giving people good reasons to rely on you. It grows when promises, actions, and evidence line up. With AI, a friendly voice or a famous brand is not enough: people need to know what was checked and what could still go wrong.

In practice, keep promises small enough to test, record mistakes, and tell people when the tool's limits affect them. If a service promises human review, make sure a person really has time and authority to review it.

Ask together: What would give the people affected a sound reason to trust this use?

Stewardship

Stewardship means caring for resources and systems that others depend on, including people who will use them later. It looks beyond the benefit of a quick launch.

Plan for maintenance, energy use, data protection, and eventual shutdown. Ask who will look after the tool when the original team moves on and how future users can avoid inheriting hidden costs.

Ask together: What are we responsible for caring for over time?

Prudence

Prudence means using careful judgment before and during action. It balances worthwhile opportunities with the need to avoid harm that could have been anticipated.

Start with a limited trial, set stopping points, and prefer choices that can be undone when uncertainty is high. Review what happens rather than assuming the original plan remains sound.

Ask together: What is a careful next step, and when should we stop or change course?

Editorial ratings

These are editorial judgments from the register, not measured probabilities or predictions about your situation.

Severity
Serious · 3/5
Likelihood
Widely observed · 4/5
Time horizon
Now
Register risk score
12
About the register and scoring →
More ways to explore

Search for more writing

For more specific or recent material, open a search below or ask for a web summary. AI-generated summaries can contain mistakes; open the original articles to check them.

Explore a proposed use of AI →