BatesFlow

How it works

Every screen, end to end — real screenshots from a fictional Smith v. Smith matter.

01

Create the case

All productions inside a matter share the same caption, parties, court, and attorney details. Enter them once and every Rider, Bates Index, and Inventory picks them up automatically.

Create New Case modal with party, court, and attorney fields.
02

Upload both demands

Two drop zones by design: the demand opposing served on you, and the one you served on them. BatesFlow parses PDF or DOCX — even scanned — and extracts every numbered request automatically.

Both demands uploaded with 17 requests detected on each side.
03

Upload client documents

Drag a folder, drop a ZIP, or use the file picker. PDFs, Word, Excel, images, emails — anything you can render. Duplicates are caught client-side before they ever hit the server.

File picker showing a batch of client financial documents ready to upload.
04

AI sorts and classifies

Twenty matrimonial-specific categories — bank statements, brokerage, W-2, retirement, pay stubs, vehicle, more. Confidence scores on every document. And the AI tags which numbered request each document responds to, so eighty percent of mapping is done before you review.

Classified documents with confidence percentages and matched demand requests.
05

Inventory before production

A pre-production checkpoint. Export a Short list or Full table of everything about to be served, grouped by category with pages and date ranges. DOCX or XLSX. Filter by Our Client or Opposing.

Document Inventory screen showing documents grouped by category with page counts.
06

Production mapping

Every numbered request down the left, every classified document down the right. Pick a response type from the vocabulary New York matrimonial practice already uses — Produce, No Docs, In Opposing Possession, Previously Produced, and more.

Production mapping workspace showing 17 requests paired with response-type dropdowns.
07

Auto-Assign with AI

One click reads the actual language of every request and matches it against document content — not filenames. Counter goes from 10-of-17 to 17-of-17 assigned. You review and override; you don’t assemble from scratch.

Production mapping after auto-assign: 17 of 17 requests mapped, Run Production button active.
08

Run production

A pre-flight modal confirms request counts, document counts, and the Bates range. One more click generates Bates-stamped PDFs, a court-ready Rider DOCX, and a Bates Index XLSX — packaged in a single zip.

Generate Production modal with 25 documents ready to stamp and a Bates range preview.
09

Gap analysis on what comes back

When opposing’s production lands, run it against your demand. BatesFlow tags every request Fulfilled, Partial, or Missing and hands you a deficiency notice DOCX ready to serve — with the reasoning on every row.

Gap analysis results: 9 withheld, 6 partial, 2 acceptable, with expandable per-request reasoning.