Every bill, every record, every provider - one running total, cited to the page.
A PI matter lives and dies pre-litigation, in the treatment phase everyone treats like a waiting room. MatterOS treats it as the real work: medical bills sum themselves into your specials automatically, and the whole file is ready the moment you decide to demand.
What drives this practice: statute-of-limitations
What actually eats a personal injury attorney's week.
Medical bills arrive constantly, from providers who don't coordinate
Specials accumulate across a dozen providers over months of treatment, and by demand time nobody's certain the running total is right. MatterOS extracts every bill on arrival and adds it to `medical_specials` automatically - a continuously updating number instead of a spreadsheet someone rebuilds the week of the demand.
A government defendant changes the clock without announcing it
Notice-of-claim requirements against public entities are short and easy to miss entirely if nobody thinks to ask the question. MatterOS asks it at intake - any government entity involved? - and arms the notice clock immediately if the answer is yes.
Liens quietly eat the recovery
Medicare, Medicaid, ERISA, and provider liens all stack against the same settlement, and the client's net-to-recovery number depends on getting every one of them resolved. MatterOS tracks `liens_total` as a running figure against the case value from day one.
The stages MatterOS already knows this practice runs through.
Not a generic case-management pipeline - the actual shape of a matter in this discipline, branches and terminal stages included.
- Intake & investigation
- Treatment ongoing
- Records collection
- Demand & negotiation
- Litigation
- Settlement / trial
- Liens & disbursement
The statute of limitations, and the notice window hiding behind it
SOL gets calendared from the incident date the day the file opens - jurisdiction-variable, tolled automatically if the client is a minor. The real trap MatterOS is built to catch: a government entity in the mix arms a separate notice-of-claim clock, often 60-180 days, the single most common way a PI case dies before anyone files anything.
Everything hangs off this date.
Derived from the date of loss via the jurisdiction overlay - confirm the overlay's count.
A minor client triggers tolling and court-approval requirements on any settlement.
A city, county, state agency, or other government body named as a defendant triggers a short, separate notice-of-claim deadline - confirm it immediately.
Per coverage layer; UM/UIM tracked separately.
Running total; auto-accumulated from extracted bills.
Demand letter draft ready; treatment records gap flagged for Dr. Okafor.
The Legal Secretary
The Fact Ledger keeps every number honest.
This practice doesn't get a bespoke calculator yet - it gets something more foundational: every fact MatterOS extracts is cited to its source, contradictions are flagged instead of smoothed over, and gaps show up as gaps rather than silence.
MatterOS already knows what this practice's paperwork looks like.
Drop a file into the matter and it gets filed to the right category on arrival - no manual sorting, no naming convention to remember.
A PI matter, assembled - from the first call to the demand.
Not five separate tools reconciled by hand: one matter, one Fact Ledger, moving through intake, records, chronology, deadlines, and demand in the order a real PI file actually moves.
The file opens itself around the incident date
A new PI client's police report or incident report gets read the day it's uploaded - incident date, parties, citations - and the statute of limitations calendars off it immediately, tolled automatically if the client is a minor. The government-entity question gets asked at intake, not discovered later: a city vehicle, a transit authority, a public building in the fact pattern arms a separate notice-of-claim clock, often 60-180 days, well before the SOL itself would ever become the problem.
Medical records ingestion, provider by provider
Records and bills arrive from four, six, sometimes a dozen providers, on no schedule anyone controls. Each one files itself into the matter's Evidence pillar under the right provider, gets deduplicated against the encounter it belongs to, and adds to a running medical_specials total the same day it lands - not at demand time, when someone has to rebuild the number from a folder. This is the exact ingestion, deduplication, and code-translation workflow the medical-records guide below walks through step by step; on a PI matter it is not a separate tool, it is the same Evidence pillar the rest of the file lives in.
Every treatment date lands in the Fact Ledger, cited to its page
As records come in, MatterOS builds the date-ordered chronology of encounters, diagnoses, and treatment directly in the Fact Ledger - the same structure that holds every other fact on the matter. Each entry is cited to the source page it came from, contradictions between providers get flagged instead of silently resolved, and a gap in treatment shows up as a gap (MatterOS flags no new medical records in 60 days) rather than a case that's quietly gone stale. MMI, when it's reached, surfaces as the soft gate it is.
SOL, notice-of-claim, and the litigation cascade, all in one place
The statute of limitations and any notice-of-claim clock sit on the matter from day one, ranked in the Cockpit against every other deadline across the caseload - not in a separate tickler system a paralegal has to remember to check. If the case doesn't resolve pre-suit, the Litigation & Disputes stage segment layers in as internal sub-stages on the same matter: the scheduling-order cascade, discovery deadlines, and the answer clock all activate without starting a second file or losing a day of the pre-litigation record.
The demand package assembles from what's already on the file
By the time treatment concludes, the demand letter isn't a fresh re-read of a year of records - it assembles from the specials total, the lost-wage figures, the liens tracker, and the cited chronology already sitting on the matter. The Coverage & Exposure module keeps case value against available policy limits visible for the life of the matter, so the moment specials approach the limits stack is the moment a policy-limits demand becomes the obvious move, not a guess made under deadline pressure.
Records ingestion and chronology building, in depth
The step above where records get deduplicated, coded, and turned into a cited chronology is its own full workflow guide - written for the attorney evaluating how the review actually happens, page by page.
Never the wrong word in front of a client - or a court.
Every draft and every synthesis MatterOS produces for this practice follows the same negative-vocabulary rules a careful associate would.
The checklist MatterOS opens before you've had coffee.
Nothing moves without records access.
Six reasons personal injury attorneys choose MatterOS.
The treatment phase - often the longest part of the case - gets its own staleness signal: no new medical records in 60 days flags the file, instead of the case going quiet for a season.
The Coverage & Exposure module keeps case value against available policy limits (UM/UIM tracked separately) visible for the life of the matter, flagging when specials approach limits - the moment a policy-limits demand becomes the right move.
Speaks adjuster language, not court language: liability, damages, specials vs. generals, MMI, subrogation, bad faith - never 'prosecutor,' never 'opposing counsel' for the adjuster.
Declarations pages get read specifically for coverage limits the day they arrive, because the limits number drives every negotiation decision after it.
Litigation entry doesn't mean starting over: the Litigation & Disputes cascade layers in as internal sub-stages the moment the case is filed, on the same matter.
HIPAA authorizations and letters of representation to every carrier are opening-day, blocking checklist items - nothing about a PI file moves without records access.
What this looks like on a real file.
A new client calls the day after a rear-end collision. Intake reads the police report the moment it's uploaded - incident date, parties, citations - and calendars the SOL before the call ends. The government-entity question gets asked immediately, because a delivery truck involved changes everything about the clock.
Over the following months, records and bills land from four different providers on no predictable schedule. Each one files itself to the right provider folder, and the specials total on the matter's dashboard ticks up the same day - no month-end reconciliation, no digging through a folder to remember what's already been counted.
MMI gets reached in month seven. MatterOS surfaces it as the soft gate it is, and the demand package assembles from the specials, lost wages, and liens already sitting on the matter - not from a re-read of a year of records the week before the letter goes out.
Questions personal injury attorneys actually ask.
Does MatterOS track medical specials automatically?
Yes - every medical bill that comes in gets extracted and added to a running `medical_specials` total on the matter, so the number is current the day you need it for a demand instead of something a paralegal reconstructs from a folder.
What if my client was hit by a government vehicle or hurt on public property?
MatterOS asks about a government entity at intake specifically because notice-of-claim deadlines against public defendants are often just 60-180 days and are the classic way a otherwise-solid PI case gets barred before suit is ever filed. Flagging a government entity arms that clock immediately.
Can it help me decide when to send a policy-limits demand?
The Coverage & Exposure module tracks case value against available limits continuously and flags when specials approach the limits stack - which is exactly the signal that a policy-limits demand is the right move, before the file drifts past the moment it would have landed hardest.
What happens if the case has to go into litigation?
The Litigation & Disputes stage segment - pleadings, discovery, trial - layers directly into the same matter as internal sub-stages. Nothing about the pre-litigation work gets orphaned in a separate file; it's the same matter, the same Fact Ledger, from intake through trial.
See how MatterOS runs a personal injury matter - on your own file.
Drop in the documents from a real matter and watch it assemble: parties, dates, deadlines, and a synthesis written the way personal injury attorneys actually talk. Free 7-day trial, no card required to start.