Regulatory Change Tracker Agent
Tracks a specific instrument or rule change through to the deadlines it creates for a matter
Compliance & Regulatory
No credit card required
| Development | Materiality | Published | Deadline |
|---|---|---|---|
| Scanning… | |||
You hand it
- Track a specific instrument from consultation to force
- Link a rule change to the matters it affects
- Confirm the in-force date and transitional provisions of a change
You get back
A tracked entry with the instrument's status, deadline, owner and linked matters.
You can rely on it because
It runs inside the matter, reads only what is on the file, and records every step under How this was made.
From the watch to the register.
The Regulatory Change Tracker follows a named regulatory instrument or rule change from first publication through consultation and into force, and links it to the matters and practice areas it affects, so a change identified by Horizon Scanning can be worked through to a concrete deadline and owner.
- 01
Name the instrument
Name the regulatory instrument or rule change to follow.
- 02
Plan and screen
Planning Protocol maps the tracking plan, and Jurisdiction Gatekeeper confirms the instrument sits within a jurisdiction the firm has enabled.
- 03
Track the diff
Produces a tracked-change diff against the prior version, correlated with the regulator's own consultation rationale and recent enforcement context.
- 04
Check freshness
Source Freshness Check confirms the version tracked is current, not stale.
- 05
Link and hand off
Links the instrument to the matters and practice areas it affects, so the change carries a deadline and an owner.
Three tasks to start with.
The prompts the agent suggests inside the workspace. Paste your own document under any of them.
Track an instrument to force
Track this instrument from first publication through consultation and into force, and tell me the transitional provisions and the in-force date:
Diff a rule against the last version
Produce a tracked-change diff of this rule against its prior version, with the regulator's own consultation rationale alongside each change:
Link a change to our matters
Tell me which of our open matters this regulatory change affects, and the deadline and owner each one now needs:
Who it is for, and what it will not do yet.
Best for
- Regulatory lawyers who need one named instrument followed from consultation to force.
- Compliance teams turning a Horizon Scanning alert into a concrete deadline and owner.
- Anyone confirming the transitional provisions before a rule bites.
Not yet
- It follows one named instrument at a time: sector-wide sweeping is Horizon Scanning's job, not this agent's.
Under the hoodProtocols, gates, skills and sources, for the reader who wants them.
Protocols
- 01Planning ProtocolMaps out the plan before any work starts: which sources answer which part of the task, in what order.
- 02Jurisdiction GatekeeperConfirms the task sits inside a jurisdiction the firm has enabled, and flags anything that strays outside it.
- 03Source Freshness CheckConfirms every source relied on was fetched during the run and has not gone stale since.
Skills
- Regulatory Diff & Gap Method
- Policy Library Indexing
Connectors in the catalogue
Catalogue tiles, not live integrations today. Documents are uploaded to the matter.
- OpenLaw
Sources it may cite
See it do real work.
- 01From a horizon development to a client updateRegulatory change usually reaches a firm as a forwarded email from whoever reads the most. Horizon Scanning turns it into a register with materiality bands, deadlines and owners, and one action moves a development straight into a client letter.
- 02Map Digital Services Act duties for an online marketplaceA marketplace operating across the EU has grown past the point where its original terms and processes fit its obligations. The run maps the duties that apply to it and matches each one against what the platform currently does.