Last reviewed: October 2026
A personal injury demand starts with information scattered across treatment notes, bills, imaging reports, correspondence, and other evidence. Before anyone can write a persuasive account of the claim, someone has to work out what happened, which treatment belongs in the narrative, and whether the numbers and supporting records agree.
That preparatory work is where AI earns its place in a personal injury practice. Its strongest contribution is speeding up the reading, extraction, organization, and comparison that come before a finished demand letter. Attorneys and their teams still decide what the evidence supports, what needs more investigation, and what position the firm should take.
Where AI Helps, and Where People Decide
| Stage | What AI can do | What a person must do |
| Records intake | Classify documents, make scans searchable, extract dates, diagnoses, and charges with page references | Reconcile against the document inventory; chase missing records |
| Medical review | Surface conflicting opinions across hundreds of pages | Read opinions in context; decide whether the conflict is real |
| Chronology and billing | Build a treatment timeline; link charges to visits; suggest codes | Verify totals and codes; separate charges, payments, and adjustments |
| Drafting | Produce an outline or first draft from structured facts | Set the demand position on liability, causation, and damages |
| Review | Point each assertion to its source page | Check every important statement and look for omissions |
Start With a File the Team Can Trace
The first stage is case-file ingestion: bringing the available records into a system that can process them. In practice that means identifying document types and providers, making scanned text searchable, and keeping references to the original files and pages. The immediate goal is an organized account of what the file actually contains.
AI can help pull dates of service, diagnoses, treatment descriptions, and charges into structured entries. A useful entry keeps both the extracted fact and its source location. Keeping a visit date separate from the date a report was signed, for example, gives the reviewer a distinction to check before either date reaches the demand.
Large files are where this help matters most. Published research supports the speed advantage on defined tasks, with real limits. In a study published in Gastroenterology, a general-purpose language model extracting data elements from liver cancer imaging reports reached about 93% accuracy compared with physician review, and physicians took 28 hours to do what the model did in two, according to UCSF’s summary. The lead researcher also noted the model did better at simple classification than at tasks involving comparison or arithmetic, which is exactly the kind of work involved in reconciling bills and totals. The study supports the potential of this stage; it doesn’t establish accuracy for an entire personal injury demand workflow.
The team should also reconcile what was processed against its document inventory. A referral to a specialist may reveal that records are missing. It doesn’t tell you what that specialist diagnosed or recommended.
Bring Conflicting Medical Opinions Into the Same View
Extracting facts becomes more useful when the system compares them across documents. Consider a hypothetical collision file with records from more than 20 providers. One physician attributes a shoulder condition to the accident. Another considers it degenerative and unrelated. Those opinions may sit hundreds of pages apart.
An AI-assisted review can bring both opinions forward, flag the apparent disagreement, and point to each source. It can also organize the distinctions worth investigating: whether the physicians reviewed the same imaging, had access to earlier records, or were addressing the same condition. A statement about the origin of a condition may answer a different question from a statement about aggravation of existing symptoms.
That gives the attorney a focused issue. The attorney still has to read the opinions in context, decide whether the conflict is real, and determine whether clarification, more records, or expert input is needed. The software can suggest questions; it can’t resolve a medical disagreement or choose the firm’s causation position. And the unresolved issue should survive into the next stage. A polished narrative shouldn’t quietly blend conflicting opinions into one confident conclusion.
Structure Treatment and Billing Before Drafting
Once extracted information is organized, AI can help build a medical chronology and connect it to billing entries. The chronology becomes an input to the demand, showing how complaints, evaluations, and treatment progressed. The reviewer decides which developments explain the claim and which are unrelated or ambiguous.
Billing needs the same separation. Charges, payments, adjustments, and balances should stay distinct, and duplicate statements should be flagged for reconciliation rather than added together. Several states now limit medical damages to amounts actually paid or owed rather than amounts billed, so keeping those figures apart isn’t just tidy bookkeeping; it can change what the demand is allowed to claim.
Coding is a narrower area where AI can help. It can suggest candidate CPT or ICD-10-CM codes from clear descriptions, or organize codes already in the records. Suggested codes should stay visibly separate from provider-reported codes until verified against the AMA’s CPT resources and the CDC’s ICD-10-CM browser and guidance, or by a qualified coding professional. A straightforward lookup is different from resolving incomplete documentation, modifiers, or bundled services. Verified coding makes treatment easier to categorize; it doesn’t establish causation or determine claim value.
Carry Structured Facts Into the Demand Letter
The drafting stage should draw on the organized file, including its open questions. AI can help turn treatment history, incident evidence, and damages documentation into an outline or first draft, identify supporting exhibits, and check that the draft’s references match the assembled package.
That continuity is the core of an AI-assisted demand-letter workflow: source material feeds structured facts, those facts support drafting and assembly, and a human reviewer checks the result before it is sent. AI-drafted demand letters are most useful when the firm can trace each important assertion back through that sequence.
The attorney supplies the demand position and decides how to present disputed liability, causation, future care, and damages. Drafting instructions should preserve uncertainty. A treatment option discussed in a record shouldn’t become a definite future surgery just because stronger wording reads better. Once the demand goes out, it starts the negotiation; this overview of how a personal injury settlement works covers what typically follows.
Review the Evidence Behind the Prose
Fluent output isn’t the same as verified output. The NIST Generative AI Profile identifies confidently presented false content, often called confabulation or hallucination, as a recognized risk. In demand preparation, that makes source review a working stage of the process, not a final spellcheck.
A practical review answers several separate questions:
- Does the provider and treatment inventory match the file, including material the draft may have left out?
- Do dates, charges, totals, and exhibit references agree with the underlying documents?
- Does each important medical statement accurately reflect its source, including uncertainty, contrary opinions, and preexisting conditions?
- Has unrelated treatment crept into the narrative, or has a tentative recommendation become an unsupported claim?
Source references make these checks easier, but the references themselves need checking. The cited page must support the specific statement, not just mention the same body part. Reviewing only what appears in a draft also leaves omissions untested, so the reviewer needs to look back at the file inventory and the flagged issues.
Strong performance on narrow tasks doesn’t make occasional errors harmless. A large file offers many chances for a small factual mistake to reach the demand. As systems improve, more of the professional’s time can shift toward auditing and correcting, but responsibility for the finished demand stays with the firm.
The Professional Responsibility Rules That Apply
A demand letter isn’t a court filing, but it is a statement of fact to a third party, and the ethics rules apply to it the same way.
- Truthfulness. ABA Model Rule 4.1 prohibits knowingly making a false statement of material fact to a third person, including an insurance adjuster. An AI-generated error that a lawyer sends without checking is still the lawyer’s statement.
- Competence with technology. Comment 8 to Model Rule 1.1 expects lawyers to understand the benefits and risks of the technology they use.
- Confidentiality. Medical records are among the most sensitive information a firm holds. Model Rule 1.6(c) requires reasonable efforts to prevent unauthorized disclosure, and ABA Formal Opinion 512 (2024) says lawyers should generally get a client’s informed consent before putting confidential information into an AI tool that may use it to train or that others can access.
- Supervision. When a vendor or tool does part of the work, the commentary to Model Rule 5.3 addresses the lawyer’s duty to make reasonable efforts to ensure that outside assistance is consistent with the lawyer’s professional obligations.
Formal Opinion 512 also cautions against surrendering professional judgment to an AI tool and discusses the need for independent verification. It interprets the ABA Model Rules; lawyers should check the rules and ethics guidance in their own jurisdiction, several of which have issued their own AI opinions.
How Verification Changes the Workload
Requiring human review doesn’t erase the efficiency gain. Finding every relevant fact from scratch, organizing it, and writing the first account can take far more effort than checking an organized work product with usable source references. How much time is saved depends on the first pass’s quality and how easily the reviewer can return to the evidence.
For a file with thousands of pages, the practical gain may be spending less time hunting for two competing opinions and more time assessing what they mean. Verification still takes attention, but the reviewer starts with the relevant material already gathered and the disagreement already flagged.
In firms with demand-ready files waiting in a queue, reducing repetitive processing can shorten the wait and increase what an existing team can handle. Missing records, unresolved medical questions, and attorney review remain real limits. Firms can measure the benefit by tracking preparation time alongside review time, corrections, and open issues, the same discipline behind most law firm efficiency improvements.
The useful endpoint is a demand whose important facts can be traced and whose judgments were made deliberately. AI can shorten the path to that point, giving attorneys, paralegals, and case managers more time for the decisions that deserve their attention.
Frequently Asked Questions
Can AI write a personal injury demand letter?
AI can draft one from organized facts, but the attorney must set the demand position, and every important statement should be verified against the records before the letter is sent.
How accurate is AI at reviewing medical records?
Research shows strong accuracy on narrow, defined extraction tasks, roughly 93% in one Gastroenterology study, but weaker performance on comparison and arithmetic. That is why billing totals and causation questions need human review.
Is it ethical for lawyers to use AI for demand letters?
Yes, with safeguards. ABA Formal Opinion 512 addresses competence, confidentiality, supervision, and verification, and Model Rule 4.1 still forbids knowingly false statements to insurers. State rules and opinions also apply.
Do I need client consent to use AI on a personal injury file?
It depends on the tool. ABA Formal Opinion 512 says informed consent is generally required before entering confidential information into tools that may retain or train on it. Check your jurisdiction’s guidance and the tool’s data terms.
Authorities & Sources
- American Bar Association, Formal Opinion 512: Generative Artificial Intelligence Tools (2024)
- American Bar Association, Model Rule 4.1: Truthfulness in Statements to Others
- American Bar Association, Comment on Model Rule 1.1: Competence
- American Bar Association, Model Rule 1.6: Confidentiality of Information
- American Bar Association, Comment on Model Rule 5.3
- National Institute of Standards and Technology, AI 600-1, Generative Artificial Intelligence Profile (2024)
- Ge et al., A Comparison of a Large Language Model vs Manual Chart Review, Gastroenterology (2024); UCSF summary
- American Medical Association, CPT code set overview; CDC, ICD-10-CM
Disclaimer
This article provides general information about the use of AI in personal injury practice and is not legal or ethics advice. Professional conduct rules and ethics opinions on AI vary by jurisdiction and are changing. Lawyers should consult the rules and guidance that apply in their own jurisdiction. The collision example in this article is hypothetical.
