What is ABA Formal Opinion 512?

Why It Matters

The opinion did something the existing rules had not: it named generative AI directly and worked through what each duty means when a tool produces the first draft. It is not binding on any jurisdiction by itself, but it is the reference point that state bars, firms, and their insurers now reason from.

The framing matters for builders. The opinion treats AI as a technology used to deliver legal services, which puts it inside the same duties as a junior associate, a paralegal, or a research service. Nothing about the tool changes the obligation; it changes what satisfies it.

What It Says

Competence (Rule 1.1). A lawyer needs a reasonable understanding of the tool’s capabilities and limitations. Not expertise in the technology, and not a one-time briefing: the opinion expects that understanding to be maintained as tools change.

Confidentiality (Rule 1.6). Client information is protected regardless of its source, which means a tool that ingests matter documents is a disclosure question before it is a productivity question.

Communication (Rule 1.4). The opinion addresses when a lawyer must tell a client that AI is being used, which turns on the client’s expectations and the significance of the use.

Fees (Rule 1.5). A lawyer may not bill for hours the tool eliminated, and may not charge for time spent learning a tool unless the client specifically requested that tool.

Supervision (Rule 5.3) and candor (Rule 3.3). The duties extend to what subordinates and tools produce, and to what gets filed.

Where It Breaks

Verification is where the opinion is deliberately open. It says the review required “will necessarily depend on the GAI tool and the specific task that it performs”, so a document review demands more independent checking than generating ideas for a memo. That is a sensible rule and an unhelpful instruction: it means a single firm-wide standard cannot cover every deliverable, and someone has to decide per task what verification is enough.

The second break is the gap between a duty and a control. The opinion describes obligations; it does not describe mechanisms. A firm can adopt a policy that restates every rule in the opinion and still have no way to show, for a given deliverable, which claims were checked or who signed. The duties are satisfied by behaviour, and behaviour is only provable through a record.

How Flytebit Handles It

We treat the opinion as a design input rather than a compliance document. Verification runs per claim before the signature, with the flagged and unsupported claims reaching the reviewer alongside their sources, and the decision record captures what was checked and who signed. The fee question is handled by separating AI-assisted time in the same record, which is what makes billing defensible rather than assumed. The industry application is on our Professional Services page, and the control design is our AI governance and risk work.