Claude Cowork just got its first grown-up workflow
The legal rollout shows what happens when Claude moves from chat polish into work that needs provenance, boundaries, and human signoff.
Anthropic expanded Claude’s legal tooling with Thomson Reuters CoCounsel and Westlaw, Harvey, Box, Everlaw, DocuSign, plus 12 legal practice plugins that can run through Claude Cowork or inside a firm’s own systems.
Read too quickly, and that announcement looks like another vertical AI launch.
Look granular and it becomes a map for where Cowork is going.
Legal work is one of the first places where Claude has to support professional workflows without asking people to trust a polished answer on vibes.
Clause review needs source support.
Vendor terms need exact risk locations.
Invoice language, policy edits, customer records, and payment approvals need clear stopping points before anything gets sent, signed, paid, changed, or published.
Borrow that lesson from legal.
Once Claude gets near work with consequences, the output can’t stay trapped inside a nice paragraph.
That safer shape is the review packet.
Where the standard gets visible
Almost-right answers are expensive in legal work.
Contract summaries can sound useful while missing the clause that matters.
Research memos can read confidently while leaning on weak authority.
Suggested edits can look harmless and still change who carries the risk.
Thomson Reuters said its expanded Anthropic partnership connects Claude to CoCounsel Legal through MCP. In plain English, MCP is one way Claude can connect with outside systems and pull in approved context. Thomson Reuters framed the integration around fiduciary-grade work, authoritative content, citations, and validated references.
According to Reuters, Thomson Reuters customers can access Westlaw Primary Law and Practical Law materials within Claude, while CoCounsel’s legal research tools can be used directly by Claude users who are already customers.
Most Cowork users don’t need a legal research stack.
Serious users still need the habit behind it.
For important work, Claude should show what it looked at, what it found, what’s missing, and where the human decision still belongs.
Normal responses don’t give enough inspection surface.
What a review packet means
Think of a review packet as a structured answer that gives the human enough context to inspect the work.
Useful packets usually include source references, key findings, missing context, suggested next steps, approval points, and blocked actions.
Blocked actions matter once tools enter the workflow.
When Claude can read files, search connected systems, draft messages, open documents, prepare edits, or route work into other apps, vague instructions get risky.
“Review this contract” is fine for a quick chat experiment.
“Read this agreement, identify risky sections, cite the exact source, flag missing context, suggest next steps, and don’t send or modify anything” is closer to a serious Cowork task.
No technical background is needed to understand the difference.
One prompt asks Claude to sound useful.
Another prompt tells Claude how to keep the work inspectable.
Tool access isn’t the whole story
TechRadar reported that Anthropic’s legal release includes more than 20 MCP connectors and 12 legal plugins, with legal professionals described as some of the most engaged Claude Cowork users.
Connector count isn’t the part operators should obsess over.
Access only tells Claude what it can reach.
Plugins package repeat behavior.
This format gives the human a place to judge the result.
Wider access can make a workflow harder to trust when there’s no review layer.
Clear boundaries matter because plugins can feel more official than they deserve.
Source trails matter because the human still has to verify the claim, inspect missing context, and decide whether the suggestion is safe.
Lawyers already know this.
Operators need to learn it before they put Cowork near customer records, vendor terms, invoices, hiring notes, finance work, compliance tasks, or public content.
Skepticism helps here
A recent r/ClaudeAI thread described Claude for Legal as a vertical connector and plugin move, then questioned whether the new practice-area plugins actually beat base Claude with strong domain context.
One commenter argued that workflow integration may matter more than legal prompting because firms already know a base model can summarize or draft.
Skepticism around legal AI is warranted.
Those plugins don’t make Claude a lawyer.
Connections don’t remove validation.
Even source-backed output doesn’t make every recommendation safe.
Jurisdiction, client context, document history, business leverage, and professional judgment still matter.
So the useful claim is narrower.
Preparing a legal-style review packet for a qualified human to inspect is the practical claim.
Saying that is different from saying Claude can handle legal work.
It’s also more useful.
Non-lawyers should steal the pattern
Founders can use review packets for vendor terms, partnership offers, investor requests, customer complaints, and hiring agreements.
Operations teams can apply the same pattern to invoices, internal policies, service changes, payment approvals, support escalations, and handoff notes.
Consultants can use it to review client materials before a meeting.
Marketers can use it to check claims, source support, compliance concerns, and brand risk before anything goes public.
Chiefs of staff can turn scattered updates into a packet where open decisions stay separate from facts.
Day one doesn’t require advanced setup.
Give Claude the material.
Define the review job.
Ask for source-backed findings.
Force uncertainty into the output.
Keep external action behind approval.
Beginners get a safer starting point.
Advanced operators get a structure they can turn into a team standard, plugin instruction, SOP, eval fixture, or MCP workflow contract.
Start with read-only work
Don’t begin with tool access everywhere.
Choose a first workflow that’s boring enough for mistakes to be easy to catch.
Proposal files work.
Meeting recaps, internal policies, project briefs, client intake forms, draft service agreements, and support escalation summaries work too.
Request a review packet.
Block sending, signing, editing, publishing, approving, paying, and triggering automation.
Manually inspect the packet.
Manual read-only review teaches you how Claude behaves before the stakes rise.
After the format works, add a second document.
Later, bring in approved internal context.
Connected tools should wait until the review process is stable.
Order matters because it keeps the human in control while the workflow matures.
Failure points still exist
Bad source material still breaks the packet.
Wrong documents can produce wrong reviews.
Missing attachments can make a summary look complete when the workflow is incomplete.
Broad permissions create risk even when the prompt sounds careful.
Sensitive data needs more than good wording.
Money, legal exposure, HR issues, compliance, customer communication, and public claims should keep human approval in the loop.
Speed can improve without making judgment disappear.
The Cowork lesson
Claude’s legal release points toward a more serious version of Cowork.
Chat polish matters less when the work needs inspection.
Instead of treating the answer as the final product, treat the packet as the first thing worth reviewing.
A connector brings in context.
Plugin behavior makes repeat work easier to package.
Packets like this give humans something to approve, revise, reject, or escalate.
That’s how Claude moves closer to real work without pretending the human vanished.
