20 Claude Prompts for Lawyers That Sharpen Every Brief

<context> Contract type: [NDA / SaaS agreement / employment contract / vendor agreement / other] My role: [buyer / seller / employer / employee / service provider / client] Jurisdiction: [governing law stated in contract, or your jurisdiction] Deal size / stakes: [approximate value or strategic importance] </context> <task> Review this contract and identify every clause that creates risk for my position: [PASTE CONTRACT TEXT] For each risk found, provide: 1. The clause (quoted verbatim) 2. Why it's risky — specific harm scenario 3. Risk rating: High / Medium / Low 4. Suggested redline — exact replacement language 5. Negotiating note — how to frame the ask to the other side </task> <constraints> - Flag one-sided indemnification, unlimited liability, automatic renewal traps, and unilateral modification rights - Identify any missing standard protections (IP ownership, confidentiality carve-outs, limitation of liability caps) - Note any ambiguous definitions that could be interpreted against my position - Do not provide legal advice — flag issues for attorney review - Present findings in a table: Clause | Risk | Rating | Suggested Fix </constraints>

<context> NDA type: [mutual / one-way] My position: [disclosing party / receiving party / both] Industry: [tech / finance / healthcare / other] Duration requested: [years] </context> <task> Compare these two NDA versions and tell me which is more favorable to my position: VERSION A: [PASTE NDA VERSION A] VERSION B: [PASTE NDA VERSION B] For each key section (definition of confidential information, exclusions, obligations, term, remedies, permitted disclosures): 1. How Version A defines it 2. How Version B defines it 3. Which is better for me and why 4. Recommended language if neither version is ideal </task> <constraints> - Pay special attention to the definition of "Confidential Information" — broad vs. narrow definitions have major practical impact - Flag any perpetual obligations or provisions that survive termination - Identify which version has stronger enforcement mechanisms - Note any missing standard exclusions (publicly known info, independently developed, compelled disclosure) </constraints>

<context> Audience: [business executive / startup founder / client / non-legal staff] Contract type: [service agreement / license / employment / partnership] Key questions they care about: [e.g. "what are we committed to?", "can we exit?", "who owns what?"] </context> <task> Summarize this contract in plain English for a non-lawyer audience: [PASTE CONTRACT] Structure the summary as: 1. What this agreement does (2-3 sentences) 2. Our key obligations — what we must do 3. Their key obligations — what they must do 4. Money: payment terms, amounts, refund rights 5. How to exit: termination rights, notice periods, fees 6. Ownership: who owns IP, work product, data 7. Biggest risks for us (top 3, plain English) 8. Anything that requires an urgent decision or deadline </task> <constraints> - No legal jargon — if a term must be used, define it in parentheses - Keep total summary under 500 words - Use bullet points, not paragraphs - Bold the most important takeaway in each section - Add a "Before you sign" checklist at the end </constraints>

<context> Contract type: [SaaS / consulting / employment / real estate / M&A / other] Transaction value: [approximate] Jurisdiction: [state/country] My role: [which party I represent] </context> <task> Review this contract for missing or inadequately addressed provisions: [PASTE CONTRACT] Check for the presence and adequacy of: 1. Limitation of liability and liability cap 2. Indemnification and its scope 3. Intellectual property ownership and assignment 4. Confidentiality / non-disclosure obligations 5. Dispute resolution (arbitration, jurisdiction, choice of law) 6. Force majeure 7. Assignment and change of control restrictions 8. Representations and warranties 9. Term, renewal, and termination rights 10. Data privacy obligations (if applicable) For each item: Present / Missing / Inadequate — and provide draft language for anything missing or weak. </task> <constraints> - Provide specific suggested language, not just descriptions - Prioritize gaps by risk level: Critical / Important / Nice-to-have - If a provision exists but is one-sided, flag it as "Present but Unfavorable" - Keep suggested language concise — 2-4 sentences per clause </constraints>

<context> Legal issue: [describe the specific legal question — e.g. "enforceability of non-compete agreements for remote workers in California"] Jurisdiction: [federal / state — specify] Time frame: [recent cases only / all relevant precedent] Purpose: [memo / brief / client advice / internal research] </context> <task> Research and summarize the relevant case law on this issue: [LEGAL QUESTION] Provide: 1. The controlling legal standard — what courts apply to decide this issue 2. Key cases — for each: case name, year, court, holding, and why it matters 3. Majority rule vs. minority/split positions if applicable 4. How recent cases have evolved the standard 5. Jurisdiction-specific nuances 6. Practical takeaway — how courts are likely to rule on facts like mine </task> <constraints> - Flag if you are uncertain about any case citation — I will verify all citations independently - Distinguish between binding precedent and persuasive authority - Note any circuits or states where the law is unsettled - Focus on holdings, not dicta, unless the dicta signals a doctrinal shift - Keep case summaries to 3-4 sentences each </constraints>

<context> Statute: [name, section, jurisdiction] Client situation: [brief description of the facts relevant to the statute] Question presented: [specific legal question the statute must answer] Audience: [supervising partner / client / court / regulatory body] </context> <task> Analyze how [STATUTE] applies to these facts: [DESCRIBE FACTS] Structure the analysis as: 1. Relevant statutory text (quote exactly) 2. Key defined terms and how courts/agencies interpret them 3. Elements required for the statute to apply — and whether each is met on these facts 4. Regulatory guidance or agency interpretations (if any) 5. Cases interpreting this statute on similar facts 6. Application to our facts — conclusion and confidence level 7. Arguments the other side would make and how to counter </task> <constraints> - Quote the statute verbatim before analyzing — don't paraphrase the text - Flag any ambiguities in the statutory language that create interpretive risk - Note if there are proposed amendments or pending regulatory changes - Conclude with a clear recommendation, not just a recitation of the law </constraints>

<context> Industry: [healthcare / finance / tech / real estate / other] Regulations applicable: [HIPAA / GDPR / SEC rules / CCPA / other — list all known] Business activity: [describe what the company does that triggers compliance obligations] Jurisdiction: [federal + state(s)] </context> <task> Create a compliance checklist for a company engaged in [BUSINESS ACTIVITY] under [APPLICABLE REGULATIONS]: For each regulation: 1. Key obligations that apply to this business 2. Specific actions required (not general descriptions — exact steps) 3. Documentation that must be maintained 4. Deadlines or renewal requirements 5. Penalties for non-compliance 6. Compliance status column: Compliant / Gap / Unknown Format as a table with a priority column (Critical / High / Medium / Low). </task> <constraints> - Tailor to the specific business activity — no generic checklists - Flag any obligations with imminent deadlines or recent regulatory changes - Include both affirmative duties and prohibitions - Note where outside counsel or specialized compliance professionals are required - Add a "Quick wins" section: 5 items that can be addressed immediately at low cost </constraints>

<context> Case type: [contract dispute / employment / IP / personal injury / other] My client's position: [brief summary] Stage of litigation: [pre-suit / motion practice / trial prep / appeal] Jurisdiction: [court and applicable law] </context> <task> Analyze the opposing party's likely arguments and help me prepare responses: MY CASE FACTS: [DESCRIBE YOUR FACTS AND POSITION] OPPOSING BRIEF / ARGUMENTS (if available): [PASTE OR DESCRIBE OPPOSING ARGUMENTS] For each opposing argument: 1. State their argument clearly and charitably 2. Rate its strength: Strong / Moderate / Weak — with reasoning 3. Best legal response (case law, statutory text, or factual rebuttal) 4. Any concessions I should consider to strengthen my overall position 5. Preemptive moves — how to undercut this argument before they raise it </task> <constraints> - Steel-man opposing arguments before rebutting — weak rebuttals to strong arguments hurt credibility - Identify which arguments are purely legal vs. fact-dependent - Flag any arguments where I have weak case law and need a policy/equity argument instead - Suggest the order in which to address arguments for maximum persuasive effect </constraints>

<context> Contract type: [the agreement this clause will go into] Clause needed: [e.g. limitation of liability, IP assignment, non-solicitation, data processing] My position: [which party I represent and what outcome I want] Jurisdiction: [governing law] Deal context: [any relevant facts — deal size, relationship type, industry] </context> <task> Draft a [CLAUSE TYPE] clause for my position as [MY ROLE]: Provide: 1. Standard version — balanced language likely to be accepted 2. Aggressive version — maximally favorable to my position 3. Fallback version — minimum acceptable terms 4. Explanation of each key term and why it matters 5. Common pushbacks from the other side and how to respond </task> <constraints> - Use precise legal language, not plain English (this is for the contract, not a summary) - Ensure the clause integrates with standard definitions (capitalize defined terms) - Flag any jurisdiction-specific requirements that affect enforceability - Aggressive version should be firm but not so extreme it damages negotiating credibility - Include optional bracketed additions that can be inserted for higher-stakes deals </constraints>

<context> Dispute type: [breach of contract / unpaid invoice / property damage / employment / IP infringement / other] My client: [brief description] Opposing party: [name and relationship to client] Facts: [what happened, when, amounts involved] Prior attempts to resolve: [calls, emails, prior notices — and responses] Desired outcome: [payment, specific performance, cease and desist, other] Deadline: [how many days to respond] </context> <task> Draft a demand letter that: 1. States the facts clearly and chronologically 2. Identifies the specific legal basis for the claim (breach, statute, common law) 3. States the specific demand (amount, action, deadline) 4. Describes consequences of non-response without overstating 5. Preserves all legal rights and remedies 6. Maintains a professional, firm tone — not threatening or emotional </task> <constraints> - Tone: firm and professional, not aggressive or emotional - Do not make threats you cannot back up (e.g., "criminal charges" if only civil remedies exist) - Include a specific dollar amount or action, not vague demands - Add a sentence preserving all rights and remedies - Length: 400-600 words — concise but complete - Format for a law firm letterhead (date, recipient address, Re: line, signature block) </constraints>

<context> Motion type: [motion to dismiss / summary judgment / preliminary injunction / motion in limine / other] Court: [federal district / state court — specify] Procedural posture: [stage of case] My position: [moving party or opposing party] Key legal arguments: [list your 2-4 strongest points] Page limit: [if any] </context> <task> Create a detailed outline for a [MOTION TYPE] brief arguing [MY POSITION]: For each section: 1. Heading and sub-headings (formatted as they would appear in the brief) 2. Key arguments to make in that section 3. Cases to cite (with a note on what they stand for) 4. Factual record cites needed (what evidence supports this section) 5. Anticipated counter-arguments and where to address them Also provide: - Recommended argument order for maximum persuasive impact - Which arguments to lead with vs. preserve as fallback - Introduction paragraph draft </task> <constraints> - Follow [CIRCUIT/STATE] formatting conventions - Lead with the strongest argument, not the first chronologically - Each point heading must be a complete sentence stating the conclusion, not a topic label - Flag any arguments that require a supporting affidavit or exhibit </constraints>

<context> Email type: [settlement demand / discovery dispute / scheduling / client update / opposing counsel response / court communication] Recipient: [opposing counsel / client / judge's clerk / mediator] Relationship tone: [adversarial / collaborative / neutral] Key message: [what I need to communicate or request] Prior context: [what has happened so far in this matter] </context> <task> Draft a professional legal email that: 1. States the purpose clearly in the first sentence 2. Provides necessary context concisely 3. Makes the specific request or communicates the key message 4. Closes with a clear next step or deadline 5. Preserves the appropriate professional tone for [RECIPIENT TYPE] Also provide: - Subject line (specific, not generic) - One-line alternate subject line option - A shorter version of the email if it exceeds 200 words </task> <constraints> - No legal jargon in client emails; technical precision in attorney-to-attorney emails - Avoid anything that could be quoted against your client out of context - If making a threat or demand, make it specific and defensible - Close with a specific deadline when a response is needed - Flag any statements that should be labeled "without prejudice" or "for settlement purposes only" </constraints>

<context> Company type: [SaaS / e-commerce / healthcare app / B2B / other] Data collected: [list types — email, payment, health data, location, etc.] Users: [US only / EU / global] Applicable regulations: [GDPR / CCPA / HIPAA / COPPA / other] Current privacy policy: [paste below or say "none yet"] </context> <task> Analyze this privacy policy against [APPLICABLE REGULATIONS] requirements: [PASTE PRIVACY POLICY] For each regulatory requirement: 1. Is it addressed? Yes / Partially / No 2. If partial or missing — what specifically is required 3. Suggested language to add or replace 4. Risk level if not fixed: Critical / High / Medium / Low Also flag: - Any statements that are legally risky or inconsistent with actual practices - Missing disclosures that regulators most commonly cite in enforcement actions - A prioritized remediation roadmap (fix these first) </task> <constraints> - Tailor to the specific regulations listed — not a generic privacy checklist - Quote the existing policy text when flagging specific problems - Keep suggested replacement language concise and legally sound - Note any provisions that require a lawyer to finalize (e.g., data processing agreements under GDPR Art. 28) </constraints>

<context> Company size: [number of employees] States of operation: [list all states where you have employees] Review scope: [hiring practices / termination / wage & hour / leave policies / discrimination policies / all] Current policy document: [paste or describe] </context> <task> Review our employment practices for legal compliance risks: CURRENT PRACTICES / POLICIES: [DESCRIBE OR PASTE POLICIES] Identify: 1. Violations or likely violations of federal employment law (FLSA, FMLA, ADA, Title VII, NLRA) 2. State-specific requirements we're missing for each state listed 3. Policies that are legally permissible but create litigation exposure 4. Recent legal changes (2024-2026) that require policy updates 5. Documentation gaps — what records we must keep but aren't 6. Priority remediation list ranked by legal risk </task> <constraints> - Flag multi-state conflicts — where a practice compliant in one state is illegal in another - Distinguish between "must fix immediately" and "best practice" improvements - Note any issues that require employment counsel to address (not just policy edits) - Pay special attention to classification issues (exempt/non-exempt, contractor/employee) </constraints>

<context> Business type: [describe what the company does] Transaction or activity being assessed: [specific deal, product launch, new market entry, etc.] Known legal concerns: [any issues you are already aware of] Stakeholder audience: [board / legal team / executive / investors] </context> <task> Build a legal risk assessment matrix for [TRANSACTION/ACTIVITY]: For each identified risk area: 1. Risk description — specific legal exposure, not a general category 2. Likelihood: High / Medium / Low — with reasoning 3. Impact if it materializes: Critical / Significant / Moderate / Minor 4. Current mitigation in place (if any) 5. Recommended mitigation action 6. Residual risk after mitigation: Acceptable / Needs Monitoring / Unacceptable 7. Owner — who is responsible for this risk Present as a table. Add an executive summary (3-4 sentences) with the top 3 risks and recommended actions. </task> <constraints> - Be specific — "contract breach risk" is not useful; "risk that [X clause] is unenforceable in California" is - Do not list every theoretical risk — focus on material, realistic exposures - Flag any risks that should be disclosed to investors or a board - Include a "risk appetite" note: which risks are worth taking given the business upside </constraints>