Who Is Accountable When AI Gets It Wrong

The email that went out on Tuesday

An account manager on your team is drafting a quarterly summary for a client. She pastes her notes into an AI assistant, asks for a tidy two paragraph update, skims the result, likes it, and sends it. Buried in the second paragraph is a figure saying spend is down eleven percent. It is not. Spend is up four percent. The assistant produced a plausible number because plausible numbers are what it produces when it does not have the real one.

The client replies three days later, politely confused. Now somebody has to answer for it.

Ask a room who is accountable and you get four answers. The person who sent it. Her manager. Whoever approved the tool. The tool itself, or the vendor behind it. Only one of those holds up.

The person who sends it owns it

This is the spine of every workable AI policy, and it is worth saying out loud in plain words to your team: the person who sends it owns it.

Not because it is harsh, but because it is the only version that survives contact with reality. Your client has no relationship with a piece of software. They have a relationship with your company and with the person whose name is on the message. When they ask why the figure was wrong, "the AI wrote it" is not an answer, it is an admission that nobody checked.

Accountability cannot be delegated to a tool, and it is worth understanding why the delegation is impossible rather than merely discouraged. To delegate responsibility you need something that can accept it: something that can be questioned, corrected, sanctioned, or asked to put it right. A model is none of those things. It has no standing, no memory of your client, and no stake in the outcome. So the responsibility never moves. It stays exactly where it was.

Where the manager does come in

Saying the sender owns it does not let leaders off. The sender owns the individual output. You own the conditions.

If your team has never been told which tools are approved, never been told what may not be pasted in, and never been told that figures must be verified against source, then a wrong figure is a system failure wearing an individual's name badge. Fix the conditions and individual ownership becomes fair. Skip the conditions and it becomes scapegoating, which your team will notice immediately and never forget.

What reasonable care looks like

Reasonable care is not reading everything twice. It is a short, specific list applied to the things that actually go wrong.

Verify every number against its source. Check every name and title. Confirm any commitment, date or deadline the draft makes on your behalf. Check any claim about what your company does or will do. Then read the whole thing once as the recipient rather than as the author.

That is five checks and it takes about ninety seconds on a short email. It would have caught the eleven percent.

Draft a [client email / internal update] using ONLY the notes below.
Rules:

Do not add any figure, percentage, date or name that is not in the notes.
Where something is missing, write TO CONFIRM in square brackets.
Do not make any commitment on my behalf.
At the end, list every factual claim you made and which note it came from.
Notes:
[paste your notes]

Running the incident, not the blame

When something does go wrong, the useful sequence is dull. Correct it with the recipient quickly and plainly. Work out which of the five checks would have caught it. Ask whether the person had ever been told to do that check. Then decide whether this is a one off or a pattern.

Here is what happened:
[what went out, to whom, what was wrong, how it was spotted]
Help me structure a short, no blame review. Cover:

What the specific error was, in one sentence
Which single check would have caught it before it went out
Whether the person had been clearly told to do that check
One change to how we work that would prevent a repeat
What we should say to the recipient
Keep it under 200 words. Do not speculate about anyone's intent.

Read the draft below as if you were the recipient.
List, as bullet points only:

Every number, percentage or amount, so I can verify each against source
Every person or company name and title
Every date, deadline or commitment it makes on my behalf
Every claim about what my company does or will do
Do not rewrite the draft. Do not comment on the tone. Just produce the checklist.
Draft:
[paste the draft]

That last prompt is the one to put in front of your team this week. It turns an abstract principle into ninety seconds of specific work, and specific work is the only kind that actually gets done.