Follow the evolution of the world's largest open legal workflow database
Open Matter Plans went online in 2026, but the work behind it did not start there. It started in 2015 with a question about how legal matters are shaped, carried on in 2019 with practice systems, precedents and workflow generators, and came together this year as a single dataset. This is that story.
We checked every case citation across the network, one by one. About one in six that could be resolved was wrong. Here is what we found, what we corrected, what we removed, and the rule we now hold every legal claim to.
More than 700 court forms, council forms and precedents, each one mapped field by field to a single standard. Here is how the library was assembled, how we watch for changes at the source, and why we publish our own weak spots.
Every court and council form on the network can now be filled, signed and assembled in your browser - and the document never leaves your machine. No upload, no retention window, no page limits, and redaction that is verified before the file is allowed to save.
Legal AI is only as reliable as the data structure beneath it. Every field in the OMPN standard ships with inbuilt, machine-readable instructions - what it means, how it is formatted, what values it accepts - so any AI tool can read, map, and fill matter data without guessing. Integration and standardisation become the easy part.
The registry no longer just lives on a website. Matter plans now stream directly into your practice management system through a keyed API, carrying a shared field vocabulary, links back to view and improve each plan, and the community feedback loop that keeps them honest.
For years we have standardised how a legal matter is run. Now we are standardising the documents it produces. This is our mission to make legal work simpler and to gather it in one place - and the community feedback tools that shaped our matter plans are coming to our documents next.
We are launching our first precedent and document assemblies, built for Australian conveyancers and starting with council lodgement forms. The forms stay current, your client's data never leaves your office, and family law documents and court forms are next.
We analysed five decades of census data, longitudinal studies, and peer-reviewed research to build a free Marriage Survival Predictor. Here is what we found - and what your odds actually are.
A milestone worth celebrating. As of June 2026, the Open Matter Plans Network has become the largest open legal workflow database in the world - with over 400 matter plans, more than 5,000 individual tasks, and plans covering five countries. Here is how we got here and where we are heading next.
We have launched 37 new matter plans covering Canadian criminal law - from summary conviction appeals to dangerous offender proceedings under the Criminal Code. Each plan includes jurisdiction-specific timelines, practitioner traps, and PMS field mappings.
The latest SALI taxonomy release adds 18 new area-of-law codes and restructures the dispute resolution hierarchy. Here is how we have mapped these changes across our existing plan library.
A deep dive into how our embedded practitioner trap system automatically surfaces critical deadlines - and how PMS integrations can auto-calculate countdown alerts at 45, 30, 14, and 7 days before expiry.
A step-by-step guide to connecting your practice management system to Open Matter Plans. Covers authentication, fetching plans by jurisdiction, and pushing task structures via the sync endpoint.
We have published 17 matter plans covering New Zealand family law - including parenting orders, relationship property division, and protection order applications under the Family Violence Act 2018.
When a practitioner forks a matter plan to adapt it for their jurisdiction, it enters our peer review pipeline. Learn how voting, reputation points, and editorial review combine to maintain plan quality.
Every plan on the network follows the same four levels: matter type, stages, milestones and tasks. Here is the methodology behind that structure, how we name plans, how forks work, and why the metadata never lives in the title.