Claude Cowork for Legal

Legal teams are reactive by design. A contract request arrives. A regulatory deadline surfaces. A matter escalates. The work happens in response to events — and then the team scrambles to reconstruct what happened, what’s pending, and what’s about to be late. Every week, some version of the same question gets asked: “Where are we on that contract?” or “When does that regulation take effect?”

Claude Cowork adds a proactive layer. Persistent agent threads that maintain context across sessions — running on Desktop, iOS, and Android — mean the contract queue is visible before stakeholders complain, the renewal window is caught before it closes, and the regulatory update is briefed before leadership asks. The legal team that knows what’s coming has more leverage than the one that finds out when it lands.

One important framing before we get into the setup: Cowork assists with legal workflows — drafting, organizing, summarizing, tracking — but does not provide legal advice. Every output from these threads should be reviewed by qualified legal counsel before use. These are operational tools for managing the volume and visibility of legal work, not substitutes for legal judgment.

---

What You’ll Build

By the end of this guide you’ll have two persistent Cowork threads running without you touching them again: a weekly contract queue monitor and a monthly regulatory update tracker. You’ll also have the exact prompt templates to build three more threads — matter status digest, contract renewal monitor, and policy review queue — copy-paste ready, not illustrative sketches.

---

Step 1: Get Set Up

What plan you need: Claude Cowork requires Claude Teams or Claude Max. For a legal team with 2–6 attorneys and paralegals, Claude Teams at $30/user/month is the right tier. Solo in-house counsel can run it on Max.

Accessing Cowork: On Desktop (Mac/Windows), open Claude and look for “Cowork” in the left sidebar — it’s a dedicated section below your regular conversations. On iOS and Android, it’s under the same sidebar menu. The interface is a thread list, not a single chat. Each thread has a name, a schedule, and its own persistent context.

The one setup step that changes everything: Go to Settings → Notifications → Cowork Delivery. Turn on “Notify me when a scheduled thread completes.” You want a push notification when the contract queue lands on Monday morning, not to remember to go look for it. The difference between a tool you use and a tool that works for you is whether it interrupts you with results or waits for you to remember to check.

---

Step 2: Create Your First Thread — Contract Queue Monitor

This is the one that solves the most immediate pain. Contract requests pile up. SLAs slip. Business stakeholders send follow-up emails that start politely and get less polite. The queue monitor makes the backlog visible before it becomes a relationship problem.

Click “New Cowork Thread” in the sidebar. Name it “Contract Queue Monitor.” Schedule it weekly — Mondays at 7 AM is the right call. You want this before the week starts, not after your inbox has already filled with questions about it.

Seed the thread with four things before the first run:

• The contract types you handle (MSA, NDA, SOW, vendor agreement, etc.)

• The standard SLA for each type (NDA: 3 business days; MSA: 10 business days, etc.)

• Your escalation criteria (deal size threshold, counterparty risk tier, regulatory exposure, etc.)

• Key stakeholders waiting on contracts (Sales, Procurement, Finance — whoever you need to communicate status back to)

Here’s the full prompt:

You are my weekly contract queue manager. I'll paste the current contract queue into this thread each Monday. Use the following context to analyze it:

CONTRACT TYPES AND SLAs:
[Paste your contract types and turnaround standards here]

ESCALATION CRITERIA:
[Paste your escalation triggers here — e.g., contracts over $500K, contracts touching regulated data, deals in final-stage pipeline]

KEY STAKEHOLDERS:
[Name the teams/roles waiting on contracts and what they need to know]

Each Monday when I paste the queue (format: contract name, type, requestor, date received, current status), produce four outputs:

1. CONTRACTS PAST SLA — List every contract past its turnaround standard. For each: how far past SLA it is, and what the downstream business impact is (deal at risk, vendor relationship, compliance deadline).

2. ESCALATION FLAGS — Any contracts that meet the escalation criteria we defined. Why they qualify and what action is needed.

3. STAKEHOLDER COMMUNICATIONS — Draft the status update to send to business stakeholders waiting on contracts. Specific by team: what's done, what's in review, what they should expect and when.

4. ONE-THING CALL — The single action that would most reduce queue backlog this week. Not a list of things. The one thing.

All outputs should be reviewed by qualified legal counsel before use or communication.

After pasting the prompt, hit “Schedule.” Then reply to the thread with your SLA table and escalation criteria. Claude will hold that context for every future run — you don’t re-explain it every week.

---

Step 3: Your First Result

The first queue run will land Monday morning. You paste the queue list (contract name, type, requestor, date received, status — takes 5 minutes to pull from your tracker), and Claude returns four outputs: the past-SLA report, escalation flags, stakeholder communications, and the one-thing call.

After the first run, do one thing: reply to the thread with a sentence or two about your team’s current capacity constraints. Something like: “We’re currently a team of two with one attorney on leave through month-end.” The prioritization gets sharper when Claude understands what’s actually available.

From your phone mid-week, you can reply to the thread with a follow-up: “What’s the downstream impact if the Acme MSA slips another week?” Claude knows the context — the contract, the SLA, the stakeholder — and gives you a specific answer rather than a generic one.

---