Features FAQ Beta Book a demo Sign in

The case file, doing the work

Every recording on this page is CaseMate itself, working one fictional trucking matter, Rowan v. Delmar Freight Systems, recorded from the installed Windows app. The one staged element is the assistant conversation — a drawn Claude Desktop window around live tool calls — and its caption says what was staged.

Assistant

Your AI works the case file itself

The case stops being something you paste into a chat. Ask a question and your assistant searches the record itself and answers with citations. What it finds, it files back into the case — tags, findings, issues — so the work outlives the conversation.

CaseMate hands your AI a full set of tools: search, read, cite, organize, draft.
Your assistant can prove a quote against the page before citing it — a misremembered quote is refused, not filed.
Its searches and sources appear inside the conversation — including the scanned page itself.

The window is a drawn recreation of Claude Desktop and the conversation was written in advance. The searches were not: CaseMate ran both, and every result and page on screen came back from it.

Transcript

A screen recording of an AI assistant working the case over MCP. The window is a recreated Claude Desktop and the conversation was written in advance; the tool calls inside it are CaseMate’s own MCP server, running. There is no audio; everything on screen is written out below.

What happens

A Claude Desktop window is on screen with CaseMate connected to it. The pointer clicks into the composer, types the question — “Was Unit 4180 actually roadworthy that night? Check the maintenance records.” — and sends it.
A working line appears, reading “Searching the case file…”, and a CaseMate search card opens inside the conversation.
The card fills: a skeleton first, then three results, each a page with its match strength and the matched passage in bold. The top one is the maintenance work order.
The working line changes to “Cross-checking the ECM download…” and a second search runs collapsed into a single row beneath the first.
The answer streams in — two paragraphs, each closing on a citation pill naming a production page.
The view scrolls back to the search card and the top result is expanded: the scanned work order renders inside the chat itself, the two BELOW MINIMUM inspection rows highlighted on the page.

What is on screen

The question: Typed in full: “Was Unit 4180 actually roadworthy that night? Check the maintenance records.”
The two searches: “brake lining below minimum returned to service”, run expanded in the recording; then “speed limit parameter raised”, run collapsed.
The results of the first: 0005_Rockvale_Maintenance.tif page 1 at 93%; 0006_Supplement_C.tif page 1 at 72%; 0001_Incident_Report.tif page 2 at 64%.
The answer, in full: “Not by its own records. The Rockvale work order found both rear-tandem forward-axle brake linings at 3/32 in. — below minimum — on Feb 29. The lining kit was backordered, so the slack adjusters were adjusted instead and the unit went back out the next morning with the linings unchanged. (PROD-002604 · p.1) The ECM download adds the sharper fact: the truck’s speed cap was raised from 62 to 68 mph the same day that work order closed, with no authorization anywhere in the production — and it was doing 58 in a 55 in the seconds before the crash. (PROD-003310 · p.1)”
What is staged: The window is a drawn recreation of Claude Desktop, and the assistant’s words were written in advance. The search tool calls, the results they return, and every page shown come from CaseMate’s MCP server over a live session.
Format: 23 seconds, 1920×1408 pixels.

Search

Ask in plain words. Land on the page.

Ask the way you would say it out loud. Search matches meaning as well as wording, so different words still find the passage. Open a result and you are looking at the scan itself, the match boxed on the page. Your assistant runs this same search over MCP.

Quoted phrases, OR, and exclusions still work — checked against the exact text, separately from the meaning match.
Narrow any search by document, folder, category, tag, file type, page range — or by whether a page was native text or a scan.
When the passage you want is buried rather than missing, one click reruns the search to favor exact wording.

The query is “brakes below minimum.” The top hit is the maintenance work order, and opening it scrolls to the inspection findings — the measurement column boxed on the scan, the two below-minimum readings inside it.

Transcript

A screen recording of CaseMate’s search over the read case, from the typed question to the scanned page it lands on. There is no audio; everything on screen is written out below.

What happens

The recording opens on the read case: the case name and its tabs across the top, the search box under them, the documents table beneath that.
The pointer clicks into the search box and types the question the way it would be said out loud — “brakes below minimum” — and runs it.
Two results come back — “Showing 1-2 of 2” — no third. Each is a page rather than a document: the file it sits in, the page number, a match strength, and the passage itself with the matched words in bold.
The top result is the Rockvale maintenance work order, page 1, at 41% similar to the query, its snippet carrying “BELOW MINIMUM BELOW MINIMUM” in bold. The second is the ECM supplement, page 1, at 37%, matching on the last-stop record’s brake-switch readings and the note that recorded speed exceeded the posted limit before brake application.
The top result is opened. The scanned work order fills the viewer, the document toolbar above it and the citations panel beside it.
The page scrolls itself to the matched passage and holds there — the whole inspection-findings measurement column boxed in yellow on the scan, the two readings of “3/32 in. BELOW MINIMUM” inside that one box.

What is on screen

The query: Typed in full: “brakes below minimum”. No operators, no field syntax, no connectors.
The results, in order: Production 003/0005_Rockvale_Maintenance.pdf page 1, 41% similar to the query; Production 003/0006_Supplement_C.pdf page 1, 37% similar to the query. “Showing 1-2 of 2” — no third result.
The boxed rows: CaseMate’s OCR groups the whole inspection-findings measurement column into one block, so the citation boxes all five readings; the two readings of “3/32 in. BELOW MINIMUM” — left and right rear tandem, forward axle — sit inside that one box, on the scan of the work order at the end of the recording.
The second result: Production 003/0006_Supplement_C.pdf, page 1: the ECM download’s last-stop record — brake-switch readings in the seconds before the stop, and the note that recorded road speed exceeded the posted 55 mph limit for the four seconds before brake application.
Format: 30 seconds, 1920×1152 pixels.

Organize

A production filed like a case file, not a folder

The Documents tab is the case’s inventory: every file with its page count, category, tags, and the quality of its read. Sort or filter by any of it. A document nobody has filed yet says so, right in the table.

Tags live in groups you define — Issues, Review, whatever the case needs — and your assistant can create and apply them too.
Everything in the case takes tags — documents, findings, drafts — and every tag is a one-click filter.
Two files with identical contents are flagged as duplicates — grouped, never silently merged.

Six documents with their categories, flags, and tags. One click on the Brakes filter narrows them to the two that carry it.

Transcript

A screen recording of the Documents tab of that same read case: the production filed, then filtered down to one issue. There is no audio; everything on screen is written out below.

What happens

The recording opens on the working inventory of the matter — six scanned documents, one row each.
Every row carries what CaseMate holds about the file: its page count, the block-character statistics from the read, its category, its OCR flags, the date it was indexed, and the tags a reviewer put on it.
Five of the six are filed to a category. The ECM supplement is not, and its Category cell still shows the affordance for filing it.
The pointer opens the Filters panel above the table.
It opens the Issues tag group and picks Brakes; the menu closes.
An active-filter chip appears and the table narrows in place, from six documents to the two that carry the tag: the maintenance work order and the ECM supplement.

What is on screen

The table: Six documents, nine pages, every one a scanned, image-only PDF, all indexed the same minute — Aug 19, 2026, 12:28 AM.
The categories: Evidence, Research, Precedent — the three every case starts with. Five documents are filed to Evidence; the sixth still shows the “File…” prompt in its Category cell.
The tags: Two groups, both the case’s own. Issues: Brakes, Hours of service, Signal timing, Damages. Review: Hot, Follow up.
The filter: Issues → Brakes. Six rows become two — 0005_Rockvale_Maintenance.pdf and 0006_Supplement_C.pdf.
Format: 28 seconds, 1920×1152 pixels.

Findings & citations

Facts that carry their receipts

Findings are the facts you will argue, in three kinds: evidence from the record, research reasoned from it, and precedent from earlier rulings. Every one is anchored by citations, and a citation is an exact quote from a specific page.

A citation is built from the page’s own text — it cannot quote something the page does not say.
Click any finding, claim, or issue and CaseMate opens the cited page with the quoted text highlighted.
It runs backwards too: open a page and see every citation that lands there, and every finding relying on it.

A finding followed all the way down: its citation, the blocks it is built from and the text they hold, then the work order itself with the cited blocks boxed.

Transcript

A screen recording of CaseMate’s Findings tab, following one finding all the way down to the page it rests on. There is no audio; everything on screen is written out below.

What happens

The recording opens on Findings, on Evidence: six findings, each a statement of fact carrying the citation chips that support it and the issue it is filed under.
Five are filed under an issue. The medical finding is still marked Unfiled.
The pointer clicks the citation chip on the finding about the brake linings.
The citation opens: its title, the block ranges on the page it is built from and the text those blocks hold, and — below — the findings that cite it: the linings finding itself, and a precedent finding filed beside it.
The pointer clicks the citation’s document line.
The scanned maintenance work order opens with the reported-defect and inspection-findings blocks boxed in yellow, the two 3/32 in. measurements darker again inside it, and the citations panel runs the relationship backwards beside the page: every finding and entity property that relies on this block.

What is on screen

The six evidence findings: 58 mph with the brake switch off until −2.0 s; HOS alerts silenced most nights; Linings below minimum at return to service; Rib fractures; out of work pending re-evaluation; Six hours off duty recorded, not ten; Speed limiter raised the day the work order closed.
The citation opened: “WO 8841-C — linings below minimum at return to service”, built from two block ranges on page 1 of Production 003/0005_Rockvale_Maintenance.pdf: blocks 1–3 (the reported-defect narrative and the inspection findings) and block 5 (the parts-and-labour note).
What relies on it: The citation’s own “Cited by” table lists the linings finding and the precedent finding “Hollis v. Tidewater Express — return to service below minimum”. On the page itself, the citations panel adds a third: the entity property “Unit 4180: Brake lining rear”.
The boxed rows: The REPORTED DEFECT and INSPECTION FINDINGS blocks, boxed on the scan of the work order — CaseMate’s light OCR groups a whole paragraph or table into one block — with the two 3/32 in. readings — left and right rear tandem, forward axle — darker again inside that box. The same rows the search recording lands on.
Format: 28 seconds, 1920×1152 pixels.

Drafting

Draft where the record lives

Drafts are Word documents that belong to the case. Read one like paper, and edit any paragraph in place, right where you are reading it. Every save lands a new version with a redline against the last. When the draft needs to leave, it exports as real .docx.

You cannot lose a draft: restoring an old version brings it forward as a new one, so history never rewrites.
The redline is exact to the word — insertions and deletions marked inside every changed paragraph.
If the draft changed while you worked, CaseMate refuses to save over it — it shows you what changed first.

A motion open for reading, then its version history: the redline against the version before, every change marked to the word.

Transcript

A screen recording of a draft inside the case: read as paper, then opened to the redline of its current version. There is no audio; everything on screen is written out below.

What happens

The recording opens on the case’s Documents tab, and the pointer clicks Drafts. The tab holds one row — “Motion to Compel — Dispatch Communications and ECM Records”, current version v2, last updated Aug 19, 2026, 12:46 AM.
The row is clicked and the draft opens in the right pane: the motion titled above the page, with zoom controls and an Export as .docx button in the toolbar.
The draft reads as paper: a heading, paragraphs with bold and italic runs, quoted testimony in italic, and bulleted record cites (PROD-002604, PROD-003310, PROD-002016).
The view scrolls down to the version history beneath the document. The draft is on its current version, v2.
The pointer opens that version’s redline against the one before it.
The counts come up first: of fifteen blocks, three changed and twelve unchanged — nothing added, nothing removed.
Under them are the changed blocks themselves, marked to the word — the insertions and deletions inside each changed paragraph, not just the fact that it changed.

What is on screen

The draft: “Motion to Compel — Dispatch Communications and ECM Records”, on its current version, v2, exportable as .docx from the toolbar.
The redline: Version 1 to version 2: 3 changed, 12 unchanged, 15 blocks in all — none added, none removed.
What changed: A relief request narrowed from “the thirty days preceding the collision” to the dates 02/12/2024 through 03/14/2024; a closing sentence — “such further relief as the Court deems just” — replaced with leave to renew on sanctions should the audit trail confirm the change was directed after the defect report; and the paragraph about a proposed order rewritten into Plaintiff reserving a spoliation motion as to the telematics log and the bay-4 footage.
Format: 27 seconds, 1920×1152 pixels.

Reading

Every page becomes searchable text

Import a folder of scans into a case and CaseMate starts reading it, page by page, until the whole matter is text you can search. A page that already carries text is read directly; an image-only scan is read by OCR.

A page the quick read cannot make out goes automatically to a slower, more careful read.
A crash or a restart picks up exactly where the reading stopped. Nothing starts over.
Any page can be sent back for the careful read later — that one page, not the whole production.

From “No cases yet.” to a read production: nine pages, none failed.

Transcript

A screen recording of CaseMate, from a fresh install to a read production, made in the product itself working one fictional matter. There is no audio; everything on screen is written out below.

What happens

The recording opens on a fresh install: CaseMate’s header, the Cases page, one “Open a new case” form, and the words “No cases yet.” beneath it. Nothing has been created and nothing has been imported.
The pointer clicks into the Case name field and types “Rowan v. Delmar Freight Systems”, and under the field CaseMate answers with the id it will use — “Will be created as ‘rowan-v-delmar-freight-systems’”.
Create case is clicked. The form clears, and where “No cases yet.” stood there is now the case: a card reading “No documents yet.” and “Import a folder to bring this case’s documents in”, carrying the three category badges every new case starts with — Evidence, Research, Precedent.
The case name is clicked and its page opens: the caption as the heading, one “Add documents to this case” panel offering “Import a folder” and “or drop a folder here”, and the case’s still-empty tabs — Documents, History, Findings, Claims / Issues, Entities, Drafts.
The pointer clicks Import a folder. The button turns to a spinner, a line under it reads “Waiting for you to choose a folder to import…”, and Windows’ own “Browse For Folder” dialog opens onto “Select a folder”.
The folder tree is scrolled to “Production 003”, it is selected, and OK is clicked.
CaseMate copies the six files into the case, and a green banner lands: “Imported 6 files — casemate is processing them”, with “Watch progress, or keep working — the batch runs on its own.”
The pointer clicks Watch progress, and the batch’s live page opens without a reload, onto a run already counting.
Left of the split is the page image being read. Coloured boxes land over one block of text after another — headings, production stamps, ruled rows, body paragraphs — as each block is located on the page.
Right of the split, those same blocks arrive as lines of text in the live feed, in the order they were read.
The counters climb through the production, each file closing as its last page lands, and the run finishes inside the recording — nine pages of nine, six files of six, none failed, marked Done, at 51.8 seconds elapsed. The recording holds on the finished state, then restarts.

What is on screen

The matter: Rowan v. Delmar Freight Systems, a fictional trucking case. No client material appears in any recording on this site.
The fresh case: Created in the recording as “rowan-v-delmar-freight-systems”, carrying the three categories every new case starts with: Evidence, Research, Precedent.
The production: “Production 003” — six scanned, image-only PDFs, nine pages in total.
The documents: 0001_Incident_Report.pdf (2 pages), 0002_Kessler_Deposition.pdf (2), 0003_Meridian_Regional_Records.pdf (1), 0004_Delmar_Correspondence.pdf (2), 0005_Rockvale_Maintenance.pdf (1), 0006_Supplement_C.pdf (1).
The boxes: Each coloured box is one block of text located on the page image. The line that appears beside it in the feed is that block’s text.
The counters: A status line counting pages and files, stat cards for files, pages, done, failed and elapsed, and a progress bar — ending at 9/9 pages · 6/6 files, none failed, in 51.8 seconds.
Reading now: The left panel is captioned “reading page N…” as it works through the production; the right panel is the live feed, the same page’s blocks filling in beside it in the colours of the boxes.
Format: 87 seconds, 1920×1152 pixels.

All of it on your own hardware

Everything above ran on one ordinary machine, and the case file stays on it — we never hold a copy of a privileged file. Reading and indexing send nothing anywhere; case material leaves only when your assistant works the file, and then only through the AI provider your firm has already approved. No per-page charges, no usage tiers, no AI bill beyond the subscription you already pay.

Book a 15-minute demo Join the beta

Or start with the overview.