Complete guide · 2026
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.
Listen to this guide
Now playing: Summary
Narrated with an AI voice. Tables, sources, and interactive tools are best viewed on the page.
Contents
See a BI file fully read, with every fact sourced.
Book a demoThe 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.
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:
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.
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.
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.
average personal auto BI liability claim in 2024, up from $17,014 in 2015 (Triple-I / ISO)
of BI claimants were represented by an attorney by 2022 (Insurance Research Council)
of auto injury claimants litigated in 2022, up from 10% in 2017 (IRC)
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)
median time to close for represented BI claimants, more than double unrepresented ones (IRC)
in nuclear verdicts against corporate defendants in 2025, from nearly 200 verdicts of $10M or more (Marathon Strategies)
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.
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.
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.
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 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.
"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.
Expert systems that score adjuster-entered injury codes to produce a value range. The Colossus era.
Machine learning trained on historical claims to score severity, litigation risk, or fraud.
OCR, classification, extraction, and language models that summarize records and answer questions.
Teams of specialized AI agents that run multi-step reviews with checkpoints and human sign-off.
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.
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.
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).
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.
| Approach | What it reads | What it produces | Explainability | Best for | Watch out for |
|---|---|---|---|---|---|
| Rules-based valuation | Injury and treatment codes entered by the adjuster | A general damages range | Medium: rules are fixed, but tuning is often opaque | Consistency on routine soft-tissue claims | Garbage in, garbage out; rigid adherence to outputs |
| Predictive models | Structured claim data | Risk scores and probabilities | Low to medium | Triage, routing, early severity flags | Bias in historical data; misses facts in documents |
| Document and generative AI | The documents themselves | Chronologies, summaries, answers | High when every statement links to a source page | Medical record review, demand review, Q&A | Omissions and hallucinations without source links |
| Agentic AI | The whole file plus claim system data | Multi-step reviews, drafts, alerts, reports | High with step-level audit trails | End-to-end file review, large loss reports, demand response | Over-automation; needs clear human checkpoints |
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:
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.
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.
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.
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.
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.
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.
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.
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.
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.
Illustrative example. Each citation opens the source page in the file.
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.
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.
| Stage | What AI does | What the adjuster decides | What goes in the file |
|---|---|---|---|
| 1. First notice and first contact | Reads the loss notice, police report, and early notes; flags injury severity indicators, attorney letters, and high-risk venues | Who to call first, coverage questions, assignment to the right desk | Triage note with flags and source pages |
| 2. Coverage and liability | Extracts limits, insureds, drivers, statements, and the police narrative; highlights contradictions | Coverage position and liability assessment | Liability summary with cited facts |
| 3. Medical records review | Builds the chronology, codes diagnoses, flags gaps, prior conditions, and causation questions | Which injuries are related, whether to order more records or an IME | Source-linked medical chronology |
| 4. Specials and billing | Reconciles bills to treatment, finds duplicates, applies offsets, surfaces liens | What is reasonable, necessary, and related | Specials worksheet with page references |
| 5. Evaluation and reserve | Assembles the evaluation inputs and drafts the rationale | The value range and the reserve | Evaluation note recording AI inputs and any overrides |
| 6. Demand and time-limited demand | Detects deadlines, extracts terms, checks statutory requirements, drafts responses | Accept, counter, or request information, with counsel where needed | Demand checklist and response letter |
| 7. Negotiation and settlement | Answers questions during negotiation with citations, tracks offers | Every offer and the final settlement | Negotiation log |
| 8. Litigation and large loss | Summarizes pleadings and depositions, flags verdict-risk signals, pre-fills large loss reports | Defense strategy, authority requests, escalation | Litigation 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 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.
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.
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.
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.
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.
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:
| State | Rule | Minimum window | Key points |
|---|---|---|---|
| Florida | HB 837 (2023), Fla. Stat. § 624.155 | 90-day safe harbor | Tendering 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) |
| Georgia | O.C.G.A. § 9-11-67.1, amended by SB 83 (2024) | At least 30 days to accept | Seven material terms, certified mail or overnight delivery, and medical records sufficient to evaluate the claim (Taft) |
| Missouri | RSMo § 537.058 | At least 90 days | Certified mail citing the statute, a list of providers with HIPAA authorizations, and an unconditional release (Missouri Revisor) |
| California | Code 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) |
| Texas | Stowers doctrine (common law, 1929) | No fixed statutory window | An insurer that unreasonably rejects a demand within limits can be liable for the full excess judgment (Cooper & Scully) |
The goal is simple: know everything in the file early enough that the decision is made on the merits, not on the clock.
"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.
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.
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.
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]
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.
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.
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.
jurisdictions have adopted the NAIC AI Model Bulletin as of October 8, 2026 (NAIC map)
states have their own insurance AI rules instead: California, Colorado, New York, and Texas
jurisdictions have implemented the NAIC Insurance Data Security Model Law (NAIC)
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'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.
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.
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 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.
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.
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.
For the full list, see 12 questions your IT team will ask about claims AI and the amaise Trust Center.
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.
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.
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.
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.
Vendor evaluation checklist
0 of 12 confirmed
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.
| Company | Serves | Focus |
|---|---|---|
| amaise | Insurers, TPAs, IMEs, defense counsel | Agentic 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 Solutions | Insurers | Casualty solutions for demand review and billing; acquired EvolutionIQ in January 2025 |
| Verisk | Insurers | Discovery Navigator medical record review, Claims Outcome Advisor (UK), ClaimSearch |
| Enlyte (Mitchell) | Insurers | Bill review and clinician-validated medical record summarization |
| CLARA Analytics | Insurers, TPAs, self-insureds | Medical summaries, demand analytics, and attorney-pattern analysis |
| Wisedocs | Insurers, TPAs, legal, IMEs | Medical record review, chronologies, and gap detection with clinician review |
| Nomad Data | Insurers | Question answering over large claim files with source pages |
| Shift Technology | Insurers | Fraud detection and agentic claims automation |
| DXC (Colossus) | Insurers | Rules-based BI valuation system dating to the 1980s and 1990s |
| EvenUp, Supio | Plaintiff law firms | AI-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.
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.
Not sure where to start? Score your team with the AI readiness assessment for claims teams or the claims maturity model for BI claims.
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:
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.
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.
Each file is rebuilt into a knowledge graph of medical history plus social and economic context, so every answer can be traced.
Ingestion, OCR, splitting, classification into 50+ document types, chronological sorting, and deduplication.
Diagnoses mapped to ICD-10, treatment periods, pre-existing conditions, causalities, and inconsistencies.
Question answering over the whole claim; answers without a source are flagged rather than presented as fact.
Secure sharing with medical experts, defense counsel, and service partners.
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.
See all 136 terms in the bodily injury claims glossary.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.

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.
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.
Choose which cookies and similar technologies we may use. You can change your choice at any time. Details are in our Cookie Notice.