Loading

Regulatory and compliance

What changed, what applies to you, what to do by when.

10 minLegalClaude Cowork
Loading

Set up

Try a plugin

The Regulatory Legal plugin ships with /policy-diff and other regulatory-change skills as a starting point, already structured to read a new rule against your current policies and pull out which ones it touches and where the gaps are. It's one of twelve practice-area plugins for legal teams. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.

Regulatory LegalWatches regulatory feeds, diffs new rules against your policy library, tracks comment deadlines and open gaps, and writes the digest your team reads Monday morning.
Add
/policy-diffDiff a specific regulatory change against the indexed policy library.
Open in Claude
/reg-feed-watcherCheck regulatory feeds now and report what’s new since the last check, filtered by your materiality threshold.
Open in Claude
/cold-start-interviewCold-start interview — builds your watchlist, indexes the policy library, and learns your materiality threshold so the monitor surfaces signal instead of noise.
Open in Claude

Connect your tools

Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access.

Add a connector for each tool you want Claude to use.

Google Drive
Connect
Microsoft 365
Connect
CoCounsel Legal (Thomson Reuters)
Ground the applicability brief in authoritative content with citations you can verify.
Connect

Set the working folder

Put the regulation PDF, your product descriptions, and your current policies in one folder on your machine, then in the Claude desktop app choose Add folder and select it. Save it as a project so your product context, instructions, and memory stay attached for the next rule that drops — Claude reads from the folder and writes the applicability brief and action table back to it.

Regulatory / EU-AI-Act
eu-ai-act-final-text.pdfApr 22, 20264.1 MB
product-descriptions.docxMar 3, 202688 KB
current-privacy-and-ai-policies.pdfJan 12, 2026612 KB
In Cowork’s chat bar:Regulatory / EU-AI-Act

The prompt

Copy this into Claude

Read this regulation against our product descriptions and current policies. Draft the compliance brief: what changed from the prior rule, which provisions apply to us and why, and for each what we need to do and by when. Save it to the folder for product and compliance leads.

Regulatory / EU-AI-Act

Why this works

Prompt

Compare against your own documents. "Against our product descriptions and current policies" turns a 400-page rule into an applicability call, so the brief talks about your products by name, not the regulation in the abstract.

Prompt

Ask for what's changed since last time. "What changed from the prior rule" skips the parts you already comply with and puts the new obligations at the top of the brief.

Prompt

Pair each action with a deadline. "What we need to do and by when" makes every applicable provision land as an owner-ready task with a deadline, not a paragraph of analysis.

Source

Let the working folder supply context. The regulation, your product descriptions, and your policies sit in the working folder, so the brief is written against what you actually ship and the action table is saved next to the source text.

Get a better draft

Practice

Add an example to match. Drop a past applicability brief you like into the folder and Claude matches your structure and voice.

Practice

Ask it to flag uncertainty. Add "flag any provision where you're not sure it applies to us" so you know which applicability calls to check first when you review the draft.

Make Claude work for you

Tell Claude your own rules for this task, such as your jurisdictions and your memo format, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.

Make what we've done in this task so far into a skill called /applicability-brief.

Regulatory / EU-AI-Act

Review the skill, and save it if Claude hasn't already.

Make it repeatable

Run it on every new regulation

When a final rule drops, the applicability brief should already be drafting. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /applicability-brief runs each weekday on any new regulation you add to a watch folder. Create it as Regulatory/Watch, next to EU-AI-Act, and give Claude access to Regulatory.

Set up a scheduled task for weekdays at 9am: check Regulatory/Watch for any new file, run /applicability-brief on it against our product descriptions and policies in Regulatory/EU-AI-Act, and write the applicability brief and action table to a subfolder named for the regulation.

Regulatory
Scheduled taskActive
New-regulation applicability brief

Runs /applicability-brief on every new file in Regulatory/Watch and writes the brief and action table to a subfolder named for the regulation.

Every Weekdays at 9amOpen in Claude

To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.

Share with your teammates

Your /applicability-brief skill now carries your jurisdictions and your memo format. Share it so product, privacy, and compliance all read the same brief, and the action table follows the same structure every time a rule drops.

Going forward