Complete guide · 2026

AI for Bodily Injury Claims: The Complete 2026 Guide

How insurers, TPAs, and defense teams use AI to review medical records, answer demands, and manage risk on injury claims, with current statistics, state rules, checklists, and an ROI calculator.

Andrej EvtimovAndrej EvtimovamaiseOct 25, 202636 min read48 min listen

Listen to this guide

Now playing: Summary

0:00 / 48:03

Narrated with an AI voice. Tables, sources, and interactive tools are best viewed on the page.

Published and updated October 25, 2026
Share
Contents
  1. Key takeaways
  2. What is AI for BI claims?
  3. Why BI claims need AI now
  4. Four kinds of AI
  5. How it works, step by step
  6. AI across the claim lifecycle
  7. Medical records review
  8. Demands and time-limited demands
  9. Evaluation and settlement
  10. Litigation and nuclear verdicts
  11. Regulation and bad faith
  12. Data security and privacy
  13. ROI and the business case
  14. Evaluating vendors
  15. Implementation roadmap
  16. Claimants and fairness
  17. How amaise approaches BI
  18. Glossary
  19. FAQ
  20. Sources

The short answer

AI for bodily injury claims is software that reads an entire injury claim file (medical records, bills, demand packages, police reports, pleadings, and adjuster notes), organizes it into a source-linked chronology and summary, and answers adjusters' questions with a citation to the exact page. The adjuster still decides coverage, liability, value, and settlement.

Key takeaways

  • The pressure is real: personal auto bodily injury severity reached $28,278 per claim in 2024, up 66% since 2015, and 57% of BI claimants had an attorney by 2022.
  • Four kinds of AI touch injury claims: rules-based valuation (the Colossus era), predictive models, document and generative AI, and agentic AI. They solve different problems.
  • The highest-value job is reading. Files of several hundred to several thousand pages are where AI saves the most time and catches what people miss.
  • Source links are non-negotiable. Every statement in an AI summary should open the page it came from, because omissions and hallucinations still happen.
  • Regulators expect governance, not bans. 29 U.S. jurisdictions have adopted the NAIC AI Model Bulletin, which explicitly covers claim administration.
  • Start with one painful workflow such as medical record review or time-limited demand response, measure it, then scale.

What is AI for bodily injury claims?

AI for bodily injury claims is a set of technologies that help insurers, third-party administrators (TPAs), independent medical examiners, and defense counsel understand injury claim files faster and more completely. It applies to third-party liability claims where someone is hurt: personal and commercial auto liability, general liability, workers' compensation, and medical malpractice.

In practice, a modern system does four jobs:

  1. Read everything. It ingests the full file, including scanned and handwritten pages, and turns it into searchable text.
  2. Organize it. It splits bundled PDFs into individual documents, classifies them, removes duplicates, and puts treatment in order by date of service.
  3. Extract what matters. It pulls out diagnoses, procedures, providers, treatment gaps, pre-existing conditions, billed amounts, and liability facts.
  4. Answer with evidence. It writes summaries and answers questions, and every statement links back to the page that supports it.

What it is not is an autonomous settlement engine. The most credible tools are built to inform the adjuster's judgment, not replace it, and regulators expect insurers to stay accountable for every decision "regardless of the tools and methods" used, in the words of the NAIC Model Bulletin on the Use of AI Systems by Insurers.

How is it different from general claims automation?

General claims automation focuses on high-volume, low-complexity work: first notice of loss intake, payments, routing, and simple property or auto physical damage claims. Photo-based damage estimation is a good example. Bodily injury is different. The facts live in long, messy, unstructured documents written by many different authors, the medical questions are subtle, and the financial stakes are high. A tool that is excellent at estimating a dented bumper from a photo cannot tell you whether a lumbar disc herniation was pre-existing.

Who uses AI on injury claims?

  • Carrier BI adjusters and casualty claims teams who review records, set reserves, and respond to demands.
  • TPAs that handle liability and workers' comp claims for self-insured clients.
  • Claims leaders and litigation managers who need early warning on severe or litigation-prone files.
  • Independent medical examiners and defense counsel who need a fast, neutral chronology.
  • Plaintiff law firms, on the other side of the table, which now use AI to assemble demand packages at scale.

Why bodily injury claims need AI in 2026

Bodily injury has become the most expensive and least predictable part of auto liability. Costs are rising faster than medical inflation, more claimants are represented, litigation is more common, and the experienced adjusters who used to absorb that complexity are retiring.

$28,278

average personal auto BI liability claim in 2024, up from $17,014 in 2015 (Triple-I / ISO)

57%

of BI claimants were represented by an attorney by 2022 (Insurance Research Council)

18%

of auto injury claimants litigated in 2022, up from 10% in 2017 (IRC)

53%

of auto liability dollars paid go to bodily injury, though fewer than 1 in 4 damage exposures carry a BI claim (CCC Crash Course 2026)

440 days

median time to close for represented BI claimants, more than double unrepresented ones (IRC)

$25.6B

in nuclear verdicts against corporate defendants in 2025, from nearly 200 verdicts of $10M or more (Marathon Strategies)

Claim severity is outrunning medical inflation

According to Triple-I, citing ISO data, the average personal auto bodily injury liability claim rose from $17,014 in 2015 to $28,278 in 2024. CCC's Crash Course 2026 reported average paid BI severity up 10.3% year over year and 32% over four years.

Average personal auto BI liability claimSource: Triple-I, citing ISO/Verisk
$17,0142015
$20,7692020
$26,1782023
$28,2782024

The Insurance Research Council's 2026 auto injury study, based on more than 7.4 million claims, found that the average BI payment grew about 7.8% a year between 2017 and 2022, roughly double the rate of medical-care inflation. Over the same period, the amount paid per dollar of medical bills rose from $1.80 to more than $2.30.

More attorneys, more litigation, longer claims

The same IRC study found that 57% of BI claimants were represented by 2022, the litigation rate for auto injury claimants nearly doubled from 10% to 18%, and represented claimants waited a median of about 440 days for their claim to close. Speed matters too. In Sedgwick's own book of business, 80% of pending auto BI claims had attorney representation within 14 days of first notice, and litigated BI claims cost about 5.5 times as much as non-litigated ones.

At the extreme end, Marathon Strategies counted nearly 200 nuclear verdicts of $10 million or more against corporations in 2025, totaling more than $25.6 billion, including $2.9 billion against automobile defendants. Triple-I and the Casualty Actuarial Society estimate that legal system abuse added $91.6 to $102.3 billion to personal auto liability losses between 2015 and 2024.

The plaintiff side is already using AI

Demand packages are increasingly assembled by software. EvenUp, the best-known plaintiff-side platform, says it works with more than 2,000 law firms and was valued at more than $2 billion after its 2025 funding round. When one side produces polished, 500-page demands in hours and the other side reviews them by hand, the side reading by hand loses time it often does not have, especially under a time-limited demand.

The adjuster capacity gap

The U.S. Bureau of Labor Statistics counts 389,700 claims adjusters, appraisers, examiners, and investigators and projects that number to fall 6% by 2035, while about 21,600 openings a year still need to be filled as people retire or leave. Sedgwick expects a quarter of claim adjusters to retire by the end of 2027. Experience is leaving the desk just as files get longer and more contested.

Four kinds of AI used on injury claims

"AI" covers very different technologies in claims. Mixing them up is the most common reason evaluations go wrong, so it helps to separate them before comparing vendors.

1

Rules-based valuation

Expert systems that score adjuster-entered injury codes to produce a value range. The Colossus era.

2

Predictive models

Machine learning trained on historical claims to score severity, litigation risk, or fraud.

3

Document and generative AI

OCR, classification, extraction, and language models that summarize records and answer questions.

4

Agentic AI

Teams of specialized AI agents that run multi-step reviews with checkpoints and human sign-off.

1. Rules-based valuation

Rules-based systems ask an adjuster to code the injuries and treatment, then apply severity points to produce a range for general damages. They are consistent and fast, but only as good as the coding, and they cannot read the file themselves. Their history (covered below) is the main reason regulators and claimants are wary of "black box" valuation.

2. Predictive models

Predictive models use structured claim data such as injury type, venue, attorney involvement, and treatment patterns to estimate the probability of an outcome: severity, litigation, or fraud. They are useful for triage and for routing complex files to experienced people early. Their blind spot is the same as rules engines: if the important facts are buried on page 312 of a scanned record, the model never sees them.

3. Document and generative AI

This is the category that changed the most since 2023. Optical character recognition (OCR) and vision models turn scans into text, classifiers sort pages into document types, and large language models (LLMs) summarize records and answer natural-language questions. Done well, it removes the hours spent finding and ordering information. Done carelessly, a general-purpose chatbot can produce fluent summaries that omit or invent facts, which is why source-linked answers matter so much (more on that below).

4. Agentic AI

Agentic AI chains several specialized steps together: one agent sorts and deduplicates records, another extracts medical facts, another checks bills against treatment, another drafts the summary, and a quality-assurance step checks that every statement has a source. Anthropic's widely cited guide to building effective agents recommends exactly this kind of design for high-stakes work: simple, composable steps with checkpoints and a pause for human review. In claims, the human checkpoint is the adjuster.

ApproachWhat it readsWhat it producesExplainabilityBest forWatch out for
Rules-based valuationInjury and treatment codes entered by the adjusterA general damages rangeMedium: rules are fixed, but tuning is often opaqueConsistency on routine soft-tissue claimsGarbage in, garbage out; rigid adherence to outputs
Predictive modelsStructured claim dataRisk scores and probabilitiesLow to mediumTriage, routing, early severity flagsBias in historical data; misses facts in documents
Document and generative AIThe documents themselvesChronologies, summaries, answersHigh when every statement links to a source pageMedical record review, demand review, Q&AOmissions and hallucinations without source links
Agentic AIThe whole file plus claim system dataMulti-step reviews, drafts, alerts, reportsHigh with step-level audit trailsEnd-to-end file review, large loss reports, demand responseOver-automation; needs clear human checkpoints

Looking for a Colossus alternative?

Colossus is the best-known rules-based BI valuation system. A 1999 Connecticut legislative research report describes it as a program originally developed in Australia and marketed in the U.S. by Computer Sciences Corporation (CSC), and CLM Magazine describes roughly 600 injury profiles that assign severity points to adjuster-entered data. It does not assess specials, liability, or offsets, and each insurer "tunes" it with its own settlement history.

That tuning became the center of controversy. In 2010, Allstate agreed to a $10 million settlement with 45 states after a multistate market-conduct examination. Regulators found inconsistent tuning across regions but "no systemic underpayment," and Allstate agreed not to require or reward settlement at the Colossus value and to tell claimants the tool might be used.

The lessons translate directly to modern AI:

  • Read the file, not just the codes. Modern document AI works from the records themselves, so the quality of the output no longer depends on how carefully someone keyed in injury codes.
  • Show your work. Every fact and suggestion should link to its source page, so the adjuster, a supervisor, a regulator, or a court can see why.
  • Keep humans in charge of value. AI should prepare the evaluation, not dictate it. Incentives tied to matching a machine number are exactly what regulators objected to.
  • Govern changes. Document model versions, testing, and overrides, as the NAIC bulletin now expects.

How AI for bodily injury claims works, step by step

Under the hood, a credible system runs the same sequence an experienced adjuster or nurse reviewer would, only faster and without skipping pages. Here is the pipeline from upload to answer.

  1. 01Ingest & OCR
  2. 02Split & classify
  3. 03Deduplicate
  4. 04Extract & code
  5. 05Chronology
  6. 06Analyze
  7. 07Knowledge graph
  8. 08Cited answers

Step 1: Ingest and OCR every page

Files arrive from the claims system or by upload. OCR and vision models convert scanned, faxed, and handwritten pages into searchable text. This matters because injury files are rarely clean: a single demand package can bundle hundreds of pages from a dozen providers in one PDF.

Step 2: Split and classify documents

The system splits bundled PDFs into individual documents and labels each one: emergency department record, MRI report, physical therapy note, operative report, bill, police report, demand letter, pleading, and so on. amaise's Core module, for example, classifies more than 50 document types.

Step 3: Remove duplicates

Demand packages repeat records. The same MRI report can appear three times, attached to different letters. Deduplication keeps repeated records from looking like separate treatment events and shrinks what a person has to read.

Step 4: Extract and code medical facts

Diagnoses, procedures, providers, dates of service, restrictions, and prescriptions are extracted and normalized, typically to ICD-10-CM for diagnoses and CPT for procedures. This is where engineering matters: a 2024 study in NEJM AI found that GPT-4 reproduced exact ICD-10-CM codes only 33.9% of the time when asked directly. Reliable coding comes from retrieval against coding knowledge bases plus validation, not from free-form generation.

Step 5: Build the treatment chronology

Events are ordered by date of service, not the date a document was printed or sent. Gaps in treatment are left visible rather than smoothed over, because a two-week delay before first treatment or a three-month break in care can matter to causation and value.

Step 6: Analyze causation, pre-existing conditions, and bills

The system flags prior injuries and degenerative findings, inconsistencies between providers' histories, and treatment that does not match the reported mechanism of injury. It reconciles bills to records and dates of service, spots duplicate charges, and applies offsets such as MedPay or PIP. Many carriers benchmark charges against data sources such as FAIR Health's property and casualty benchmarks, and Medicare conditional payments must be resolved before settlement; Milliman notes that Medicare can recover double damages if it is not repaid within 60 days.

Step 7: Store the facts in a knowledge graph

Instead of a pile of text, the extracted facts are stored as linked entities: the claimant, each provider, each diagnosis, each date, each bill, each source page. That structure makes cross-document questions possible ("Which providers documented prior neck pain?") and lets the system spot contradictions. amaise calls its per-claim knowledge graph CaseDNA.

Step 8: Answer with citations

Summaries and answers are generated from retrieved facts and pages, a pattern known as retrieval-augmented generation (RAG), first described by Lewis and colleagues in 2020. In a claims context, the non-negotiable feature is page-level provenance: click a statement, see the page.

AdjusterDid the claimant have neck pain before the accident?
AI answerYes. A chiropractic note from 14 months before the loss documents cervical pain and reduced range of motion p. 212, and the post-accident MRI describes degenerative changes at C5–C6 p. 347.

Illustrative example. Each citation opens the source page in the file.

Why source links are non-negotiable

The research on AI medical summarization is encouraging but not perfect. In a Stanford study published in Nature Medicine, physicians rated the best adapted model's summaries as equivalent to expert summaries 45% of the time and superior 36% of the time. A large clinical evaluation of nearly 13,000 note sentences found a hallucination rate of 1.47% and an omission rate of 3.45%, and 44% of the hallucinations were classed as major.

Translated to a 500-page injury file, small error rates are still meaningful. The practical safeguards are the same ones a good supervisor would insist on: constrained extraction instead of free writing, a source link on every statement, explicit flags when something cannot be sourced, and a human who checks the facts that drive the decision. amaise's own guide shows how to check a claims AI answer against the source page in under a minute.

Where AI fits in the bodily injury claim lifecycle

The clearest way to see what AI should and should not do is to walk through a BI claim stage by stage. At every stage, the pattern is the same: AI reads and prepares, the adjuster decides, and the file records both.

StageWhat AI doesWhat the adjuster decidesWhat goes in the file
1. First notice and first contactReads the loss notice, police report, and early notes; flags injury severity indicators, attorney letters, and high-risk venuesWho to call first, coverage questions, assignment to the right deskTriage note with flags and source pages
2. Coverage and liabilityExtracts limits, insureds, drivers, statements, and the police narrative; highlights contradictionsCoverage position and liability assessmentLiability summary with cited facts
3. Medical records reviewBuilds the chronology, codes diagnoses, flags gaps, prior conditions, and causation questionsWhich injuries are related, whether to order more records or an IMESource-linked medical chronology
4. Specials and billingReconciles bills to treatment, finds duplicates, applies offsets, surfaces liensWhat is reasonable, necessary, and relatedSpecials worksheet with page references
5. Evaluation and reserveAssembles the evaluation inputs and drafts the rationaleThe value range and the reserveEvaluation note recording AI inputs and any overrides
6. Demand and time-limited demandDetects deadlines, extracts terms, checks statutory requirements, drafts responsesAccept, counter, or request information, with counsel where neededDemand checklist and response letter
7. Negotiation and settlementAnswers questions during negotiation with citations, tracks offersEvery offer and the final settlementNegotiation log
8. Litigation and large lossSummarizes pleadings and depositions, flags verdict-risk signals, pre-fills large loss reportsDefense strategy, authority requests, escalationLitigation plan and large loss notice with an audit trail

Notice what never moves into the AI column: coverage decisions, liability decisions, value, reserves, offers, and settlement. Those stay with licensed people, and the file should show that they did.

Medical records review, chronologies, and summaries

Medical record review is where most BI teams feel AI first, because it is where most of the reading time goes. A routine demand can run to several hundred pages and serious injury files can pass a thousand, and the facts that change value are often a single line in a single note.

Medical summary vs. medical chronology: what is the difference?

A medical chronology is a date-ordered list of every encounter: date of service, provider, complaints, findings, diagnoses, treatment, and the source page. A medical summary is a narrative that explains what the chronology means for the claim: the injuries, the course of treatment, prior history, gaps, and open questions. Good AI produces both, and the summary is only as trustworthy as the chronology underneath it.

What a good AI medical summary must preserve

  • Material facts: alleged injuries, diagnoses, treatment, restrictions, and relevant nonmedical evidence.
  • Chronology: service dates separated from document dates, with treatment gaps visible.
  • Attribution: who said what, whether claimant report, provider opinion, or objective finding.
  • Prior history: pre-existing conditions and degenerative findings, with their sources.
  • Conflicts: inconsistent histories kept visible rather than silently reconciled.
  • Record gaps: references to missing records (for example, an MRI mentioned but not included).
  • Source links: every material statement tied to the page that supports it.

How does AI handle pre-existing conditions?

The system searches the whole file, not just post-accident records, for prior complaints, imaging, and treatment involving the same body part, and for degenerative language in radiology reports. It then flags them with their source pages. It should not decide causation. Whether a herniation is acute, aggravated, or pre-existing is a medical and legal judgment, and the AI's job is to make sure the person making it has seen every relevant page.

How accurate is AI medical record review?

Accuracy depends on the design more than the model. Peer-reviewed studies show modern models can match or beat expert summaries on many tasks, while still omitting or occasionally inventing details (see the research above). For an evaluation, measure accuracy on your own files: how many material facts the summary captured, how many statements were unsupported, and how often the cited page actually supports the statement. amaise's guide to building a medical chronology from a 400-page claim file walks through the manual method you can use as a baseline.

Claims Convos EP.04: "A Good Claim Is a Closed Claim." Awais Farooq, Chief Claims Officer at Venbrook, on cycle time and giving adjusters tools that summarize 500-page demand packages before negotiation. 9:11

Demand packages and time-limited demands

A demand package is the claimant's case for payment: a demand letter plus medical records, bills, wage loss documentation, photos, and sometimes expert reports. A time-limited demand (TLD), sometimes called a policy-limits demand, adds a deadline. If the insurer does not accept a reasonable demand within limits in time, it can face bad-faith exposure for a verdict above the policy limits. amaise's complete guide to bodily injury demand packages covers the anatomy in detail.

What AI checks in a demand package

  • The deadline and how it is triggered: date of receipt, mailing rules, and payment window.
  • The terms: amount, release scope, lien handling, payment method, and conditions.
  • Completeness: whether the records needed to evaluate the claim are actually included, and which are referenced but missing.
  • Specials: billed totals reconciled against records, with duplicates and unrelated charges flagged.
  • Consistency: whether the letter's description of injuries and treatment matches the records it attaches.
  • Altered or AI-generated documents: nearly half of carriers report suspicious claims linked to AI-generated documentation, according to Gallagher Bassett research reported by Carrier Management.

Time-limited demand rules in key states

Rules vary by state and change often, so confirm current law with counsel. As of October 2026, these are the frameworks BI teams most often work under:

StateRuleMinimum windowKey points
FloridaHB 837 (2023), Fla. Stat. § 624.15590-day safe harborTendering the lesser of limits or the demand within 90 days of notice with sufficient evidence shields the insurer from bad-faith liability; rollback bills died in 2025 and 2026 (Greenberg Traurig, Florida Senate)
GeorgiaO.C.G.A. § 9-11-67.1, amended by SB 83 (2024)At least 30 days to acceptSeven material terms, certified mail or overnight delivery, and medical records sufficient to evaluate the claim (Taft)
MissouriRSMo § 537.058At least 90 daysCertified mail citing the statute, a list of providers with HIPAA authorizations, and an unconditional release (Missouri Revisor)
CaliforniaCode of Civil Procedure § 999 et seq. (2023)At least 30 days (33 if mailed)Applies to pre-litigation time-limited demands within limits (DK Law, Goldberg Segalla)
TexasStowers doctrine (common law, 1929)No fixed statutory windowAn insurer that unreasonably rejects a demand within limits can be liable for the full excess judgment (Cooper & Scully)

An AI-assisted 30-day response plan

The goal is simple: know everything in the file early enough that the decision is made on the merits, not on the clock.

  1. Day 0–1
    Intake and deadline. AI classifies the demand, extracts the deadline and terms, and flags statutory requirements. The deadline goes on the diary immediately.
  2. Day 1–3
    Full-file review. AI builds the chronology, specials worksheet, and list of missing records; the adjuster reviews flagged items and requests anything missing in writing.
  3. Day 3–10
    Evaluation. The adjuster evaluates liability, causation, and damages, consults medical or legal experts, and documents the reasoning with source pages.
  4. Day 10–20
    Authority and decision. Authority is requested with a complete, source-linked package, so approvers do not need to re-read the file.
  5. Before the deadline
    Written response. Accept, counter, or request clarification in writing, with time to spare.

"We're often given 10-30 days on time-limited demands." With amaise, Acuity says its team can respond in 10 days or less.

Jamie Loiacono, Acuity Insurance, quoted on amaise.com

For a day-by-day version with templates, see the 30-day time-limited demand playbook for adjusters.

Claims Convos EP.05: "Take Notes Like They'll Be Read Aloud in Court." Mike LaFond, AVP Claims at Pekin Insurance, on policy-limit and time-limited demand traps and file notes that hold up in court. 5:28

Evaluation, reserving, and settlement: what AI should and should not decide

Insurers have used analytics in settlement for years. In the NAIC's survey of private passenger auto insurers, 70% reported using AI or machine learning in claims, the highest share of any insurer function, and uses included helping determine settlement amounts (2021 data, published in 2022). What has changed is the kind of AI, and the expectations around it.

Where AI adds the most value in evaluation

  • Completeness: making sure the evaluation reflects every injury, every treatment, every prior condition, and every bill in the file.
  • Speed to an accurate first reserve: reserves set from a full read on day one develop less than reserves set from a cover letter. amaise explains why in Reserve accuracy starts on day 1.
  • Consistency: the same facts are surfaced the same way for every adjuster, regardless of experience.
  • Preparation for authority: a supervisor can approve from a source-linked summary instead of re-reading the file.

What AI should not decide

AI should not set the value of pain and suffering, decide causation, approve reserves, or make offers on its own. Those are judgments that depend on credibility, venue, counsel, and context, and they are the decisions regulators and courts will ask a person to explain. The NAIC bulletin makes insurers responsible for AI-supported decisions under unfair claims settlement practices law "regardless of the tools and methods" used.

How to document AI-assisted decisions

Bad-faith discovery increasingly asks how AI tools were used on a file, and Claims Journal contributors recommend that adjusters document when they depart from AI outputs. A simple, consistent file note does that. Here is a template your team can adapt:

File note template: AI-assisted review

Tool and version: [system name, version or date]
Documents reviewed: [count, date range, any missing records requested]
Key AI findings relied on: [finding] (source: p. [ ])
Findings I disagreed with or corrected: [finding] because [reason] (source: p. [ ])
My evaluation and the factors behind it: [value range, reserve, rationale]
Decision made by: [name, role, date]

Litigation and nuclear-verdict risk

Most nuclear verdicts start as ordinary claims. The warning signs are usually in the file early, but scattered across documents that nobody reads together: an aggravating fact in a police narrative, a surgical recommendation in a pain management note, a high-risk venue, a commercial defendant, a claimant who felt ignored.

Early signals AI can surface

  • Surgical recommendations, injections, or permanent restrictions appearing in treatment notes.
  • Aggravating liability facts: distraction, speeding, impairment, hours-of-service issues, or prior incidents.
  • Commercial or corporate defendants, which attract larger verdicts.
  • Venue and plaintiff-firm patterns associated with high awards.
  • Long gaps between first notice and meaningful claimant contact.
  • Life-care plans, economist reports, or vocational experts appearing in a demand.

Use these as triage signals for senior review, not as automated decisions. amaise's nuclear verdict risk checklist and its guide to early signals a claim will go to suit turn them into a repeatable review.

Claims Convos EP.09: "Your Biggest Enemy Is Your Own Bias." Kim Moody, VP and Head of Claims at Golden Bear Insurance, on reading a file the way a plaintiff's attorney would pitch it to a jury, and 30/60/90-day litigation checkpoints. 10:26

Regulation, bad faith, and explainability

There is no federal U.S. law that bans AI in claims handling. Instead, insurers face a growing set of state expectations built on existing unfair claims practices law. This section is a summary, not legal advice.

29

jurisdictions have adopted the NAIC AI Model Bulletin as of October 8, 2026 (NAIC map)

4

states have their own insurance AI rules instead: California, Colorado, New York, and Texas

28

jurisdictions have implemented the NAIC Insurance Data Security Model Law (NAIC)

The NAIC AI Model Bulletin

Adopted on December 4, 2023, the NAIC Model Bulletin on the Use of Artificial Intelligence Systems by Insurers expects each insurer to maintain a written AI systems program covering the full life cycle of its AI use, explicitly including "claim administration and payment, and fraud detection." It calls for governance, risk management, testing, documentation, and oversight of third-party vendors, and it says insurers remain responsible for decisions made with AI. As of October 8, 2026, 29 jurisdictions (27 states, the District of Columbia, and Puerto Rico) had adopted it, according to the NAIC's adoption map.

Colorado

Colorado's SB21-169, signed in July 2021, prohibits unfair discrimination through external consumer data, algorithms, and predictive models. Its governance regulation, 10-1-1, was extended to private passenger auto insurers effective October 15, 2025, with the first compliance report due July 1, 2026.

Can an insurer deny a claim based solely on AI?

Several states have enacted laws that bar AI from being the sole basis for medical-necessity denials, such as California's SB 1120, but those apply to health plan utilization review, not property and casualty claims. Florida's HB 527, which would have required a qualified human to make every claim denial, passed the House 108-0 but died in the Senate in March 2026. Whatever the statute says, the practical answer for BI is the same: a licensed person should make and document every coverage, liability, and value decision.

Europe and the EU AI Act

For insurers operating in Europe, the EU AI Act classifies AI used for risk assessment and pricing in life and health insurance as high-risk. Draft Commission guidance indicates that claims management falls outside that category, and the Digital Omnibus moved the high-risk obligations to December 2, 2027. GDPR applies to claim files regardless.

Explainability is a claims-handling skill

Explainability is not an abstract AI-ethics concept in BI. It is the ability to show a claimant, a regulator, a jury, or your own supervisor why a decision was made, which facts it rested on, and where those facts are in the file. Source-linked AI makes that easier than it has ever been; opaque AI makes it harder. Choose accordingly.

Data security and privacy for injury files

Injury files contain some of the most sensitive data an insurer holds: diagnoses, mental health history, Social Security numbers, wage records. Your IT and security teams will ask hard questions, and they should.

Does HIPAA apply to bodily injury claims?

Usually not directly to the carrier. The U.S. Department of Health and Human Services lists automobile liability insurance, workers' compensation, and automobile medical payment insurance as excepted benefits that are not HIPAA health plans. The providers who send records are covered entities, though, and state insurance privacy and data security laws still apply, including the NAIC Insurance Data Security Model Law in 28 jurisdictions. Many carriers require their AI vendors to meet HIPAA-level safeguards anyway.

The security checklist for a claims AI vendor

  • Independent attestation such as SOC 2 Type II and certification such as ISO 27001.
  • Encryption in transit and at rest, with customer-managed keys if your policy requires them.
  • Single sign-on, multi-factor authentication, and role-based access down to the claim.
  • A choice of data residency (for example, U.S. or EU data centers).
  • A written commitment on whether your data is used to train models.
  • Subprocessor list, retention and deletion terms, and breach notification timelines.
  • Audit logs that show who viewed or exported what, and when.

For the full list, see 12 questions your IT team will ask about claims AI and the amaise Trust Center.

ROI: how to build the business case for AI on BI claims

Most AI business cases for injury claims rest on three sources of value: time saved reading and organizing files, better indemnity outcomes from more complete evaluations, and fewer claims that escalate to litigation. The first is the easiest to measure, so start there and treat the others as upside you will validate in a pilot.

The formula

Annual value = (BI claims per year × review hours per claim × share of review time saved × loaded hourly cost) + (BI claims per year × average paid per claim × indemnity improvement)

Industry estimates give a sense of the range. Bain & Company estimates that generative AI could reduce loss-adjusting expense by 20–25% and leakage by 30–50% in P&C claims. Those are estimates, not guarantees, which is why your own pilot numbers matter more than anyone's benchmark.

Quick ROI estimate

Change the inputs to match your book. Nothing you enter leaves this page.

5,000review hours saved per year
2.8adjuster capacity freed (FTE)
$275,000labor value
$840,560estimated annual value

Assumes 1,800 working hours per FTE. The default hourly cost is a loaded estimate based on the BLS median adjuster wage of $37.51 an hour; the default average paid is Triple-I's 2024 personal auto BI severity. For a fuller model, use the P&C claims ROI calculator.

What to measure in a pilot

  • Time to an approved summary, not just time to a draft.
  • Material facts found that the manual review missed, and vice versa.
  • Reserve accuracy at 30, 90, and 180 days compared with a control group.
  • Time-limited demand response time and the share answered before the deadline.
  • Litigation rate and cycle time on comparable files over a longer window.
  • Adjuster experience: would they want to keep the tool?

How to evaluate AI vendors for bodily injury claims

Demos are designed to impress. Evaluations should be designed to find failure. The single most useful thing you can do is test every candidate on the same set of your own hardest files and score the results against a human-reviewed reference.

The test-file protocol

  1. Pick five to ten real files (de-identified if required) that include a large demand package, poor scans, duplicates, extensive prior treatment, and conflicting histories.
  2. Build a reference. Have an experienced adjuster or nurse list the material facts, with their pages, before anyone sees a vendor's output.
  3. Run every vendor on the same files with the same instructions, and keep the raw outputs.
  4. Score the outputs on material facts captured, unsupported statements, citation accuracy, chronology errors, and time to an approved summary.
  5. Decide on evidence. If nothing passes your bar, keep your current process. Do not lower the standard for material evidence.

Vendor evaluation checklist

0 of 12 confirmed

The vendor landscape at a glance

The market includes established data and claims-platform providers, specialist document AI vendors, and plaintiff-side tools. The descriptions below are summarized from each company's public materials.

CompanyServesFocus
amaiseInsurers, TPAs, IMEs, defense counselAgentic AI and per-claim knowledge graph for full BI file review, chronologies, ICD-10 coding, and source-linked Q&A; available in Guidewire ClaimCenter
CCC Intelligent SolutionsInsurersCasualty solutions for demand review and billing; acquired EvolutionIQ in January 2025
VeriskInsurersDiscovery Navigator medical record review, Claims Outcome Advisor (UK), ClaimSearch
Enlyte (Mitchell)InsurersBill review and clinician-validated medical record summarization
CLARA AnalyticsInsurers, TPAs, self-insuredsMedical summaries, demand analytics, and attorney-pattern analysis
WisedocsInsurers, TPAs, legal, IMEsMedical record review, chronologies, and gap detection with clinician review
Nomad DataInsurersQuestion answering over large claim files with source pages
Shift TechnologyInsurersFraud detection and agentic claims automation
DXC (Colossus)InsurersRules-based BI valuation system dating to the 1980s and 1990s
EvenUp, SupioPlaintiff law firmsAI-generated demand letters and case chronologies

For a deeper comparison, see the best AI tools for bodily injury claims, the buyer's guide to AI vendors for BI claims, and how to evaluate AI software for summarizing BI claim files.

Implementation roadmap: from pilot to scale

Adoption is broad but shallow. Bain found that 78% of P&C insurers use generative AI in claims in some form, but only 4% have scaled it. The difference between a pilot and a program is usually not the model. It is workflow, measurement, and trust.

  1. Days 1–30
    Pick one painful workflow and baseline it. Medical record review on litigated or high-severity files, or time-limited demand response, are good candidates. Measure today's time and quality, complete security review, and choose a small group of experienced adjusters as champions.
  2. Days 31–60
    Run the pilot in the real workflow. Use live files, not demos. Track time to approved summary, facts found, and adjuster feedback weekly. Agree on the file-note standard for AI-assisted decisions.
  3. Days 61–90
    Decide and expand. Compare results with the baseline, fix the friction points, integrate with the claims system, and extend to the next team or workflow, such as large loss reporting or litigation management.

Not sure where to start? Score your team with the AI readiness assessment for claims teams or the claims maturity model for BI claims.

What AI means for claimants and fairness

Claimants and their lawyers worry that AI exists to lowball injury claims. The history of rules-based valuation explains why, and insurers should take the concern seriously. Used well, AI can make claims handling faster and fairer:

  • Faster answers. Represented claimants wait a median of about 440 days for closure, according to the IRC. Understanding the file in hours instead of weeks shortens the wait for everyone.
  • Complete reading. A system that reads every page is as likely to surface facts that support the claimant (a documented injury, an unpaid bill) as facts that do not.
  • Human decisions. People, not models, decide value and make offers, and they can be asked to explain them.
  • Testing for bias. Regulations such as Colorado's require insurers to test models for unfair discrimination.
  • Transparency. Source-linked reasoning can be shown, challenged, and corrected.

Early, respectful contact also matters. In Claims Convos, former chief claims officer Michelle Raue argues that AI should take manual work off adjusters so they can actually talk to people, which is often what keeps a claim out of litigation.

How amaise approaches bodily injury claims

amaise is an agentic AI platform purpose-built for casualty and bodily injury claims. The company was founded in 2019 in Bern, Switzerland, as legal-i, and today serves insurers, TPAs, independent medical examiners, and defense counsel in the U.S. and Europe. It reads every page of a bodily injury file, often 250 to 600 pages or more, and returns a decision-ready, source-linked summary in minutes.

CaseDNA knowledge graph

Each file is rebuilt into a knowledge graph of medical history plus social and economic context, so every answer can be traced.

Core

Ingestion, OCR, splitting, classification into 50+ document types, chronological sorting, and deduplication.

MedInsights

Diagnoses mapped to ICD-10, treatment periods, pre-existing conditions, causalities, and inconsistencies.

CasePilot

Question answering over the whole claim; answers without a source are flagged rather than presented as fact.

Collaboration

Secure sharing with medical experts, defense counsel, and service partners.

Large Loss Notices

Agents pre-populate about 80% of a large loss notice for adjuster review, with an audit trail for every data point.

amaise is available as a service inside Guidewire ClaimCenter, as a stand-alone workspace, or through its SDK. It is SOC 2 Type II audited, ISO 27001 certified, GDPR compliant, and HIPAA-aligned, with U.S. or EU data centers (Trust Center). Customers named on its website include Acuity, NAMICO, MileAuto, Baloise, and Dextra.

"amaise helps adjusters completely understand a BI claim very quickly."

Dale Diamond, VP of Claims, NAMICO

It is not built for first-party property claims, and it does not give medical or legal advice: the adjuster stays in charge of every decision.

See your own BI file, fully read, in minutes

Bring a real claim file and see the chronology, flags, and source-linked answers amaise produces from it.

Book a demo

Glossary: key terms in AI for bodily injury claims

Agentic AI
AI that completes multi-step tasks by coordinating specialized agents and tools, with checkpoints where a person reviews and approves the work.
Bad faith
An insurer's unreasonable handling of a claim, such as failing to accept a reasonable settlement within policy limits, which can expose it to damages above the limits.
Bodily injury (BI) liability
Coverage that pays for injuries the insured causes to other people, including medical expenses, lost wages, and pain and suffering.
Causation
Whether the accident actually caused, or aggravated, the injuries claimed, as opposed to a prior or unrelated condition.
Claims leakage
The difference between what was paid on a claim and what should have been paid with optimal handling.
Colossus
A rules-based expert system, marketed in the U.S. since the 1990s, that produces a general damages range from adjuster-entered injury and treatment data.
Demand package
A claimant's or attorney's request for payment, combining a demand letter with medical records, bills, and supporting evidence.
Deduplication
Identifying and removing repeated copies of the same record so they are not counted as separate treatment.
General damages
Non-economic losses such as pain, suffering, and loss of enjoyment of life.
Hallucination
A statement produced by an AI model that is not supported by its source material.
ICD-10-CM
The U.S. clinical modification of the International Classification of Diseases, used to code diagnoses.
Knowledge graph
A structured network of linked facts (people, providers, diagnoses, dates, bills, source pages) that supports cross-document questions.
Medical chronology
A date-of-service-ordered record of every medical encounter in a file, with providers, findings, treatment, and source pages.
NAIC AI Model Bulletin
Guidance adopted by the National Association of Insurance Commissioners in December 2023 that sets governance expectations for insurers' use of AI, including in claims.
Nuclear verdict
A jury award of $10 million or more.
OCR
Optical character recognition: converting scanned or photographed text into machine-readable text.
Pre-existing condition
An injury or disease documented before the loss, which may affect causation and value.
Retrieval-augmented generation (RAG)
A design in which an AI model answers from retrieved source documents, so answers can cite their evidence.
Social inflation
The rise in claim costs beyond economic inflation, driven by litigation trends, jury attitudes, and legal system factors.
Specials
Special (economic) damages: medical bills, lost wages, and other quantifiable losses.
Time-limited demand (TLD)
A settlement demand, often for policy limits, that must be accepted by a deadline.

See all 136 terms in the bodily injury claims glossary.

Frequently asked questions

What is AI for bodily injury claims?

AI for bodily injury claims is software that reads an entire injury claim file, including medical records, bills, demand packages, and legal documents, then organizes it into a source-linked chronology and summary and answers adjusters' questions with citations. Adjusters still make coverage, liability, and settlement decisions.

Can AI make bodily injury claim decisions?

It should not. AI is best used to read, organize, and flag information so that a licensed adjuster can decide faster and with complete facts. Regulators expect insurers to remain accountable for AI-supported decisions, and decisions about causation, value, reserves, and offers should be made and documented by people.

Will AI replace claims adjusters?

Not on bodily injury claims. AI removes the reading, sorting, and summarizing work, which lets adjusters spend more time on investigation, claimant contact, negotiation, and judgment. With a quarter of adjusters expected to retire by the end of 2027, most teams need the extra capacity.

How accurate is AI medical record review?

Well-designed systems can match or exceed manual summaries on many tasks, but studies still find omissions and occasional unsupported statements. The safeguards are source links on every statement, flags for anything that cannot be sourced, and human review of the facts that drive the decision. Test accuracy on your own files before buying.

Can AI review a bodily injury demand package?

Yes. AI can split and classify the package, remove duplicates, build the medical chronology, reconcile bills, identify missing records, and extract the demand's terms and deadline, usually in minutes rather than days. The adjuster then evaluates the demand and decides how to respond.

How does AI help with time-limited demands?

It finds the deadline and terms immediately, checks the demand against statutory requirements, builds the full file review within days, and drafts responses and requests for missing information. That gives the adjuster time to make a decision on the merits before the deadline.

What is the difference between a medical summary and a medical chronology?

A chronology lists every medical encounter in date-of-service order with the provider, findings, treatment, and source page. A summary explains what the chronology means for the claim: injuries, course of treatment, prior history, gaps, and open questions.

Is it safe to use ChatGPT or Copilot on bodily injury claim files?

General-purpose chatbots are not designed for claim files. They may not read every page of a large file, may not cite their sources, and may not meet your security and data-retention requirements. Purpose-built claims AI reads the whole file, links every statement to its page, and is governed by contracts and certifications such as SOC 2 Type II.

Is there a modern alternative to Colossus?

Modern document and agentic AI works differently from Colossus. Instead of scoring injury codes keyed in by an adjuster, it reads the records directly, shows the source for every fact, and leaves valuation to the adjuster. Many carriers use it alongside, or instead of, rules-based valuation tools.

Do AI claims tools work with Guidewire ClaimCenter?

Some do. amaise, for example, is available as a service inside Guidewire ClaimCenter, as a stand-alone workspace, or through an SDK. Ask each vendor how it retrieves files from your claims system and writes results back.

Does HIPAA apply to AI used on bodily injury claims?

HHS treats automobile liability insurance, workers' compensation, and auto medical payments coverage as excepted benefits rather than HIPAA health plans, so carriers are generally not HIPAA covered entities for these claims. Providers sending records are, and state privacy and insurance data security laws still apply. Many carriers require HIPAA-level safeguards from AI vendors.

What does the NAIC AI Model Bulletin require for claims?

It expects insurers to maintain a written program for AI systems that covers claim administration and payment, with governance, risk management, testing, documentation, and oversight of third-party vendors. As of October 8, 2026, 29 jurisdictions had adopted it.

How long does it take to implement AI for bodily injury claims?

A focused pilot on one workflow typically runs 60 to 90 days, including security review, baseline measurement, and live use on real files. Integration with the claims system and expansion to more teams follow once the pilot results are clear.

What is the ROI of AI on bodily injury claims?

Start with review time saved: claims per year times review hours per claim times the share saved times your loaded hourly cost. Indemnity improvement and litigation avoidance are additional upside to validate in a pilot. Bain estimates generative AI could cut loss-adjusting expense by 20 to 25% in P&C claims.

Sources

  1. Triple-I. Facts + Statistics: Auto insurance (ISO/Verisk data, 2024).
  2. Insurance Research Council. Auto Injury Insurance Claims: A Study of Increasing Claim Severity (July 30, 2026).
  3. CCC Intelligent Solutions. Crash Course 2026 (March 31, 2026) and webinar recap (May 20, 2026).
  4. Sedgwick. 2025 Year-End Auto Liability.
  5. Marathon Strategies. Nuclear Verdicts Report 2026 (August 18, 2026).
  6. Triple-I and Casualty Actuarial Society. The Impact of Increasing Inflation on Liability Insurance: 2015–2024 (October 30, 2025).
  7. Dealroom. EvenUp raises $385M, valued over $2B (October 2025).
  8. U.S. Bureau of Labor Statistics. Occupational Outlook Handbook: Claims Adjusters, Appraisers, Examiners, and Investigators.
  9. Carrier Management. Sedgwick Loss Adjusting Insights 2026 (October 5, 2026).
  10. NAIC. Model Bulletin on the Use of Artificial Intelligence Systems by Insurers (December 4, 2023) and adoption map (October 8, 2026).
  11. NAIC. Private Passenger Auto AI/ML Survey memo (December 8, 2022).
  12. NAIC. Insurance Data Security Model Law brief (October 2026).
  13. Connecticut Office of Legislative Research. Report 99-R-0058 on Colossus (1999).
  14. CLM Magazine. Colossal Cleanup (2011).
  15. Insurance Journal. Allstate multistate Colossus settlement (October 19, 2010).
  16. Anthropic. Building effective agents (December 2024).
  17. Soroush et al., NEJM AI, via ScienceDaily. Large language models are poor medical coders (April 2024).
  18. Lewis et al. Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks (2020).
  19. Stanford HAI. AI can outperform humans writing medical summaries (Van Veen et al., Nature Medicine, 2024).
  20. Asgari et al. A framework to assess clinical safety and hallucination rates of LLMs for medical text summarisation (2024).
  21. FAIR Health. Property and casualty solutions.
  22. Milliman. Resolving Medicare Secondary Payer issues.
  23. Carrier Management. Gallagher Bassett carrier research on AI-generated documentation (March 6, 2026).
  24. Greenberg Traurig. Tort reform overhauls Florida's litigation landscape (April 2023); Florida Senate, HB 1553 (2026).
  25. Taft. Georgia legislature overhauls Holt demand statute (2024).
  26. Missouri Revisor of Statutes. RSMo § 537.058.
  27. DK Law. CCP 999 time-limited demands in California; Goldberg Segalla, Navigating the time-limited policy limits demand (2025).
  28. Cooper & Scully. Stowers update (2026).
  29. Claims Journal. Expert viewpoint on AI in claims discovery (April 29, 2026).
  30. Colorado Division of Insurance. SB21-169 and amended Regulation 10-1-1.
  31. Office of Sen. Josh Becker. SB 1120 (December 9, 2024).
  32. Florida Senate. CS/CS/HB 527 (2026).
  33. White & Case. EU AI Omnibus enters into force (August 2026).
  34. U.S. HHS. Which insurances are covered under HIPAA?
  35. Bain & Company. A $100 billion opportunity for generative AI in P&C claims handling (October 31, 2024); Insurance Business, Most P&C insurers still in pilot mode with GenAI (December 2025).
  36. MobiHealthNews. CCC acquires EvolutionIQ; Verisk, Discovery Navigator generative AI launch (February 2024).
  37. amaise. Official information about amaise, agenticAI Platform, Core, and Trust Center.
Andrej Evtimov

Andrej Evtimov

Andrej writes about AI, bodily injury claims, and claims operations at amaise. This guide was researched from primary sources including the NAIC, the Insurance Research Council, Triple-I, CCC, state legislatures, and peer-reviewed studies, and is reviewed as the data and regulations change.

Share this guide
Listen

Cookies & privacy

We’d like to use cookies and similar technologies to analyze site use and support our marketing, including identifying companies and people that visit us. We only do this if you accept. You can change your choice anytime under “Cookie settings” in the footer.

See our Privacy Policy and Cookie Notice.