Guides
Prompt Engineering for Lawyers: Techniques That Actually Work
Prompt engineering for lawyers as a method: six elements, six complete legal prompts (NDA review, research memo, clause redraft, client email) and iteration.
On this page
Prompt engineering for lawyers is the habit of briefing a model the way you would brief a capable trainee: who it is, what it has in front of it, what you want, what it must not do, what the output looks like, and an example of good. Briefed that way, the model that produces a generic memo produces a usable first draft. Here is the method, with six prompts to copy.
Why the prompt matters more than the model
On 30 August 2026 the head of technology at a 30-lawyer US firm described a bake-off on r/legaltech: the same client intake notes, containing a disqualifying heirship issue, run through CoCounsel, Harvey and Legora. "Every system missed it," he wrote; the only configuration that caught the problem "without further prompting" was Claude Opus on maximum effort (r/legaltech, 30 Aug 2026). The phrase to notice is "without further prompting". With a prompt that told the model what a disqualifying issue looked like, any of the four would probably have found it.
A senior associate on r/biglaw put the same point differently in June 2026: "Claude Opus is at least a fourth year right now, but with the wrong prompter in its eagerness to find a tidy answer, it misses things. The fourth year would know what got missed, but not the second year" (r/biglaw, 29 Jun 2026). The model is not the constraint; the brief is.
Two further data points set the scale. In a 2026 Redgrave LLP study, a partner spent 18 hours writing 43 prompt iterations before a generative review of 45,000 documents matched a 24-person, 1,123-hour contract review (eDiscovery Journal). And Stanford's 2026 AI Index reports that when a false premise is presented as the user's own belief, model accuracy collapses, from 98.2% to 64.4% for GPT-4o on one benchmark (Stanford HAI). A prompt that says "confirm that the tenant is not liable" gets a different answer from one that says "is the tenant liable". The mechanics behind both effects are in how large language models work; the short version is that the model completes the pattern you start.
The six elements of a legal prompt
| Element | What it does | Weak version | Strong version |
|---|---|---|---|
| Role | Sets register, jurisdiction and level of assumed knowledge | "You are a helpful assistant" | "You are a senior employment lawyer in California with 15 years of experience advising employers" |
| Context and sources | Tells the model what it may rely on and what the matter is | Nothing, or a two-word matter name | Attached documents named, the client's position stated, and "use only the documents provided" |
| Task | One sentence that says what finished looks like | "Review this contract" | "List every clause that departs from our playbook, with a rating and replacement wording" |
| Constraints | What the model must not do, and hard limits | "Be concise", "don't hallucinate" | "Maximum 600 words. Quote only text that appears in the document. If no authority is supplied, write GAP" |
| Format | The shape of the output | Unspecified | "A table with these four columns, then a three-line cover note" |
| Example | A sample of the standard you want | A description of house style | A pasted precedent clause with "draft in the same style" |
Published legal prompting guides converge on the same list. LegalFly's September 2026 guide calls the five-part version role, context, task, format and constraints, and adds two rules that hold up in practice: prefer positive examples over "do not" lists, and give summaries a hard word limit ("plain English, max 120 words, under English law") rather than an adjective (LegalFly, 17 Sep 2026).
One caveat for 2026 models. Anthropic's release notes for Claude Opus 5 say the model now "verifies its own work without being told to", writes longer deliverables by default and delegates more readily (Anthropic, Jul 2026). Boilerplate from 2025 such as "think step by step, then check your answer" now causes over-verification and padding. Keep the six elements; drop the choreography.
Six prompts to copy
Each prompt below is complete. Replace the bracketed details, attach the documents, and read the output the way you would read a trainee's first attempt.
1. NDA review against a playbook
You are a senior commercial lawyer advising the disclosing party, an Austrian software company, under English law.
Context: The attached NDA is the counterparty's first draft. Our playbook positions are listed below. Treat the playbook as the only source of our positions; do not invent others.
Playbook:
- Confidentiality term: 5 years from disclosure (fallback 3 years, never less).
- Definition of Confidential Information: marked or reasonably understood as confidential; oral disclosures confirmed in writing within 30 days is acceptable.
- Residuals clause: not acceptable.
- Governing law and forum: England and Wales; LCIA arbitration in London acceptable as fallback.
- No licence to our IP; no non-solicitation.
Task: Review every clause against the playbook. For each clause that departs from a playbook position, give (a) the clause number and quoted text, (b) the departure, (c) a rating of RED, AMBER or GREEN with one sentence of reasoning, and (d) replacement wording ready to paste.
Constraints: Quote only text that appears in the document. If a playbook position is not addressed by any clause, list it under "Missing". Do not comment on clauses that match the playbook. Do not summarise the agreement.
Format: A table with columns Clause | Issue | Rating | Replacement wording, then the "Missing" list, then a three-line cover note to the partner. Maximum 600 words.
"Review this NDA" typically returns 900 words that restate each clause and end with advice to consult a lawyer. The version above returns a table in which, for example, clause 7.3 (residuals) is RED with a deletion, clause 3 (term) is AMBER at three years, and "non-solicitation" appears under Missing because the draft is silent. Scaled across a portfolio, this is the pattern behind NDA review at scale.
2. Legal research in two stages
Stage one asks for thinking, not authority.
You are an experienced litigation associate in New York helping a partner scope a research question. Do NOT provide case citations, case names, statute section numbers or quotations: anything you provide will be treated as unverified.
Context: Our client, a commercial tenant, received a notice of default for failing to maintain HVAC equipment. The lease requires the tenant to "maintain and repair" building systems; the landlord replaced the entire unit and demands reimbursement.
Task:
1. Identify the legal issues in order of likely importance.
2. For each issue, state the questions a court would ask and the facts that would matter.
3. Draft 5 Boolean search strings for Westlaw and 5 natural-language queries for Lexis+ Protégé.
4. List the strongest arguments each side is likely to make.
Format: Numbered sections, plain prose, no citations, under 500 words.
Run the searches yourself. Then stage two:
You are the same litigation associate. Work ONLY with the authorities pasted below, which I have verified in Westlaw. Do not add, infer or recall any other authority.
[Paste verified authorities with pinpoint pages]
Task: Draft a memo answering whether "maintain and repair" obliges a tenant to replace an HVAC unit at the end of its useful life. Structure: Question Presented, Brief Answer, Facts, Discussion, Conclusion. Every proposition in the Discussion must carry a pinpoint citation to one of the supplied authorities. Where the supplied authorities do not answer a point, write "[GAP: no authority supplied]" instead of filling it.
Format: Under 900 words. End with the three weakest points in our position.
The two-stage pattern comes from a February 2026 guide to safe AI research and is the single most protective habit on this page (The Legal Prompts, 18 Feb 2026). Every "[GAP]" marker is a research task for a human. The verification that follows, existence, support and treatment, is set out in how to verify AI legal research, and the reasons the first stage must exclude citations are in AI hallucinations in legal practice.
3. Clause redraft from a precedent
You are a corporate lawyer drafting an English-language share purchase agreement governed by German law.
Here is a limitation of liability clause from a precedent in the house style we want:
"11.1 The aggregate liability of the Sellers under or in connection with this Agreement shall not exceed an amount equal to the Purchase Price. 11.2 The Sellers shall not be liable for any individual Claim unless the amount of that Claim exceeds EUR 25,000 (the "De Minimis Amount"), and shall not be liable unless the aggregate amount of all Claims exceeding the De Minimis Amount exceeds EUR 250,000 (the "Basket"), in which case the Sellers shall be liable for the whole amount and not only the excess."
Task: Draft the equivalent clause for the current deal in the same style, numbering and defined-term conventions, with these changes: cap of 30% of the Purchase Price for business warranties and 100% for title and capacity warranties; De Minimis Amount EUR 50,000; Basket EUR 500,000, tipping; carve-out for intent (Vorsatz), which cannot be excluded in advance under § 276 Abs. 3 BGB, and for fraudulent concealment (§ 444 BGB).
Constraints: Keep the sentence structure of the example. Add nothing that is not requested. Output only the clause, then a bulleted list of any point where you departed from the example and why.
The pasted precedent does more work than any description of style could. Without it the model produces a competent generic clause in US drafting conventions; with it, the output slots into the agreement. The same technique drives AI contract drafting more generally.
4. Deposition digest with page and line references
You are a litigation paralegal preparing a deposition digest for trial counsel. The transcript is attached (Smith deposition, 212 pages, page:line format), together with the witness's declaration of 3 March 2026.
Task: Produce a digest a partner can read in ten minutes.
Format:
1. Witness and context (3 lines).
2. Key admissions: one sentence each, followed by the page:line reference, e.g. (47:12-48:3). Quote the witness's exact words for anything you label an admission.
3. Contradictions with the declaration: a table with columns Topic | Declaration says | Deposition says (page:line).
4. Topics counsel did not cover that the pleadings suggest matter.
5. Exhibits referenced, by number and page.
Constraints: Every factual statement must carry a page:line reference. If you cannot find one, omit the statement. Do not characterise credibility. Maximum 800 words.
The constraint "if you cannot find one, omit the statement" is the whole safeguard: it converts a summariser into an indexer. More on transcript work in AI deposition and transcript summaries.
5. Client email in plain English
You are a solicitor writing to a client who runs a small business and has no legal training.
Context: The client asks whether they can end a 12-month supply contract early because the supplier has delivered late three times. Clause 14.2 of the attached contract allows termination for "material breach" after a 14-day cure notice. Late delivery is not expressly defined as material.
Task: Draft an email explaining (1) what the contract lets them do, (2) what they must do first, (3) the risk if they terminate without following clause 14.2, and (4) our recommended next step.
Constraints: Plain English, no Latin, no case citations, English law. Maximum 180 words. Do not promise an outcome. Do not use the words "unfortunately" or "please note".
Format: Subject line, greeting, four short paragraphs, sign-off. Then, separately for me, a two-line note of any assumption you made.
The word limit and the two banned phrases do more for tone than "be friendly and professional" ever will. The separate assumptions note is where the model tells you it assumed the cure notice had not yet been served.
6. Red team from the other side
You are opposing counsel: a sceptical, experienced arbitration practitioner acting for the respondent.
Context: Attached is our draft statement of claim in an ICC arbitration seated in Vienna under Austrian substantive law, alleging breach of an exclusive distribution agreement.
Task: Give the five strongest arguments against our case, ranked by how much damage each could do. For each: the argument in two sentences, the paragraph of our draft it attacks, the evidence the respondent would need, and the single change to our draft that would blunt it.
Constraints: Argue in good faith as the other side; do not soften. Do not cite authorities. Do not restate our case.
Format: A numbered list of five, under 600 words. Finish with one sentence: which argument you would lead with at the hearing, and why.
Role-reversal prompts are the cheapest second opinion in the building. A fuller routine, including how to run the same draft past two models, is in red-team your argument with AI.
Iterate in three turns
The first output is a draft, not an answer. A three-turn pattern gets most of the remaining value:
- Draft. Run one of the prompts above.
- Critique. "Read your draft as a sceptical partner. List every assumption you made, every sentence a partner would strike, and every point where the supplied documents do not support what you wrote." Naming the perspective matters more than asking for "feedback".
- Revise. "Apply only the critique points that are supported by the documents. Show changes as a list before the revised text."
Two things not to do. Do not ask the model whether its citations are real; the lawyers in Mata v. Avianca (S.D.N.Y. 2023) did exactly that, and a New Jersey lawyer was sanctioned a second time in April 2026 for "using AI to verify AI" (ComplianceHub). And do not treat the model's own caveats as decoration: in Cork v Smith [2026] EWHC 1199 (Ch) the tool flagged that its answer might be inaccurate, the associate filed anyway, and the firm was referred to the SRA (UK Human Rights Blog, 4 Jun 2026).
Make the good prompt permanent
A prompt that works twice should stop living in the chat box. As of September 2026 there are four places to put it.
A system prompt or custom instruction sits above every conversation and carries the role, jurisdiction and house rules. A Claude Project holds static context, the matter documents and the playbook, uploaded once; the Claude Projects for a matter playbook walks through the setup. A Claude Skill is a folder with a SKILL.md file of instructions plus optional scripts and reference documents that fires only when a task matches its trigger and works across Claude.ai, Claude Code and the API (Layer 3 Labs, updated 7 Sep 2026); a small-firm lawyer's post about Skills that edit Word tracked changes directly drew seven million views in March 2026 (Artificial Lawyer, 2 Mar 2026). Anthropic's own open-source Claude for Legal plugins take the idea to its conclusion: every plugin starts with a "cold-start interview" that writes the firm's practice profile, which every later skill reads. On the OpenAI side, a custom GPT for your practice does the same job.
Quinn Emanuel's Christopher Kercher described the firm's breakthrough with Claude as "treating Claude like a case team member" and feeding it chronological materials (Fortune, 12 May 2026). That is a prompting decision, made once and inherited by everyone.
Build your library this week
Pick the two tasks you did most often last month and write the six-element prompt for each, using the templates above. Run each three times on real (or anonymised) material and keep the version that needed the least editing. Put the winners in a shared document with a named owner, then move them into a Project, a Skill or a custom GPT; the prompt library playbook gives the folder structure and a change-log template. Module 1 of the AI Lab for Lawyers course spends its first session on exactly this method, building and testing the six-element prompt live on legal documents before moving on to research, drafting and agents.
Frequently asked questions
What is the best prompt structure for legal work?
Six elements in roughly this order: the role the model should adopt, the context and the sources it may use, the task in one clear sentence, constraints such as word limits and forbidden moves, the output format, and an example of what good looks like. Published guides call a five-part version of this RCTFC; the order matters less than making sure nothing is missing.
Can I ask ChatGPT or Claude for case law in a prompt?
You can, but you should not rely on it. General models invent citations that look right, and courts have sanctioned lawyers who filed them. The safer pattern is a two-stage prompt: first ask for issue framing and search strings with an explicit instruction not to cite cases, run the search in Westlaw or Lexis, then paste the verified authorities back and instruct the model to work only from those.
Does prompt engineering still matter with reasoning models like Opus 5 or GPT-6 Astra?
Yes, though the emphasis has shifted. Reasoning models need less step-by-step hand-holding and now verify their own work, so old instructions like add a final verification step can cause over-verification. What still matters is context, sources, constraints and format: a strong model with a vague brief produces a confident answer to the wrong question.
How do I share good prompts across my firm?
Store them where the tool reads them automatically rather than in a Word document nobody opens. Options in 2026 are a system prompt or custom instructions, a Claude Project with the matter documents uploaded once, a Claude Skill that fires when a task matches its trigger, or a custom GPT. A shared library with a named owner and a change log keeps them consistent.
Put this into practice
AI Lab for Lawyers: a live, hands-on course for practising lawyers
4 live sessions (8 hours), recordings included, taught by Dr. Niklas Schmidt of Wolf Theiss. Rated 4.7/5 from 381 ratings; alumni from Norton Rose Fulbright, Paul Hastings, Pillsbury and Taylor Wessing.
Related reading
Playbooks
Build a Prompt Library for Your Practice: Structure, Governance and 12 Starter Prompts
Build a law firm prompt library lawyers will use: folder structure, a header for every prompt, a review cadence for model changes and 12 tested starter prompts.
11 min read
Glossary
System Prompt — Definition for Lawyers
A system prompt is the standing instruction an AI model reads before your message. Where it lives in Claude, ChatGPT and Skills, a legal template, and its limits.
4 min read
Playbooks
Red-Team Your Argument with AI: Adversarial Prompts for Litigators and Negotiators
Red-team your legal argument with AI in five rounds: prompts that make the model argue the other side, play a sceptical judge and score your case before filing.
12 min read
Guides
How Large Language Models Work, Explained for Lawyers
How LLMs work, explained for lawyers: tokens, prediction, training versus inference, context windows, knowledge cutoffs, reasoning modes and the September 2026 model line-up.
8 min read
Playbooks
Set Up Claude Projects for a Matter: Instructions, Files and Memory
Set up a Claude Project for a legal matter in 30 minutes: sample instruction text, which files to upload, Skills, memory, Team sharing and three prompt flows.
10 min read
Use Cases
Writing Legal Memos with AI: A Method That Survives Partner Review
An AI legal memo survives partner review when the model drafts only from sources you supply, every authority is checked three ways and the checks are logged.
10 min read