Document reader
Reads text out of a scanned or photographed document and matches it into structured fields like the issue, the jurisdiction, the parties, the dates, and the amounts.
I'm building thisThese are the tools the legal help field keeps rebuilding alone. Any team could build each one, and every team could reuse it.
A tool travels across teams and platforms because you reach it rather than rebuild it. The same reader, classifier, or connector can serve a team on a commercial assistant, a team on a self-hosted platform, and a team running its own code. We are gathering the tools worth building once for the whole field, and we want to know who is already working on each one. Working on one of these? Raise your hand on its card.
Reads text out of a scanned or photographed document and matches it into structured fields like the issue, the jurisdiction, the parties, the dates, and the amounts.
I'm building thisStrips personal information out of documents and conversations before any of it reaches a model.
I'm building thisTurns real, PII-rich materials into realistic fake versions you can safely share and test against, including poor-quality images that mirror what people actually upload.
I'm building thisMaps a person's description of their problem to a legal category so a tool can route them and ground its answer.
I'm building thisTurns a place into the right court and the right local rules.
I'm building thisSorts who qualifies for a service and who the tool is speaking to, sometimes by asking a short set of questions.
I'm building thisSends a matter to the right service, queue, or person.
I'm building thisFinds the right passage in a knowledge base and hands it to a tool to ground an answer.
I'm building thisPulls client, case, and court-record data from the systems an organization already runs, so a person never re-enters what a system already knows.
I'm building thisFills official court and government forms and assembles complete filing packets from a person's answers, so they hand in the right paperwork the first time.
I'm building thisFiles a document into a court's electronic filing system and returns the receipt or rejection. Because most courts run on a small number of common backends, one connector can reach many jurisdictions at once.
I'm building thisSurfaces the filing fee, the fee-waiver path, and the way to pay.
I'm building thisChecks whether a document was actually served on the other party, follows the proof of service, and flags when service has not happened.
I'm building thisCounts the real deadline for an action, handling court days versus calendar days, service-by-mail tolling, and the triggers that start the clock.
I'm building thisKeeps a tool inside legal information and out of advice that crosses into the unauthorized practice of law.
I'm building thisSpots a domestic-violence disclosure or a safety emergency and routes it to a human and the right resources.
I'm building thisRuns a tool against gold-standard legal questions on a schedule and watches for hallucinations and quality drops over time.
I'm building thisRuns the standard attacks against a tool, including attempts to leak personal information or subvert its instructions, before it reaches the public.
I'm building thisTell us what you are working on, and we will connect you with the others building it, add it to the commons, and help the field build it once instead of many times over. If you are using one of these and would build on it, we want to hear that too.
Tell us what you're building →Don't see your tool on the list? Tell us about it.