Every plan, including Free · v1.0.0
Regulatory Change Tracker
Tracks a specific instrument or rule change through to the deadlines it creates for a matter
- Protocols
- 3
- Skills
- 2
- Public sources
- 3
- Workflows
- 1
The Sources tab: the regulators and publishers scanned, with the date each was last read.
What it does
Tracks a specific instrument or rule change through to the deadlines it creates for a matter.
Typical tasks
- 01Track a specific instrument from consultation to force
- 02Link a rule change to the matters it affects
- 03Confirm the in-force date and transitional provisions of a change
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.
How it works
From task to memo, in 5 steps.
Every step is recorded under How this was made on the finished run, with a pass, a needs a look, or a failure against each check. Nothing here is a description of intent. It is what the software does.
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.
Governed by
3 protocols.
Protocols run before and during the work: they plan, confirm the jurisdiction, screen personal data, check privilege. Gates run after, on the output, and they are code rather than a model's opinion. A failed gate is shown, never hidden.
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
What comes back
A document with its working attached.
- 01Status
- 02Deadline
- 03Linked matters
- 04Open questions
Sources it may cite
Connectors in the catalogue
Catalogue tiles, not live integrations today. Documents are uploaded to the matter.
- OpenLaw
Try it
Three tasks to start with.
These are the prompts the agent suggests inside the product. 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:
What it does not do yet
- It follows one named instrument at a time: sector-wide sweeping is Horizon Scanning's job, not this agent's.
Workflows