
Business technology resource
What Should Never Be Fully Delegated to a Legal AI Agent?
Legal AI can assist with bounded preparation, but consequential professional judgments and irreversible actions need clearly assigned human responsibility and review.
Delegate preparation, not accountability
The useful question is not whether an AI agent can technically perform an action. It is whether the firm can assign the action, information, consequence, verification, and remedy to an accountable person. Legal work combines factual uncertainty, professional judgment, client objectives, authority, deadlines, and duties that a product cannot assume on the lawyer’s behalf.
An AI system may help collect, compare, classify, draft, calculate, monitor, or propose. It should not become the final decision maker for legal advice, strategy, conflicts, privilege, client disclosure, citation validity, filing, signature, production, sending, deadline satisfaction, settlement authority, or other actions whose error can materially affect a client or tribunal.
Match the gate to the consequence
Human review is meaningful only when the reviewer has the competence, authority, time, sources, and context to detect a bad result. A generic approval button does not establish supervision. Define what the system may prepare, what evidence it must provide, which conditions require escalation, and what the reviewer must independently confirm before authorizing downstream use.
The American Bar Association’s Formal Opinion 512 identifies duties involving competence, confidentiality, client communication, supervision, meritorious claims, candor, and reasonable fees. It also says lawyers cannot rely solely on generative AI for functions requiring personal judgment and remain responsible for client work. Applicable state rules, court orders, client commitments, insurer conditions, and matter circumstances may add stricter requirements.
| Action area | AI may assist with | Human gate |
|---|---|---|
| Advice and strategy | Issue lists, alternatives, draft questions, and source organization | Responsible lawyer determines advice, objectives, and strategy |
| Authority and filings | Research leads, citation tables, draft language, and format checks | Lawyer verifies authority, record support, candor, signature, and filing |
| Client information | Approved processing inside a defined information boundary | Firm determines confidentiality, privilege, disclosure, and permitted use |
| External action | Prepare a message, calendar item, form, or system change | Authorized person confirms recipient, content, timing, and consequence |
Design for interruption and disagreement
Require the system to stop when sources conflict, authority is missing, jurisdiction is uncertain, a deadline cannot be verified, a recipient is ambiguous, restricted information appears, or a requested action exceeds the approved tool scope. A well-designed workflow reports uncertainty and preserves evidence instead of hiding it behind confident prose.
Reviewers must be able to reject, correct, narrow, or rerun the work without pressure to approve automation. Record important overrides and recurring failure patterns. If people routinely click through a gate, the organization should redesign the workload, staffing, interface, or authority rather than treating nominal human involvement as a control.
Increase authority one reversible step at a time
Start in observation, draft, or recommendation mode. Separate retrieving information from changing it, and separate preparing external communication from sending it. Use allowlisted tools, limited destinations, least privilege, transaction previews, explicit confirmation, logging, and rollback where available. Test prohibited and ambiguous requests, not only the happy path.
Some activities may remain permanently human even after strong pilot results because their consequence, professional character, or remedy makes automation inappropriate. This is not a judgment that legal AI lacks value. It is an operating design that places automation where it can reduce routine effort while preserving human responsibility where judgment and accountability matter most.
- Keep advice and strategic choices with the responsible lawyer.
- Verify every material citation against the actual current authority.
- Require named approval before filing, signing, sending, or producing information.
- Do not let automation calculate or satisfy deadlines without independent confirmation.
- Escalate privilege, conflict, disclosure, and client-consent questions to qualified counsel.
- Log consequential approvals, rejected actions, exceptions, and recurring failure patterns.
- Review gate effectiveness when workload, staffing, rules, or product capabilities change.
- Disable action authority when reviewers cannot reliably inspect the proposed result.
Related next steps
Related articles
Continue exploring this topic
Sources and further reading
- American Bar Association: Formal Opinion 512
- South Carolina Judicial Branch: Rule 1.1: Competence
- South Carolina Judicial Branch: Rule 1.6: Confidentiality
This resource provides general business-technology guidance. Engagement scope, evidence, and recommendations depend on the organization’s actual condition.