How Lawyers Use AI in 2026: 12 Workflows With Evidence, Not Hype

Ask more than 1,300 legal professionals what they use generative AI for and the answers come back in a neat, slightly alarming order. Drafting correspondence: 58%. General research: 58%. Brainstorming: 54%. Summarising documents: 47%. Drafting documents: 43%. That is how lawyers use AI in 2026, according to the 8am Legal Industry Report, and the two entries tied at the top could not be more different. One is the safest thing you can do with a language model. The other is what lies behind the 811 lawyer-involved entries in Damien Charlotin’s database of court decisions involving hallucinated material, which stood at 2,039 cases on 12 September 2026.

So the twelve workflows below are ranked the other way round: by how reliably they work, not how often lawyers do them. Document-grounded tasks come first. Open legal research comes last, with a warning label. In between are the practitioner workflows vendors never publish, because the people who invented them were venting on Reddit rather than writing case studies.

What the surveys say lawyers use AI for (and how often)

Every adoption number has a denominator. “Uses any AI in the firm” (Clio 2025: 79%), “personally uses general-purpose GenAI for work” (8am 2026: 69%) and “uses AI for legal work” (LexisNexis, September 2026: 94%) are three different questions.

Frequency is high: Thomson Reuters’ Future of Professionals 2026 report (1,816 professionals, 62 countries) found 74% use AI several times a week and 44% several times a day. The Texas survey puts ChatGPT at 63% of AI-using lawyers, Microsoft Copilot at 44% (up from 31%) and Westlaw/CoCounsel, the top legal-specific tool, at 30%.

Time saved is more modest than the marketing: 38% save one to five hours a week, 14% save six to ten, and a third report better quality without saving any time. Verification is work, and it is the part vendors leave out of the arithmetic.

The reliability ladder: document Q&A first, open research last

The only public head-to-head of the big legal platforms is the Vals Legal AI Report of February 2025, which gave Harvey, CoCounsel, vLex Vincent and Vecflow Oliver the same documents and instructions as a baseline of practising lawyers. The pattern in the scores is the most useful thing to know about legal AI.

The tools also ran six to eighty times faster, with Harvey and CoCounsel averaging under a minute per task against a two-week window for the humans.

Now put open legal research at the bottom of the ladder. Stanford RegLab’s pre-registered 2024 benchmark found Lexis+ AI hallucinated on more than 17% of queries and Westlaw AI-Assisted Research on more than 34%, and those were the tools built specifically to avoid it. General chatbots did worse. The Ninth Circuit cited that benchmark in its June 2026 sanctions order in Lnu v. Blanche.

The rule is simple. When the answer must come out of a document you supplied, AI beats lawyers. When it must come out of the model’s memory of the law, AI loses, and loses in ways that end up on a docket. Harvey’s own user guidance says the quiet part well: “The summary is a map, not the territory.”

Workflows 1 to 3: summarising, correspondence, first drafts from clean facts

Workflow 1: summarising with the quotes attached

Summarisation is where the largest gap opened between tools and people (77.2% vs 50.3%), and also where a bad summary is invisible. The fix is to make the model show its evidence.

Summarise the attached [judgment / expert report / lease] for a [partner who has ten minutes / client with no legal training].
Before writing, extract into <quotes></quotes> every passage you will rely on, each with its page or paragraph number.
Then write the summary in no more than [300] words, referencing quotes by number after each sentence.
Any statement not traceable to a quote must be labelled INFERENCE.
Do not add context from your own knowledge of the law. If the document does not address something I would expect it to, say "NOT IN DOCUMENT".

A litigator on r/Lawyertalk described the value precisely: “Where it really shines is finding me my needle in the haystack of a large file.”

Workflow 2: correspondence

The most common use and the lowest-risk one, provided client identifiers stay out of consumer tools. A general-practice partner quoted in Clio’s 2025 Legal Trends Report uses it to “rewrite something I’ve used a million times and see what’s missing for the client”. Workflow 11 below has the prompt.

Workflow 3: first drafts from clean facts

Here is the honest ceiling, from a practitioner on r/Lawyertalk: “AI is decent at a first draft of a pleading if you give it clean facts and a tight instruction. That’s about the limit.” A divorce lawyer agrees: it “cranks out standard petition and motions easily.”

Draft a first draft of a [petition for dissolution / letter before claim / standard motion to compel] under [jurisdiction] rules for [PARTY_A] against [PARTY_B].
Use only the facts in <facts>...</facts>. Do not add, infer or embellish facts. Where a fact you need is missing, write [MISSING: describe].
Follow the structure of our precedent in <precedent>...</precedent>, keeping its defined terms and numbering.
Do not cite any case, statute or rule. Where authority belongs, write NO AUTHORITY SUPPLIED and stop; I will insert it.
Formal, plain English, active voice, under [800] words. List at the end every judgement call you made.

The evidence on quality is sobering. A randomised trial of 60 law students with GPT-4 (Choi, Monahan and Schwarcz, Minnesota Law Review) found access “only slightly and inconsistently improved the quality of participants’ legal analysis but induced large and consistent increases in speed”. A 2025 follow-up with a reasoning model and a retrieval-based legal tool found productivity gains of 50 to 130% in five of six tasks, with quality gains too. The tools improved. The need to read the output did not go away.

Workflows 4 to 6: contract review against a playbook, due diligence extraction, chronologies

Workflow 4: contract review against a playbook

The 2024 “Better Call GPT” study found GPT-4 matched junior lawyers at determining whether a contract raised an issue (F-score 0.871 against 0.860) but was weaker at locating where the issue sat (0.686 against outsourcers’ 0.770). So the prompt must force the model to quote the words.

Review the attached [NDA / vendor MSA] against our playbook <playbook>...</playbook> from the perspective of [our side]. Read the whole agreement before flagging anything.
For every playbook item, one row: Playbook item | Contract clause (number and the quoted operative words) | GREEN (meets preferred) / YELLOW (within fallback) / RED (beyond walk-away or missing) | Business impact in one sentence | Proposed redline language | Escalation required (Yes/No).
Then list any provision the playbook does not cover that shifts risk to us, and any internal inconsistency between clauses.
Finish with what you could not assess because a schedule or exhibit is missing.

The playbook review guide explains how to build the playbook first, which about a third of legal teams do not have. Redlining is where lawyers still win comfortably: the tool flags, you decide what to change.

Workflow 5: due diligence extraction

Tabular review across a data room is what the big platforms were built for, every cell linked to its source. Katten’s instruction to a junior works as the prompt: identify every contract that requires third-party consent or is terminable on a change of control, with the counterparty, the triggering language and the remaining term. Harvey’s own benchmark team adds the caution: agents’ “bias is to search efficiently, not completely. Diligence requires reversing this intuition.” So open every red cell yourself.

Workflow 6: chronologies

Harvey’s published example uploaded 800 emails to a review table with questions as columns (“Who is the sender?”, “Does the email mention travel on Air Force One?”) and got “4,000 data points at once in minutes”, each linked to its email. In the Vals bake-off, chronology generation was the one task where tool and lawyer tied exactly, at 80.2%; the tool just did it in under a minute. The chronology guide runs the same column-per-question method in NotebookLM and a Claude Project.

Workflows 7 to 9: deposition prep, oral-argument moots, generative document review

Workflow 7: deposition summaries with page-line citations

Transcript analysis was one of AI’s clearest wins in the Vals report (77.8% vs 53.7%). Everlaw’s AI Assistant returns summaries, discrepancies within a deposition and answers to custom questions with page-line citations; any frontier model can do the same if you demand the citation format. What you must not do is ask for a “bulletproof summary”.

The deposition prep guide separates extraction (page:line quotes) from judgement (credibility), which is exactly the separation that workflow lacked.

Workflow 8: oral-argument moots

A Virginia appellate lawyer’s published workflow: get the client’s consent, load the briefs and record excerpts into a ChatGPT project, then ask for the panel’s likely concerns, unaddressed counter-arguments, 25 preparation questions and a moot “in the voice of” a named judge, interruptions included. A law professor who tested the approach warns that one confidently wrong case summary made her “really question myself”; start with questions you already know the answers to.

Act exclusively as a sceptical [appellate judge / arbitrator] in a matter where I appear for [party]. You have read my brief <brief>...</brief> and the opposing brief <opp>...</opp>.
Ask me one challenging question at a time about my argument and wait for my answer. Follow up if my answer is evasive or incomplete.
Do not break character, do not summarise, and do not step out of the conversation until I say "Time Out".
Refer only to authorities that appear in the briefs; do not introduce cases of your own.
Begin with the question you think I least want to be asked.

Nothing here gets filed, but briefs and record excerpts are client material: use a no-training tier.

Workflow 9: generative document review, validated

In Schulte v. LinkedIn (N.D. Cal., 1 July 2026) a federal court treated Relativity aiR as “a form of technology-assisted review”, accepted keyword pre-culling and refused the plaintiffs’ demands for validation metrics as “discovery on discovery”. The difference from generative research is discipline: Reed Smith’s protocol tests prompts on 50 to 100 seed documents, expands to 500 to 1,000, then runs the full population with sampling throughout and every prompt logged. The e-discovery guide has the protocol in full.

Workflows 10 to 12: translation, client communication, business development

Workflow 10: translation. In the Bayerischer AnwaltVerband’s survey of 558 participants, DeepL was the most-used AI tool in Bavarian law firms at 70.7%, ahead of ChatGPT at 69.2%. Translation is document-grounded and has an obvious check: a bilingual reader. State the jurisdiction and register in the prompt; a German “Kündigung” and an English “termination” carry different procedural baggage.

Workflow 11: client communication. Clio’s prompt, verbatim, is nearly the whole workflow: “Draft a client-facing email explaining the discovery timeline for our employment discrimination case in plain English. Tone should be reassuring but honest about potential delays. Keep it under 200 words.” Add a structure and you have a template.

Draft a client email explaining [the next hearing / why the other side's offer is low / the discovery timeline] in our [matter type] matter.
Plain English; no term a non-lawyer would not know; under 200 words; reassuring but honest about [the risk / the delay].
Structure: what happened; what it means for you; what we are doing; what we need from you by [date]; when to expect the next update.
Do not promise an outcome. Do not add facts beyond <facts>...</facts>. Sign off as [name].

Workflow 12: business development. Originality.AI classified 81.2% of a July 2026 sample of 5,000 LinkedIn posts as “Likely AI”, and LinkedIn is rolling out a “Seems like AI slop” feedback option. So the workflow that works is not “write me a post”. It is Jay Harrington’s cadence: weekly bullets on what changed in your area, a monthly compilation, and personalised emails to a handful of clients. The model compiles and drafts; you add the one detail only you know.

What lawyers say does not work: judgement, jurisdiction-specific procedure, negotiation

The most quoted verdict on the limits came from a Minnesota litigator on r/Lawyertalk:

“In my area, AI is terrible at knowing the law, mainly because it mixes up jurisdictions. However, knowing the law is only 10% of what I do. Knowing the personalities of the judge, mediator, opposing counsel and my client to effectively negotiate is 70%.” — /u/KingoftheNordMN, r/Lawyertalk, 12 September 2026

Three failure zones recur across every source.

Jurisdiction-specific procedure. Models default to whichever law dominates their training data. The Wadsworth v. Walmart sanctions came from asking an in-house tool to add “Federal Case law from Wyoming” to a motion in limine: eight fake cases out of nine. Rules of court change faster than models retrain.

Negotiation and redlining. Lawyers beat every tool on redlining in the Vals report. A Magic Circle senior associate told Legal Cheek the tools “cannot be relied on for judgment calls”, comparing them to “a moderately capable 2nd/3rd seat trainee”.

Valuation. A PI lawyer’s warning: “AI substantially over values cases if you ask it about what a reasonable settlement should be”. Structure the settlement memo with the model; put the numbers in yourself.

Ten workflows lawyers on Reddit swear by

Vendors publish case studies. Practitioners publish complaints with workflows buried inside them. These ten come from r/legaltech, r/Lawyertalk and r/biglaw threads in 2026, quoted as posted and unverified; try them on anonymised material.

1. The two-model adversarial loop. Ask Claude, ask ChatGPT, feed each answer to the other “telling it to review it with scepticism and make an independent assessment”, then combine.
2. Playbook in a Project. Describe your workflow to a model in detail, have it write a playbook file, load that into a Claude Project or custom GPT, and after each matter ask it to update the playbook from the chats. Its author credits it with a 40% revenue increase (self-reported).
3. The docx template. Give the model a Word template and tell it to follow that formatting, which answers the question a 31-year practitioner put to r/legaltech: “how do you get them to output their product in a Word .docx executable file?”
4. The audit checklist instead of a debate. “Start with a checklist the model must fill: issue, jurisdiction, source relied on, uncertainty, recommended human review point.”
5. Bank statements to Excel. A divorce lawyer feeds “a couple years’ worth of bank & credit card statements”, asks for specific payment types or recipients, then has it “segregate & export that information into an Excel spreadsheet”. Totals get rechecked in Excel.
6. Small discrete sections. “It’s better at drafting if you ask it to craft small discrete sections (a few paragraphs at most) and give it the arguments.”
7. Checklist coherence across documents. “Sanity check all items in a massive checklist are included”, says a BigLaw lawyer, adding: “I still manually validate everything it does.”
8. Brief editing, not brief writing. “Suggesting stronger sentences or pointing out where the argument could use more details.”
9. The three-agent moot. Two agents argue each side to a third “judge” agent; the litigator reads the “hearing” transcripts: “It’s actually really helped me prepare for oral argument.”
10. Non-legal research only. A Texas lawyer with a cancer-assay case uses AI “to learn all that I can about that field, including disease etiology. I do not use it for legal research.”

How to pick your first workflow

Three questions decide it: what data goes in, how you will check the output, and whether the model must know any law.

Two things happen after a month. Your job changes shape: Harvey’s line about agentic work, “The skill shifts from editing to auditing”, applies to every workflow above. And you learn whether the time saving is real for you. A Spellbook user on r/legaltech says the tool “made me at least 4x more efficient” with an effective hourly rate “hovering around 2.3x through 2026’s first 8 months”; a BigLaw associate says it “has probably lost me more time than it has saved”. Which one you become depends on picking document-grounded tasks and building the verification habit before the workload builds it for you.

That habit is the design of AI Lab for Lawyers: four live two-hour sessions in browser tools, working these workflows on your own anonymised material, so there is something to run on Monday. The prompt library has the full versions of every prompt here.

Where to go next: the client communication guide for the lowest-risk workflow, the due diligence workflow for the highest-volume one, and the tools comparison to decide which tier of which tool your firm should be on. All the task-level guides live in the use cases hub.