AI in personal injury.

Why personal injury is the clearest AI fit in any practice #

Most practice areas have an ambiguous AI thesis. Personal injury does not. The single largest cost on the typical contingent-fee case is medical-records review and chronology, and that workflow is uniquely well-suited to AI.

The reasons:

• The records arrive in a known form. They are PDF or HL7-formatted exports from hospital records systems, with a finite number of dialects. The variability is manageable.
• The output is structured. A medical chronology is a table: date, provider, encounter type, complaint, finding, treatment. The format is the same on every case.
• The judgement layer is explicit. What the lawyer wants from the records is mostly extractive (what happened) plus a narrow inferential layer (what the records support arguing). AI is good at the first; the lawyer does the second.
• The volume is high. A serious case can produce two to ten thousand pages of medical records. Manual chronology of that volume runs to dozens of paralegal hours.

By contrast, almost every other practice area has either lower volume, less-structured documents, more judgement-bearing output, or all three. Personal injury is the practice where the AI thesis is least ambiguous in 2026.

Where AI fits without sanctions risk #

The defensible AI workflows in plaintiff-side personal-injury practice cluster around four tasks.

Medical-records chronology. This is the headline use case. The records are uploaded to the chronology tool; the tool produces a date-ordered table of encounters with extracted complaints, findings, and treatments. The lawyer reviews the chronology against the records (sample-checked, not page-by-page) and then uses the chronology as the basis for the demand letter, mediation memorandum, deposition prep, and trial exhibits.

Liability-document review. Police reports, EMS reports, scene photographs, vehicle-damage estimates. Less voluminous than medical records but structurally similar. AI extracts the key facts into a liability summary; the lawyer reviews and supplements with attorney-work-product analysis that the AI does not see.

Damages calculation worksheet. Once the chronology is built, the damages worksheet is mechanical: bills incurred, paid, written off, future medical projection, lost wages, pain-and-suffering bracket. AI produces the first version of the worksheet; the lawyer adjusts the projection assumptions.

Deposition preparation. Once the medical chronology and liability summary are in place, AI can produce a first-pass outline of treating-physician deposition questions, accident-reconstruction-expert questions, and defendant-driver questions. The lawyer revises in light of the strategic theory the AI does not have.

What ties these together: AI produces a structured artefact (chronology, summary, worksheet, outline) that the lawyer then uses as input to a strategic-judgement step. The AI is not making the strategic judgement.

Where AI breaks: demand letters and exhibit-bound prose #

The most common bad AI use in personal-injury practice is demand-letter generation.

The temptation is obvious. The medical chronology is built; the damages worksheet is populated; the legal theory is settled. Asking an AI to convert these inputs into a polished demand letter saves an hour or two per case. At a hundred cases a year, the time savings look meaningful.

The risk is that the demand letter is almost always an exhibit. It appears in the subsequent litigation as evidence of pre-suit communications. If the demand letter contains a misstatement of fact — a treatment date that does not appear in the records, a damages figure that the worksheet does not support, a citation to a case the lawyer never read — the misstatement is preserved in the litigation file forever and is exhibitable in cross-examination of the lawyer.

Sanctions-adjacent rulings in 2025 and 2026 have included demand letters with AI-fabricated case citations. The court has not always reached a sanctions question — demand letters are pre-suit and the Federal Rules of Civil Procedure do not directly govern them — but the cases have settled with the bench's strong implication that they would have. The bar opinions track the same view.

The implementation rule: AI builds the chronology, the worksheet, and the outline of the demand letter. The lawyer (or a paralegal under the lawyer's supervision per Rule 5.3) writes the actual prose of the demand letter. AI may suggest sentence-level edits the way a copy-editor would; it should not be the source of the document's voice or its factual claims.

Vendor selection: medical-records-trained vs general-purpose #

Personal-injury firms face a vendor-selection question that does not arise as sharply in other practices: do we use a tool trained on medical records, or a general-purpose tool with a long context window?

The trade-offs:

• Medical-records-specific tools (Casepoint, RecordsONE, Steno's medical-records products, the medical-records modules in CoCounsel and Lexis+ AI). Trained on or fine-tuned for medical-records language. Better at extracting non-obvious entries (anaesthesia notes, nursing flowsheets, lab values) than general models. Typically more expensive per matter or per page.
• General-purpose enterprise AI (ChatGPT Enterprise, Claude for Work, Gemini for Workspace) with a long context window. Will produce a usable chronology if the firm provides clear extraction instructions. May miss specialist terminology. Lower per-matter cost but more lawyer-time per case to verify the output.

The crossover point is roughly fifty cases per year per attorney. Below that, a general-purpose AI plus some lawyer-time for verification is cheaper. Above it, the specialist tools win.

For larger plaintiff's firms, the practical pattern in 2026 is to run a specialist tool for chronology and a general-purpose AI for the surrounding workflow (demand-letter outlining, deposition prep, mediation memorandum first drafts).

The recommended stack #

For a typical solo or small plaintiff-side firm with twenty to two hundred cases per year:

• Practice management. Clio Manage or MyCase, both with personal-injury-specific case templates. SmartAdvocate and CASEpeer for firms that want plaintiff-specific PMS rather than horizontal PMS. (Cross-reference our 2026 PMS buyer’s guide.)
• Embedded AI. Clio Duo or MyCase IQ, or the AI features inside SmartAdvocate / CASEpeer. Used for matter-summarisation and intake-narrative generation.
• Medical-records chronology. RecordsONE, Casepoint, or the medical-records workflow inside CoCounsel or Lexis+ AI. The single highest-leverage AI choice for this practice.
• Demand-letter and analysis support. ChatGPT Enterprise or Claude for Work. Used for outlines, edits, and strategic-question first drafts. Not for final-prose generation of demand letters.
• Legal research. CoCounsel or Lexis+ AI. The personal-injury caselaw layer; the Mata-driven verification standard applies.
• Settlement-tracking and lien-resolution tooling. Synergy Settlement Services or comparable. AI is not the value here; the tooling is the value.

Indicative monthly stack budget per attorney: $300-$700, with the biggest variable being whether the firm runs a specialist medical-records tool. The math is in section seven.

Implementation playbook (six weeks) #

Personal-injury implementations are faster than family-law implementations because the workflow is more standardised and the AI fit is sharper.

Week one: case selection. Pick five recently-closed cases of varying complexity. These will be the regression-test set: the firm already knows the answer (chronology, damages number, settlement amount). The AI tools will be benchmarked against the closed-case answers, not against the firm’s aspirations.

Weeks two and three: chronology vendor evaluation. Run the same five cases through two or three medical-records chronology vendors. Compare the chronologies the vendors produce against the firm’s closed-case chronology. Differences fall into three buckets: vendor missed something the firm caught, vendor caught something the firm missed, vendor and firm disagree about classification. The first two are diagnostic; the third needs a workflow rule.

Week four: practice-management integration. Connect the chosen chronology vendor to the firm’s practice-management platform. Both Clio and MyCase have established medical-records vendor integrations; the SmartAdvocate / CASEpeer ecosystems have their own.

Week five: workflow standardisation. Document the new standard: when records arrive, who uploads to the chronology vendor, who reviews the chronology, where the chronology lives in the matter file, how it links to the damages worksheet. One page is enough; the goal is consistency.

Week six: training and live cut-over. Two-hour training session for all attorneys and paralegals. Cut over to the new workflow on every new case from that day; legacy cases continue with the old workflow until they close.

ROI: the contingent-fee math #

Personal-injury ROI math is unusually clean because the firm captures the savings as margin, not as billable hours.

For a representative serious case, the firm spends roughly:

• Twelve to twenty-five paralegal hours on medical-records ordering, organisation, and chronology
• Two to four attorney hours reviewing the chronology and pulling the damages number
• Three to six attorney hours on the demand letter and supporting documentation
• Variable additional time on deposition prep and mediation

The chronology workflow alone, with AI, drops paralegal time by roughly sixty to seventy-five percent and attorney review time by twenty to thirty percent. On a paralegal time saving of fifteen hours per case at a fully-loaded paralegal cost of $50 per hour, that is $750 per case. On the attorney saving, another $200-$400 per case.

For a two-attorney firm running two hundred cases per year, the chronology workflow alone produces $190,000-$230,000 in cost savings annually. The AI-stack budget for that firm is $25,000-$50,000 annually. The first-quarter ROI math is comfortably positive.

The contingent-fee structure means the savings flow to the firm rather than to the client (the client pays the agreed contingent percentage regardless of how much the firm spent). This makes personal injury different from hourly-billing practices: the AI economics are unambiguously in the firm’s favour.

Bar-rules and ethics flags specific to personal injury #

The general ABA Op. 512 framework applies. The personal-injury-specific overlays:

• HIPAA on the medical-records side. The firm is a Business Associate of the client (the patient) for the protected health information that comes into the matter file. AI vendors that ingest these documents are sub-processors; the firm needs a Business Associate Agreement with the AI vendor or written documentation that the vendor is acting on behalf of the client’s records release. ChatGPT Enterprise, Claude for Work, Casepoint, and the major specialist vendors all support BAA execution; consumer-tier AI does not.
• Lien resolution. Medicare, Medicaid, ERISA, and hospital liens often consume thirty to fifty percent of a settlement. AI tooling for lien-resolution is improving but the determinations are statutory and the lawyer is responsible. The lien analysis is not an AI-delegable task in the way chronology is.
• Solicitation rules. Most state bars permit AI-assisted client communications but not AI-initiated solicitation of accident victims. AI-driven outbound contact (e.g., scraping accident reports and sending letters) is not protected by Op. 512 and is governed by the solicitation rules in Rules 7.2 and 7.3.
• Contingent-fee disclosure. The lawyer is not required to disclose AI use as a line item on the closing statement, but the savings are not the client’s. The Op. 512 fee analysis (Rule 1.5) reaches the same answer for contingent-fee work as for hourly: the lawyer cannot ‘bill’ the AI’s time. In contingent-fee practice this just means the savings stay with the firm rather than appear as a discount on the bill.

Citations and further reading.

• Mata v. Avianca, Inc., 678 F. Supp. 3d 443 (S.D.N.Y. 2023). Sanctions for AI-fabricated citations.
• ABA Formal Opinion 512 (July 2024).
• Health Insurance Portability and Accountability Act (HIPAA), 42 U.S.C. § 1320d et seq.
• ABA Model Rule 1.6 (confidentiality).
• ABA Model Rule 5.3 (supervision of nonlawyer assistance).
• IXSOR: Legal Practice Management Software 2026 — Buyer’s Guide.
• IXSOR: AI Vendor Diligence Catalogue.
• IXSOR: Mata v. Avianca, three years on.