Approved tools and data
Use only firm-approved systems, permissions and data categories.
Legal AI guidance
ABA Formal Opinion 512 applies existing professional duties to generative AI. Your firm's decisions should consider the tool, information and assignment. It is a starting point for counsel's review, not a product endorsement or proof that an AI workflow is compliant.
Custom pricing. Scope and price confirmed in writing.
Legal support outsourcing should begin with role fit. Review the proposed specialist’s education, relevant experience, writing and practical work against the task. LL.B., LL.M., J.D. and paralegal training describe different pathways; they do not establish U.S. attorney licensure.
Use a synthetic exercise that requires source checks and handling an unclear answer. Agree the review owner and permissions before a person or tool receives access.
Explore education and vetting ↗Start with a defined assignment: what comes in, what the system may draft, and who may approve the result. A records index, an internal task suggestion and a client-facing legal answer require different review paths. Write down the boundary before comparing software or requesting a build.
For an initial test, use fictional documents with known answers. Include an unreadable page, a conflicting date and a missing attachment. This is a proposed acceptance exercise, not a claim about a tool's measured accuracy. Keep client information out until counsel and the responsible technical team approve the arrangement.
Opinion 512 does not set one blanket consent rule for every AI use. It addresses informed consent before representation information enters the described self-learning tools that risk disclosure. When consent is required, generic engagement-letter permission is insufficient. The lawyer assesses the facts and other communication duties.
Model Rule 1.6 protects information relating to representation and requires reasonable efforts against unauthorized disclosure or access. Review the actual data path, including uploads, outputs, logs and connected services. A local installation still needs that review.
ABA Formal Opinion 512, confidentiality and communicationABA Model Rule 1.6
Model Rule 1.1 requires competent representation. Rule 3.3 addresses false statements and other duties to a tribunal. A fluent paragraph or working link does not establish that a fact, quotation or authority supports the matter.
For the workflow you approve, specify the evidence a reviewer must inspect: original page, audio segment, matter record or cited authority. Keep extracted text separate from the reviewer's conclusion. If the source is absent or contradictory, return an exception instead of silently completing the gap. Legal analysis, strategy and the final use of an output stay with your attorney.
Formal Opinion 08-451, issued August 5, 2008, addresses outsourcing legal and nonlegal support while the lawyer remains responsible for competent service. It covers supervision, provider diligence, confidentiality, client disclosures and reasonable fees. Outsourcing is not a transfer of professional responsibility.
Model Rule 5.3 addresses nonlawyer supervision. Its commentary includes education, experience and the service arrangement among relevant considerations. Ask how the proposed assistant's training fits the assignment, then review a relevant work sample and the reporting arrangement. A degree title alone does not prove performance on your workflow.
Model Rule 1.4 concerns consultation, keeping clients informed and explaining matters so clients can make informed decisions. Counsel should determine the communication needed for the particular representation.
A useful internal record separates three decisions: the firm's approval of a tool, a client's required disclosure or consent, and an attorney's approval of a specific output. They answer different questions. One checkbox should not stand in for all three.
Model Rule 1.5 prohibits unreasonable legal fees and expenses and addresses communication of their basis. Your attorney sets the firm's client-billing approach.
For procurement, request a written breakdown of software or API charges, the custom build, hosting, maintenance and the human operator. Record the agreed deliverable and acceptance checks. Do not turn a projected reduction in manual steps into guaranteed savings or automatically pass a vendor price through as a legal fee.
Use a short decision record that your team can actually follow: approved inputs, prohibited inputs, named operator, reviewer, escalation contact, test evidence and release authority. Revisit it when the model, connector, permissions or task changes.
For legal process outsourcing with AI automation, the handoff matters as much as the draft. The person checking a chronology should be able to show the source and explain what remains uncertain. The attorney should receive a reviewable work product, not a hidden chain of automatic decisions.
Use the editable policy worksheet to record your proposed rules and questions for counsel. It includes tool approval, information boundaries, exception handling and a release decision. Complete it for one workflow before extending it across your practice.
An editorial review of this guide is not attorney approval of your deployment. Check controlling state rules, court requirements, client instructions and contractual restrictions with your counsel.
A person remains accountable
Use only firm-approved systems, permissions and data categories.
Label every AI output as a draft and route it to a named human reviewer.
Keep a source link or document/page reference for every extracted fact.
Log missing evidence, conflicting inputs and failed steps. Never silently fill gaps.
AI never makes legal decisions or gives advice. Nothing is sent to a client, court or opposing party without attorney approval.
Remote Legal Team LLC states SOC 2 Type II security. Confirm report scope, period and covered services during diligence; it does not certify every proposed tool or make a workflow automatically compliant.
No. This guide does not treat an ABA opinion as vendor approval, certification or a substitute for your firm's review of the proposed service.
In our service model, the assistant supports the approved workflow as a nonlawyer. Your attorney retains legal judgment and approves advice, filings and external legal work.
No. It is an informational starting point. Your counsel should adapt it to your firm's jurisdictions, client duties, tools and actual work.
Checked October 13, 2026. Product access depends on the current account, plan and configuration.
Informational only, not legal advice. ABA materials are model guidance; controlling jurisdiction and court requirements must be checked by your counsel. Sources checked October 13, 2026.
LET’S PLAN YOUR ORGANIZATION’S SUPPORT
Describe the workflow, approved systems, expected draft output and review owner. We will confirm the scope and custom pricing in writing before work starts.
We’ll discuss relevant education and experience, workload, coverage, commercial terms and your review process.
Describe the workflow, expected outputs, review owner and preferred timing. Business requirements only; do not include confidential documents or personal data. Required fields are marked *. Read our Privacy Policy and Website Terms.
Discuss how does aba opinion 512 apply to my firm's ai?, your team’s workload and the next steps for your organization.