Legal Document Review

What You’ll Learn

• How to use Claude to quickly map the structure and key provisions of unfamiliar legal documents
• Techniques for identifying one-sided clauses, unusual terms, and potential risks in contracts
• How to prepare informed questions for your attorney, even when you can’t afford full legal review on every document

The Use Case

Most people encounter legal documents in moments of time pressure: a vendor contract that needs to be signed before a project starts, a software license agreement that’s 40 pages long, a lease with unfamiliar clauses, or a terms of service for a new tool your team is adopting. The practical reality is that most of these documents don’t get read — they get signed. This is where Claude can make a meaningful difference.

Claude doesn’t replace a lawyer. For high-stakes agreements — employment contracts, equity documents, major commercial contracts, litigation-related documents — you need qualified legal counsel. But Claude can be an invaluable first pass: helping you understand what you’re looking at, identifying provisions that deserve attention, flagging clauses that are unusual or one-sided, and preparing you to have a more productive (and therefore less expensive) conversation with your attorney.

The most common use cases: a startup founder reviewing an enterprise customer contract before signing, a freelancer reviewing a client’s Master Service Agreement, a small business owner reviewing a vendor SLA, a developer reviewing an API terms of service to understand data rights, or a team lead reviewing an NDA before sharing sensitive information with a prospective partner. In each case, the goal is comprehension and risk awareness — not legal advice.

Critical disclaimer: Claude is not a lawyer and cannot provide legal advice. Its analysis of legal documents reflects general knowledge about common contract provisions, not jurisdiction-specific law or advice tailored to your specific circumstances. Always consult a qualified attorney for important legal decisions.

Step-by-Step Guide

Step 1: Identify the Document Type and Your Position

Different legal documents have different risk profiles and different things to watch for. Before pasting any document, tell Claude:

• What type of document it is (NDA, SaaS subscription agreement, employment contract, licensing agreement, commercial lease, terms of service, etc.)
• Your position in the agreement (are you the vendor or customer? employer or employee? licensor or licensee?)
• The context (what’s the business relationship, what are you getting, what are you giving?)
• What concerns you most (liability exposure, IP ownership, data rights, termination rights, payment terms)

Your position in the agreement determines which clauses are most likely to affect you adversely. A limitation of liability clause that protects a software vendor is the same clause that limits your remedies as their customer.

Step 2: Request a Structural Overview First

Before asking Claude to identify risks, ask for a structural overview. This gives you a mental map of the document before diving into details:

“Please provide a section-by-section overview of this agreement. For each section, give: the section name, a one-sentence description of what it covers, and a 1–5 risk flag (5 = high, 1 = routine). This overview will help me prioritize where to focus my attention.”

This step is especially useful for long documents (10+ pages). It surfaces which sections are boilerplate versus which sections contain the unusual or high-stakes terms.

Step 3: Extract and Explain Key Clauses

Once you have the structural overview, ask Claude to extract and explain the clauses that matter most for your situation. Common high-priority clause categories:

For service agreements and SaaS contracts:

• Limitation of liability: What’s the cap? Is it mutual? Are consequential damages excluded?
• Indemnification: Who indemnifies whom for what? Are IP infringement claims covered?
• Data rights and privacy: What data does the vendor collect? How can they use it? Who owns it?
• Termination: What triggers termination? Is there cure period? What happens to your data after termination?
• Auto-renewal and cancellation: How much notice is required? What are the financial consequences?

For NDAs:

• Definition of confidential information: Is it too broad? Too narrow? Does it include verbal disclosures?
• Exclusions: Standard carve-outs for publicly available info, independently developed info, legally required disclosure?
• Duration: How long does the obligation last? Is it reasonable for the type of information?
• Return or destruction: What happens to confidential information when the relationship ends?
• Residual knowledge: Is there a “residual clause” that allows signatories to use information retained in unaided memory?

For employment contracts:

• Non-compete: Geographic scope, duration, industry scope — is it enforceable in your jurisdiction?
• IP assignment: Does it cover only work-related IP, or all inventions during your employment?
• Non-solicitation: Does it cover customers, employees, or both? For how long?
• At-will vs. for-cause termination: What protections do you have?
• Severance: What are you entitled to if terminated without cause?

Step 4: Ask for Red Flag Analysis

After understanding the structure and key clauses, ask Claude to identify anything unusual or one-sided:

“Based on this agreement, what clauses are notably one-sided in favor of [the other party]? What provisions are unusual compared to standard industry practice? What rights am I waiving that I might not expect to be waiving?”

Claude’s knowledge of common contract norms is useful here — it can identify when a limitation of liability cap is unusually low, when an indemnification clause is unusually broad, when a data rights provision grants the vendor more rights than typical, or when a non-compete is unusually restrictive.

Ask also: “Are there any clauses that appear in the other party’s favor that you would expect to also appear in my favor, but don’t? (Look for asymmetries.)”

Step 5: Generate Questions for Your Attorney

For significant contracts, the goal is not to understand every word yourself — it’s to identify the questions you need answered before signing. Ask Claude:

“Based on your analysis of this agreement, generate a list of 8–10 specific questions I should ask my attorney before signing. Prioritize them by importance.”

This is one of the highest-leverage uses of Claude in legal document review. A well-prepared client asks better questions, gets faster answers, and spends less time (and money) in attorney meetings. If you can walk into a legal review meeting with 10 specific, well-framed questions, you will get much more value from the session.

Step 6: Draft a Summary for Stakeholders

If you need to brief colleagues or leadership on a contract you’re reviewing, ask Claude to write a plain-language summary:

“Write a plain-English summary of this agreement for a non-lawyer executive. Focus on: what we’re committing to, what protections we have, what our main risks are, and what I’d recommend we push back on before signing.”

This is particularly useful for procurement teams, startup founders, and business leads who need to make sign/negotiate/reject decisions quickly.

Prompt Template

Please review the following [document type: NDA / SaaS agreement / employment contract / vendor contract / terms of service].

**My context**:
- My position: [e.g., I am the customer / the employee / the licensor]
- The other party: [e.g., a software vendor / a prospective employer / a client]
- What this agreement governs: [brief description]
- My primary concerns: [e.g., data rights, liability exposure, IP ownership, termination flexibility]

Here is the document:
[Paste full document text]

**Analysis I need**:

1. **Structural overview**: Section-by-section summary with a 1–5 risk flag for each section (5 = high, 1 = routine).

2. **Key clauses**: Extract and explain in plain English the following clause types: [list the ones most relevant to your document type from the guide above].

3. **Red flags**: Identify any provisions that are: (a) unusually one-sided in the other party's favor, (b) unusual compared to standard industry practice, or (c) rights I'm waiving that I might not realize.

4. **Missing protections**: Are there any standard protections I would typically expect in this type of agreement that are absent?

5. **Attorney questions**: Generate 8 specific questions I should ask my attorney before signing this agreement, ordered by priority.

6. **Plain-language summary**: Write a 3-paragraph plain-English summary suitable for briefing a non-lawyer decision-maker.

Note: I understand this is not legal advice and I will consult an attorney for final review of this agreement.

Tips & Best Practices

1. Always flag the document type and your position — “Review this contract” produces generic output. “Review this SaaS subscription agreement where I am the customer, and I’m concerned about data rights and termination flexibility” produces targeted, useful analysis. The more context, the better the analysis.

2. Ask about missing clauses, not just problem clauses — Standard contracts have expected provisions. Ask Claude: “What clauses would I normally expect in this type of agreement that are not present?” Absence of a data deletion clause, a limitation of liability, or a dispute resolution mechanism can be as significant as a bad clause.

3. Use Claude to decode legal language, not just summarize it — When you encounter a clause you don’t understand, paste just that clause and ask: “Explain what this clause means in plain English, and give me an example of a real situation where it would be triggered.” Concrete examples make abstract legal language immediately comprehensible.

4. Compare versions when you’re negotiating — If you’re in a contract negotiation and the other party sends a revised draft, paste both versions and ask Claude: “What changed between version 1 and version 2 of this agreement? Were the changes favorable or unfavorable from my position?” This saves hours of manual comparison.

5. Prepare, don’t replace, attorney review — Use Claude to prepare for attorney review, not to replace it. High-stakes agreements (equity, employment, major commercial contracts) always deserve attorney review. But if you come to that review having already identified the key provisions and your specific questions, you’ll use attorney time far more efficiently — which usually means lower legal bills.

Try It Yourself

Find a terms of service or privacy policy for any software tool or website you currently use. These are publicly available legal documents. Paste it into Claude with this prompt:

“This is the terms of service for [product name]. I use this tool professionally. Please: (1) identify the top 3 provisions that most affect my rights as a user, (2) flag any clauses that grant the company unusual rights over my content or data, (3) identify what happens to my data if the company is acquired or shuts down, and (4) write a 2-sentence summary of what I’m agreeing to in plain English.”

Most people have never actually read the terms of service for tools they use daily. This exercise is often genuinely surprising — and it builds the habit of using Claude as a first-pass legal reader for any document you encounter.