PriorCall

Your firm already reviewed these documents.

Metadata onlyDeterministicPer-client vaultsNever per-GB
Fig. 1One client’s memory, compounding
Animated diagram: a privilege call made in Matter A drops into the client vault, Matter B adds two more, and when Matter C opens on the same documents the vault returns those calls and they are applied automatically. MATTER A CLOSED 2024 MATTER B CLOSED 2025 CLIENT VAULT EVERY CALL KEPT MATTER C OPENED TODAY PRIOR CALLS APPLIED — NO SECOND REVIEW

Cross-matter litigation memory The problem The Solution

PriorCall keeps every privilege call and production decision your firm has made for a client, across every matter. When the next one opens, the review starts where the last one ended.

Nothing at your firm remembers across matters. You defend the same carrier in dozens of matters a year. Same custodians, same email threads, same privilege calls. Every new matter, your team reads thousands of documents the firm already coded last quarter, because the review platform starts each matter at zero.

Three matters side by side, each holding the same three documents and each running its own full review. Nothing passes between them. MATTER A MATTER B MATTER C FULL REVIEW FULL REVIEW FULL REVIEW THREE DOCUMENTS. NINE REVIEWS.

It costs margin.

Under carrier flat fees and panel rates, the hours spent reading a document twice are unrecoverable. ABA Opinion 93-379 says you can't bill recycled work anyway, so the redundancy isn't revenue deferred. It's just gone.

Diagram: a flat fee sets a ceiling. The first review fits inside it. The second review runs past it, and the overrun is written off. FLAT FEE — WHAT THE CARRIER PAYS FEE CEILING FIRST REVIEW SECOND REVIEW WRITTEN OFF TWO REVIEWS. ONE FEE.

It costs exposure.

Produce an email in one matter that an associate withheld as privileged in another, and you've handed opposing counsel a waiver argument and your malpractice carrier a problem. No system at your firm checks for this, because none of them remember the last matter.

Diagram: the same document, identified by identical hash, stamped Produced in Matter A but Withheld as privileged in Matter B. MATTER A — HENDERSON MD5 a1b2c8…94ff PRODUCED BATES HEN000123 MATTER B — ALVAREZ MD5 a1b2c8…94ff WITHHELD · PRIV. NO BATES — PRIVILEGE LOG SAME DOCUMENT — CONFLICTING TREATMENT

You send load files. You get back a report and overlays your platform can read.

Your documents never move. PriorCall reads the metadata your vendor already exported — never document bodies, never attachments, never text.

Ingest

Point PriorCall at the DAT, OPT and production logs you already have. It reads them the way your vendor wrote them, sniffs the encoding, and maps the fields. Corrupt rows are quarantined and reported, not crashed on.

Match

Every document is fingerprinted and compared against the client's vault through four deterministic tiers. The same inputs always produce the same match, and no model sits anywhere in the matching path.

Recall

When a matter opens, you get what's already been reviewed, the prior call with its rationale attached, and every place your calls disagree. Reviewers spend their hours on what's actually new.

Animated diagram: a load file is read, tested against four deterministic tiers in turn, banked in the client vault, and returned as an audit report and a coding overlay. LOAD FILES · DAT / OPT I · NATIVE HASH II · TEXT HASH III · NEAR-DUP IV · THREAD DETERMINISTIC TIERS · NO MODEL CLIENT VAULT AUDIT REPORT · PDF CODING OVERLAY · CSV
Fig. 3 The whole pipeline: metadata in, memory out

PriorCall is not another eDiscovery vendor. It is a different kind of tool.

How PriorCall compares with legacy eDiscovery platforms and AI review tools
Category Legacy eDiscovery platforms AI review tools PriorCall
What they remember One matter at a time. The next one opens at zero. The statistics inside a model, which are not the calls your lawyers made. Every decision your firm has made for a client, in every matter.
How you pay By the gigabyte, for as long as you hold the data. The meter never stops. By the document and by the matter, then again when the next matter opens. A flat rate for each client vault. Nothing is charged by the gigabyte or by the document stored.
What touches your documents All of it. They hold the corpus. A model reads every document body. Metadata, and only metadata. Document bodies never arrive.
How matching is decided Not applicable. A probability score, which you would then have to explain to a judge. Deterministic and tiered. Run the same inputs again and you get the same answer.
Consistency across matters Outside what the platform is for. Decided from scratch on each matter, so the same risk comes back each time. This is the whole point of the product. Conflicts are audited and reported wherever your calls disagree.

Flat, per vault. The meter never runs on your data.

Consistency Audit $1,500flat · 90 days We backfill one client vault from load files you already have and deliver the full cross-matter audit. Credited in full against your first year if you continue. This is where every firm starts.
Client vault $500per month One vault is your firm plus one carrier or corporate client. Unlimited matters, unlimited users, full history.
Matter activation $150per matter Charged when a new matter opens, which is the thing that actually grows. Covers ingest and matching.

Month to month after the first year. Cancel whenever you like and export everything in an open format. The memory is yours — we just keep it.

Start by finding out what your firm already knows.

Ninety days, one client vault, one audit. We show you what overlapped and what conflicted, and you keep the report either way.

Book a Consistency Audit

$1,500, fully credited · Works alongside your review platform · Metadata only