PLATFORM
The rest of the machine.
The flagship modules get the headlines. These keep the case moving.
Chronology
Every fact in the case lands on one timeline, each entry cited to the exhibit, transcript, or filing it came from. Ask what happened between the March 12 inspection and the April 2 termination, and the chronology answers in seconds, built from the same sealed record everything else in LITIGATER reads from. The night before trial, that is the difference between finding the seven-week gap in your own account and having opposing counsel find it on cross.
Case Law Research
Search runs across case law, statutes, and secondary sources, and results land cited directly against the element they support, not as a memo you have to reverse-engineer into your outline. Every citation passes the Gate before it reaches your draft, checked once that it is still good law, once that it says what you are citing it for. At midnight before a reply brief is due, that is one less citation you have to re-check by hand, and one you will not have to explain in a sur-reply.
Damages & Settlement
Damages models are built from the facts already placed in the Proof Engine: medical bills, wage records, a life-care plan, each one traceable back to the exhibit behind it. Settlement posture is tracked against what the record can currently prove, not against what the complaint originally demanded. Walk into a mediation the week before trial, and the number on the table is the number the sealed record actually supports, not a guess from the original demand letter.
Trial Command
Exhibit lists, witness order, and deposition designations assemble from the record you already sealed, not from a fresh binder built the week of trial. Move a witness on Tuesday, and the exhibit list and the designations move with it instead of drifting out of sync. The night before opening, the binder you hand the paralegal is the same record the Proof Engine has been checking all along.
Post-Trial & Appeal
Preservation tracking starts at the first objection, not at the notice of appeal, so the record of what was preserved and what was waived builds itself across the whole case instead of getting reconstructed from memory after the verdict. If the verdict goes the wrong way, whether an issue was preserved is already answered, cited to the transcript line where you raised it. That is the record most appellate practices spend the first month after trial trying to piece back together by hand.
Practice Operations
LITIGATER is the system of record. Practice Operations runs intake, billing, and firm reporting natively, in the same file as the case, not synced in from somewhere else. Drafts still sync to Word, calendaring still syncs to Outlook. Clio-class sync exists for firms mid-migration: it's the off-ramp, not the destination.
One matter file, six modules deep.
Chronology, Case Law Research, Damages & Settlement, Trial Command, Post-Trial & Appeal, and Practice Operations all read from the same matter file: the facts placed in the Proof Engine, the exhibits sealed in the record, and the citations that have passed the Gate. None of the six keeps a separate copy of the case.
Each module writes something concrete back into that file in return: a cited timeline, authority pinned to the element it supports, a damages model tied to the exhibits behind it, an exhibit and witness list ready for the binder, a preservation record for appeal, and intake, billing, and firm reporting run natively through Practice Operations, with Word and Outlook still synced for drafts and calendaring.
Strategy stays yours: which theory to run, what to demand, when to settle. What these six modules remove is the manual reconciliation, the separate documents that used to drift out of sync the moment one of them changed. LITIGATER is the system of record now. Clio-class sync stays available while a firm migrates off its old one; it's the off-ramp, not the destination.