Case Bound
Sign in
Any US court · Invitation-only workspace

Every filing, order, and message in your case. In one record you can actually use.

Case Bound pulls your docket into a working timeline, reads the documents behind it, and cross-references what was ordered against what actually happened. You confirm every finding before it counts.

Sign in to your workspaceSee how it works

Access is by invitation. Accounts are provisioned per case.

The record, the documents, and the argument

Three layers that build on each other. Nothing is inferred without a source you can open.

A docket you can read

Entries arrive grouped by date with classification, linked filings, and the full order text a click away. Suffix cases stay separate but can be reviewed as one series.

Documents that answer back

PDFs and scans are extracted, put through OCR when they have to be, and indexed. Ask the record a question and get an answer with the page it came from.

Attorney Prep

Import parenting-app and email threads, map the participants, and test an issue against the record. It surfaces adverse evidence on purpose, not just the helpful parts.

A phone contact log

Record each call, or import the spreadsheet you have been keeping. Ordered calls are counted separately from extra ones, so you can see what actually happened against what was required.

How it works

Three things go in, four things come out. You are in control of every step, and nothing is collected in the background.

What you bring

  1. Your docket. The list of everything filed in your case. One click in the browser extension on Missouri Case.net, a spreadsheet exported from any other court portal, or entries typed in by hand.
  2. Your documents. Orders, motions, exhibits. PDFs and scans both. Photographed and faxed pages are read with OCR.
  3. Your communications. Exports from a parenting app, email, or texts. Plus a log of phone calls, imported from a spreadsheet or recorded as they happen.

What Case Bound does

  1. Organizes. Everything lands on one timeline, grouped by date, with related case numbers kept separate but reviewable together.
  2. Reads. Text is pulled out of every document once and indexed, so the same file is never processed twice.
  3. Cross-references. What an order requires is compared against what the record shows actually happened.
  4. Waits for you. Everything it finds arrives as a draft. You open the source, and you decide whether it counts.

What you get

  1. A readable record. A docket you can search and scan instead of a wall of court shorthand.
  2. Answers with receipts. Ask a question in plain words; every statement in the answer cites the page it came from.
  3. A compliance picture. Ordered phone contact counted against what happened, charted over time.
  4. A packet for your attorney. A reviewed, exportable compilation with exhibits, so you arrive organized instead of with a box.

What it will not do

Worth knowing before you start, so nothing here surprises you later.

Built for a file that matters

This holds a real, active legal matter. It is engineered accordingly.

  • Row-level security in the database. Case access is enforced in Postgres, not only in the application. Every table holding case data ships with its policies.
  • Keys stay on the server. No model key ever reaches the browser, and no service-role key is used by the app.
  • Nothing is logged that shouldn't be. Document text, extracted content, prompts, and auth codes stay out of the logs.
  • Invitation only. Accounts are created against a pending invitation for a specific case. There is no open signup.
  • Model output is proposed, never controlling. Confirmation gates are a design boundary, not a setting.

Your case already has a record. Make it legible.

Sign in to pick up where you left off, or ask the case owner for an invitation.

Sign inRequest access