ABA Formal Opinion 512, Explained: The Six Duties and the Small-Firm Moves That Satisfy Them

ABA Formal Opinion 512, issued July 29, 2024 by the ABA Standing Committee on Ethics and Professional Responsibility, is the ABA's first formal ethics opinion on generative AI. It creates no new rules. It maps six existing duties onto AI use: competence (Rule 1.1), confidentiality (Rule 1.6), communication (Rule 1.4), candor and meritorious claims (Rules 3.1, 3.3, 8.4(c)), supervision (Rules 5.1 and 5.3), and reasonable fees (Rule 1.5).

Most coverage of it is BigLaw client alerts and academic summaries. Neither tells a three-lawyer firm what to do on Monday morning. Here is each duty's actual position, quoted from the text, and the move that satisfies it at small-firm scale.

What is ABA Formal Opinion 512?

Its summary paragraph sets the frame: lawyers using generative AI "must fully consider their applicable ethical obligations," including the duties "to provide competent legal representation, to protect client information, to communicate with clients, to supervise their employees and agents, to advance only meritorious claims and contentions, to ensure candor toward the tribunal, and to charge reasonable fees."

Note what it does not say. It does not prohibit AI use or treat it as presumptively suspect; that threshold question was settled before 512 arrived, as we cover in can lawyers use AI for legal research. The Committee is candid that it "offers general guidance" and expects to update it as the tools develop.

Is ABA Formal Opinion 512 binding?

No. The Model Rules are a template; no lawyer is licensed under them. Your state's version governs, your state bar issues its own ethics opinions, and discipline runs through both.

It would be a mistake to relax. The state AI opinions before it (Florida's 24-1, Pennsylvania and Philadelphia's Joint Opinion 2024-200, West Virginia's 24-01) and the wave since, such as Oregon's Formal Opinion 2025-205, work the same ground. When a disciplinary panel in a state without its own AI opinion reaches for persuasive authority, 512 is what it reaches for. Treat it as the floor, then check what your state has added. Utah practitioners can start with our Utah AI ethics guide.

The six duties at a glance

Duty 1 — Competence (Rule 1.1): understand the tool, own the output

The standard is attainable: "lawyers need not become GAI experts." What Rule 1.1 demands is "a reasonable understanding of the capabilities and limitations of the specific GAI technology that the lawyer might use." The Committee adds a warning: "This is not a static undertaking."

The hard edge is on delegation. Lawyers "may not abdicate their responsibilities by relying solely on a GAI tool to perform tasks that call for the exercise of professional judgment." A draft or an analysis can start with the tool. Responsibility cannot. Whatever level of review the lawyer selects, "the lawyer is fully responsible for the work on behalf of the client."

The small-firm move: name the tools your firm uses, the specific products, not "AI." For each, read a serious account of what it does well and where it fails, then test it against a matter you already know cold. Calendar a quarterly recheck; a 2024 understanding does not cover a 2026 tool.

Duty 2 — Confidentiality (Rule 1.6): consent before client information goes in

This is the section with teeth. Before inputting anything relating to a representation into an AI tool, a lawyer "must evaluate the risks that the information will be disclosed to or accessed by others outside the firm," and to people inside the firm who should not see it. For self-learning tools, the ones that can surface what users feed them, the Committee's conclusion is flat: "a client's informed consent is required prior to inputting information relating to the representation into such a GAI tool." The Committee ties that conclusion to today's tools and allows that it may change as they do.

The consent has to mean something. The client needs the lawyer's best judgment on why the tool is being used, the specific risks, and the benefits, and "merely adding general, boiler-plate provisions to engagement letters purporting to authorize the lawyer to use GAI is not sufficient." The diligence floor: "all lawyers should read and understand the Terms of Use, privacy policy, and related contractual terms and policies" of any tool they use, or consult someone who has. Uses that involve no information relating to the representation, such as general idea generation, need no consent at all.

The small-firm move: sort every AI tool the firm touches into two lists: tools that may see client information, and tools that never do. A consumer chatbot on default settings belongs on the second list; we explain why in can I upload client documents to ChatGPT. Architecture matters here. CaseRead keeps each firm's documents in the firm's own isolated database schema; your data stays yours and trains nothing shared. Be clear-eyed, though: a tool can support your Rule 1.6 duties; it can never discharge them.

Duty 3 — Communication (Rule 1.4): when you must tell the client

The opinion refuses a blanket rule. "The facts of each case will determine" whether Rule 1.4 requires disclosure, it says, and client disclosure "may be unnecessary" depending on the circumstances. That is more forgiving than most summaries suggest.

But the opinion names five situations where disclosure is required: when the client asks how the work was done; when the engagement agreement or outside counsel guidelines require it; before information relating to the representation goes into a self-learning tool; when AI use is relevant to the basis or reasonableness of the fee; and when the tool's output "will influence a significant decision in the representation." The opinion's examples: evaluating potential litigation outcomes and jury selection. The list is not exhaustive, and the Committee says so. Underneath all five: clients are entitled to know whether they are getting your judgment or a model's.

The small-firm move: put a short, specific AI paragraph in your engagement letter; the opinion calls the engagement agreement "a logical place" for these disclosures. Then honor the simplest rule in the opinion: when a client asks, answer honestly.

Duty 4 — Candor (Rules 3.1, 3.3, 8.4(c)): verify everything you file

Rule 3.3 forbids knowingly making false statements to a tribunal and requires correcting material ones already made. Rule 8.4(c) reaches further: "Even an unintentional misstatement to a court can involve a misrepresentation under Rule 8.4(c)." So "output from a GAI tool must be carefully reviewed to ensure that the assertions made to the court are not false." The failures already on record, in the opinion's words: "citations to nonexistent opinions, inaccurate analysis of authority, and use of misleading arguments."

None of that is hypothetical. In Mata v. Avianca, Judge Castel of the Southern District of New York sanctioned two lawyers and their firm $5,000 on June 22, 2023, for a brief built on fabricated cases, and courts have kept sanctioning the same failure since; our Rule 11 sanctions guide tracks the docket. The opinion's own footnotes cite the Stanford study that found leading legal research companies' GAI systems "hallucinate between 17% and 33% of the time."

The small-firm move: make verification a step in the workflow: before anything AI-assisted is filed, every citation gets checked for existence and support. CaseRead's Hallucination Shield does the mechanical half free. Paste the draft and it checks each citation it finds (up to 25 per run) against real court data, flagging anything that does not exist or does not say what the brief claims. The judgment half stays with the lawyer whose name is on the signature block.

Duty 5 — Supervision (Rules 5.1 and 5.3): a policy and training, in writing

In a three-lawyer firm, you are the managerial lawyer these rules address. The opinion is direct: "Managerial lawyers must establish clear policies regarding the law firm's permissible use of GAI," and supervisors must make reasonable efforts to see that lawyers and staff comply. Training is part of the duty; the opinion suggests it cover the basics of the technology, each tool's capabilities and limits, and "best practices for secure data handling, privacy, and confidentiality." The outsourcing rules reach AI vendors too: vet security and retention terms before relying on one. One footnoted suggestion worth stealing: mark AI-produced materials as such in the client file.

The small-firm move: write the policy. One page covers a small firm: approved tools, which list each sits on, the pre-filing verification step, the engagement-letter language, and who answers questions. Our law firm AI policy guide turns each duty into policy language you can adopt. Then hold one training hour, paralegal and assistant included, because Rule 5.3 makes their AI use your responsibility.

Duty 6 — Fees (Rule 1.5): bill your time, not the machine's

The principle comes from 1993 and ABA Formal Opinion 93-379; Opinion 512 applies it without flinching: hourly lawyers "must bill for their actual time." The example is concrete. If a tool lets you draft a pleading with 15 minutes of input, you bill the 15 minutes plus your review time. Not the three hours the pleading used to take. The logic reaches flat fees: "it may be unreasonable under Rule 1.5 for the lawyer to charge the same flat fee when using the GAI tool as when not using it."

Two more rules with dollar signs. A lawyer "may not charge a client to learn about how to use a GAI tool" the lawyer will use regularly; the exception is a client who requests an unfamiliar tool and agrees to the billing in advance. And a tool that functions like office equipment is overhead, while a per-use charge incurred for one client's matter can ordinarily pass through at actual cost.

The small-firm move: bill AI-assisted work as what it is, prompting time plus review time, and put your approach in the engagement letter before it becomes a dispute. The full mechanics are in billing for AI-assisted work.

The Monday-morning compliance checklist

Every item maps to a duty the opinion articulates. A small firm can finish the list in a week.

• Competence: List approved AI tools by name. Test each against a matter you know. Put a quarterly recheck on the calendar.
• Confidentiality: Read each tool's data-handling terms. Sort tools into "may see client information" and "never." Draft specific consent language for any self-learning tool that will touch matter information.
• Communication: Add an AI paragraph to your engagement letter. Decide now what you will say when a client asks.
• Candor: Make pre-filing citation verification a required step. Run every AI-touched draft through the free Hallucination Shield.
• Supervision: Write the one-page policy (template walkthrough here). Hold one training hour, staff included. Mark AI-generated documents in the file.
• Fees: Bill actual time only. Don't bill learning time for tools you'll use across your practice. Reprice flat fees AI has made materially cheaper to deliver.

The duties in Opinion 512 are the ones you have practiced under your whole career. The opinion insists you keep honoring them with a faster pencil in your hand. If part of compliance is choosing tools built for these duties rather than retrofitted to them, that is CaseRead: the AI associate that knows your matter. It searches your firm's files and the public law together, keeps your documents in your firm's own isolated schema, and flags what it cannot verify rather than asserting it.

Frequently asked questions

Is ABA Formal Opinion 512 binding? No. ABA formal opinions interpret the Model Rules of Professional Conduct, and the Model Rules are a template: no lawyer is licensed under them. Your state adopts its own version of the rules, and discipline runs through those state rules and your state bar's own guidance. Opinion 512 is persuasive authority that disciplinary bodies and courts read closely, and many state AI opinions track its reasoning, so the prudent move is to treat it as the floor for your practice.

Do I need client consent to use AI under ABA Formal Opinion 512? Sometimes. Opinion 512 concludes that because many of today's self-learning generative AI tools could surface what a lawyer inputs, "a client's informed consent is required prior to inputting information relating to the representation into such a GAI tool." The consent must be specific; the opinion says boilerplate AI provisions in an engagement letter are not sufficient. If no information relating to the representation goes in, such as pure idea generation, consent is not required.

When does a lawyer have to tell a client they are using AI? Under Opinion 512, disclosure is fact-dependent and sometimes unnecessary. You must disclose when the client asks how the work was done, when the engagement agreement or outside counsel guidelines require it, before inputting information relating to the representation into a self-learning tool, when AI use is relevant to the fee, and when the tool's output will influence a significant decision in the representation, such as evaluating potential litigation outcomes or jury selection. The list is not exhaustive; the opinion says the facts of each case control.

Can lawyers bill clients for time spent using AI? Yes, for actual time only. Opinion 512 says hourly lawyers "must bill for their actual time": the minutes spent prompting the tool and the time spent reviewing its output. You may not bill for the hours the tool saved you, and you may not charge clients for time spent learning a tool you will use regularly across your practice. The exception: a client who explicitly requests a specific unfamiliar tool may agree, in advance, to pay for the lawyer's ramp-up.

Has the ABA issued another AI ethics opinion since Opinion 512? No. As of August 2026, Formal Opinion 512 remains the ABA's only formal ethics opinion devoted to generative AI; the formal opinions issued since address other subjects, and the Committee itself anticipates updated guidance as the technology develops. The AI activity has come from the states, including Oregon's Formal Opinion 2025-205 on artificial intelligence tools, so check your own jurisdiction's guidance alongside 512.