Full profile
The practical question in law and artificial intelligence is no longer whether lawyers may use AI. They already are. The harder question is whether a firm can explain, before a judge or client asks, who used the tool, what went into it, what came out of it, who checked it, and how the client was charged for the work.
That is the AI ethics stack in 2026: a national professional-responsibility floor, state-level variation that changes the answer in material ways, and an enforcement record that has moved from embarrassing correction orders to sanctions, disqualification, and bar referral. None of those layers creates a separate AI ethics universe. They apply familiar duties to a tool that can make familiar mistakes faster and harder to spot.

The Baseline: ABA Formal Opinion 512
ABA Formal Opinion 512, issued in July 2024, is the cleanest national starting point because it does not treat generative AI as a regulatory blank slate. It maps AI use onto existing Model Rules: competence, confidentiality, supervision, candor, communication, and fees.[1] For a fuller rule-by-rule treatment, see What the ABA and State Bars Require of Lawyers Using AI.
The opinion’s competence analysis matters because it puts AI into the same practical bucket as other legal technology: lawyers must understand the benefits and risks enough to use it responsibly, not become software engineers. The confidentiality analysis is more operational. A lawyer who enters client information into an AI system has to make reasonable efforts to prevent inadvertent or unauthorized disclosure, which means vendor terms, data retention, training use, access controls, and security cannot be left to whoever first opened an account.[1]
The supervision point is equally important. If a junior lawyer, paralegal, contract attorney, or nonlawyer staff member uses AI in client work, the supervising lawyer still owns the professional-responsibility problem. Formal Opinion 512 treats AI-assisted work by nonlawyers as nonlawyer assistance requiring supervision under Rule 5.3, not as some autonomous process outside the chain of responsibility.[1]
Candor is where the opinion becomes less abstract. A false citation, invented quotation, or unsupported legal proposition does not become less false because a model produced it. Good-faith reliance on a tool may explain how the error occurred, but it does not convert an unverified filing into a responsible one. The duty to the tribunal remains with the lawyer who signs, files, or advocates from the work product.[1]
Fees complete the baseline. Under Rule 1.5, fees must remain reasonable, and clients may need to be told when AI materially affects the basis for billing. The national answer is not that AI time is automatically billable or automatically nonbillable. The answer is that lawyers cannot use AI efficiency to obscure what work was actually performed, what value was delivered, or what the fee agreement permits.[1]
Why the ABA Floor Is Not Enough
A national framework is useful for training, but firms do not practice in a national abstract. They practice before particular courts, for particular clients, under particular engagement letters, with lawyers admitted in particular jurisdictions. That is where the state opinions become more than footnotes.
The fee issue shows the problem most clearly. Florida Opinion 24-1 says any fee increase attributable to AI efficiency gains must be disclosed to the client, and that “the client should benefit from the efficiency.” Texas Opinion 705 similarly expects AI efficiency savings to be passed to clients as a benefit. Virginia LEO 1901 takes a different route, stating that clients should be charged based on “the value of the output, not the time saved.” California’s practical guidance takes a more functional approach, emphasizing competence and communication while deferring specific fee treatment. NYC Bar Opinion 2024-5 requires disclosure of material AI use to clients and defines material use as any use that could reasonably affect client decision-making.[2][3]
| Jurisdiction or source | Fee and disclosure posture described in the research materials | Operational consequence |
|---|---|---|
| ABA Formal Opinion 512 | Fees must be reasonable; clients must be advised when AI affects billing. | Engagement letters and billing narratives should not hide AI-driven changes in work or cost. |
| Florida Opinion 24-1 | Fee increases attributable to AI efficiency gains must be disclosed; the client should benefit from the efficiency. | A firm needs a way to identify whether AI changed the fee basis or generated an efficiency benefit. |
| Texas Opinion 705 | AI efficiency savings should be passed to clients as a benefit. | Billing policies should address savings, not only time entries. |
| Virginia LEO 1901 | Clients should be charged based on the value of the output, not the time saved. | A pure billable-hour control may miss the state’s value-based framing. |
| California practical guidance | Functional focus on competence and communication; specific fee guidance deferred. | Do not assume silence equals permission to ignore fee transparency. |
| NYC Bar Opinion 2024-5 | Material AI use must be disclosed when it could reasonably affect client decision-making. | Matter-opening and client-communication practices need a materiality trigger. |
That split is not academic. A single firm policy saying “AI time may be billed if reasonable” may be too thin for Florida or Texas. A policy that treats saved time as the central billing metric may not answer Virginia’s value-of-output framing. A policy that waits for an express client question may miss the NYC Bar’s material-use disclosure trigger. If the firm’s lawyers cross state lines, the compliance answer has to travel with the matter, not with the most convenient opinion.

Texas is a useful example because the issue is concrete enough to put into policy language. A firm tracking Texas matters should not stop at “do not reveal confidential information to AI tools.” It should also ask whether AI changed the cost of producing the work and whether that efficiency was treated as a client benefit. For a focused treatment, see Texas State Bar AI Ethics Opinion 2024.
Adoption Pressure Is Real, but It Is Not a Compliance Program
Industry surveys do show pressure. The 8am/ABA 2026 Legal Industry Report reports 69% AI adoption, while Clio’s 2026 Legal Trends Report reports 79%.[4][5] Those figures should not be averaged into a pretend consensus. They come from different research efforts and likely measure somewhat different populations, behaviors, and definitions of adoption.
Still, they point in the same direction: enough lawyers are using AI that blanket bans are increasingly poor risk controls. A ban that is not enforced usually becomes an invitation to personal accounts, unscreened vendors, copied client facts, and no audit trail. That is not conservatism. It is governance by not knowing.
This is the governance gap many firms now have to close: lawyers are experimenting because the tools save time at the front end, while firm guidance lags behind the actual work. That mismatch is treated in more depth in Personal AI Use Is Outpacing Firm Governance in Law Practice.
The Sanctions Line Has Become the Enforcement Layer
The sanctions cases are where the ethics stack stops looking like a CLE outline and starts looking like a supervision file. The common failure is not that lawyers used AI. It is that they failed to verify legal authorities, then filed or defended the work as if the tool’s output had been checked.

Mata v. Avianca is the starting point most lawyers remember: a 2023 sanctions order for fabricated citations generated through AI, with a monetary sanction of $5,097.[2] The lasting lesson was not that one lawyer was careless. It was that a court treated unverified AI-generated authority as sanctionable when lawyers put it into a filing.
The line did not stop there. Park v. Kim, in 2024, involved referral of an attorney to the state bar for disciplinary proceedings.[2] That matters because a referral changes the audience. The problem is no longer just the judge managing a bad filing. It becomes a professional discipline issue, with all the collateral consequences that follow for the lawyer, the firm, and the client relationship.
By 2025, the monetary consequences reported in the research materials were larger. Lacey v. State Farm is described as involving a $31,000 sanction, with the court linking the sanction amount to the duty to verify regardless of the tool used. Couvrette v. Wisnovsky is described as involving $110,000 in sanctions, fees, and related monetary consequences, although that figure should be treated carefully because it combines categories and warrants review of the primary order for exact attribution.[2]
Johnson v. Dunn, in 2026, is the escalation point that should get management attention: disqualification from ongoing representation plus referral to the bar.[2] Disqualification is not just a lawyer discipline problem. It can disrupt the client’s litigation strategy, force replacement counsel to get up to speed, create fee disputes, and require the firm to explain why a tool-assisted workstream became a case-management event.
| Case | Reported consequence | Compliance significance |
|---|---|---|
| Mata v. Avianca, 2023 | $5,097 sanction | AI-hallucinated citations became a sanctions problem, not merely a drafting mistake. |
| Park v. Kim, 2024 | Bar referral | Courts signaled that disciplinary channels may be appropriate. |
| Lacey v. State Farm, 2025 | $31,000 sanction | The duty to verify applied regardless of the tool used. |
| Couvrette v. Wisnovsky, 2025 | $110,000 in sanctions, fees, and related monetary consequences | The monetary exposure reported in the research materials became materially larger; attribution should be checked against the primary order. |
| Johnson v. Dunn, 2026 | Disqualification plus bar referral | The consequence reached ongoing representation, not only after-the-fact punishment. |
Clio’s 2026 guide cites researchers tracking more than 955 U.S. cases and more than 1,400 globally involving AI hallucinations, with more than 128 lawyers identified, including lawyers from top-tier firms.[5] That count should be used with care because the underlying tracking methodology is not independently verified from the Clio page. It is still a useful directional signal: hallucination is not confined to solo practitioners, unsophisticated users, or obsolete tools.
For lawyers new to the terminology, a hallucination is not a quirky label for a harmless typo. In legal work, it can mean an invented case, a distorted holding, a false quotation, or a real citation attached to a proposition the case does not support. The relevant professional act is verification, not surprise.
What a Firm Policy Has to Be Able to Answer
A usable AI policy does not need to be long. It does need to be specific enough that a lawyer can apply it at 10 p.m. before filing, and a risk officer can audit it two months later. The best policies answer four questions: what tools may be used, what information may be entered, what work must be verified, and when the client or court must be told.
A traffic-light policy is a simple way to start because it sorts behavior before a crisis. The GC AI framework describes green, yellow, and red uses as a practical policy artifact, and that format works because it gives lawyers a decision path instead of a lecture.[2]
| Category | Typical treatment | Examples of policy questions |
|---|---|---|
| Green | Permitted under standard safeguards | Is the tool approved? Is confidential information excluded or protected? Is output reviewed before use? |
| Yellow | Permitted with approval or additional controls | Will client information be entered? Will the output affect legal advice, billing, or a filing? Is client disclosure required? |
| Red | Prohibited absent a specific exception | Does the use expose privileged material to an unapproved system? Does it generate authority for filing without human verification? Does it impersonate client or court communications? |
The value of the traffic-light model is not the color coding. It is the forced classification. A lawyer who wants to paste a deposition transcript into a public AI tool should not have to infer the answer from a twelve-page policy on innovation. The policy should tell that lawyer whether the action is prohibited, whether an approved secure tool exists, and who can authorize an exception.
Vendor Review Belongs in the Ethics File
Vendor diligence is not a procurement nicety when client information, privileged work product, or litigation strategy may enter the system. ABA Formal Opinion 512’s confidentiality analysis makes reasonable efforts the lawyer’s duty, and in practice those efforts often run through vendor review.[1]
- Confidentiality: what data the vendor receives, who can access it, and whether it may be used to train or improve models.
- Security: encryption, access controls, incident response, audit logs, and administrative permissions.
- Retention and deletion: how long prompts, files, outputs, and metadata are kept, and whether deletion can be verified.
- Contract terms: confidentiality commitments, data-processing terms, jurisdictional issues, subcontractors, and remedies.
- Auditability: whether the firm can reconstruct tool use if a client, court, insurer, or disciplinary authority asks.
The vendor does not have to be perfect. The firm does have to know what risk it accepted. A lawyer should not discover during a sanctions motion that no one knows whether the tool stored the prompt, used it for training, or can produce usage logs.
Prompt, Verify, Audit
The practical protocol that connects the ethics opinions to the sanctions cases is Prompt, Verify, Audit. GC AI describes this as a three-part framework: use precise prompts with source requirements, cross-check every AI-generated citation and legal proposition, and maintain a documented record of AI tool use that can survive later review.[2]
Prompt
Prompting is not a substitute for legal judgment, but sloppy prompting creates avoidable cleanup. A usable prompt tells the tool the jurisdiction, date sensitivity, procedural posture, requested format, and source expectations. If the tool cannot provide authorities that can be checked in primary sources, the output should be treated as brainstorming or drafting support, not as research ready for citation.
For example, a research prompt can require the tool to separate binding authority, persuasive authority, and background commentary. That structure will not make the output reliable by itself. It will make review less chaotic, which matters when a supervising lawyer has to see quickly whether the associate checked the right layer of law.
Verify
Verification is the part that deserves the most discipline because it is the part courts keep finding missing. Every AI-generated citation should be checked in a reliable legal research database or primary source. The case must exist. The reporter citation must match. The quoted language must appear where represented. The holding must support the proposition. Negative treatment must be checked. Jurisdiction and date must be confirmed.
- Open each cited authority outside the AI tool.
- Confirm the citation, court, date, and procedural posture.
- Read the relevant passage, not only the headnote or summary.
- Check whether the quoted text is exact and whether any ellipsis changes meaning.
- Confirm the authority still supports the proposition after updating and negative-treatment review.
- Record who verified the authority and when, at least for filings and client-facing legal analysis.
This protocol should apply whether the output came from a general-purpose model, a legal AI product, a retrieval-augmented generation system, or an agentic workflow. Better architecture may reduce some risks; it does not move the professional duty from the lawyer to the software. For definitions of terms such as RAG and agentic AI, see the glossary.
Audit
Audit does not mean saving every experimental prompt forever. It means keeping enough record to reconstruct material AI use when the work affects client advice, billing, discovery, negotiations, or a court filing. The record can be simple: tool used, date, user, matter, general purpose, whether confidential information was entered, verification completed, and any required disclosure made.
Corporate Compliance Insights describes a 90-day implementation timeline for AI risk controls in 2026.[6] That is a useful planning horizon for a firm that is not starting from scratch: inventory tools, classify uses, approve vendors, issue interim guidance, train lawyers on verification, and set an audit cadence. The point is not to produce a beautiful policy binder. The point is to reduce the amount of remedial lawyering needed after someone files a bad citation or bills a client for unexplained AI-assisted work.
Disclosure Triggers Need to Be Written Down
Disclosure is one of the easiest places for firms to drift because the word can mean several things: disclosure to a client, disclosure to a court, disclosure to opposing counsel, or internal disclosure to a supervising lawyer. A policy that simply says “disclose when required” is not much help.
Client disclosure should be tied to materiality, confidentiality, billing, and the client’s instructions. If AI use could reasonably affect the client’s decision-making, the NYC Bar guidance described in the research materials would treat that as material.[3] If AI changes the fee basis or creates efficiency savings, Florida, Texas, Virginia, and the ABA framework may push the analysis in different directions.[1][2][3] If a client has prohibited certain tools or requires notice, the engagement terms control the operational answer.
Court disclosure is different. Some courts have standing orders or local rules addressing AI use; others do not. Even where no AI-specific disclosure rule applies, candor and Rule 11-type obligations still require the lawyer to ensure that filed material is accurate and supportable. The absence of a checkbox on the filing system is not permission to outsource verification.
The Malpractice Question Should Be Kept in Its Lane
There is a growing argument that lawyers may eventually face malpractice claims for failing to use AI where a reasonable lawyer would have used it. That is a plausible future issue, especially if tools become standard for certain review, research, or drafting tasks. But the research materials identify no malpractice case, as of mid-2026, based solely on failure to use AI. Predictions of such claims within one to five years are professional opinion, not precedent.[6]
For current governance, the more immediate risk is not that every lawyer must use AI on every suitable task. It is that lawyers who do use AI must remain competent, candid, confidential, supervised, and fair in billing. That is the risk with a sanctions record behind it.
A Readiness Test for 2026
A firm does not need a perfect AI governance system before any lawyer can use a tool. It does need a maintained system that can answer basic questions without convening an emergency committee.
- Can lawyers identify which AI tools are approved for client work and which are prohibited?
- Can they tell whether client confidential information may be entered into each approved tool?
- Does the firm have jurisdiction-aware guidance for fees, efficiency savings, value billing, and material AI-use disclosure?
- Is every AI-generated legal authority in a filing independently verified before submission?
- Can supervising lawyers see who used the tool, what role it played, and what review occurred?
- Can billing personnel and relationship lawyers explain AI-assisted work consistently with the engagement letter and applicable ethics guidance?
Those are not innovation questions. They are professional-responsibility questions with a technology interface. Lawyers do not need a separate AI ethics universe. They need a maintained way to apply existing duties across tools, jurisdictions, vendors, bills, and filings.
References
- ABA Formal Opinion 512. American Bar Association. July 2024.
- AI Legal Ethics in 2026: 6 Cases, 4 Rules, 1 Policy Template. GC AI.
- Legal Ethics and Practical Considerations for Business Lawyers Using AI in Modern Legal Practice. ABA Business Law Today. July 2026.
- 2026 Legal Industry Report. 8am / ABA. 2026.
- AI Legal Compliance for Law Firms: Complete 2026 Guide. Clio. 2026.
- AI Risk in 2026: 3 Critical Changes for the General Counsel. Corporate Compliance Insights.
Comments
Join the discussion with an anonymous comment.