Who owns the mistake when AI gets it wrong

Regulators and courts have not created a separate "AI defense" or "AI liability shield." The existing standard of care still applies: a professional is expected to exercise the same competence whether they used AI or not. The American Bar Association's Formal Opinion 512 (2024) on generative AI made this explicit for lawyers: competence, confidentiality, and supervision duties apply fully to AI-assisted work. Expect equivalent guidance from accounting bodies (AICPA) and actuarial and valuation associations to keep tightening through 2026.

Mapping the liability chain

When something goes wrong, four parties can be in the liability chain, and firms should mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → this before deployment, not after an incident.

1. The firm and the signing professional. Malpractice claims target the person or firm who delivered the opinion, filing, or valuation, regardless of what tool produced the draft. Signing off means owning it.

2. The AI vendor. Contracts with vendors like Microsoft (Copilot), Thomson Reuters (CoCounsel), or Workiva typically disclaim liability for output accuracy through terms of service. Vendors sell "assistive" tools, not opinions.

3. The client, if they misused the tool themselves or ignored disclosed limitations.

4. Insurers, whose professional indemnity (errors and omissions, E&O) policies increasingly ask explicit questions about AI use during underwriting.

The practical result: liability defaults back to the firm almost every time. Vendor disclaimers are broad and largely untested but generally enforceable for tool-level errors. This means the firm's internal controls, not the AI vendor's promises, are the real risk mitigant.

The human sign-off: what actually counts as one

"A human reviewed it" is not a defense on its own. Regulators and courts are starting to ask for evidence of *meaningful* review. Build sign-off around three tests:

• Traceability: can the reviewer see what the AI generated versus what a human added or changed?
• Independent verification: were citations, figures, or calculations checked against a primary source, not just checked for plausibility?
• Competence to catch the error: was the reviewer senior enough, and given enough time, to actually catch the class of error the tool is known to make?

A partner glancing at a 40-page AI-drafted valuation report for five minutes before signing does not meet this bar. A structured checklist tied to specific known failure modes (numerical fabricationfabricationA hallucination is when an AI model generates output that is fluent and confident but factually wrong, fabricated, or unsupported by its source data.View full definition →, outdated regulatory citations, mismatched comparables in a valuation) does.

The documentation trail: what to keep

If a claim arises two years later, the firm needs to reconstruct exactly what happened. Minimum documentation:

• Which AI tool and model version was used (model versions change silently; GPT-4 outputs in 2024 differ from GPT-4o or later versions).
• What prompt or input was given.
• The raw AI output, unedited.
• What the human reviewer changed and why.
• Who signed off and on what date.

This kind of audit log turns "we used AI" from a liability admission into evidence of a controlled process. The EU's AI Act (Regulation 2024/1689), which began phasing in through 2025 and 2026, pushes in the same direction for "high-risk" AI systems: it requires documentation, logging, and human oversight capable of intervening, particularly relevant for AI used in credit, employment, or legal-adjacent decisions that some professional services touch.

The insurance conversation

Professional indemnity insurers have moved fast. By 2025, major E&O underwriters (including specialty insurers like Beazley and Chubb) were adding explicit AI-use questionnaires to renewal applications, asking:

• Do you use generative AI in client deliverables?
• Do you have a policy governing AI use and human review?
• Have you had any AI-related incidents or near-misses?

Firms that answer vaguely or admit to no policy risk higher premiums or exclusions. A firm with documented guardrails (this lesson's checklist, essentially) is a materially better underwriting risk. Some insurers, per industry commentary from brokers like Marsh, are starting to treat "no AI governance policy" the way they once treated "no cybersecurity policy": a red flag that triggers higher scrutiny or surcharge.

Practical move: before renewal, get the firm's actual AI use inventoried and put a one-page governance policy in front of the broker. It changes the negotiating position.

Guardrails to run before deployment

A pre-deployment checklist, adaptable across audit, tax, legal, actuarial, and valuation work:

1. Classify the use case by risk. Drafting an internal summary is low risk. Generating numbers that go into a signed valuation report is high risk. Apply proportionally heavier review to the latter.

2. Restrict which tasks AI can touch unsupervised. No AI-generated legal citation, financial figure, or regulatory reference goes to a client without independent verification against a primary source.

3. Version-lock and log the model. Know exactly which model version produced which output; models get updated and behavior shifts without warning.

4. Train reviewers on known failure modes, not general AI literacy. A tax reviewer needs to know AI tools fabricate IRS revenue ruling numbers; a valuation reviewer needs to know AI tools misapply comparable-company multiples.

5. Define the sign-off chain in writing, naming who is accountable at each stage, before the engagement starts, not after a problem surfaces.

6. Loop in the insurer and general counsel on any new high-risk AI use case before, not after, rollout.

For a broader regulatory grounding, the NIST AI Risk Management Framework (US, voluntary but widely referenced) is a solid free baseline for structuring exactly this kind of guardrail program.

🎬 [VIDEO: "AI and the Law: Liability, Ethics, and Legal Risks" - youtube.com - a walkthrough of real sanctioned cases where generative AI produced fabricated legal citations, and what courts required afterward]

Key Takeaways

• Liability defaults to the firm and the signing professional; AI vendor disclaimers do not transfer accountability for the final professional opinion.
• Existing standards of care already apply to AI-assisted work (see ABA Formal Opinion 512, 2024); there is no separate, lighter "AI made the mistake" defense.
• A defensible human sign-off requires traceability, independent verification against primary sources, and a reviewer competent enough to catch known AI failure modes, not a cursory glance.
• Keep a documentation trail (tool version, prompt, raw output, edits, reviewer, date) so an incident two years later can be reconstructed and defended.
• Treat the insurance conversation proactively: insurers are already pricing AI governance into professional indemnity underwriting, and a written policy improves the firm's negotiating position.