Impact feed
When legislation changes, precedent documents go stale — quietly.
StatuteGraph watches every amendment as it commences and shows you exactly which clause patterns and precedent templates it breaks. Start with the latest changes below, open one to see everything it touches, then click straight through to the document itself.
- Amendments shown
- 30
- Clause patterns touched
- 110
- Template families affected
- 0
- Critical or high
- 0
Get alerted when your area of law moves
Alerts onDemo only — nothing is sent anywhere. Your choice is saved in this browser and flags the matching rows below.
Demo only — no notifications are sent. Matching rows below carry the alert marker.
Latest changes
The ten most recent amendments to commence.
No results for these filters.
Trends
How legislative change is flowing into precedent documents. Pick your area of law and every chart below scopes to it — or keep the whole-of-law view.
Your area of law
Showing the whole of law. Pick one or more areas to scope every chart on this page.
Top 8 provisions by affected clause patterns — whole corpus
Hover an edge for the clause-pattern count. Click a node to isolate its edges; click again to release.
Table view — every edge in this graph
| Provision | Document type | Clause patterns |
|---|
Amendments by month
Last 12 months to August 2026 · whole of law, all jurisdictions
Table view
| Month | Amendments |
|---|
Affected clause patterns by practice area
Whole of law · 110 clause patterns across 30 amendments
Pricing & API
What it costs to get alerts for your area of law — with every affected clause found in your precedents and a redline suggested. The API underneath is for software vendors.
What it costs for your team
Estimates use this demo's fictitious dataset. Alerts, affected-clause highlighting and suggested redlines are all included in the seat price.
The plans, in plain English
Per-seat revenue is the wedge. Per-call licensing to other vendors is the business.
Under the hood — the API vendors buy
You don't need any of this to get alerts. It's how document management and contract tools embed the same answers inside their own products.
Request builder
Responses are generated from this demo’s local dataset — nothing leaves the page.
Response
200 OKGET /v1/impacts
About this play
The second-order thesis behind StatuteGraph, in plain English.
The first-order wedge
The obvious product is a tool that updates a law firm’s precedent documents when legislation changes. A statute is amended, the tool finds the clauses in the firm’s templates that no longer work, and proposes a redline. Firms buy it per seat, because keeping a precedent bank current is expensive, dull, and the sort of work that quietly slips until something goes wrong.
What the wedge actually accrues
To do that job at all, the tool has to build a map: which legislative provisions touch which clause patterns in which kinds of document. That map is the real asset, and it is the thing nobody currently owns, because nobody else sits inside the update workflow. Every time a lawyer accepts or rejects a proposed change, the system gets a labelled edge between a provision and a clause — a piece of ground truth that cannot be scraped, only earned by being in the loop. The redlines are the by-product; the graph is what compounds.
The two parties it connects
On one side are the legislative and regulatory feeds: bills, gazettals, commencement dates, explanatory memoranda. On the other side is every product that touches a document — document management systems, contract lifecycle tools, drafting assistants, in-house legal teams, and rival firms. Those products all face the same question and none of them can answer it: when this amendment commences, which of my templates break? StatuteGraph is the layer that sits between the two and answers it in a form software can consume.
The endgame
Bloomberg for statutory change impact. Seats fund the build and keep the labelling flowing; the licensed feed is the business, priced per call to vendors who would rather buy the map than build it. Churn stays low because the graph gets better with age and leaving means losing the history behind every edge. The thing that would validate it is narrow and testable: get one document management or contract lifecycle vendor to say they would pay for a feed telling them which templates a bill amendment touches — and ask that before building anything past the prototype.
Table view — affected clauses in this document
| Clause | Heading | Clause pattern | Provision |
|---|