The exhibit tour.

A board that holds the file to a standard.

Every matter moves through phases, and every phase carries its own task list. Between phases stand gates: conditions the file must satisfy before it advances. A gate can warn, block outright, or demand an admin — and every override is written to the audit trail.

• 73starter phase tasks loaded on day one — edit them into your firm’s playbook
• Gates configured per phase: warn · block · require-admin
• Overrides are permitted, named, and audited — never silent

Deadlines computed, not remembered.

A court-rules engine with 6 jurisdiction packs — California, Florida, Georgia, New York, Texas, Federal — computes the docket from counting rules, holidays and service methods. Upload a scheduling order and the dates are extracted for your review before anything touches the calendar. Presuit clocks and in-app SOL alarms run underneath it all.

• 6 jurisdiction packs, each verified against a golden-date test suite
• CMO extraction — dates proposed, reviewed, then applied
• Presuit clocks for notice-and-demand regimes
• In-app SOL alarms on every matter

Two hundred pages in. Five documents out.

Drop a records dump on CaseIntel and it reads the whole thing: splits the file at the real document boundaries, classifies each piece, and summarizes what it found. Nothing is filed until you review the split — the analysis proposes, the lawyer disposes.

• Splits multi-document PDFs at the true boundaries
• Classifies each segment — records, bills, reports, wage docs
• Every split reviewed before it becomes part of the file

Clients see status. Providers see requests.

A client portal with two-way messaging, document uploads and plain-language case status — the calls asking “anything new?” stop. A separate provider portal gives medical providers exactly the requests and correspondence that concern them, and nothing else.

• Client portal: status, uploads, e-sign, two-way messaging
• Provider portal, scoped to the provider’s own matters
• Every portal grant — and every revocation — is audited

The record of the record.

Every state change is written to an append-only audit trail that users cannot alter — there is no edit path in the product. Money movements carry the amount, in both directions: the disbursement and the void that reversed it. Disclosures carry a tag in both directions too: the grant of access and its revocation.

• Append-only — the product ships no edit path, for anyone
• Money events tagged with amounts — entries and their reversals alike
• Disclosure events tagged — shares, exports, and revocations
• 200+ tables carry the audit trigger

How the trail is kept →