Plain words on what happens to your documents, in what order, and what you can check at each step.
Run personally by Kevin Matos, Tessera Strategy, Queens, New York.
The 72 hours start at the last of three things: the full set received, the protective order signed, and payment cleared. The clock runs nights and weekends.
| When | What happens | Where you can check it |
|---|---|---|
| Day 1 | The set moves to the offline machine and is hashed again. Every file gets a document ID and a hash in the source index. Text is extracted. A sample of pages from every document type is checked by hand against the extracted text. The analysis starts. | Source Index tab; audit log |
| Day 2 | The analysis finishes. The citation gate checks every finding. I start reading each finding against its source page. | Audit Log Summary tab |
| Day 3 | Review finishes. Each finding gets a confidence level and a reviewer note. Unreadable pages and gaps go to Open Questions. The memo is written, quality checks run, and the package is assembled with checksums and delivered. | Findings tab; Open Questions tab; checksum file |
If delivery by hour 72 is at risk, I call you before the deadline with the reason and a new time.
A finding cannot be written without a source reference. That rule is part of the structure, not a setting.
After the analysis, a verification pass checks every finding four ways: the document ID exists in the source index, the page exists in that document, a line is given, and the text at that page and line contains the figure. A finding that fails is blocked. It goes to Open Questions or is dropped, and it never reaches the Findings tab.
The gate makes sure every figure has a source. It does not make every reading right. That is why I read each finding against its page before delivery, and why every row tells you exactly where to look.
Every processing step writes to an append-only log as it happens: unpacking, the manifest, extraction, the page check, the analysis, the citation gate, and any re-run. Lines are added. Nothing is edited or deleted afterward.
The log comes with the package, with a hash of the log recorded at the end of each run. The workbook's Audit Log Summary tab lists each run and, for your matter only, how many findings the system proposed, how many the gate blocked, and how many changed or were withdrawn in review. Those are counts, not accuracy claims.
If someone asks how a number was produced, the answer is a line in the log and a page and line in the source.
The business day after the corrections window closes, the set is destroyed: the documents and every copy and derived file I hold, including extracted text, indexes, working files and my copies of the deliverables.
Free and vendor-neutral: a one-page protective-order checklist for any outside document vendor. Email for the checklist.
Email the matter type and rough document count. You will have a reply the same business day.
Send no documents yet. Matter type and a rough count is enough. Open a prefilled email, copy the address below, or go to Start a matter on the main page.