Something lands, and within an hour three people have asked whether it applies to us. The honest answer usually depends on a threshold buried in Article 3 and an exemption that only makes sense if you already know how the definitions work.

That's why briefing a regulation is mostly scope rather than summary. Anyone can restate what a law says. The useful work is deciding who's actually caught by it, what they have to do, and when the clock started.

Start with what it actually is

Binding law in force, law adopted but not yet applicable, a proposal still moving, and non-binding guidance are four different things, and people act on all of them as though they were the first one.

So the briefing establishes that up front and keeps the distinction all the way through. It's the single most common way a regulatory update misleads the person reading it.

Want to try it?

Ask your Strawberry companion: “Brief me on this instrument: what changed, who it applies to, the obligations, penalties, and key dates, with provision references I can check.”

Skill

Brief a new law or enforcement action

Brief me on this instrument and what it requires.

Work from the instrument, not the coverage

Most of what's written about a new law in its first week is written from other people's summaries. Strawberry can go to the official register, the regulator's own site, and the subscriptions you already have, then read the provisions themselves and use commentary afterwards to check that reading.

Matter details stay out of the search box while it does that. The instrument is public; your interest in it may not be.

Written for whoever has to read it

The same instrument needs to become three quite different documents, and the register matters as much as the content:

ReaderWhat lands
A specialistFull detail with article-level references, no explanation of terms they already use daily
A clientPlain language, defined terms, and a numbered list of what they need to do
A boardOne page, the headline exposure, and the number attached to getting it wrong

Underneath, the substance is the same: what changed and where, who's caught and at what threshold, which obligations fall on which kind of actor, the penalties, and the dates that matter. In force, applicable from, transition ending, deadline. Those get confused constantly and they're the part people plan against.

Checked before it goes out

Every provision reference is confirmed against the instrument itself. Article and section numbers are structural and hold up well. Page references don't, and get treated as unverified until someone looks.

Dates come from the official text rather than from reporting about it, and the version is checked for amendments since publication. Anything that can't be confirmed is flagged rather than left sitting there looking as solid as the rest.

If you track an area continuously, this becomes a Routine that watches the agreed official sources and tells you only when something genuinely moves. Worth setting up once you know which sources count and what you'd want to be interrupted for.

Official Strawberry skill
Copy skill file Download skill file

Brief a Regulation

Turn a published instrument — a new law, an enforcement action, updated guidance — into a briefing someone can act on. The work is scope and applicability, not summary.

1. Identify the instrument and the audience

Confirm exactly which instrument is in scope, in which jurisdiction, and at what stage: binding law in force, adopted but not yet applicable, a proposal, or non-binding guidance. Those are different things and readers act on them differently.

Establish who the briefing is for, because it changes the register more than the content:

  • Expert: full legal detail, article-level references, assumes familiarity.
  • Client-facing: plain language, actionable takeaways, technical terms defined.
  • Board-level: one page, headline risk, financial exposure, no citations in the body.

2. Work from the instrument itself

Read the actual text, not commentary about it. Use commentary afterward to check your reading and to find what practitioners think matters. Strawberry can work through official registers, regulator sites, and subscriptions the user already has, and follow citations into the underlying provisions.

Keep confidential matter details out of search queries.

3. Cover what a reader needs to act

Depending on audience and instrument:

  • what changed, with specific article or section references;
  • who is affected, and the thresholds or exemptions that decide it;
  • obligations, separated by the type of actor they fall on;
  • enforcement and penalties;
  • key dates — in force, applicable from, transition periods, deadlines;
  • practical implications, and what is still pending or expected.

Distinguish binding obligation from guidance and from proposal throughout. Readers routinely act on proposals as though they were law, and a briefing that blurs the two causes that.

4. Verify before returning it

Confirm every provision reference against the instrument itself. Article and section references are structural and reliable; page references are not. Confirm dates against the official text rather than reporting about it, and confirm the instrument has not been amended since the version you read. Flag anything unverified rather than leaving it unmarked.

5. Deliver and continue

Lead with what the reader must do and by when. Keep the detail beneath it.

Use strawberry/legal/compare-across-jurisdictions when the same obligation needs comparing across several regimes, and strawberry/legal/research-a-legal-question when the real need is an answer to a question rather than a briefing on an instrument.

When the user tracks an area continuously, a Routine can watch agreed official sources and report only material developments — new binding instruments, enforcement actions, imminent deadlines. Agree the sources, what counts as material, the cadence, and the review point before setting one up.