Specials, gaps, pre-existing findings, surgical recommendation.
Litigation funding record review pulls the four facts an advance decision turns on out of the medical file: documented specials, treatment gaps, pre-existing findings, and any surgical recommendation. Every line is cited to its source page, for one plaintiff or for a fifty-thousand-claimant portfolio in diligence. Underwriters decide; we read.
The matrix is written down. So is the scoreboard.
We do not build for a case type until we can name the standard that defines a correct output and the person who grades the file against it. In litigation funding, both are unusually explicit: the matrix is written, and the deal either returns or it does not.
That makes this one of the few niches where a record read can be checked against a number that arrives on its own, without anyone grading the read.
Between 150 and 800 pages, and none of them sorted.
A funding request rarely arrives as one clean file. It arrives as whatever the plaintiff firm had on hand: an ER packet, a chiropractic ledger, an orthopedic office file, sometimes an imaging disc report, sent across two, three or four productions. The median file we scope for this work sits around 475 pages.
The pages themselves fight back. Faxed scans that have been printed and re-scanned twice, handwritten intake and treatment notes, billing sheets photographed on a phone, and the same discharge summary appearing in three productions at once. Under a flat 10¢ a page with duplicates free, that overlap is not billed twice.
The volume behind it is real. Industry estimates put consumer legal funding at roughly 150,000 to 300,000 advances a year, and Westfleet's annual report counts about $2.3 billion a year in new commercial litigation finance commitments. Mass tort diligence compounds that: one docket can put tens of thousands of claimant files in front of a single underwriting desk.
Four steps, starting with one real file.
Send one real file
A live advance request or a docket sample, in whatever shape it reached your desk. In the demo case that was 342 pages across 2 packets, with a wrong-patient page quarantined before the read started.
We return the read, page-cited
Documented specials, treatment gaps, pre-existing findings and any surgical recommendation, each one linked to the page it came from. You check it against what your own reviewer found on the same file.
We scope the build against your matrix
Your grid, your fields, your thresholds and your output format. We fit the extraction to the matrix you already underwrite on, rather than asking you to underwrite on ours.
You run it
Your underwriters price the deal and set the advance. We never estimate case value, score merit, or approve or decline a request. The read is an input to your decision, not the decision.
The rules the platform never breaks.
EVERY LINE CITED
HIPAA, under a signed BAA
Every file is handled under our Business Associate Agreement, from the first byte.
Never trains a model
Your records are never used to train any AI model — ours or anyone else's.
Every line cited
If we can't cite it, we don't say it. Every sentence links to its source page.
Deleted after delivery
Files are deleted 30 days after delivery, with a full audit log of every access.
Four capabilities behind every funding read.
The funding read is one deliverable of the same platform that reads, sorts, and cites the whole record.
Claims & Billing Ledger
Every billed amount in the specials traces to a source page. Click a figure and land on the document that justifies it.
Medical Chronology
The treatment timeline builds itself, so the gaps between visits are visible as intervals rather than buried in date stamps.
Mass Tort Batch Processing
The same extraction criteria run across an entire docket, so portfolio diligence reads every claimant file instead of a sample of them.
Treatment Relatedness Signals
Every visit and charge tagged related, unrelated or disputed against the covered incident, with the cited reasoning behind each tag. You adjudicate.
Litigation funding record review, answered.
Send one file. We'll tell you what we can read.
No obligation. If the case type is buildable we'll scope it; if it isn't, we'll say so.