Claude CoWork for Paralegals

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a persistent, knowledgeable co-worker embedded in your daily paralegal workflow. This is not about asking a chatbot a one-off question and hoping the output is good enough. It is about configuring Claude with your firm's context, your supervising attorney's style, and your matter conventions so that every interaction produces draft work product the attorney can actually use.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <format>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity. They work in ChatGPT too, but are optimized for Claude.

Think of Claude as the smartest junior paralegal you have ever worked with — one who never forgets the firm's formatting conventions, knows your matters cold, and can scaffold a discovery response, deposition summary, or research memo in seconds. The difference between paralegals who dabble with AI and those who become indispensable to their attorneys comes down to setup and consistency.

This guide walks you through setting up Claude specifically for paralegal work, the five workflows that will save you the most time, and the prompting techniques that separate generic output from production-ready drafts.

Install the Paralegal Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Paralegal plugin packages the workflows below as native skills and slash commands.

Open the Cowork plugin directory in your desktop app.
Filter by Cowork, search for "Paralegal", and click Install.
The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/paralegal

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command	What it does
`/legal-draft`	Generate first drafts of contracts, demand letters, discovery responses, and legal memoranda
`/research-memo`	Draft structured legal research memos with case holdings, statutory analysis, and precedents
`/case-summary`	Create concise case summaries, deposition digests, and chronological case timelines
`/client-letter`	Draft professional client correspondence and status updates maintaining privilege boundaries

Auto-activating skills (no command needed — Claude applies them when relevant):

Legal Writing — Contracts, memoranda, discovery responses, demand letters, and professional legal correspondence
Legal Research — Case analysis, statutory interpretation, precedent identification, and structured research organization

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting up Claude for paralegal work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. The key to getting consistently useful output from Claude is using Claude Projects. A Project lets you set custom instructions that persist across every conversation, so you are not re-explaining your firm and your supervising attorney every time.

Step 1: Create a Paralegal Practice Project. In Claude, click "Projects" and create one called something like "Firm Paralegal Workspace."

Step 2: Set your custom instructions. In the Project settings, add instructions like:

You are my paralegal practice assistant. Here is my context:

<firm-profile>
- Firm: [Your firm name]
- Practice areas: [Personal injury / Commercial litigation / Family law / Estate planning]
- Jurisdiction: [State(s)] and [Federal district(s) if applicable]
- Supervising attorneys: [Names and their typical writing style]
- Client base: [Plaintiff PI / Insurance defense / Small business / etc.]
- Court formatting preferences: [Local rules, font, spacing, citation format]
</firm-profile>

<rules>
- Never fabricate case citations, statutes, or legal authorities. If unsure, say so explicitly.
- All output is a DRAFT for attorney review. Include a header at the top: "DRAFT — FOR ATTORNEY REVIEW ONLY."
- When drafting correspondence, match the supervising attorney's voice: [paste 1-2 sample letters].
- Always flag conflicts of interest, ethical concerns, or missing information you notice.
- Use anonymized references for any client information ("Client A," "the plaintiff," "Plaintiff's vehicle").
</rules>

Step 3: Upload reference documents. Add your firm's pleading templates, sample discovery responses, deposition summary templates, brief templates, and any local court rules to the Project knowledge base. Claude will reference these when generating content.

Step 4: Start every session inside this Project. This ensures Claude always has your firm context loaded.

Your top 5 workflows with Claude

1. Discovery responses

Drafting objections and responses to interrogatories and requests for production is one of the most time-consuming tasks in litigation paralegal work. Claude can scaffold the boilerplate and structure so you focus on the substantive responses that need attorney input.

<task>Draft responses to these interrogatories on behalf of the defendant.</task>

<context>
Commercial breach of contract matter — our client (a software vendor) is the defendant.
Plaintiff alleges failure to deliver contracted features.
Our position: features were delivered as specified; plaintiff changed requirements mid-project.
</context>

<instructions>
- Draft standard objections (overbroad, unduly burdensome, attorney-client privilege, work product) where appropriate
- Draft substantive responses where the question is properly scoped
- Use "Responding Party" instead of client name throughout
- Flag any interrogatory that requires client input to complete substantively
- Format in standard interrogatory response format with question / objection / response structure
</instructions>

<avoid>Waiving privilege, making admissions of liability, including any confidential business information</avoid>

Before Claude: 2-3 hours drafting objections and responses for attorney review. After Claude: 10 minutes to input the discovery, 30 minutes to review and customize the draft.

2. Deposition and document summaries

Litigation matters generate enormous volumes of documents and transcripts that need to be summarized for the attorney before depositions, motions, or trial prep. Claude is exceptionally good at structured summarization.

<task>Summarize this deposition transcript for the supervising attorney.</task>

<context>Personal injury matter — deposition of the defendant driver in a rear-end collision case. Liability is disputed; defendant claims plaintiff stopped suddenly.</context>

<instructions>
- Produce a structured summary with sections: (1) Witness identifying information, (2) Key admissions, (3) Key denials, (4) Inconsistencies with prior statements (flag as questions for follow-up), (5) Page-line citations for the most important testimony
- Keep the summary under 1,000 words
- Flag any answers that suggest follow-up questions or additional documents to request
</instructions>

<avoid>Editorializing about credibility; making legal conclusions about admissibility</avoid>

Before Claude: 4-6 hours reading and writing a careful summary. After Claude: 15 minutes to input, 60 minutes to verify and refine.

3. Legal research memos

Once you have done the research, writing it up in IRAC format for the attorney's review is the part that consumes the most time. Claude can structure your findings into a memo that the attorney can read in 5 minutes.

<task>Draft an internal research memo on whether our client has a viable wrongful termination claim.</task>

<context>
Client: 7-year regional sales manager terminated 3 weeks after filing a workers' compensation claim.
Employer cited "restructuring" but replaced client within 2 weeks.
Client has emails from supervisor expressing frustration about the WC claim.
Jurisdiction: California
</context>

<instructions>
- Structure as IRAC (Issue, Rule, Analysis, Conclusion)
- Analyze under California Labor Code Section 132a and the public policy wrongful termination doctrine
- Address temporal proximity and pretext evidence
- Include a candid risk assessment
- Keep under 800 words
- DO NOT fabricate case citations. Cite the statute correctly; flag where you would normally cite case law for the supervising attorney to verify.
</instructions>

Before Claude: 3-4 hours drafting after you've already done the research. After Claude: 10 minutes to input findings, 30 minutes to verify and finalize.

4. Routine drafting and pleadings

Routine motions, demand letters, and standard correspondence follow predictable structures. Claude scaffolds them so you can focus on the case-specific facts and the attorney can focus on strategy.

<task>Draft a motion to compel responses to interrogatories.</task>

<context>
Personal injury matter, plaintiff's counsel.
Defendant's responses to plaintiff's first set of interrogatories were due 3 weeks ago.
Defense counsel has not responded to two meet-and-confer letters dated [dates].
Jurisdiction: California Superior Court, [County]
</context>

<instructions>
- Use the standard format for a motion to compel in this jurisdiction
- Include: notice of motion, points and authorities, declaration of counsel referencing the meet-and-confer attempts, request for sanctions
- Cite CCP 2030.290 for the failure to respond and CCP 2023.030 for sanctions
- Mark all citation placeholders for attorney verification
- Include a placeholder for the proposed order
</instructions>

Before Claude: 2-3 hours drafting. After Claude: 10 minutes to input, 30-45 minutes to review and finalize for the attorney.

5. Client correspondence

Routine client communication — status updates, document requests, scheduling letters, conflict checks — fills a paralegal's inbox and can be handled with template-driven AI drafting in a fraction of the manual time.

<task>Draft a client status update letter.</task>

<context>
Client: estate planning matter, married couple in their 60s.
Status: drafts of wills, POAs, and revocable living trust are ready for review.
Next steps: schedule a 90-minute review meeting; client should bring beneficiary information for retirement accounts.
Voice: warm, professional, plain language (not legalese).
</context>

<instructions>
- Address to both clients
- Confirm what's done, what's next, and what they need to bring
- Offer 2-3 specific meeting time options (use placeholders)
- End with a friendly close from the supervising attorney
</instructions>

Before Claude: 20 minutes per client letter. After Claude: 3 minutes to input, 5 minutes to review and personalize.

Prompt engineering tips for paralegals

1. Always specify the jurisdiction. "Draft this under California law" produces very different output than "Draft this under Texas law." Never assume Claude will default to the right jurisdiction.

2. Require citation transparency. Add "Do not fabricate case citations. Use placeholders where case law would normally be cited and flag them for attorney verification" to every research-related prompt. Verify every citation Claude provides through Westlaw or Lexis.

3. Match the supervising attorney's voice. Different attorneys have different preferences. Paste a sample letter or memo from the attorney you're working with into the Project knowledge base so Claude matches their tone.

4. Use legal frameworks explicitly. Asking Claude to "use IRAC format" or "structure this as a motion with notice, points and authorities, and declaration" produces dramatically better legal writing than generic prose requests.

5. Set length limits ruthlessly. Attorneys are time-poor. "Keep the memo under 800 words" or "Limit the summary to two pages" produces tighter, more useful output.

6. Always mark drafts as drafts. Every output should start with "DRAFT — FOR ATTORNEY REVIEW ONLY." This protects you and reminds anyone who sees it that the document needs attorney sign-off before it goes anywhere.

Privacy and compliance

Attorney-client privilege demands extreme caution. Do not paste privileged communications, confidential client documents, or sensitive case strategy into Claude without confirming your firm's AI usage policy. Use anonymized facts and general descriptions wherever possible.

Never include identifying client details. Replace client names with "Client A" or "the plaintiff." Never include Social Security numbers, financial account numbers, dates of birth, or other personally identifiable information in prompts. The AI does not need them to draft.

Verify every citation. Claude can generate plausible-sounding but nonexistent case citations. Every statute, case, and rule must be independently verified through Westlaw, Lexis, or an official source before inclusion in any filing or correspondence.

Final responsibility is the attorney's. AI-generated content is a draft. The attorney is responsible for the accuracy, completeness, and ethical compliance of everything filed under their name. Your job is to flag the parts that need their attention — not to paper over them.

Court disclosure requirements. Some jurisdictions now require disclosure of AI use in legal filings. Check the local rules and standing orders for any court your firm files in before submitting any AI-assisted work product.

Going further

Ready to build on this foundation? Check out these resources:

Browse our full collection of legal prompt packs and cheat sheets for ready-to-use templates
Run an AI readiness audit for your legal practice to identify your biggest opportunities
Explore AI-powered tools built specifically for paralegals and legal teams to automate even more of your workflow