Practical AI Guide for Legal Work
How to Use Claude for Lawyers: Drafting, Review, and Research Support
A document-heavy profession meets a model built to read long documents carefully.
Legal work runs on documents: contracts, briefs, memos, discovery files, regulatory filings. Anthropic's Claude can speed up the document-heavy parts of that work, from first-pass contract review to plain-language client summaries, while the judgment calls stay with you. This page covers where it genuinely helps, where it doesn't, and how to keep your professional responsibility obligations intact while you use it.
How to use Claude for lawyers comes down to treating it as a fast, careful first-pass assistant, not a substitute for legal judgment. It reviews contracts against a checklist you give it, compares clause versions, drafts memo sections, and turns dense agreements into plain-language summaries clients can actually read. It handles long documents well without losing track of defined terms. Claude does not retrieve current case law and cannot verify statutes have been amended, so any citation it produces needs confirmation in Westlaw, Lexis, or an equivalent source before it goes anywhere near a filing.
Published · Last reviewed
Free lesson · no account neededThe Iteration LoopMaster the Essentials6 minStart the free lessonKey Takeaways
- Claude is strongest on document-heavy tasks: first-pass contract review, clause comparison, and plain-language summaries, not on retrieving current case law.
- Every citation Claude produces needs verification in an authoritative legal database before it reaches a brief, memo, or filing.
- Specific prompts naming the contract type, perspective, and exact clauses to flag produce far more usable output than a general 'review this' request.
- Confidentiality depends on which Claude product and data terms your firm has agreed to. Check your firm's policy and your jurisdiction's ethics guidance before pasting client documents.
- Claude drafts; you decide. Professional responsibility for accuracy, confidentiality, and supervision does not shift to the tool.
What to Hand to Claude vs. What Stays With You
| Task | Claude's Role | Attorney's Role |
|---|---|---|
| Contract review | Reads the full document and flags clauses against your checklist | Confirms the flags are accurate, adds judgment calls the checklist missed, decides what to negotiate |
| Legal research | Organizes cases or statutes you provide and drafts argument outlines | Retrieves and verifies every citation in an authoritative database before it's used |
| Client communication | Drafts a plain-language summary of a document or decision | Reviews the draft for accuracy and tone, and is the one who sends it |
| Drafting | Produces a first-draft memo, brief section, or standard contract | Edits for firm standards, verifies the law, and takes ownership of the final version |
Copy and Paste
Prompts You Can Use Today
First-pass contract review against a checklist
You are reviewing a [SaaS vendor agreement] on behalf of the [buyer]. Read the full contract and flag every clause that limits our right to audit vendor data handling, caps liability below [three times annual fees], allows auto-renewal without at least [90 days] notice, or assigns IP ownership to the vendor. For each flag, quote the clause, cite the section number, and explain the risk in one sentence.
Swap the bracketed contract type, party perspective, and specific thresholds for your own deal terms.
Clause comparison between two contract drafts
Compare [Version 1] and [Version 2] of this [master services agreement] and produce a table of every substantive change between them. Ignore formatting, whitespace, and typo fixes. For each change, note the section, summarize what changed in plain language, and flag whether the change favors [our company] or the counterparty.
Paste both versions in full; Claude works from what you give it, not from memory of the document.
Plain-language summary for a client
Summarize this [settlement agreement] for a client with no legal background. Explain in plain English what they are agreeing to, what they give up, what they receive, and any deadlines they need to track. Keep it under [400 words], avoid legal jargon, and flag anything that needs my review before it goes out.
Always review the summary yourself before it reaches the client; treat it as a draft, not a finished communication.
First-draft section of a legal memo
Draft the [statement of facts] section of a legal memo on [the issue you're researching], based on these facts: [paste facts]. Write for an internal audience of attorneys familiar with [jurisdiction] law. Use a neutral, factual tone, organize chronologically, and flag any fact that seems disputed or unclear so I can verify it.
Give Claude the raw facts rather than asking it to recall or infer facts on its own.
Organizing research you've already gathered
I've pasted the text of [five cases] below on the topic of [the legal issue]. Identify the common legal test each case applies, note where the cases agree or diverge, and outline a two-sided argument structure I could use in a brief. Do not add any case law beyond what I've provided.
The instruction not to add outside case law matters. It keeps Claude working from verified source material instead of guessing at citations.
Sorting a discovery batch
Here are summaries of [50 documents] from a discovery production related to [the dispute]. Categorize them into groups such as privileged, responsive, non-responsive, and needs-attorney-review, and give a one-sentence reason for each categorization so I can spot-check your work before finalizing it.
Useful for triage on large productions; an attorney should still spot-check the privileged and borderline categories.
Start Here
The First Three Lessons for Legal Work
These three lessons build the habits that make Claude useful on documents: iterating instead of accepting the first draft, reading long files accurately, and knowing exactly where its judgment stops.
Core Use Cases
Where Claude Fits Into a Law Practice
These are the document-heavy tasks where Claude's long-context reading and instruction-following make a concrete difference this week, not someday.
First-Pass Document Review
Feed Claude a contract and a checklist of clauses to flag. It reads the full document, surfaces missing provisions, and notes anything that deviates from your standard positions.
Clause Comparison
Give Claude two versions of an agreement and ask it to identify every substantive change. It produces a plain-language diff faster than a manual redline pass.
Plain-Language Client Summaries
Claude translates a dense agreement or court order into a summary a non-lawyer client can read and act on. You review and approve before it goes out.
First-Draft Memo and Brief Sections
Describe the legal issue, the relevant facts, and the jurisdiction. Claude produces a structured first draft you then research-check, edit, and own.
Research Organization
Claude can synthesize a set of cases or statutes you paste in, identify themes, and outline arguments. It does not replace a verified legal research platform for citation accuracy.
Discovery and Due Diligence Sorting
In large document sets, Claude helps categorize and summarize batches of materials so attorney time goes to the items that actually matter.
How to Write a Prompt for Contract Review
Getting Useful Output Instead of a Generic Summary
Specificity is everything with document review. A prompt like 'review this contract' produces a generic response that reads like a law school outline. A prompt like 'review this SaaS agreement for a vendor and flag any clause that limits our ability to audit data processing, caps liability below three times annual fees, or auto-renews without 90 days notice' produces something you can actually use as a starting point, because you've told Claude exactly what a problem looks like.
Name the contract type, the party perspective, and the exact provisions that concern you. Claude doesn't know whether you're representing the buyer or the seller unless you say so, and a clause that's a risk for one side is standard for the other. The more constraints you provide up front, the less editing the output needs afterward.
For drafting tasks, give Claude the facts, the audience, the jurisdiction, and the standard you're trying to meet. Tell it which sections to write and which to leave for you. If you already have a template or a firm-standard clause, paste it in and ask Claude to match that structure rather than inventing its own.
Use Claude iteratively rather than expecting a finished product on the first pass. Paste in its draft, mark what needs to change, and ask it to revise. This is usually faster than starting over, and it lets you steer the output toward your firm's voice and standards without rewriting from scratch. This iterative back-and-forth is worth practicing deliberately; it's the whole idea behind the Iteration Loop lesson in the starter path below.
Worked Example
A First-Pass Review of a Vendor Agreement, Start to Finish
Say you're on the buyer's side of a new SaaS vendor agreement and you have a standing checklist of five issues your firm always checks: audit rights, liability caps, auto-renewal terms, data processing obligations, and termination for convenience. Paste the full agreement into Claude along with that checklist, framed as a specific instruction rather than an open-ended request.
Claude reads the document in full, including definitions and cross-references, and returns findings organized by your checklist items rather than by the contract's own section order. For each flag, it quotes the relevant language, cites the section number, and gives a one-sentence explanation of the risk. That structure matters because it lets you scan the output quickly and go straight to the sections that need attorney attention.
From there, the work is yours. You verify each flag against the actual clause language, decide which points are worth pushing back on with the vendor, and draft the redline. Claude's output is the first pass that gets you to that decision point faster; it doesn't make the decision, and it doesn't know your client's risk tolerance or the leverage you have in the negotiation.
The same pattern extends to clause comparison. If the vendor sends back a revised draft, you can hand Claude both versions and ask for a table of every substantive change, which is often faster than a manual line-by-line comparison, especially on a long agreement where the changes are scattered across many sections. You still confirm the table is accurate before relying on it in a call with the client.
Getting Started
The First Three Lessons, and How They Map to Your Work
The fastest way to get comfortable with Claude on legal documents is to work through three specific lessons in order, each one tied directly to something above. Start with The Iteration Loop, a 6-minute lesson in Master the Essentials that teaches the back-and-forth pattern described in the prompt-writing section: draft, mark what's wrong, revise, repeat. This is the habit that turns a mediocre first draft into something usable, and it applies just as much to a memo section as it does to a client summary.
From there, move to Document Analysis, a 7-minute lesson also in Master the Essentials. This is where you practice the exact workflow from the worked example above: feeding Claude a long document and a specific set of things to look for, and getting structured findings back instead of a vague summary. If you do nothing else on this page, working through this lesson with an actual contract from your own practice will tell you more than reading about it here.
Finish with Claude's Strengths & Limits, a 6-minute lesson in Why Claude?, which covers exactly the boundary this page keeps returning to: what a model like Claude is reliable at and what it isn't, so you're not guessing about where to double-check its work. Together these three lessons cover the habit of iterating, the skill of document review, and the judgment of knowing where Claude's limits are, which is most of what you need before you bring it into real client work.
Professional Responsibility
Guardrails Worth Following Before You Start
Check Your Ethics Guidance First
Your state bar or law society may have issued guidance on AI tools and confidentiality. Read it, and check your firm's own AI use policy, before you put any client information into Claude.
Never Submit an Unverified Citation
If Claude names a case or statute, look it up in Westlaw, Lexis, or an equivalent authoritative source before it goes into a brief or memo. Courts have sanctioned attorneys for unverified AI-generated citations.
Disclose When Required
Some jurisdictions and clients require disclosure when AI tools are used in their matters. Know your obligations and keep a record of your workflow.
Keep a Human in Every Loop
Claude drafts; you decide. No AI output should reach a client, a court, or opposing counsel without attorney review and sign-off.
Honest Limits
What Claude Is Bad at in Legal Work
Claude does not have access to live legal databases. It cannot retrieve a current version of a statute, confirm a case hasn't been overturned, or check a court's local rules on filing formats. Any legal proposition it states is drawn from patterns in its training, not from a live check against the law as it stands today, which is exactly why citation verification isn't optional.
It's also unreliable on anything that requires access to material it hasn't been given. Claude cannot pull a document from your firm's case management system, check a court's docket, or know what happened in a call you had with opposing counsel unless you tell it. Treat it the same way you'd treat a very well-read associate on their first day at your firm: capable, but starting from zero context on your specific matter until you provide it.
Finally, Claude lacks the contextual judgment that experience gives a practicing attorney: it can't assess witness credibility, weigh litigation risk against a client's business goals, or make a strategic call about when to settle versus litigate. Those decisions depend on relationships, incentives, and history that exist outside any document you could paste in, and they remain squarely attorney territory, no matter how good the tool gets at reading and summarizing the paperwork around them.
Start the First Free Lesson
Reading about what Claude can do and actually using it well on a real contract are two different things. The Nightschool AI curriculum walks through prompt construction and document workflows hands-on, starting with the exact lesson referenced above.
Frequently Asked Questions
Is Claude safe to use with confidential client documents?
That depends on which Claude product you use and what your firm's policy allows. Different Claude products carry different data handling terms. Before using any AI tool with client information, check your jurisdiction's ethics opinions on cloud processing of client data and confirm with your firm's risk management team. Confidentiality obligations apply regardless of the tool.
Can Claude replace legal research?
No. Claude does not have access to live legal databases and cannot retrieve current case law or confirm whether a statute has been amended. It can help you organize research you provide, identify argument structures, and draft around legal concepts, but every citation and legal proposition it produces must be verified in an authoritative research platform before you rely on it professionally.
What kinds of contracts is Claude best at reviewing?
Claude handles standard commercial contracts well: SaaS agreements, NDAs, service agreements, employment contracts, and similar documents with recognizable clause structures. You get the most value by giving it a specific checklist rather than asking for a general review. Highly specialized or jurisdiction-specific documents still need an attorney who knows that area deeply.
Will Claude hallucinate legal citations?
It can. Large language models sometimes produce plausible-sounding case names and citations that don't exist or don't say what the model claims. This is a known risk across AI systems, not unique to any one product. Treat every citation Claude generates as unverified until you've looked it up in Westlaw, Lexis, or an equivalent source.
How do I write a good prompt for contract review?
Be specific about what you're looking for. Name the contract type, the party perspective, and the exact provisions that concern you. For example: 'Review this vendor agreement from the buyer's perspective. Flag any clause that limits our right to audit, excludes consequential damages, or restricts our ability to terminate for convenience.' Specific instructions produce specific, usable output.
Can Claude draft a full contract from scratch?
It can produce a first draft of a standard agreement given a clear description of the deal terms, parties, and jurisdiction. The output still needs attorney review, editing to match your firm's standards, and verification that the clauses reflect current law. Use it as a starting point, not a finished product.
Does using Claude change my professional responsibility obligations?
No. Your duties of competence, confidentiality, supervision, and candor to the tribunal apply regardless of the tools you use. Bar guidance in many jurisdictions has clarified that attorneys remain responsible for AI-assisted work. Using Claude well is a competence question; submitting its output without review is a professional responsibility risk.
What is Claude bad at for legal work?
Claude is not reliable for up-to-date statutory or regulatory research, precise citation retrieval, jurisdiction-specific procedural rules, or tasks requiring access to documents it hasn't been given. It also lacks the contextual judgment to assess litigation risk, evaluate credibility, or advise on strategy. Those remain squarely in attorney territory.
Build the habits before you rely on them
Practical, document-focused training that starts with the first lesson.