ABA Formal Opinion 512, issued in July 2023, is the American Bar Association's first comprehensive guidance on generative AI in legal practice. It runs to twenty-three pages. Most small-firm attorneys have heard of it. Far fewer have read it. And fewer still have connected it to anything their firm is currently doing.

That gap is understandable. Twenty-three pages of ethics guidance is not the first thing that gets opened when a client file is due. But the opinion carries real weight: it applies to every attorney subject to the Model Rules, and it stakes out positions on three obligations that every practicing attorney already has. Competence. Supervision. Confidentiality. Opinion 512 doesn't create new duties. It explains what those existing duties now require in a practice environment where AI tools are available and, in many firms, already in use.

This article covers what the opinion says in each of those three areas and what it means concretely for a small estate practice with one attorney, two paralegals, and a handful of AI tools either actively in use or sitting one click away.

The Three Obligations the Opinion Addresses

Opinion 512 is organized around three Model Rules. Each one existed long before generative AI did. The opinion's work is to extend their application to a new context, not to change the underlying standards.

The Governing Rules
Rule 1.1
Competence

An attorney must provide competent representation, which includes the legal knowledge, skill, thoroughness, and preparation reasonably necessary for the representation. Comment 8 to Rule 1.1 adds that competence requires keeping abreast of changes in the law and its practice, including the benefits and risks associated with relevant technology.

Rule 1.6
Confidentiality

An attorney may not reveal information relating to the representation of a client without informed consent, implied authorization to carry out the representation, or a specific exception. Rule 1.6(c) adds an affirmative obligation: attorneys must make reasonable efforts to prevent the inadvertent or unauthorized disclosure of client information.

Rule 5.3
Supervision

A partner or supervising attorney must make reasonable efforts to ensure that the conduct of nonlawyer assistants is compatible with the professional obligations of the attorney. This obligation applies whether the nonlawyer is a paralegal, a vendor, or, as the opinion now clarifies, an AI tool being used in connection with a matter.

Understanding the opinion requires holding all three rules at once, because they interact. A confidentiality failure caused by a paralegal using an unsanctioned AI tool is simultaneously a Rule 1.6 problem, a Rule 5.3 problem, and, if the attorney didn't understand what the tool does, a Rule 1.1 problem. The opinion's analysis of each rule reinforces the others.

What the Opinion Says About Competence

Opinion 512's treatment of Rule 1.1 makes a claim that some practitioners find uncomfortable: an attorney who uses a generative AI tool without understanding how it works is not competent in its use, and incompetent use of AI in a representation is a Rule 1.1 violation in the same way that incompetent use of any other tool would be.

The opinion does not require attorneys to become engineers. The standard is functional understanding, not technical mastery. An attorney needs to know what the tool does with input, what its known error patterns are, how its output should be verified, and what kinds of tasks it is and isn't suited for. That understanding can be acquired through reading the vendor's documentation, testing the tool on non-client matters, and staying current with bar guidance and legal commentary. It cannot be acquired by simply starting to use the tool and hoping for the best.

The obligation is to understand, not to abstain. Opinion 512 takes no position against AI use. It takes a clear position against uninformed AI use.

The opinion is careful to say that competence doesn't require perfection and doesn't prohibit the use of AI tools that occasionally produce errors. Every tool has failure modes. What it does require is that the attorney understand those failure modes well enough to catch them in the work product before it reaches the client or the court. A tool's confident output is not a substitute for professional judgment. It never has been with any other research tool, and it isn't now.

For a small estate practice, this means having a working understanding of whatever tools the firm uses: what the tool produces, where it tends to go wrong, and what review process is in place to catch errors before they become the client's problem. The attorney who can answer those three questions for each tool in use has a defensible competence position. The attorney who cannot is exposed.

What the Opinion Says About Confidentiality

This is where Opinion 512 has the most direct practical bite for small firms. The opinion holds that submitting client information to a generative AI tool can constitute a disclosure under Rule 1.6, depending on what the tool does with that information, and that attorneys must assess this before using any such tool in connection with a client matter.

The relevant questions the opinion identifies are concrete: Does the tool transmit input to third-party servers? Does the provider retain that input, and for how long? Is the input used to train or improve the model? Who at the provider can access submitted content? Are there contractual protections in place, and if so, what do they actually cover?

Consumer-tier accounts at major AI providers generally cannot answer these questions in ways that satisfy Rule 1.6. The terms of service are written for mass audiences, not professional practices. Data retention defaults have historically favored the provider. And there is typically no contractual relationship between the firm and the provider at all, because the attorney or paralegal signed up individually, not on behalf of the firm.

Consumer Tier vs. Enterprise Tier

Most of the major AI providers offer both a consumer product and an enterprise or business product. The distinction matters significantly for Rule 1.6 purposes. Enterprise products typically include a data processing agreement, explicit commitments about data retention and training exclusions, and a contractual relationship with the subscribing organization. Consumer products typically include none of these things.

A firm that is using the free or personal-subscription version of a major AI tool and telling itself it has addressed confidentiality has not addressed confidentiality. The product tier is the starting point, not an afterthought. Before any AI tool touches a client matter, the firm should know exactly which tier it is on and what the associated data terms are.

The opinion also addresses informed consent as a potential path to compliance. If the attorney obtains the client's informed consent to use a specific AI tool in connection with the matter, the disclosure concern is resolved for that engagement. But the opinion is clear about what informed consent requires: the client must understand which tool is being used, what that tool does with their information, and what the alternatives are. A retainer agreement clause that mentions "technology" in general terms is not informed consent under Rule 1.6. Neither is a verbal acknowledgment that the firm uses AI tools.

For most small estate practices, the practical answer is not to seek consent for every tool on every matter. It is to adopt enterprise-tier products with appropriate data terms, create a clear policy about what information may and may not be submitted, and build that policy into the workflow so that compliance is structural rather than a judgment call made under deadline pressure.

What the Opinion Says About Supervision

Rule 5.3 is where Opinion 512 closes what might otherwise seem like an escape hatch. An attorney who didn't personally submit client information to an AI tool might assume that Rule 1.6 doesn't apply to her. Opinion 512 addresses this directly: the supervising attorney's obligations extend to the AI tools that nonlawyer staff use in connection with the representation.

The opinion draws an analogy to existing supervision obligations. An attorney who supervises a paralegal is responsible for the paralegal's work product under Rule 5.3. If that paralegal uses an AI tool in preparing that work product, the attorney's supervisory obligation covers the tool's use, not just the paralegal's general conduct. This means the attorney cannot discharge her supervision duty by reviewing the final work product alone. She must also ensure that the process by which that work product was generated was consistent with the firm's professional obligations.

In practical terms, this requires three things the opinion identifies explicitly: a policy governing which AI tools may be used and how, training sufficient to ensure that nonlawyer staff understand and follow that policy, and ongoing review mechanisms that are actually used rather than merely existing on paper.

Incident in the Framework Mata v. Avianca · 2023

Attorneys representing a plaintiff in federal court submitted a brief containing citations to cases that did not exist. The citations had been generated by ChatGPT. When opposing counsel and the court could not locate them, the attorneys initially maintained the cases were real and submitted fabricated printouts as verification.

Judge Castel of the Southern District of New York sanctioned both attorneys and their firm. The opinion is worth reading in full for any attorney using AI tools in litigation. Its core holding is simple: signing a filing certifies its accuracy. That certification is not satisfied by trusting the output of a tool you did not adequately supervise. The supervising attorney was sanctioned alongside the attorney who submitted the brief. Rule 5.3 ran both directions.

The Billing Dimension Opinion 512 Also Addresses

One section of Opinion 512 receives less attention than the competence, confidentiality, and supervision holdings, but it is directly relevant to any firm billing by the hour. The opinion applies the reasonableness requirement of Rule 1.5 to AI-assisted work.

The holding is not that AI-assisted work must be billed differently. It is that the reasonableness standard applies regardless of how the work was produced. A fee that would be unreasonable for work done by an attorney remains unreasonable when that work is done or assisted by an AI tool. If AI reduces the time required for a task, the opinion notes, that time reduction is relevant to whether a fee is reasonable. An attorney who bills the same number of hours for a task that took a fraction of the time because AI was used, without any adjustment or disclosure, is in territory the opinion flags as ethically problematic.

The opinion stops short of mandating disclosure of AI use in billing statements. But it frames the reasonableness inquiry in a way that makes unsupported full-rate billing for AI-assisted work difficult to defend if a client ever questions it. The practical takeaway for small firms is to have a deliberate billing policy for AI-assisted work before the first such bill goes out, not after a client raises the issue.

What a Three-Person Estate Practice Should Actually Do

Opinion 512 does not specify what compliance looks like for any particular firm. It sets out the obligations and leaves implementation to professional judgment. For a solo attorney with two paralegals doing estate, trust, and probate work, the following four steps address each of the opinion's three core holdings directly.

  1. Audit the tools currently in use. This means all of them, including tools the paralegals are using on their own initiative. List every AI product that has touched a client matter in the last twelve months, identify the account tier for each, and pull the current data terms. This is the competence baseline the opinion requires: you cannot supervise what you don't know is being used.

  2. Resolve the confidentiality exposure for each tool on the list. For consumer-tier accounts, the options are to upgrade to an enterprise tier with appropriate data terms, restrict use to non-client-matter tasks only, or discontinue use. For any tool that will be used with client information, the firm needs a data processing agreement, explicit retention terms, and an understanding of what the provider does with submitted content. If the provider cannot supply those terms, the tool should not touch client data.

  3. Write a one-page AI usage policy and give it to everyone. The policy needs to cover: which tools are approved, at what tier, for what tasks; what categories of information may not be submitted to any AI tool; what the escalation path is when a staff member is unsure; and how AI-assisted work product is reviewed before it reaches a client. One page is sufficient. The point is that the rule exists in written form, that everyone has seen it, and that there is a date on it.

  4. Build a review step into the workflow for AI-assisted work product. This is the supervision obligation made concrete. AI-generated or AI-assisted drafts should be reviewed by the attorney before they are sent to clients or filed with any tribunal. The review should be documented in the file. "Reviewed and revised" is enough. What it establishes is that supervision was ongoing, not just theoretical.

None of this requires new software, significant time investment, or outside counsel. A three-person practice can complete all four steps in an afternoon. The reason most haven't is not complexity. It is that AI governance reads like a future problem in a practice where every day is already full of present ones.

The Document That Defends You Later

Bar discipline for AI-related conduct is still in its early stages. The first wave of guidance documents, the first wave of opinions, and what will eventually be the first wave of formal discipline are all moving on roughly the same timeline. Small firms that act now are not racing a deadline that has already passed. They are building the file that will matter if a complaint ever arrives.

Opinion 512 is not punitive guidance. It is a framework for practicing competently in an environment that has changed. The attorney who reads it, connects it to her current tools, and makes the four adjustments above is not in compliance because she checked a box. She is in compliance because she did what a competent attorney in 2026 is expected to do: she understood the technology well enough to supervise its use, she protected her clients' information, and she made sure her staff was operating within a structure she could stand behind.

That is what the opinion requires. It is also, not incidentally, what good practice has always required. The technology is new. The obligations are not.