What You Will Learn

• Explain Claude's capabilities, limitations, and how to manage hallucination risk.
• Set up persistent projects and craft system prompts for practice-specific results.
• Brief Claude effectively to produce focused, near-final drafts.
• Use Claude for document work: client summaries, red-flag checklists, comparisons, and extraction.
• Streamline drafting workflows: file notes, demand letters, engagement and counsel briefs.
• Apply professional responsibility: confidentiality, citation verification, and jurisdictional compliance.

Study Guide

Introduction: Why This Course Exists

Let's be honest about what the practice of law actually looks like. Law school didn't prepare you for the volume. Nobody warned you that the job would be roughly sixty percent reading documents you didn't write, drafting under time pressure, and explaining complicated things to clients who just want a straight answer. Pure legal reasoning,the stuff they tested you on in law school,might account for a third of your day. The rest is sheer volume management.

The lawyers who feel most stretched aren't overwhelmed because the work is intellectually difficult. They're stretched because the work is relentless. Across commercial litigation, construction, employment, tax, government, and in-house practice, the pattern repeats itself. Smart, capable attorneys drowning in documents, deadlines, and demands on their attention.

This course is about changing that ratio. Claude AI, when properly configured and deliberately deployed, fundamentally shifts how you handle the volume. Tasks that take thirty minutes become five-minute activities. The blank page problem,one of the most cognitively expensive obstacles you face daily,gets replaced with something substantive to react to and refine. Preparation work that usually gets squeezed out of overloaded schedules becomes manageable even during your most demanding weeks.

Here's what this course will teach you. First, what Claude actually is and isn't,the capabilities and the limitations, including the hallucination risk that keeps every responsible lawyer honest. Second, the foundational setup that separates lawyers who get transformative results from those who conclude the tool doesn't work. Third, the briefing principle,how to communicate with Claude the way you'd brief a capable colleague. Fourth, the five application areas where Claude delivers real value: document work, drafting, preparation, and the business of running a practice. Fifth, the professional responsibility guardrails that keep you safe and compliant.

The difference between disappointment and transformation lies almost entirely in setup and communication methodology. Lawyers who approach Claude with vague, search-query-style prompts receive generic, low-value responses and conclude the tool is ineffective. Lawyers who invest approximately fifteen minutes in establishing a structured project workspace with a comprehensive system prompt,and who learn to brief Claude properly,unlock a drafting and analysis partner of unprecedented capability.

Let's get into it.

Section 1: Understanding Claude,Capabilities and Limitations

Before you can use Claude effectively, you need to understand what you're actually working with. Most of the disappointment people experience with AI tools comes from misunderstanding what the tool is and isn't designed to do.

What Claude Is
Claude represents a fundamentally different category of tool from both traditional legal software and junior associates. Three capabilities define its value proposition.

First, it has a vast knowledge base. Claude has processed more contracts, case analyses, and legal correspondence than any individual practitioner could encounter in a lifetime. When you're dealing with an unfamiliar clause structure or an unusual contractual arrangement, Claude has likely seen variations of it thousands of times. This isn't the same as having a photographic memory of every case ever decided,it's pattern recognition at massive scale.

Second, it's available without limits. Claude doesn't get tired at 4 PM. It doesn't resent being asked to review a forty-page lease at 11 PM on a Sunday. It doesn't have billing constraints or utilization targets. It's simply there, ready to work, at any hour you need it. For lawyers whose schedules are dictated by court deadlines and client demands rather than business hours, this availability is transformative.

Third,and this is the critical distinction,Claude reasons and generates. A search engine retrieves existing documents. Claude doesn't retrieve; it reasons through problems and generates original content. You can ask it to draft a demand letter that has never existed before, tailored to facts it has never seen. You can ask it to model opposing counsel's likely negotiation positions. You can ask it to identify weaknesses in your trial strategy. This is generation, not retrieval. It's the difference between a library and a thinking partner.

What Claude Is Not
Equally important is understanding the tool's limitations. Three things Claude is not.

Claude is not a search engine. It does not retrieve documents or case law from a database. It generates responses based on patterns in its training data. This means it can produce inaccurate information with complete confidence. It won't tell you "I'm not sure about that citation" the way a careful associate would. It will simply give you an answer, and that answer might be wrong. This is the hallucination problem, and we'll address it head-on shortly.

Claude is not a magic button. Vague input produces generic output. If you type "summarize this contract" with no other context, you'll get a summary that reads like it was written for nobody in particular,because it was. Claude didn't know who you are, what kind of lawyer you practice, what your client needs, or what you'll do with the summary. The quality of results is directly proportional to the quality of the brief you provide. Garbage in, garbage out, as the programmers say.

Claude is not infallible. It makes mistakes. Sometimes it states legal propositions with full confidence that are wrong, imprecise, or only accurate in a different jurisdiction. It doesn't know what it doesn't know, and it won't flag uncertainty the way a careful lawyer would. This isn't a flaw you can engineer around; it's a reality you must manage through verification.

The Hallucination Imperative
Let's talk directly about hallucination, because it's the thing that keeps responsible lawyers honest when using AI. Hallucination is the phenomenon where AI generates confident but false or inaccurate information. Claude doesn't know what it doesn't know. It won't flag uncertainty the way a careful attorney would. If you ask it for a legal proposition and it's not sure, it will still give you an answer,and that answer might be confidently wrong.

Here's the rule that keeps you safe: for anything that matters,a citation, a legal conclusion, a date, a clause you're relying on,you verify against the primary source. This isn't optional. In a legal context, the consequences of not checking are professional consequences, and they're yours to carry, not Claude's.

But here's the perspective shift that makes this manageable: you were going to read the output anyway. You're a lawyer. Reviewing work before it goes out the door is what you do. It's not an additional burden; it's the job. Claude doesn't remove that step. It just makes everything that comes before it faster. The verification requirement isn't a reason to avoid AI,it's a reason to use it intelligently, knowing that the final review is your professional responsibility regardless of whether the first draft came from you, an associate, or an AI.

Let me give you a concrete example. Suppose you're drafting a motion and you ask Claude to identify the standard for summary judgment in your jurisdiction. It gives you an answer that sounds authoritative. It cites a case. The citation looks real. But is it? You need to check. You need to verify that the case exists, that it stands for the proposition Claude cited, and that it hasn't been overruled. This is the same diligence you'd apply to a junior associate's research. Claude is a powerful tool, but it's not a substitute for professional judgment.

Professional Obligations and Regulatory Compliance
The legal profession has been slower than most to embrace AI, and for good reason,the stakes are high and the ethical framework is still evolving. Most bar associations have now issued ethics opinions covering AI use. Three areas consistently appear in these opinions.

First, competence obligations. You have a duty to understand the tools you're using. This doesn't mean you need a computer science degree, but it does mean you should understand the basics of how Claude works, including its limitations and risks. Reading this course is a step toward satisfying that obligation.

Second, confidentiality requirements. When you input client information into a third-party platform, you need to be confident that doing so is consistent with your professional obligations. This is where lawyers need to be careful. Client confidential material should only go into tools that meet your jurisdiction's standards for data protection and confidentiality. This isn't a reason to avoid AI, but it's a reason to be intentional about what you use and what you put into it.

Third, disclosure obligations. In some contexts, you may be required to disclose your use of AI to courts or clients. Some jurisdictions have specific rules about AI-generated content in court filings. Others require disclosure when AI was used in preparing documents. You need to know what your jurisdiction requires.

Here's the practical guidance: review your bar association's AI guidance before you place client confidential material into any AI tool. This is a thirty-minute exercise, not a lengthy research project. Most jurisdictions have published ethics opinions or practice guides. Read them. Understand them. Then use Claude with confidence, knowing you're operating within your professional framework.

The guidance varies by jurisdiction and continues to evolve. What's acceptable in one state might violate ethical rules in another. Don't assume,verify. Thirty minutes of reading now can save you from a professional conduct complaint later.

Section 2: Foundational Setup,Projects and System Prompts

Here's the pattern that plays out thousands of times: a lawyer hears about Claude, tries it, types something vague like "summarize this contract," receives something generic back, and concludes the tool doesn't work. They close the browser tab and go back to doing things the hard way.

The problem isn't Claude. The problem is the setup,or more precisely, the lack of setup. The lawyer gave Claude no context about who they are, what they need, or why they need it. Claude responded in kind with a generic output. Both parties were doing exactly what they were asked to do.

The solution is persistent workspace configuration. The gap between a generic Claude response and a genuinely useful one is almost entirely about context. The way to build that context isn't by adding more words to every individual prompt,it's by doing setup work once at the beginning so every conversation afterward starts from a position of Claude knowing who it's working with.

The Project Workspace
A project is a persistent workspace within Claude that fundamentally changes how the tool functions. Think of it as a dedicated office for your legal practice, pre-configured with everything Claude needs to know before you even type your first prompt.

Three things happen when you create a project. First, persistent context. Once configured, every conversation within the project begins with Claude already knowing your practice area, jurisdiction, preferences, and templates. You don't need to re-establish context or restate preferences in each new conversation. The information is just there.

Second, elimination of repetition. Without a project, every conversation starts from scratch. Claude has no memory of previous conversations. It doesn't know you're a lawyer, doesn't know your jurisdiction, doesn't know your preferred formats. Every new chat is like a stranger walking in off the street. With a project, you're not starting over each time. You're building on established context.

Third, a document library. You can upload reference documents to your project,standard engagement letters, file note templates, clause libraries, anything you want Claude to reference in every conversation. When you then ask Claude to draft an engagement letter, it already has your template. It produces something that looks like your work, not a generic version that vaguely resembles what a law firm might use.

Projects are available on Claude Pro and Claude for Teams. If you're on the free plan, this is the single most significant reason to upgrade. The difference between Claude with a project and Claude without one isn't marginal,it's the difference between a tool that works for you and one you have to work around.

Here's a concrete example of the difference. Without a project, you might type: "Draft a demand letter for a client who's owed money." Claude produces something generic, because it has no idea what kind of law you practice, what jurisdiction you're in, what your client's situation is, or what tone you prefer. With a project, you type the same request and Claude already knows you're a commercial litigator in California, your clients are mid-market businesses, and you prefer a firm but professional register. It produces something that reads like it came from your desk.

The System Prompt: The Foundation of Everything
Within the project, the instructions field,known as the system prompt,is the most critical setup element. Most lawyers leave it blank. This is the single most common setup mistake and the primary reason many users receive only a fraction of Claude's potential value.

The system prompt tells Claude who it's working with, what expectations exist, and how it should behave. It's the difference between Claude producing generic, layperson-oriented content and producing professional-grade legal work that reads like it came from a practicing attorney.

Here's a strong starting template. I want you to look at each element and understand why it matters:

"You're working with a practicing attorney. I'm a commercial litigation attorney. My clients are primarily mid-market businesses, privately held companies, founders, and executives. I practice in California. When I ask you to draft anything, write in a professional legal register unless I explicitly ask for something else. When I ask you to explain a legal concept, assume I understand the law. Give me the depth I can actually use, not a plain English overview designed for a non-lawyer. Flag any assumptions you've made in your response. Never present a speculative legal conclusion as settled authority. If you're uncertain about jurisdiction-specific rules, recent case law, or regulatory developments, say so explicitly rather than guessing."

Let me break down each component so you understand what it does and why it matters.

The identity line,"You're working with a practicing attorney",calibrates the entire register of everything Claude produces. Without it, Claude defaults to a general audience. It explains legal concepts the way it would to a non-lawyer, because it doesn't know any better. With it, Claude knows it's not explaining legal concepts to a layperson. It's talking to someone who passed the bar and has handled hundreds of matters. The explanations get denser, the assumptions get more sophisticated, and the output becomes actually useful.

The practice area and client description,"commercial litigation attorney" with "mid-market businesses, privately held companies, founders, and executives" as clients,serves two functions. It tells Claude what kind of work is likely to come up, so it can anticipate the types of issues and formats you'll need. And it informs client-facing communications. "My clients are mid-market businesses" produces a different email register than "my clients are individuals going through family law proceedings." Both are correct for their context, but they're very different.

The jurisdiction line,"I practice in California",is critical and often overlooked. Without it, Claude defaults to a blended general answer that may not reflect the law where you actually practice. Specify your jurisdiction and Claude grounds its responses in the right legal system. This doesn't guarantee accuracy,you still need to verify,but it dramatically improves the relevance of what you receive.

The assumption-flagging instruction,"Flag any assumptions you've made in your response",is essential. Claude will sometimes make assumptions to fill gaps in your instructions. If you ask it to draft a demand letter without specifying the governing state, it will pick one. Without the flagging instruction, it may not reveal that it did so. With it, Claude surfaces those assumptions so you know where to check.

The uncertainty acknowledgement,"If you're uncertain about jurisdiction-specific rules, recent case law, or regulatory developments, say so explicitly rather than guessing",mandates explicit admission when Claude isn't sure. This doesn't eliminate hallucinations, but it reduces them by creating a culture where uncertainty is surfaced rather than hidden.

Here's a second example, this time for a family law practitioner: "You're working with a practicing attorney. I'm a family law attorney in Texas. My clients are individuals going through divorce, custody disputes, and property division. When I ask you to draft anything, use a professional but accessible register,my clients need to understand what's happening, but the documents should still be court-appropriate. When I ask you to explain a legal concept, assume I understand the law but need to explain it to a non-lawyer client. Flag any assumptions you've made. Never present a speculative legal conclusion as settled authority. If you're uncertain about Texas-specific rules or recent case law, say so explicitly."

Adding Practice-Specific Layers
Once the foundation is in place, you can add layers specific to your practice. These are the details that make Claude produce work that looks like yours, not generic legal work.

File note preferences: "When drafting file notes, use this structure: date, attendees, matter reference, matters discussed, instructions received, follow-up actions, and responsible party." This tells Claude exactly what format you want, so every file note it produces follows your preferred structure.

Critical analysis requirement: "When I'm working through a legal problem, don't simply agree with my analysis. Identify weaknesses and anything I may have missed." This transforms Claude from a yes-man into a thinking partner that challenges your reasoning. For lawyers, this is invaluable,you want to know where your argument is weak before opposing counsel finds out.

Client communication preferences: "When drafting client communications, use plain English and avoid legal jargon unless it's necessary, in which case explain it immediately." This ensures client-facing content is accessible without being patronizing.

The system prompt doesn't need to be perfect on the first pass. It will be refined over time as you learn what's missing and what Claude needs to know. Even a rough first version immediately improves everything produced. The initial setup should take approximately fifteen minutes. That's the investment. Fifteen minutes of setup that pays dividends every time you open Claude from that point forward.

Uploading Reference Documents
Your project allows you to upload documents Claude will reference in every conversation. This is where you build your document library. Standard engagement letters, file note templates, preferred clause libraries,upload them once, and Claude will reference them automatically.

Here's how this plays out in practice. You upload your standard engagement letter template to your project. Later, you ask Claude to draft an engagement letter for a new client. Claude already has your template. It adapts it to the new engagement,client name, matter description, fee arrangement,while preserving your standard terms and formatting. The output looks like it came from your desk because it's built on your template.

The same applies to file notes. Upload your preferred file note format, and every file note Claude drafts will follow that structure. No more generic Word document formatting that you have to fix before it goes into your system.

Take the fifteen minutes to set this up properly. It's the difference between Claude as a generic tool and Claude as a tailored assistant that produces work in your voice, with your templates, and according to your preferences.

Section 3: The Briefing Principle,Communicating with Claude

Here's the single most important skill in effective Claude use: abandon the search-query mindset. Stop thinking in keywords. Stop typing "draft demand letter" and expecting something useful. Instead, think about briefing a capable colleague who is brilliant and well-read but entirely new to the matter.

When you brief a colleague before a drafting task, you provide context. You explain who the client is, what the dispute involves, what's already happened, what outcome the client wants, what tone is appropriate, and what constraints apply. You don't just say "draft a demand letter" and walk away. So why would you treat Claude any differently?

The difference between a weak prompt and a strong brief is approximately thirty to sixty seconds of additional typing. The difference in output quality is significant. Let me show you what I mean.

Weak vs. Strong Briefing Example
Weak prompt: "Draft a demand letter"

That's it. No context. No information about the client, the dispute, the desired outcome, or the tone. Claude produces a generic demand letter that could apply to any debt collection matter. It's technically correct but practically useless,you'd have to rewrite most of it to make it fit your client's situation.

Strong brief: "A letter of demand on behalf of my client, a commercial painting contractor based in Los Angeles. The respondent is a general contractor who owes my client $42,000 for completed work on a commercial building project in Santa Monica. The work was completed and accepted in March. We've got a signed subcontract and a completion certificate. My client sent two emails requesting payment, both ignored. No dispute has been raised about the quality of the work. The tone should be firm and professional. We want to make clear that legal proceedings will follow if payment isn't received within 14 days, but we're not trying to blow up the commercial relationship. My client works with this contractor regularly and wants the money, not a fight. One page maximum."

Look at what this brief contains. Client identity: commercial painting contractor in Los Angeles. Dispute facts: general contractor owes $42,000 for completed work. History: work completed and accepted in March, signed subcontract and completion certificate exist, two emails sent and ignored. Desired outcome: full payment within 14 days, willing to commence proceedings. Tone: firm and professional, not trying to destroy the relationship. Constraints: one page maximum.

The weak prompt produces generic content requiring substantial rewriting. The strong brief produces something close to sendable on the first pass. You check the facts, adjust the tone to match your firm's voice, add letterhead, and send. Eight minutes total instead of thirty.

Here's a second example. Weak prompt: "Summarize this lease." Strong brief: "Please summarize this commercial lease for my client. My client's the tenant, a small retail business owner who hasn't signed a commercial lease before. Focus on their key obligations under this lease, the main financial commitments and how they work, anything they'll need to do or decide before signing, any provisions that are unusual or that I'll need to explain to them separately, and any significant risks they should be aware of. Write this in plain English, no legal jargon,or if jargon's unavoidable, explain it immediately. Aim for two pages."

The Pre-Submission Checklist
Before you submit anything to Claude, run through this checklist. It takes ten seconds and dramatically improves your results.

Who is the client? Have you told Claude who you're acting for,their business, their situation, their needs?

What is the matter? Have you explained the dispute, the facts, the history, the context?

What should Claude produce? Have you specified the document or analysis you want,a demand letter, a file note, a red flag review, a negotiation model?

What tone is appropriate? Have you indicated whether this should be firm, conciliatory, formally neutral, or something else?

What constraints apply? Have you mentioned page limits, legal requirements, strategic considerations, or deadlines?

If the answer to any of these is no, add the information before you hit submit. The thirty to sixty seconds you spend writing a proper brief pays for itself in the quality of the output you receive.

Section 4: Document Work

Document processing is where most lawyers begin with Claude, and for good reason,the time savings are immediate and the risk is manageable because output is always reviewed against a document physically in front of you. You're not relying on Claude's memory or judgment; you're using it as a processing tool on a document you can see and verify.

Claude accepts PDF uploads, Word documents, plain text files, and direct text pasting. For most legal documents, PDF upload works well. For very long documents,over fifty to sixty pages,you may hit context limits. Break large transactional documents or due diligence packages into sections and process them separately.

Use Case 1: Client-Facing Summaries
Picture this: you have a twenty-page commercial lease that needs to be explained to a small business owner with no prior commercial leasing experience. The client doesn't need the lease itself,they need to understand what it means for them, their business, and their obligations.

Without Claude, this is a forty-minute drafting exercise. You read the lease, identify the key provisions, translate them into plain English, structure the explanation, and draft a document that's clear without being patronizing. With Claude, you upload the document, provide context, and let it do the heavy lifting.

Here's the approach. Upload the document and provide context: "Please summarize this commercial lease for my client. My client's the tenant, a small retail business owner who hasn't signed a commercial lease before. Focus on their key obligations under this lease, the main financial commitments and how they work, anything they'll need to do or decide before signing, any provisions that are unusual or that I'll need to explain to them separately, and any significant risks they should be aware of. Write this in plain English, no legal jargon,or if jargon's unavoidable, explain it immediately. Aim for two pages."

The output won't be perfect, but the structure will be there. The key obligations, the financial commitments, the decision points, the unusual provisions, the risks,all organized in plain English. You review, edit, and refine. The forty-minute task becomes approximately ten minutes of editing.

Here's a second example. An employment contract for a senior executive who's considering a new role. The client wants to understand the restrictive covenants, the termination provisions, and the equity arrangements. Same approach: upload the document, provide context about who the client is and what they care about, and let Claude produce a plain-English summary that you then refine.

Use Case 2: Red Flag Checklists
When you receive a commercial contract on behalf of a client, you need a map of issues before you do the careful read. Claude can produce that map in seconds.

Here's the approach: "Please review this agreement and produce a red flag checklist. I'm acting for the party described as the service provider. I need you to identify: first, any clauses that are unusual or that depart significantly from what you'd expect in a standard services agreement of this type, with a brief explanation of why they're unusual. Second, any provisions that are particularly favorable to the other party that I should consider pushing back on in negotiation. Third, any standard protections for my client that appear to be absent from this agreement. For each item, note the relevant clause reference so I can find it in the document."

What comes back is a working checklist that orients you before you read the document in full. You know where the issues are, what to look for, and what to push back on. The careful read still happens,this doesn't replace your review,but you're reading with direction rather than reading cold.

Here's a second example. A client is buying a business and the purchase agreement has arrived from the seller's counsel. You need to identify the key risks before you advise the client on next steps. Same approach: upload the agreement, specify which party you're acting for, and ask for a red flag checklist organized by category,representations and warranties, indemnification, closing conditions, post-closing obligations.

One critical note: the red flag review is a tool for your first pass, not your only pass. It supplements your own careful read. It doesn't replace it. Claude may miss issues that require human judgment or context-specific knowledge, and it may flag things that aren't actually problems. The final read of any document must be your own work.

Use Case 3: Document Comparison
Comparing two versions of a document is one of the most tedious tasks in legal practice. The original draft, the other party's markup, the redlined changes,manually identifying every substantive change takes time and attention. Claude can do this in minutes.

Here's the approach: "I'm going to give you two versions of a distribution agreement. Version one is the draft we sent to the other party. Version two is their markup. Please compare the two versions and identify every substantive change. Ignore formatting and punctuation differences. For each substantive change, tell me what was changed, in which clause, and whether the change appears more favorable to the distributor or the supplier. Flag any changes significant enough that I should push back, with a brief explanation of why."

What might take forty-five minutes to redline manually becomes a structured summary in under two minutes. You know exactly what changed, where it changed, and which changes matter. The negotiation becomes more focused because you're not spending your preparation time on document comparison.

Here's a second example. You're reviewing a lease amendment against the original lease. You need to know what changed, what stayed the same, and what the amendment actually accomplishes. Same approach: upload both documents, specify what you're looking for, and let Claude identify the substantive differences.

Use Case 4: Systematic Information Extraction
Some exercises require extracting the same class of information from multiple documents. Payment terms from a dozen contracts. Governing law clauses from a portfolio of leases. Expiry dates from a stack of agreements. This is the kind of work that eats an afternoon and provides no intellectual satisfaction whatsoever.

Claude can process document sets systematically and present results in a table format. You upload the documents, specify what you're looking for, and Claude extracts the information into a structured format.

Here's the approach: "I'm going to upload a set of ten commercial leases. For each lease, please extract the following information and present it in a table: the parties, the premises, the lease term, the rent amount and escalation provisions, the governing law clause, and the expiry date. If any of this information is missing from a lease, note that it's missing rather than guessing."

This applies to due diligence packages, lease portfolios, employment agreement reviews, and any exercise that would otherwise require an afternoon of manual extraction. The table format makes the information immediately usable,you can sort it, compare it, and identify anomalies at a glance.

Here's a second example. You're reviewing a portfolio of vendor contracts for a client who's considering an acquisition. You need to know which contracts have change-of-control provisions, which have termination-for-convenience clauses, and which are silent on assignment. Same approach: upload the contracts, specify the information you need, and let Claude produce the structured summary.

Section 5: Drafting Workflows

Drafting is where lawyers spend more time than almost anywhere else, and it's the most cognitively demanding part of the job. It requires holding facts, legal framework, client instructions, relationships with the other side, and appropriate tone simultaneously. Claude doesn't hold all of that,you still have to know the matter and exercise judgment,but it radically reduces the friction of getting started and takes on the structural work, freeing your cognitive bandwidth for the judgment work that only you can do.

Every drafting task follows the same pattern. Give Claude context. Tell it what's needed. It produces a first draft. You review and improve. The quality of the first draft depends on the quality of the brief. Improving a solid first draft is significantly faster than building from zero.

File Notes: The Low-Risk Entry Point
File notes are the perfect place to start with Claude because they're low risk,they stay in your system rather than going out the door,and they're high frequency. You write them after every client call, every meeting, every substantive conversation.

Here's the scenario. A client call just ended. You have raw notes,incomplete sentences, shorthand, half-finished thoughts, and a list of promised actions. Normally, you'd spend twenty minutes turning those notes into a professional file note. With Claude, you feed the raw notes directly and let it do the translation.

Here's the approach: "These are my rough notes from a client call that just finished. Please draft a professional file note based on these notes using the following format: Date, attendees, matter name, matters discussed, client instructions received, and follow-up actions with responsible parties noted. Flag anything in my notes that's unclear or where you've had to make an assumption to fill a gap."

Then paste the raw notes exactly as they are. Don't tidy them up first,that defeats the purpose. Claude handles the translation from rough to professional. What comes back is ninety percent of the way to a finished file note. You review it against your recollection and raw notes, make any corrections, and file it. Total time: five minutes instead of twenty.

Here's a second example. You've just come out of a settlement conference. Your notes are a mess,scraps of paper, scribbles on a legal pad, half-remembered conversations. Same approach: feed the raw material to Claude, specify the format you want, and let it produce a coherent file note that captures the key discussions, the offers exchanged, and the next steps.

Demand Letters: The Complete Brief in Action
Demand letters are where the briefing principle really shines. A well-briefed Claude produces a demand letter that's close to sendable on the first pass.

Here's the scenario. A commercial interior design firm in Chicago needs to demand payment of a $48,000 invoice that has been outstanding for 93 days from a property developer. The work was completed, accepted, and invoiced. Two written payment requests have been ignored. The client wants payment in full within 14 days and is prepared to commence proceedings if payment isn't received.

Here's the complete brief: "Draft a letter of demand on behalf of my client. My client's a commercial interior design firm based in Chicago. The recipient is a property developer who contracted my client to design and oversee the fit out of three retail tenancies in a new development. My client completed the work in full. The developer accepted the completed fit out without raising any defects. The final invoice, $48,000, has been outstanding for 93 days. We've sent two written payment requests by email. No response has been received. No dispute about the work or the invoice has been raised. My client wants payment. They're not interested in negotiating a discount or a payment plan. They want the full amount within 14 days. They're prepared to commence proceedings if payment's not received. Tone firm, professional, and unambiguous. Don't threaten. State the consequence clearly. One page."

Approximately one minute of typing produces a letter that states the facts clearly, references the outstanding amount, specifies the deadline, and states the consequence. You read it, check the facts, adjust the tone to match your firm's voice, add letterhead, and send. Eight minutes total instead of thirty.

Here's a second example. A client's commercial lease has expired and the landlord is refusing to return the security deposit. The client wants the deposit returned plus interest. Same approach: provide the facts, the history, the desired outcome, the tone, and the constraints. Claude produces a demand letter that's ready for your review.

Engagement Letters
If you've uploaded your standard engagement letter template to your project, Claude can adapt it to a new engagement in seconds. You provide the client name, the matter description, the fee arrangement, the retainer, and the scope. Claude produces your standard template adapted to the specifics.

Here's the approach: "Draft an engagement letter for a new client using my standard template. The client is a technology startup that's engaged us to handle a commercial contract dispute with a former vendor. Fee arrangement is hourly, with a retainer of $15,000. Scope is limited to the dispute itself, not general corporate advice. I've uploaded my standard template to the project,please adapt it to these specifics."

The output is your template, adapted to the new engagement. You review it, adjust as needed, and send. A task that might take twenty minutes becomes five.

Here's a second example. A client is expanding into a new jurisdiction and needs an engagement letter for work that crosses state lines. Same approach: provide the specifics, and Claude adapts your template while flagging any jurisdiction-specific issues you should consider.

Briefs to Counsel
When you need to brief external counsel, Claude can structure the information into a clear, organized document that gets counsel oriented quickly and asks the right questions.

Here's the approach: "Draft a brief to counsel for a commercial dispute. My client is a logistics company that contracted with a software vendor for a fleet management system. The system was delivered late and doesn't perform to specification. My client has lost revenue as a result. I need counsel to advise on whether we have a claim for breach of contract and what damages we can recover. Here are the key facts: [paste facts]. Here's the contract: [upload contract]. Here are the questions I need counsel to address: [list questions]."

What comes back is a structured brief that gets counsel up to speed quickly and poses the right questions. A well-structured brief is worth significantly more than a document dump with a covering email.

Internal Matter Memos
When files change hands, partners need updates, or you're picking up a matter you haven't touched in weeks, Claude can produce the structure for a matter memo that you then correct and refine.

Here's the approach: "Draft an internal matter memo for a partner update. The matter is a construction dispute where we're acting for the head contractor. Key developments since the last update: we've filed the statement of claim, the respondent has filed a defense, and we're now in the discovery phase. The next deadline is for discovery responses, due in three weeks. I'm concerned about the respondent's delay tactics. Please structure the memo to include: current status, key developments, upcoming deadlines, risks and concerns, and recommended next steps."

The output is a structured memo that communicates the essentials clearly. You review, add your judgment on the risks and recommended steps, and send. A task that might take thirty minutes becomes ten.

Section 6: Preparation Work

Preparation is one of the most cognitively expensive things lawyers do,and it's the work that gets squeezed when the week is full because it doesn't have a deadline attached the way filings or contracts do. Claude is exceptionally well suited to preparation because what it does,modeling scenarios, identifying gaps, surfacing arguments you haven't considered,is essentially what good preparation requires. And it's available at any hour.

The lawyers who get the most value from Claude aren't the ones who use it the most. They're the ones who use it deliberately. And the use case that lawyers discover last but value most over time is preparation.

Directions Hearings
Directions hearings are treated as low-stakes administrative events, but they can turn quickly. A judge with a view about the timetable. An opposing party raising something unexpected. A procedural issue that wasn't flagged. Being caught flat-footed at a directions hearing is embarrassing disproportionately to the event.

Here's the preparation approach: "I've got a directions hearing tomorrow morning. Here's a brief summary of the matter and where we are in the proceedings: [paste 3-5 sentences]. I'm seeking [describe the orders you want]. The other side's likely to resist [describe the expected opposition]. Please give me: first, the questions I'm most likely to be asked from the bench with suggested responses for each. Second, any procedural issues the other side might raise that I should be ready to address. Third, anything I should proactively bring to the court's attention before being asked."

Going through that output the night before and formulating answers out loud prepares you to walk in ready for what's likely to happen rather than hoping nothing unexpected comes up. You're not caught flat-footed because you've already thought through the likely questions and the possible curveballs.

Here's a second example. You have a case management conference in a complex commercial matter. There are multiple parties, several interlocutory applications pending, and a tight timetable. Same approach: brief Claude on the current state of the proceedings, what you're seeking, and what the other side is likely to resist. Use the output to prepare for the questions you're likely to face.

Trial Preparation
The week before trial is one of the most overwhelming weeks in professional life. Documents, witnesses, submissions, logistics, and a hundred small tasks competing for attention. Claude won't replace your substantive preparation work, but it serves as an excellent thinking partner for structuring your approach and identifying gaps.

Here's the approach: brief Claude with the matter, the key factual issues in dispute, your client's position, and the other side's position. Then ask for: the most important issues that need clear answers before you go in; the weaknesses in your client's position that need responses; the strongest points in your client's favor that need to come through clearly; and the likely cross-examination lines for key witnesses.

The output is a preparation checklist that ensures you've thought through the critical issues before you walk into the courtroom. You're not going in hoping you've covered everything,you're going in knowing you've considered the likely scenarios and prepared responses.

Here's a second example. You're preparing for an arbitration hearing. Same approach: brief Claude on the dispute, the evidence, and the parties' positions. Ask it to identify the key issues, the weaknesses in your case, and the likely lines of questioning. Use the output to structure your preparation and ensure nothing falls through the cracks.

One additional benefit that lawyers consistently report: the act of articulating the matter clearly enough for Claude to engage with it is itself a thinking exercise that often reveals issues you hadn't previously noticed. The process of briefing Claude forces you to organize your thoughts, which is valuable regardless of what Claude produces.

New Client Meetings in Unfamiliar Industries
You're a general commercial lawyer. A new client walks in who operates a small regional freight logistics company. You've never worked with a logistics company before. You don't know the industry's common legal issues, regulatory requirements, or typical contract structures. You have a first meeting tomorrow and you want to sound like you know what you're talking about.

Here's the approach: "I'm meeting tomorrow with a new client who operates a small regional freight logistics company with about 40 employees. I'm a general commercial lawyer. This isn't a sector I know particularly well. Please brief me on the most common legal issues that arise in this industry, covering employment and contractor classification, regulatory and licensing requirements, contract structures with customers and carriers, liability exposure, and anything else a commercial lawyer should have front of mind walking into a first meeting. Keep it practical. I need to know what questions to ask and what problems to look for, not a comprehensive treatise."

Thirty seconds of processing produces a briefing that would have taken an hour to research manually. You walk into the meeting knowing the industry's key issues, the questions to ask, and the problems to look for. You demonstrate industry understanding that adds value to the first meeting and builds the client's confidence in your capabilities.

Here's a second example. You're meeting with a client who runs a chain of childcare centers. You know employment law and property law, but you've never advised a childcare business. Same approach: ask Claude to brief you on the regulatory framework, the common legal issues, and the questions you should ask in a first meeting.

Negotiation Modeling
Negotiations are where preparation pays off most directly. Going in having already thought through the other side's likely positions and your responses is a material advantage,and it's the part of preparation that most lawyers skip when time is short.

Here's the approach: brief Claude with the commercial context, the key points in dispute, your client's objectives and real constraints. Ask it to model the other side's likely positions and the commercial logic behind them. Ask where your client will need to show flexibility to get a deal done. Ask what you should try to understand about the other side's priorities during the negotiation itself.

Here's a second example. You're mediating a construction dispute. The other side has made an offer that's below your client's bottom line but not absurdly so. You need to understand their likely negotiation range, what they might be willing to concede, and how to structure a counteroffer that moves the negotiation forward rather than stalling it. Same approach: brief Claude on the facts, the positions, and the constraints. Use the output to structure your negotiation strategy.

Frequently Asked Questions