# Generative AI in Insurance, Explained

> What generative AI is, how it differs from the predictive models insurers already use, where it is being applied, and why regulators treat its risks differently.

- Source: https://insureaiwire.com/generative-ai-in-insurance/
- Publication: InsureAI Wire
- Author: Simon Li
- Updated: 2026-07-31

---
Generative AI is the phrase behind much of the current noise about AI in insurance. It is also applied too broadly. The useful distinction concerns the task: does the system estimate or classify something, or does it generate new content? Input and output format alone do not settle it. A classifier can read language, and a generative model can return structured data.

## What generative AI is, and how it differs from the AI insurers already use

Insurers have used predictive and classification systems for years. A pricing model estimates loss, a fraud model ranks a claim, and an underwriting model classifies or scores an application. The task is to estimate an outcome or assign a category.

Generative AI produces new content: a paragraph, summary, answer, image, audio clip, or structured response assembled from a prompt and context. Most text systems in use today are built on a [large language model](/glossary/large-language-model/), itself a kind of [foundation model](/glossary/foundation-model/).

The distinction changes validation. A predictive model may be tested for calibration, rank ordering, stability, and error against observed outcomes. A generative system needs task-specific evaluation of factuality, grounding, completeness, consistency, and safe refusal. Both require evidence. They require different evidence.

## Where generative AI shows up in insurance

The early, practical uses are unglamorous, which is a good sign. They cluster in document-heavy work, the reading and writing that fills an insurance day.

In underwriting, generative models read submissions, emails, PDFs, and images and pull the relevant facts into a system, work that used to mean manual data entry. In claims, they summarize long files so an adjuster can grasp a case quickly. In service, they draft the routine correspondence and power the chat windows customers now expect. Across all of these, the pattern is the same: the model handles the first draft or the raw extraction, and a person reviews and decides.

The money behind this is real. McKinsey has estimated that generative AI could add $50 billion to $70 billion in insurance industry revenue, with the impact concentrated in marketing, customer operations, and software engineering.[^1] Treat that as a consultancy's projection rather than a booked result, but the reason carriers are moving is not mysterious: the work it targets is expensive and slow.

## The new risk: the confident wrong answer

Generative systems add a distinctive failure: the fluent answer that is unsupported or false. They can also expose confidential data, follow malicious instructions embedded in retrieved documents, or produce inconsistent answers to equivalent questions. Hallucination is the easiest failure to recognize, not the only one.

A generative model is not a policy database. It generates a response from patterns in its training and the context supplied at runtime. Sometimes it invents a policy provision, misstates a coverage limit, or cites a rule that does not exist, using the same tone it uses for a supported answer. In insurance, that presentation can make an error look like authorized advice.

For insurance, where a misstated coverage term can become a claim dispute years later, this is not a small problem. It is why the serious deployments keep a person between the model and the customer, and why "the model said so" is never a defense.

## Why regulators look at it differently

Traditional model governance often starts with defined inputs, outputs, performance measures, and observed outcomes. A large language model's explanation is generated text, so it cannot serve as the audit trail by itself. [Explainability](/glossary/explainability/) instead depends on preserved prompts, retrieved sources, model and configuration versions, evaluation results, and the downstream action. [Model validation](/glossary/model-validation/) still applies, but the test set and acceptance criteria must match the task.

<figure class="figure">
<svg viewBox="0 0 460 330" width="460" role="img">
<title>A two-column comparison of predictive and generative AI across four rows. Task: estimate or classify, against create new content. Checking: calibration, ranking, and stability, against factuality, grounding, and task success. Evidence: variables, versions, and outcomes, against prompts, sources, versions, and evaluations. Signature failure: proxy discrimination on the predictive side, and, marked in red, the confident wrong answer on the generative side.</title>
<defs>
<pattern id="hatch-gen" width="7" height="7" patternUnits="userSpaceOnUse"><path d="M-1 1 L1 -1 M0 7 L7 0 M6 8 L8 6" class="s-red" stroke-width="1.1"/></pattern>
</defs>
<text x="191" y="20" text-anchor="middle" class="t-label f-ink" font-size="15">PREDICTIVE</text>
<text x="191" y="38" text-anchor="middle" class="t-note f-soft" font-size="14">predicts or classifies</text>
<text x="367" y="20" text-anchor="middle" class="t-label f-ink" font-size="15">GENERATIVE</text>
<text x="367" y="38" text-anchor="middle" class="t-note f-soft" font-size="14">creates something new</text>
<line x1="8" y1="46" x2="452" y2="46" class="s-ink" stroke-width="2"/>
<line x1="100" y1="46" x2="100" y2="318" class="s-rule" stroke-width="1"/>
<line x1="280" y1="6" x2="280" y2="318" class="s-rule" stroke-width="1"/>
<line x1="8" y1="114" x2="452" y2="114" class="s-rule" stroke-width="1"/>
<line x1="8" y1="182" x2="452" y2="182" class="s-rule" stroke-width="1"/>
<line x1="8" y1="250" x2="452" y2="250" class="s-rule" stroke-width="1"/>
<line x1="8" y1="318" x2="452" y2="318" class="s-ink" stroke-width="2"/>
<text x="14" y="85" class="t-label f-soft" font-size="14">TASK</text>
<text x="14" y="153" class="t-label f-soft" font-size="14">CHECKING</text>
<text x="14" y="221" class="t-label f-soft" font-size="14">EVIDENCE</text>
<text x="14" y="289" class="t-label f-soft" font-size="14">FAILURE</text>
<text x="191" y="76" text-anchor="middle" class="t-note f-ink" font-size="14">estimate</text>
<text x="191" y="94" text-anchor="middle" class="t-note f-ink" font-size="14">or classify</text>
<text x="367" y="76" text-anchor="middle" class="t-note f-ink" font-size="14">create new</text>
<text x="367" y="94" text-anchor="middle" class="t-note f-ink" font-size="14">content</text>
<text x="191" y="144" text-anchor="middle" class="t-note f-ink" font-size="14">calibration, ranking,</text>
<text x="191" y="162" text-anchor="middle" class="t-note f-ink" font-size="14">and stability</text>
<text x="367" y="144" text-anchor="middle" class="t-note f-ink" font-size="14">factuality, grounding,</text>
<text x="367" y="162" text-anchor="middle" class="t-note f-ink" font-size="14">and task success</text>
<text x="191" y="213" text-anchor="middle" class="t-note f-ink" font-size="14">variables, versions,</text>
<text x="191" y="231" text-anchor="middle" class="t-note f-ink" font-size="14">and outcomes</text>
<text x="367" y="204" text-anchor="middle" class="t-note f-ink" font-size="14">prompts, sources,</text>
<text x="367" y="222" text-anchor="middle" class="t-note f-ink" font-size="14">versions, and</text>
<text x="367" y="240" text-anchor="middle" class="t-note f-ink" font-size="14">evaluations</text>
<text x="191" y="288" text-anchor="middle" class="t-note f-ink" font-size="14">proxy discrimination</text>
<rect x="286" y="258" width="160" height="52" fill="url(#hatch-gen)" class="s-red" stroke-width="2"/>
<rect x="294" y="266" width="144" height="36" class="f-paper s-red" stroke-width="1"/>
<text x="366" y="281" text-anchor="middle" class="t-label f-red" font-size="14">THE CONFIDENT</text>
<text x="366" y="297" text-anchor="middle" class="t-label f-red" font-size="14">WRONG ANSWER</text>
</svg>
<figcaption>FIG. 1 - TWO KINDS OF MODEL, AND WHY THE TESTS DO NOT TRANSFER</figcaption>
</figure>

None of that puts generative AI outside the rules. It puts it inside the same [AI governance framework](/ai-governance-in-insurance/) as everything else, while making that framework harder to apply. The NAIC Model Bulletin is written around AI systems generally, and asks for governance, risk management, and internal controls scaled to what a system can do to a consumer.[^2] It is not silent on the technique, either: it defines generative AI as its own class of system, and it tells examiners that validation, testing, and auditing should reflect whether what they are looking at rests on a predictive model or a generative one.[^2] It stops short of writing a separate program for it. An examiner still expects you to know where the model is used, what it touches, and how you check it. The NAIC evaluation tool starts by counting models by operational area, then branches to governance, high-risk detail, or the data categories behind them depending on what those counts show.[^3] You just cannot lean on the same tests you use for a scoring model. Where generative tools sit relative to other AI across the business is mapped in the [AI use cases by business line](/ai-by-business-line/) guide.

## How to think about governing it

The starting move is the same one that governs all insurance AI: sort by what the output does to a consumer, not by how advanced the model is. A generative model that drafts internal notes is low stakes. One that writes something a customer relies on, or that feeds a coverage or claims decision, is not.

From there the controls follow the risk. Build an evaluation set from real insurance tasks and define acceptance criteria before deployment. Ground answers in approved documents where accuracy matters, preserve the prompt, retrieved sources, model version, response, and downstream action, and route uncertain or consequential outputs to a person. For customer-facing use, the evidence should show how unsupported answers are detected and what happens when the system cannot answer safely.

<!-- CLOSING: 未决型 (unsettled thing, named + timed) -->
Generative AI is governed today, under rules already on the books. Whether it gets rules of its own is still open. At this article's July 2026 review, the [NAIC framework](/naic-model-bulletin/) and state instruments treated it as ordinary AI rather than a separate regulatory category, and the [Big Data and Artificial Intelligence Working Group](/glossary/naic-big-data-ai-working-group/) was the place where a change would surface first. Until that changes, the newest tool in insurance runs on rules written before it existed, and the seams are being found by whoever hits one.


[^1]: McKinsey & Company estimate, as reported by Reinsurance News, "Gen AI could unlock $50-$70bn in insurance revenue, estimates McKinsey & Company," February 27, 2026: https://www.reinsurancene.ws/gen-ai-could-unlock-50-70bn-in-insurance-revenue-estimates-mckinsey-company/ . A consultancy projection reported via trade press, not a booked result; the trade report gives the figure as additional industry revenue.
[^2]: NAIC, "Model Bulletin: Use of Artificial Intelligence Systems by Insurers," adopted December 4, 2023: https://content.naic.org/sites/default/files/inline-files/2023-12-4%20Model%20Bulletin_Adopted_0.pdf
[^3]: NAIC, "AI Systems Evaluation Tool 4.0" (Exhibit A asks only for counts by operational area; Exhibit B governance, Exhibit C high-risk system detail, Exhibit D data details each branch from those counts): https://content.naic.org/sites/default/files/inline-files/AI%20Systems%20Evaluation%20Tool%204.0%20%28Clean%29.pdf