ABA Formal Opinion 512 is no longer new. It was issued on July 29, 2024, and by now it has become the baseline ethics reference point for lawyers evaluating generative AI. That makes it more useful, not less useful. The novelty has worn off. What remains is the harder question: what does the opinion actually require from the systems lawyers use in practice?
Most commentary on Opinion 512 treated it as a warning label for lawyers using generative AI. That was always too narrow. The opinion is better read as a systems-design document.
The ABA did not say lawyers must avoid AI. It said lawyers remain responsible for competent representation, protection of client information, communication with clients when appropriate, supervision, candor, and reasonable fees when AI is part of the work. Those are not abstract principles. They imply design requirements.
If a legal AI system is going to be used in real practice, it has to make those duties easier to satisfy rather than harder to satisfy.
What Opinion 512 Actually Covers
Formal Opinion 512 addresses six familiar professional duties in the context of generative AI:
- competence
- confidentiality
- communication
- candor toward tribunals
- supervisory responsibilities
- reasonable fees and expenses
That matters because the opinion is not limited to one failure mode. It is not just about fake citations or first-wave chatbot mistakes. It is about whether the surrounding workflow makes a lawyer able to use AI responsibly at all.
The official opinion is here:
The Common Misread
The lazy reading of Opinion 512 was: be careful with ChatGPT.
The better reading is: if AI is going to touch client work, the system needs enforceable boundaries around how that work is produced, reviewed, verified, and billed.
That is the difference between a novelty tool and a professional system.
What 512 Means Architecturally
Once you read the opinion through a systems lens, several design requirements fall out quickly.
1. Competence requires reviewable output, not black-box automation
Opinion 512 makes clear that lawyers cannot rely on AI output they do not understand or review. That means a legal AI system cannot be built around the idea that the model knows best.
In practice, competent use of legal AI requires:
- visible source context
- clear task boundaries
- outputs that can be inspected and edited
- workflow states that distinguish draft from final work
If the system encourages silent acceptance of output, it pushes the lawyer away from competence rather than toward it.
2. Confidentiality means scoped retrieval and disciplined data handling
The opinion does not prohibit hosted AI services. It does require lawyers to understand how client information is handled and to use reasonable safeguards.
For product architecture, that points toward:
- bounded retrieval instead of broad, open-ended corpus access
- firm-scoped storage and retrieval paths
- provider controls and contract terms that match the sensitivity of the work
- deliberate rules about what information is sent to a model at all
The practical question is not whether a tool says it is secure. The practical question is whether the system limits what gets loaded into each run and keeps client data inside a controlled retrieval boundary.
3. Supervision requires visible provenance
Opinion 512 reinforces that lawyers remain responsible for the work. That means the system should make review and supervision easier, not harder.
A legal AI system should be able to show:
- what task ran
- what information was retrieved
- what output was produced
- what the human changed
- what was ultimately approved or rejected
Without that, supervision becomes thin and hard to defend. A supervising attorney cannot meaningfully supervise a process the system does not expose.
4. Candor requires approval boundaries before external effect
One of the clearest implications of the opinion is that externally effective legal work should not move from generation to use without human review.
That does not only mean briefs filed in court. It also includes the broader set of outputs that can materially affect a matter:
- court filings
- legal correspondence
- factual summaries used in advocacy
- citations and authorities presented as reliable
The architecture implication is straightforward: draft state and externally effective state should not be the same thing.
5. Fees require billing clarity
Opinion 512 also addresses billing. Lawyers cannot disguise AI efficiency as mystery time, and they cannot pass through unreasonable AI expenses without justification.
That points toward systems that make AI-assisted work more legible:
- what was automated
- what was reviewed
- what was edited
- what the actual cost boundary was
This is not just an accounting question. It is part of the ethics of using the tool.
What 512 Does Not Require
The opinion does not require:
- avoiding AI entirely
- local-only models in every case
- custom model training
- a ban on hosted providers
What it requires is reasonableness, judgment, and safeguards matched to the actual use.
That is an important distinction. Too much legal AI commentary treats the issue as model selection. The harder and more important question is system design.
The Real Buyer Question
When a firm evaluates legal AI, draft quality is only part of the picture.
What matters just as much is the surrounding control surface:
- what happens before the draft is created
- what information reaches the system
- what review boundary exists before the work has legal effect
- what a partner or supervising attorney can actually see
- how the tool supports ethical billing and client communication
Those are architecture questions. They determine whether the product fits legal practice or merely imitates it.
Why This Matters
The next generation of legal AI will not be judged only by output quality. It will be judged by whether the surrounding system lets a lawyer use it competently, supervise it, protect client information, explain it, and bill for it ethically.
That is why Opinion 512 still matters. It is not merely an early warning about mistakes. It remains the clearest ABA statement of what legal AI systems will be expected to support when they are used in real practice.
The firms that take that seriously will buy differently. The companies that take it seriously will build differently.