Legal AI Operating Essentials

Day 1 · Automation boundaries

Start with the task, not AI

Start with a workflow, not a tool. "Contract review" is too broad. "First-pass review of a customer's contract, from receipt to approved redline" has a trigger, a finish line and an owner.

Split that route into steps. A rule can route a request or fill stable text. Extraction can locate named facts. Generated output can propose language or analysis. A qualified person decides what can be relied on. These steps do not fail in the same way, so they should not share one vague control.

Try this today: write the workflow name, trigger, finish line and one named owner. List the steps in order. For each non-human step, write what happens when it cannot complete safely and who sees the failure.

What good looks like: another lawyer can explain the route and its stop point without seeing a product demonstration.

Day 2 turns confidentiality from a broad warning into an operating boundary people can follow.

Day 2 · Confidentiality boundaries

Set the data boundary first

A warning to protect confidentiality is not yet an operating instruction. People need to know what may enter which service, under whose authority.

Start with green, amber and red. Green covers approved tools and low-risk uses, such as process counts or properly approved fictional material. Amber needs a named supervisor and an approved data route. Red covers material that cannot enter an unapproved service, or any route where retention, training use or deletion is unknown.

Map prompts, uploads, outputs and logs; each supplier and subprocessor; location, retention, model-training use and deletion. The firm and its advisers decide the final boundary.

Try this today: take one proposed use and write one green, amber and red example. If a supplier answer is missing, record the gap rather than guessing.

What good looks like: a colleague can decide whether to proceed, pause or escalate without asking what the policy meant.

Day 3 · Document extraction

Separate extraction from judgement

Generation should not be the first move in a document workflow. Start with a small extraction record.

For each required field, keep the extracted value beside the exact page or clause that supports it. Mark a value as missing or conflicting when the source does not settle it. Useful fields might include parties, dates, defined terms, required clauses and document version. Each field needs an owner and a correction route.

Only then decide whether a later step needs a summary, proposed wording or analysis. The reviewer can check the extracted facts first, then test any proposed conclusion against the source and the firm's own standard.

Try this today: using fictional or approved test material, create five columns: field, value, source, status and correction owner. Do not fill a blank with a plausible answer.

What good looks like: the reviewer can open the source for every material value and correct one field without rerunning the whole workflow.

Day 4 · Verification design

Who approves the output?

"The lawyer checks it" leaves too much undefined. Tool operation, professional review and approval are different jobs.

Name five roles for one workflow. The operator runs the approved task within the data boundary. The reviewer checks the output against the source and legal requirements. The workflow owner measures performance and resolves exceptions. Security or privacy reviews access, processors and incidents. The stop owner can halt use without waiting for a committee. One person may hold several roles, but no role should belong to "the team".

Try this today: put a name beside who may submit material, who checks the source, who approves reliance, who monitors recurring errors and who can stop the route. Add the actual check each person performs.

What good looks like: every output has a qualified review route, allotted review time and a known escalation point.

Day 5 · External processors

What the supplier must answer

A demonstration answers "can the product do something?" It does not answer "can this firm operate it safely and leave it cleanly?"

Write the requirement from the workflow backwards. Ask for retained evidence about the exact service: subprocessors, location, retention, backups, training use, access and incident logs, change notices, export, deletion and credential closure.

Try this today: choose three non-negotiable requirements for one workflow. For each, write the evidence you need, the person who accepts it and the pass or stop condition. Treat a blank supplier answer as a gap, not as permission.

What good looks like: the firm can compare buying and building by their operating obligations, not by the smoothest demonstration.

Day 6 · Turnaround and capacity

Measure the work, not the demo

A faster first output is not the same as a better workflow. Qualified review, corrections, support and queueing still consume capacity.

Freeze five current measures before a test: monthly volume, hands-on lawyer time across every role, elapsed turnaround, corrections or extra review cycles, and write-off or fixed-fee overrun evidence. Keep hands-on time separate from elapsed time, and count the reviewer and support burden rather than treating them as free.

Use a normal month or the next twenty items in sequence. Do not choose memorable successes or failures. Label estimates, retain the source and name the person who accepts the baseline. No client details belong in the worksheet.

Try this today: choose the measurement window and write the source and owner beside each of the five measures.

What good looks like: the same method can be repeated after a change, including review and correction time.

Day 7 · Pilot to operation

End the pilot with a decision

A pilot is complete when it produces a decision, not when the demonstration ends. A useful pilot can fail.

Before the first run, freeze one task, one user group, one tool version and one time window. Use approved representative material, record the baseline, define error labels, name the qualified reviewer and write the condition that stops the test.

At the end, choose the route supported by the record: fix the underlying process, buy a product that passes the operating questions, run or extend a controlled proof, or leave it alone. Name the owner, approvers, decision date and the condition that would reopen the question.

Try this today: write a one-page decision with the chosen route, evidence, main limitation, owner and review date.

What good looks like: leadership can explain why the next obligation is justified, or why no change is the disciplined answer.