Claude Use Cases for Lawyers: 10 Applications, Prompts & Limitations

Lawyers use Claude AI for legal research, contract review, document drafting, due diligence, and client communication. Claude AI is a general-purpose large language model developed by Anthropic, trained with Constitutional AI and not built specifically for legal work.

Ten workflows account for most of that use, and each has a point where it stops being reliable. Those points are not scattered at random. They fall into three groups that get progressively harder to work around: what Claude can read, what it can write, and what it cannot hold on to between one session and the next.

What Claude Reads

Capacity is the part that is already solved. A single session now takes in more legal text than anyone will read by hand in a matter, so the binding constraint has moved off volume entirely. It sits on verification, and it sits there whether the reading is case law, a contract, or a data room.

1. Legal Research and Case Law Analysis

Claude’s context window processes entire trial transcripts, full appellate briefs, or hundreds of contracts in a single session, with no document splitting required. Opus 5, Sonnet 5 and Fable 5 each carry a one million token window, which Anthropic describes as roughly 555,000 words.

Model choice decides this. Haiku 4.5 carries 200,000 tokens, around 150,000 words, so a long-document task routed to the wrong model will truncate. Every figure below is from Anthropic’s models overview as of August 2026.

Legal research teams use Claude to summarise case law holdings, extract statutory provisions, and identify jurisdictional differences in rulings. Attorneys upload relevant precedent and ask for the legal standard, the court’s reasoning, and the distinguishing facts across several cases at once.

Benefits:

• Processes book-length documents in one session on the 1M-token models, covering full appellate briefs and complete discovery sets

• Summarises case law holdings, reasoning, and issues in seconds

• Identifies jurisdictional differences across state or federal rulings

• Extracts key legal principles from statutes and administrative codes

Example prompt:

“You are in-house counsel preparing for a contract dispute. Summarise the following three appellate cases on liquidated damages enforceability in California, focusing on: (1) the court’s test for reasonableness, (2) whether the clause was upheld or struck down, (3) distinguishing facts. Output as a comparison table.”

Claude cannot cite case law accurately without independent verification. It has no live access to Westlaw or LexisNexis, and it can fabricate case names, holdings, or procedural history. Every citation must be checked against a primary legal database before it reaches a brief or memo.

Its other limits follow from the same gap. It cannot confirm whether precedent is still good law, so currency checks remain manual. It cannot apply binding precedent from a specific jurisdiction without being told which one. It has no playbook to check firm-wide standards against. The context window widens what can be read at once and does nothing for whether the reading is correct.

That verification burden does not lighten when the document under review is a contract rather than a case.

2. Contract Review and Analysis

Claude helps with contract review by extracting key clauses, flagging missing terms like indemnification limits or termination rights, and identifying ambiguous language across NDAs, MSAs, and vendor agreements. Lawyers reach for it on one-off analysis: a quick risk read, a gap check, a version comparison. It surfaces missing force majeure clauses, vague liability caps, overly broad confidentiality definitions, and termination provisions that favour the counterparty.

Claude produces tracked changes in Word through the Claude for Word add-in, which drafts, edits and revises inside the document while preserving formatting. Anthropic released it in public beta on 10 April 2026, and the Word, Excel and PowerPoint add-ins are now generally available to Team and Enterprise subscribers.

Benefits:

• Extracts termination, indemnification, liability cap and confidentiality clauses from NDAs, MSAs and vendor agreements

• Flags missing or weak terms, including absent force majeure clauses and unlimited liability exposure

• Identifies ambiguous language that could lead to disputes

• Compares contract versions to surface changes in redlines

Example prompt:

“Review the attached NDA for the following risks: (1) missing mutual confidentiality obligations, (2) unlimited liability exposure, (3) overly broad definition of confidential information, (4) no return-or-destroy clause. Output as a bullet list ranked by severity.”

Limitations:

• No playbook enforcement, so contracts are not checked automatically against firm-wide standards or a pre-approved clause library

• One-off analysis only, not built for repeating workflows where sales, HR or procurement teams self-serve contract generation

• No tracking of post-signature obligations, renewal dates, or termination windows

Producing tracked changes is not the same as checking those changes against a clause library. Platforms like Miramis hold the second job: a contract management platform enforces the playbook automatically and carries obligations forward after signature.

The harder case is not one contract but five hundred, which is where diligence work begins.

3. Due Diligence and Document Analysis

Claude processes entire due diligence data rooms in a single session on the 1M-token models. Legal teams upload large contract sets during M&A transactions and ask for obligations, change-of-control provisions, liability caps and auto-renewal clauses with short notice periods. The output arrives as a structured table in minutes rather than days.

The pattern generalises past M&A. Compliance teams run it against contract portfolios to surface missing GDPR clauses and outdated indemnification language. Litigation teams run it against medical records, expert reports and technical documents, where the task is pulling liability exposure and testimony points out of material nobody has time to read twice. Model choice still binds: Haiku 4.5 at 200,000 tokens will not hold a data room that Opus 5, Sonnet 5 or Fable 5 take in whole.

Example prompt:

“Review the attached 200 supplier contracts for the following due diligence issues: (1) contracts with auto-renewal clauses and notice periods under 60 days, (2) unlimited liability exposure, (3) missing force majeure or pandemic-related clauses, (4) contracts expiring within 90 days of the acquisition close date. Output as a spreadsheet-style table with columns: Supplier Name | Issue | Contract Section | Risk Level.”

Once diligence closes, everything it found stops being tracked. Claude cannot monitor renewal dates, compliance deadlines or performance milestones, it stores nothing between sessions, and it cannot enforce playbook standards across the acquired portfolio. Every repeat analysis is a fresh upload. That gap is the whole of post-close governance, and a contract repository holds what a session cannot.

What Claude Writes

Reading feeds writing, and the same session that took in the case law can produce the motion. What changes once Claude is producing rather than ingesting is where the risk sits: not in whether the model understood the input, but in whether anyone checked the output before it went out under a lawyer’s name.

4. Legal Document Drafting

Claude generates first drafts of pleadings, motions, demand letters, client memos, and discovery responses in minutes. Attorneys supply case facts, applicable law and desired tone, and Claude mirrors prior document style when given templates or past examples. What it removes is the blank page, which is the slowest part of the drafting pass and the one least dependent on judgement.

Example prompt:

“Draft a motion to compel discovery in California state court. Facts: Defendant has not responded to our interrogatories (Set One, served 45 days ago). We sent a meet-and-confer letter 15 days ago with no response. Include: (1) procedural background, (2) legal standard under CCP § 2030.290, (3) argument that defendant’s silence justifies sanctions, (4) request for monetary sanctions equal to $2,500 in attorney fees. Use formal court motion formatting.”

The output is a first draft and nothing more. Claude lacks jurisdiction-specific procedural knowledge, so it may omit required local court rules, caption formats or filing requirements; it produces generic argument unless given detailed facts and applicable law; and it cannot verify whether its own language meets ethical standards or complies with court rules. Attorney review for accuracy, tone, compliance and citation validity is a required step, not an optional one.

5. Litigation Support and Case Preparation

Claude simulates cross-examination scenarios, generates witness question scripts, analyses opposing counsel’s briefs for weaknesses, and summarises expert reports to pull out key testimony points. Litigation teams upload witness statements, deposition transcripts and the opposing summary judgment motion, then ask for cross-examination questions structured by topic.

Benefits:

• Simulates cross-examination scenarios from witness statements and case facts

• Generates witness question scripts structured by topic: background, liability, damages

• Analyses opposing briefs and motions to identify argumentative weaknesses

• Summarises expert reports and deposition transcripts into key testimony points

Example prompt:

“You are trial counsel in a breach of contract case. The defendant claims force majeure excused non-performance due to COVID-19 supply chain delays. Based on the attached contract (which includes a narrow force majeure clause limited to ‘acts of God’), draft a cross-examination outline for the defendant’s CEO focusing on: (1) whether the delay was truly unforeseeable, (2) whether defendant took reasonable steps to mitigate, (3) whether defendant notified us within the contractually required timeframe. Include follow-up questions for evasive answers.”

Limitations:

• No substitute for trial strategy expertise, since generated questions lack courtroom instinct and miss case-specific nuance

• No live trial feedback, so questioning cannot adapt to witness demeanour or unexpected testimony

• Requires attorney review against evidence rules and procedural limits

• Cannot assess credibility or advise on settlement strategy

Litigation decisions stay with the attorney. The model shortens preparation, and a contractual dispute is still won on judgement it does not have.

Preparation stays inside the firm, so the work that actually reaches the client is the correspondence around it.

6. Client Communication and Engagement Letters

Claude drafts engagement letters, client status updates, explainer emails and settlement demand letters. Lawyers use it to translate legal concepts into plain language for non-lawyer clients and to produce negotiation correspondence in a consistent register. Tone adapts to the prompt: formal for filings, reassuring for client updates, firm for demand letters.

The volume case is status updates. When a matter reaches a procedural milestone, an email explaining what happened, what comes next and when a ruling is expected becomes a two-minute task rather than a twenty-minute one, and the client hears from the firm on a cadence the firm can actually sustain.

Example prompt:

“Draft a client status update email for a commercial lease dispute. Facts: We filed a motion to compel arbitration 10 days ago. The court hearing is scheduled for [date]. Opposing counsel has not yet filed a response. Tone: professional but reassuring. Include: (1) brief case status, (2) what happens next, (3) timeline for expected ruling, (4) no legal jargon. Length: under 200 words.”

Judgement is what it cannot supply here. It cannot assess whether a communication strategy suits the client relationship or case posture, it will produce an overly formal or overly casual register without explicit guidance, and it has no view on what to share and what to withhold in a sensitive negotiation. Client work also carries a confidentiality risk on Free, Pro and Max, which sit under Anthropic’s consumer terms.

What Claude Cannot Hold

Reading and drafting both serve a single matter, and Claude handles a single matter well. Compliance, firm knowledge, training and portfolio analysis are different in kind: each is a standing obligation rather than a task, and each fails at the same place. Claude has no memory between sessions, so it gives a snapshot where the job needs a monitor.

7. Compliance and Risk Management

Claude reviews contracts for regulatory gaps, drafts internal compliance policies, summarises new regulations, and analyses vendor agreements for supply chain risk. Compliance teams upload portfolios and ask for missing GDPR data processing addendums, non-compliant arbitration clauses or outdated indemnification provisions, ranked by severity. When a new regulation lands, the question of which existing contracts it touches is answerable in one pass rather than one contract at a time.

Benefits:

• Reviews contracts for regulatory gaps including missing GDPR clauses and outdated data processing provisions

• Drafts internal policies on data retention, whistleblowing and anti-bribery from stated standards

• Summarises new regulations and flags the contracts or processes they affect

• Analyses vendor agreements for supply chain risk: single-source dependencies, force majeure gaps, liability caps

Example prompt:

“Review the attached 50 vendor contracts for GDPR compliance. Flag contracts missing: (1) data processing addendum (DPA), (2) sub-processor notification rights, (3) data breach notification obligations within 72 hours, (4) right to audit data handling practices. Output as a risk-ranked table.”

Compliance here is a snapshot, not a monitor. Claude tracks no new laws or enforcement actions, enforces no standard across repeating contract workflows, carries no jurisdiction-specific knowledge unless the prompt supplies it, and follows no remediation through to closure. Platforms with playbook enforcement check every contract against firm-wide standards as it is created, which is the difference between finding contract management challenges once and preventing them continuously.

Knowing which contracts are exposed depends on knowing what the firm has already decided about clauses like these.

8. Internal Knowledge Management

Claude summarises past case files, extracts reusable precedent from internal memos, and builds question-and-answer resources from firm knowledge. Claude Projects is the mechanism: a self-contained workspace with its own chat history and knowledge base, so playbooks, templates and style guides are uploaded once rather than per session. According to Anthropic’s Projects documentation as of August 2026, Projects are available to all users including free accounts, which are capped at five projects. On paid plans, project knowledge scales through retrieval-augmented generation, which Anthropic states expands capacity by up to ten times when project knowledge approaches context limits.

Example prompt using Projects:

“Using the firm’s M&A playbook uploaded to this Project, draft a summary of our standard position on indemnification caps in acquisition agreements under $50M. Include: (1) our preferred cap structure (basket + cap), (2) carve-outs for fraud and fundamental reps, (3) rationale for each position. Format as a two-page training memo for junior associates.”

Limitations:

• Requires deliberate document curation, since a Project is a knowledge base rather than an indexed firm-wide records system

• Carries its own project knowledge context, which is not the same as the model’s context window and should not be conflated with it

• No firm-grade access controls or versioning

• Connector reach into SharePoint, OneDrive and Outlook is not the same as an indexed, permissioned firm record

Purpose-built document management systems handle enterprise-scale indexing, search and permissions that Projects does not attempt.

All of that assumes someone who knows what to ask for, which makes it a training problem before it is a retrieval one.

9. Legal Training and Skills Development

Claude generates training material on contract drafting, legal research method and negotiation strategy. Supervising lawyers use it to give feedback on associate-drafted motions, covering argument structure, citation accuracy, register and clarity. It also simulates negotiation scenarios so junior attorneys can practise responding to opposing counsel objections or client pushback without the cost of doing it live for the first time.

Example prompt:

“Review the attached associate-drafted motion for summary judgment. Provide feedback on: (1) argument structure (does it lead with the strongest point?), (2) citation accuracy (are cases cited for the correct proposition?), (3) tone (is it persuasive or overly adversarial?), (4) clarity (any jargon or run-on sentences?). Output as a bullet list of specific edits.”

What it cannot do is certify any of it. Generated continuing education material is not accredited and satisfies no mandatory requirement, writing feedback stays generic without jurisdiction-specific style guides or court preferences, and simulated negotiations lack the pressure that makes real ones instructive. The value sits in iteration volume rather than instruction quality: practice against fast feedback beats fewer rounds against better feedback.

Skills develop one person at a time. The patterns worth acting on show up only across the whole portfolio.

10. Data-Driven Insights and Analytics

Claude analyses contract portfolios for trends: the most common termination triggers, average liability cap amounts, renewal patterns across vendors. Legal operations teams also use it to extract billing insights and to summarise discovery data into case themes. Output is text, not charts, but it surfaces patterns that manual review across hundreds of contracts would miss. The recurring finding is usually which terms get negotiated away every time, which is a playbook problem rather than a drafting one.

Benefits:

• Identifies portfolio trends: termination triggers, average liability caps, renewal patterns

• Extracts billing insights on matter duration and scope creep by client

• Flags firm-wide risk patterns and recurring compliance gaps

• Summarises discovery data into case themes and key evidence

Example prompt:

“Analyse the attached 100 vendor contracts and extract the following portfolio insights: (1) percentage with auto-renewal clauses, (2) average notice period for termination, (3) most common liability cap structure (dollar amount, revenue multiple, or unlimited), (4) percentage missing force majeure clauses. Output as a summary with statistics and a risk assessment.”

Limitations:

• No analytics dashboards, since output is text rather than visual charts

• Every portfolio analysis is a one-off session rather than ongoing monitoring

• No tracking of change over time and no alerting on emerging risk

• No integration with business intelligence tools for firm-wide reporting

Analytics here describe rather than prescribe. Platforms with built-in contract analysis provide dashboards and automated alerts when portfolio risk shifts.

Claude vs ChatGPT for Lawyers

Both are general-purpose large language models used by legal professionals for research, drafting and document analysis, and the ChatGPT use cases for lawyers run largely parallel to Claude’s. On the dimension most often cited as separating them, how much text each reads at once, they are now at parity.

Claude compares to ChatGPT for legal research at effective parity on document capacity. As of August 2026, Claude’s largest models carry one million tokens and OpenAI’s GPT-5.6 models carry 1.05 million, so neither holds a meaningful advantage on document length.

A pricing row was researched for this table and left out. OpenAI’s pricing page returned HTTP 403 to automated retrieval on 18 and August 2026, so the ChatGPT figures could not be confirmed against the vendor. An unverified row would have been worse than a missing one.

Where Claude has the edge: edits delivered as tracked changes inside a Word document rather than described in a chat window, and a consumer-tier training default that is opt-in rather than opt-out.

Where ChatGPT has the edge: a marginally larger context window at 1.05 million against one million, which carries no practical consequence at these scales, a broader third-party plugin ecosystem, and a deeper native position for teams already standardised on Microsoft 365 Copilot.

Both vendors hold ISO/IEC 42001 for AI management systems, which clears the same procurement bar rather than distinguishing either. Neither replaces Westlaw or LexisNexis. Neither provides repeating workflow automation, playbook enforcement or post-signature obligation tracking.

When to Use Claude vs Purpose-Built Legal AI

Lawyers should use Claude for exploratory research, first-draft document generation and one-off document analysis. Purpose-built legal AI handles repeating contract workflows, playbook enforcement, obligation tracking and business team self-serve within legal guardrails.

That split is the third group above, stated as a buying decision. Claude works session by session, from an empty context each time. Operational contract management runs continuously, across teams who are not lawyers and should not need one for a standard NDA.

Claude is good at exploratory, one-off legal work. Platforms like Miramis are purpose-built for operational contract management, covering the repeating workflows where Sales, HR and Procurement generate and manage contracts without a legal bottleneck. Miramis enforces playbooks automatically, tracks obligations after signature, and provides a searchable repository with renewal alerts.

Integration is the objection that used to settle this question and no longer does. Claude reaches Microsoft 365 through Office add-ins and SharePoint, OneDrive and Outlook through Model Context Protocol connectors, though no native connector into legal practice management software appears in Anthropic’s own documentation. A connector opens a contract in SharePoint. What it does not do is route that contract for approval against a Delegation of Authority, enforce a clause library, or raise an alert ninety days before a renewal window closes. That is contract workflow automation, and it is a different thing from access. The distinction is not reach, it is process ownership.

Claude handles one-off legal work. Miramis is built for repeating contract workflows, where Sales, HR and Procurement teams generate and manage contracts without a legal bottleneck. Book a demo to see how Miramis enforces playbooks, tracks obligations, and gives legal full visibility without doing everything itself.