Lesson objective
Identify the decisions that stay with a person at every firm, and connect each one to the professional duty that makes it a human decision.
Plain-language explanation
Why this matters now
Every firm's authority statements will differ in their first two lists. One firm lets an agent file documents into the DMS; another requires a paralegal to approve every move. That variation is healthy, because what is safe to automate depends on the firm's systems, practice and appetite.
The third list is different. There is a core of decisions that no authority statement at any firm should place in "may do alone", and that most firms should keep out of "may propose" too, in the sense that the agent may prepare material but must not frame the decision as a simple approve-or-reject click. These are the reserved decisions. They are reserved not because software is poor at them, although it often is, but because the licence carries the accountability for them and the software carries none.
This lesson names that core so that every design in the rest of the level can refer to it rather than re-arguing it.
A question to sit with
An agent is right about a privilege call ninety-nine times out of a hundred, and faster than any associate. Does that make the decision any less the lawyer's? If not, what exactly is the agent allowed to contribute?
What goes wrong
1. Judgment is disguised as a workflow step. "Classify the inquiry as accept or decline" looks like data handling. It is an engagement decision. Once it sits inside a pipeline, nobody treats it as one.
2. The approval click replaces the decision. An agent recommends that a document is not privileged and a person clicks approve. The person did not review the document. The reserved decision has been made by the agent and signed by a person.
3. A commitment is made in passing. An intake agent tells a prospective client the firm "will be able to help" or quotes a fee range. A matter update tells a client a filing "will be made on Friday". Words like these commit the firm, and nobody with authority chose them.
4. Advice leaks through summaries. A matter summary sent to a client describes "the strongest argument" or "what you should do next". It is advice, and it went out without a lawyer deciding to give it.
5. The agent is the only one who saw it. A reserved decision is made correctly by a person who relied entirely on the agent's account of the underlying material. The person owns a decision based on a summary they could not check.
The practical answer
Start from a firm-wide reserved list. Each authority statement inherits it, and no individual design may move an item off it without a documented decision by the firm's accountable leadership.
| Reserved decision | Why it stays with a person | Professional duty it connects to |
|---|---|---|
| Giving legal advice or a legal opinion to anyone | Advice is the practice of law and carries the lawyer's accountability | Competence; unauthorised practice (ABA Model Rules 1.1, 5.5) |
| Deciding whether to accept or decline a client or matter | It commits the firm and depends on conflicts, competence and judgment | Competence; supervision (1.1, 5.1, 5.3) |
| Setting or changing fee terms | Fees are a matter between lawyer and client under the firm's rules | Fees (1.5) |
| Making a privilege or confidentiality call | An error can waive protection or disclose client information | Confidentiality (1.6) |
| Signing, filing or submitting anything to a court or tribunal | The signer makes representations the software cannot make | Candor toward the tribunal (3.3) |
| Communicating a material development, risk or recommendation to a client | The client is entitled to hear it from a person who can answer questions | Communication (1.4) |
| Committing the firm to a deadline, action or outcome with a third party | It binds the firm and the client | Competence; communication (1.1, 1.4) |
| Deciding whether conduct is permitted | Only a person can take responsibility for that call | Misconduct (8.4) |
Professional rules: the rule numbers above are the ABA Model Rules of Professional Conduct, which are model provisions only. Each jurisdiction adopts its own rules with its own numbering and wording, and some jurisdictions differ in substance. Read the rules of every jurisdiction where the firm practises before relying on this table.
Let the agent contribute, but label the contribution. A reserved decision can be supported by an agent in three ways, and the design should say which.
- Assemble. Gather the documents, dates, names and prior decisions a person needs. The person reads the material, not only the assembly.
- Flag. Point out something a person should consider: a possible conflict, an unusual clause, a document that may be privileged. The flag starts a review; it does not conclude one.
- Draft. Prepare a letter, an engagement document, a filing or a client update for a person to edit, adopt or discard. The draft carries no authority until a person adopts it.
What the agent may not do is present a reserved decision as a pre-made answer awaiting a click. The approval screen for a reserved decision shows the material and the flags, asks the person to decide, and records what they decided and why.
Design the approval so that it cannot be rubber-stamped. Module 7 covers approval gate design in depth; for reserved decisions the minimum is that the approver sees the underlying source, not just the agent's summary; that the record names the approver; and that the approver can decide something other than what the agent suggested without extra effort.
Remember this
- A firm-wide reserved list sits beneath every authority statement: advice, engagement, fees, privilege, filing, material client communication, commitments to third parties, and whether conduct is permitted.
- These decisions are reserved because the licence carries the accountability, not because software is poor at them.
- An agent may assemble, flag and draft for a reserved decision, but never present it as a pre-made answer awaiting a click.
- The approver for a reserved decision sees the source material, is named in the record, and can depart from the agent without extra effort.
- The rule numbers used here are ABA Model Rules; read the adopted rules of your own jurisdiction.
Legal example
The fictional firm Pellbrook & Stone LLP builds a privilege-review workflow for a large fictional commercial dispute. The first design has an agent read each document and set a field to "privileged" or "not privileged". A paralegal reviews a queue of the agent's calls and clicks approve in batches of fifty. In a test run, the paralegal approves 1,200 calls in an afternoon. The automation lead, Tamsin Oyelaran, asks one question at the design review: who decided whether each document was privileged? The paralegal says the agent did and she checked it. On inspection, the approval screen showed the agent's label and a two-line summary, not the document. Nobody had decided anything; a person had signed the agent's decision. The responsible partner, Hollis Marchetti, agrees that privilege calls are on the firm's reserved list and the workflow is redesigned. The agent now does three things. It assembles each document with its metadata, the sender and recipients, and any lawyers it recognises in the distribution. It flags reasons a document may be privileged or may have lost protection, such as a third party copied in. It drafts a one-line privilege log description for documents a reviewer marks privileged. The reviewer's screen opens on the document itself, shows the flags beside it, and has no default selection. Every call records the reviewer's name and whether they agreed with each flag. Review is slower; the paralegal team now completes around 300 documents a day with an associate checking a sample. In the second week an associate notices that the agent never flags documents where in-house counsel of the fictional client used a personal email address, because it did not recognise the address as a lawyer. Under the first design, that pattern would have produced hundreds of approved errors before anyone saw it.
Responsible-use warning
Never build an approval step for a reserved decision that shows the agent's answer and asks a person to confirm it. That design produces a named person, a timestamp and no decision, and it will survive audit until the day it matters. The approver must see the source material, must be able to decide differently without extra effort, and must be recorded as the decision maker. Equally, never move an item off the reserved list because an agent is fast and accurate at it; accuracy makes a good assistant, not a licensed decision maker.
Human-review requirement
The licensed attorney who owns the matter or practice area makes, or directly supervises, every reserved decision, and signs off any workflow that supports one. The reviewer confirms that the workflow keeps the agent to assembling, flagging and drafting; that the approval screen opens on the underlying material rather than a summary; that no default selection nudges the approver; that the record names the decision maker; and that the reserved list has been checked against the adopted conduct rules of each jurisdiction where the firm practises.
Practical exercise
Separate reserved decisions from agent work in a fictional workflow.
- Invent a firm and a workflow in which an agent handles client matter updates from start to finish: reading new documents, summarising them and messaging the client.
- List every decision made anywhere in that workflow, including ones hidden inside wording, such as describing a development as good news.
- Mark each decision that belongs on the reserved list and name the category it falls into.
- For each reserved decision, write what the agent may contribute, using only the words assemble, flag and draft.
- Sketch the approval screen for the most consequential reserved decision. State what the approver sees first, what the flags look like, and whether there is any default selection.
- Write the fields the record captures for that decision, including the reviewer's name and whether they departed from the agent.
- Identify one sentence the agent might write that would commit the firm to something. Rewrite it so it commits nobody.
- Name the rules in your own jurisdiction that correspond to the ABA Model Rules in the lesson table, and note any difference in numbering or substance you find.
- Write a short note to the practice group explaining, in plain language, why the agent in your workflow may assemble, flag and draft but will not decide.
Knowledge check
-
Name at least five decisions on the firm-wide reserved list.
Answer guidance: Giving legal advice; accepting or declining a client or matter; setting or changing fee terms; making a privilege or confidentiality call; signing, filing or submitting to a tribunal; communicating a material development or recommendation to a client; committing the firm to a deadline or outcome with a third party; and deciding whether conduct is permitted.
-
What three contributions may an agent make to a reserved decision?
Answer guidance: It may assemble the material a person needs, flag issues the person should consider, and draft a document for the person to edit, adopt or discard. It may not present the decision itself as a pre-made answer awaiting approval.
-
Why is an approve button beside an agent's answer inadequate for a reserved decision?
Answer guidance: Because it lets a person sign a decision they did not make. Unless the approver sees the source material, can decide differently without extra effort, and is recorded as the decision maker, the agent has in effect made the reserved decision.
-
What caveat applies to the rule numbers in the reserved-decisions table?
Answer guidance: They are ABA Model Rules, which are model provisions only. Each jurisdiction adopts its own rules with its own numbering and wording, sometimes with substantive differences, so the firm must read the adopted rules of every jurisdiction where it practises.
Sources and further reading
- American Bar Association — Model Rules of Professional Conduct. Accessed 2026-09-14.
- American Bar Association Standing Committee on Ethics and Professional Responsibility — Formal Opinion 512: Generative Artificial Intelligence Tools (2024-07-29). Accessed 2026-09-14.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-14.
- OWASP Foundation, OWASP GenAI Security Project — OWASP Top 10 for Agentic Applications for 2026 (2025-12-09). Accessed 2026-09-14.