Legal AI

Legal AI failures — contract review and legal-document agent mistakes

30 patterns

Legal AI failures — contract review and legal-document agent mistakes. We've tracked 30 distinct Legal AI patterns across production AI agent deployments — most commonly in Legal Contracts systems. One recurring example: Contract Amendment Tracking Failure — Contract Modified Multiple Times; Model Analyzes Original, Ignoring Amendments; Outdated Analysis Given

Each pattern below documents the specific failure mode, why it happens, and how teams have mitigated it in practice — use this page as a reference when building guardrails, writing evals, or debugging an agent that's already misbehaving in this way.

Embedding Retrieval Applies Wrong Jurisdiction's Clause Template by Name Similarity

Frequency:Common
Category:Legal Contracts

A Drafting Agent Asked to Insert a Jurisdiction-Specific Clause (a Non-Compete, a Consumer-Arbitration Provision, a Statutory Notice) for a Contract Governed by One State or Country's Law Retrieves the Clause From a Multi-Jurisdiction Template Library Using Semantic Similarity Over the Clause's General Subject Matter, Rather Than Matching Strictly on Governing Jurisdiction, and Pulls a Differently-Jurisdictioned Template That Is Lexically Almost Identical but Legally Ineffective or Unenforceable Under the Contract's Actual Governing Law

Embedding Retrieval Applies Wrong Jurisdiction's Disclosure Template by Name Similarity

Frequency:Occasional
Category:Legal Contracts

A Compliance Agent Assembling a Required Regulatory Disclosure for a Filing Retrieves the Applicable Disclosure Template From a Multi-Jurisdiction Template Library Using Semantic Similarity Over the Regulation's Name and Subject Matter, Rather Than Matching on the Controlling Jurisdiction Itself, and Pulls a Template Built for a Differently Named but Substantively Different Regulatory Regime in Another Jurisdiction That Happens to Share Closely Overlapping Terminology

Embedding Retrieval Pulls Generic OSS License as IP Assignment Template

Frequency:Occasional
Category:Legal Contracts

A Contract-Drafting Agent's RAG Step, Asked to Retrieve the Company's Standard Work-for-Hire IP-Assignment Template for a New Contractor Agreement, Retrieves a Lexically and Semantically Similar but Substantively Different Document -- An Open-Source Contributor License Agreement or Inbound-IP Template -- Because Both Documents Share Dense "Intellectual Property," "Assignment," and "License Grant" Vocabulary

Embedding-Retrieval Pulls Wrong Clause Version from Template Library

Frequency:Common
Category:Legal Contracts

A Contract-Drafting Agent's RAG Step, Used to Pull the Firm's or Company's Approved Boilerplate Clause for a Given Section (Limitation of Liability, Indemnification, Governing Law) from the Template Library, Retrieves a Lexically Similar but Superseded or Jurisdiction-Wrong Version of the Clause, and the Drafted Contract Is Issued with the Wrong Terms

Embedding Retrieval Surfaces Similarly Named, Unrelated Subsidiary in Corporate-Structure Chart

Frequency:Occasional
Category:Legal Contracts

A Due-Diligence Agent Building a Target Company's Corporate-Structure Chart From Filings and Registry Data, Using Semantic Similarity Search to Match Entity Names Across Documents, Merges or Links a Subsidiary Into the Target's Structure Based on Name Similarity Alone, When the Matched Entity Is in Fact an Unrelated Company With a Coincidentally Similar Name

Multi-Agent Handoff Drops Field-of-Use Limitation Between Clearance Agent and Licensing Agent

Frequency:Occasional
Category:Legal Contracts

An IP-Clearance Agent That Reviews an Inbound License and Determines, in Its Own Narrative Analysis, That the Granted Right Is Limited to a Specific Field of Use or Product Line Hands Off Its Finding to a Downstream Licensing Agent Through a Structured "Rights Cleared: Yes/No" Field That Has No Place to Carry the Field-of-Use Limitation, So the Licensing Agent Treats the Right as Cleared for Any Use

Multi-Agent Handoff Drops Flagged Risk Between Review and Summary Agent

Frequency:Occasional
Category:Legal Contracts

A Document-Review Agent in a Multi-Stage Due-Diligence Pipeline Identifies a Material Risk (a Change-of-Control Clause, an Undisclosed Litigation Reference, a Non-Standard Indemnification Carve-Out) Only in Its Own Free-Text Annotation of the Reviewed Document, and a Downstream Summary Agent That Generates the Diligence Memo from a Structured Findings List Never Sees It

Multi-Agent Handoff Drops Jurisdiction-Specific Exception Between Compliance-Review and Filing Agent

Frequency:Occasional
Category:Legal Contracts

A Compliance-Review Agent That Determines, in Its Own Narrative Analysis, That a Filing Qualifies for a Jurisdiction-Specific Exception to a General Disclosure Requirement Hands Off to a Filing Agent Through a Structured Checklist That Has No Field for the Exception, So the Filing Agent Applies the General Requirement the Exception Was Meant to Override

Multi-Agent Handoff Drops Negotiated Deviation Between Redline Agent and Final-Assembly Agent

Frequency:Occasional
Category:Legal Contracts

A Redlining Agent That Negotiates a Deal-Specific Deviation From Standard Contract Terms in Its Own Turn-by-Turn Conversation With Counterparty Counsel Hands Off the Negotiated Document to a Separate Final-Assembly Agent Through a Structured "Accepted Clause Set" Record That Captures Only the Clause IDs Used, Not the Specific Negotiated Variable Within Each Clause, So the Assembly Agent Reinserts the Clause's Standard Default Variable Instead of the Negotiated One

Rendered Export Not Verified Against Edited Clause Text

Frequency:Occasional
Category:Legal Contracts

A Contract-Drafting Agent Edits a Clause Correctly in the Working Draft, Reports the Edit as Applied, and Sends the Document for Signature Without Verifying That the Final Rendered/Exported Document Actually Reflects the Edited Text Rather Than a Stale Merge Artifact

Unverified Clearance Opinion Filed Without Checking Cited Clause Against Source Agreement

Frequency:Occasional
Category:Legal Contracts

An IP-Clearance Agent Asked to Confirm a Company Holds Sufficient Rights to Use a Third-Party Asset (a Licensed Image, a Vendor-Supplied Code Library, a Co-Developed Patent Disclosure) Generates a Clearance Opinion That Quotes a Specific License Clause as Granting the Needed Right, Then Autonomously Files or Releases That Opinion to the Requesting Team Without Re-Reading the Actual Source License Text It Just Cited to Confirm the Quoted Clause Says What the Opinion Claims It Says