Skip to content

AI uses for records

Insurance multi policy reasoning data: one event, several policies

By SourceX Editorial · Reviewed by Noah Loul ·

9 sections

Short answer

Build each task around one loss event. List every policy that could respond, freeze each at the form edition and endorsements in force on the loss date, and quote its trigger, deductible and other insurance wording. Then ask which policies respond, in what order and for which damage, with the gold answer, deciding documents, resolved conflicts and authority taken from the closed file.

Document stack

Insurance multi policy

This page covers insurance multi policy reasoning data: one event, several policies.Illustrative

Key takeaways

  • A multi policy task starts from the loss event and includes every policy that could respond, including ones that paid nothing.
  • Other insurance, excess and payer-order wording decides the order of response, so the task quotes it verbatim from each policy.
  • Wind against water, mid-term endorsements, duplicate flood policies and Medicare conditional payments are the conflicts that change answers.
  • Gold answers come from the closed file's final dispositions and the authority that made them, never from a reviewer's reading of the forms.
  • Unresolved conflicts become escalation tasks, and a model that decides them anyway is scored as wrong.

How do you construct insurance tasks where one event involves several policies?

Start from the loss event, not from a policy. Gather every policy that could respond to that event, freeze each one at the form edition and endorsements in force on the date of loss, copy its coverage trigger, deductible and other insurance wording, then ask a question that no single policy can answer: which policies respond, in what order, for which part of the loss, and what still has to be proven.

The gold answer comes from the closed file, not from a reviewer's reading of the forms. It records the disposition under each policy, who had authority to decide it, the documents that decided it and the conflicts that had to be resolved first. A task built this way tests reasoning across documents, because the policy that looks relevant at first glance rarely settles the question on its own.

This page is about tasks where several separate policies meet one event. A companion question, how an exclusion in one document changes the reading of another document in the same policy, is a different design problem and is treated separately in the planned material on exclusion reasoning.

Which policy combinations does one loss event typically pull together?

The most useful events are ones where coverage is split by design, because the split is written into public policy forms and consumer guidance that a reviewer can check. Four patterns cover most personal and small commercial lines files.

The common thread is that each policy answers a narrower question than the claimant asks. A homeowner asks whether the storm is covered; the files answer that wind, water and medical bills each sit with a different payer.

Which policy combinations does one loss event typically pull together?
EventPolicies that may respondCross-policy question the task asksPublic anchor
Hurricane on a coastal propertyHomeowners policy, a separate windstorm policy where homeowners excludes wind, NFIP or private flood policyWhich damage is wind, which is flood or surge, and which deductible applies to eachNAIC and TWIA consumer pages; NFIP Dwelling Form
Flood in a condominium unitUnit owner Dwelling Form policy and the association's residential condominium building policyWhether the unit policy pays first or sits in excess over the association policyNFIP Dwelling Form other insurance condition
Flood with a private flood policy also in forceNFIP policy and a non-NFIP flood policy on the same buildingWhether the losses are shared pro rata, or one policy is primary because the other declares itself excessNFIP Dwelling Form other insurance condition
Auto collision injuring a Medicare beneficiaryAuto liability, no-fault or medical payments coverage, Medicare as secondary payerWhich payer is primary for medical bills and whether a conditional payment must be repaidCMS Medicare Secondary Payer recovery guidance
Work injury in a company vehicle (illustrative)Workers compensation, commercial auto, the injured worker's other coverageWhich coverage is primary for medical costs and which handles the liability claimCMS guidance that workers compensation pays before Medicare; state law otherwise

Why the other insurance clause decides the order, not the claim file

When two policies cover the same loss, the order of payment is set by the policies' own other insurance wording and by statute, so the task must carry that wording verbatim. A summary such as 'flood policy is primary' loses the conditions that decide when it is.

The NFIP Dwelling Form is a good public example. The edition FEMA applies to claims reported on or after October 1, 2021 says that when a loss is also covered by other flood insurance not issued under the program, the NFIP policy pays no more than its proportional share; if the other policy states it is excess, the NFIP policy is primary; and without such a clause the NFIP policy is primary up to the other policy's deductible and then shares the remainder. The same form makes the unit owner's policy excess over other NFIP insurance issued in the condominium association's name, and it asks the insured to give details of any other insurance that may cover the loss as part of the proof of loss.

Duplicate coverage inside the same program has its own rule. FEMA's April 2024 flood insurance manual says only one NFIP policy with building coverage may be in effect for the same building, the policy with the earlier effective date generally continues, and damaged items are paid under one policy only. A task that offers two NFIP policies for one building is therefore testing whether the model notices the duplicate, not whether it can add two limits together.

Outside flood, the order can be set by federal law rather than by contract. CMS explains that Medicare does not pay to the extent that payment has been, or may reasonably be expected to be, made by a liability or no-fault insurer or a workers compensation entity, and that when Medicare pays first the payment is conditional and must be repaid once the beneficiary receives a settlement, judgment or award from the primary payer. Tasks that touch this pattern carry health information and need privacy review before they leave the insurer or administrator.

The multi policy task record, field by field

The record below is the asset this page proposes, drafted for review by an insurance operations professional and a privacy or rights reviewer before use. Each task is one event with a policy set, an evidence set and one or more questions. Copy the fields as they stand; add line-of-business fields only when a question needs them.

The multi policy task record, field by field
FieldWhat it holdsWhere it comes from in a closed fileWhy the task needs it
EventEvent ID, peril, date and time of loss, location precision kept after de-identificationFirst notice of loss and adjuster reportFixes which policy versions were in force
Policy setOne entry per policy: line, carrier type (admitted, residual market, federal program), form edition, endorsements in force on the loss dateDeclarations pages and endorsement schedules at the loss datePrevents the model from reading a later renewal
Trigger and peril wordingInsuring agreement and exclusions quoted for the peril in questionPolicy forms as issued, not marketing summariesShows which policy can respond at all
Other insurance wordingEach policy's other insurance, excess or primary clause, verbatimPolicy conditions sectionDecides the order of response
DeductiblesDeductible type per policy: all-peril, named storm or hurricane percentage, floodDeclarations and deductible endorsementsA wind loss and a flood loss on one house rarely share a deductible
Cause allocationFindings that split damage by cause, with the author and date of each findingEngineer reports, adjuster scope notes, appraisal awardsWind versus water is often the whole dispute
Evidence itemsEach document with ID, type, date, author role and the claim it supports or contradictsClaim file indexLets graders check the evidence path, not just the answer
Missing itemsDocuments the policies require that the file does not hold, with request datesDiary notes, request letters, proof of loss checklistsAbsence often explains a delayed or partial payment
AuthorityWho decided each disposition: adjuster, supervisor, appraisal panel, program administrator, secondary payerAuthority grants and sign-offsSeparates a decision from a recommendation
Disposition and rationalePer-policy outcome (paid, partly paid, denied, closed without payment) with the cited provisionClosing letters and payment recordsThe gold answer, stated per policy

Which evidence conflicts change the expected answer?

A conflict belongs in the task when resolving it changes which policy responds or in what order. Record the conflict, both pieces of evidence and the document that resolved it; if nothing resolved it, the task's correct answer is to escalate.

At a glance

Which evidence conflicts change the expected answer

Wind against water is the conflict that matters most in coastal files, because the policies are drafted to split on it. NAIC's consumer guidance says standard homeowners policies do not cover flood, and TWIA states that its policies cover direct wind and hail damage only and exclude flood and storm surge even when hurricane wind and rain caused the flooding. The Texas Department of Insurance notes that coastal homeowners may need a separate windstorm policy because their homeowners policy may not cover wind and hail.

  • Cause conflict: an engineer attributes interior damage to surge while the adjuster's first scope attributes it to roof failure. The resolving document is usually a later report or an appraisal award.
  • Version conflict: an endorsement added mid-term appears in the current policy system but was not in force on the loss date. Use the endorsement's effective date, never the system snapshot.
  • Deductible conflict: one policy applies a named storm deductible that NAIC describes as often a percentage of insured value, while another applies a flat flood deductible. The task asks which applies to which damage, not the arithmetic.
  • Duplicate conflict: two flood policies on one building. Check whether both are NFIP policies, which triggers the one-policy rule, or one is private, which triggers the other insurance condition.
  • Payer conflict: an auto claim file shows medical bills paid by Medicare before the liability claim settled. The question is whether the conditional payment must be repaid, which CMS guidance answers.
  • Authority conflict: a field adjuster recommends payment that a program administrator later reverses. The reversal is the disposition; the recommendation is evidence.

Illustrative case: a coastal house, a named storm and three policies

Every detail here is illustrative and invented for the example; counts and durations are labelled, and no money amounts are used. A single-family house on the Texas coast carries a homeowners policy that excludes wind, a TWIA windstorm policy and an NFIP Dwelling Form policy. A named storm damages the roof and floods the ground floor.

The illustrative file holds 41 documents across the three policies. The windstorm adjuster's first scope, written 6 days after the storm, treats ceiling damage on both floors as wind-driven rain. An engineer's report 19 days later finds a surge line on the ground floor walls and attributes ground floor damage to flood. The NFIP adjuster's report agrees with the engineer. The homeowners carrier closes its claim without payment for wind damage under its wind exclusion and pays a small theft item found during cleanup.

Three tasks come from this one event. The first asks which policy responds to second-floor ceiling damage; the gold answer is the windstorm policy, citing its wind and hail insuring agreement and the engineer's report. The second asks which policy responds to ground floor drywall and what the windstorm policy does with it; the gold answer is the flood policy, with the windstorm policy excluding flood and surge. The third asks what the insured had to disclose on the flood proof of loss; the gold answer includes the windstorm policy as other insurance that may cover part of the loss.

The exception worth keeping: in a second illustrative file from the same storm, no engineer was engaged and the two adjusters never reconciled their scopes. That file becomes an escalation task. The correct output is a request for a cause determination, and a model that picks a policy anyway should be scored as wrong.

Five task types and how to grade each one

Grade the answer and the evidence path separately, and score escalation as an answer in its own right. A model that names the right policy for the wrong reason has learned the base rate, not the structure.

Five task types and how to grade each one
Task typeQuestion patternCorrect outputHow to grade
Responding policiesWhich policies can respond to this item of damage?List of policies with the insuring agreement or exclusion that decides eachExact set match plus a cited provision per policy
Order of responseWhich policy pays first, and on what condition?Primary, excess or pro rata, with the other insurance wording that sets itOrder correct and the clause quoted from the right policy
Cause allocationWhich part of the loss belongs to which peril?Allocation by damage item with the finding relied onItem-level agreement with the closed file and the finding cited
Document sufficiencyWhat is missing before this policy can pay?Missing items with the condition that requires eachRecall of the file's missing items; extra items count as errors
EscalationCan this be decided from the file?Decision, or a named escalation with the unresolved conflictEscalating when the file resolved the conflict is wrong, and so is deciding when it did not

Files that break the structure, and who signs off the rest

Leave a file out when its outcome is not settled or its documents do not belong to the company offering them. Everything else passes through two reviewers before a single task is released.

An insurance operations reviewer checks that the policy set is complete for the loss date, that the quoted wording matches the forms in force and that the gold disposition reflects the final decision rather than an interim one. A privacy and rights reviewer checks who controls each document and what must be removed. The structure on this page is a draft for that review, not a statement of how any particular claim should be handled.

  • Open, reopened or litigated claims: the disposition can still change. Use closed files only.
  • Files under appraisal or a coverage dispute that ended in settlement without a stated rationale: keep only if the settlement terms allow the use, and mark the gold answer as negotiated.
  • Files holding medical bills or Medicare information: route to privacy review first, and keep only the payer order and dates the task needs.
  • Manuscript or nonstandard policy wording: the task is still useful, but the quoted wording must come from that policy, not a standard form.
  • Files where the company handled one policy only, for example an independent adjusting firm working one carrier's claim: the other policies' documents may not be the company's to share.
  • State-specific rules on deductibles, residual market plans or payer order: record the state and the rule version, and do not mix states inside one task.

Supplying closed multi-policy files through SourceX

Carriers, managing general agents, third-party administrators and adjusting firms often hold years of closed files where several policies met one event. For firms like these, SourceX turns selected claim records into licensed datasets for AI, running qualification, rights review, contracting, preparation and delivery.

Whether such files can be licensed depends on contracts with carriers and policyholders, not only on de-identification, so that question is settled first. An adjusting firm or carrier can check whether it qualifies through a short assessment with no files uploaded, and no claim file is delivered until it has approved the scope and terms and signed the agreement.

Frequently asked questions

What is multi policy reasoning in insurance AI?

It is the ability to decide how several separate policies respond to one loss event: which ones apply, in what order and to which part of the damage. It requires reading each policy's insuring agreement, exclusions, deductibles and other insurance wording together with the evidence in the claim file. Single-policy question answering does not test it.

Can public policy forms replace real claim files for these tasks?

Public forms such as the NFIP Dwelling Form supply the wording, but not the conflicts, missing documents and final dispositions that make a task hard. Forms alone produce reading comprehension questions. Closed files supply the decisions the gold answers depend on.

How many policies should one task include?

Include every policy that could plausibly respond to the event, even ones that ended up paying nothing. A policy that excluded the loss is often the most informative part of the task, because the model has to recognize the exclusion rather than assume coverage.

Should tasks use the current policy or the one in force on the loss date?

Always the version in force on the loss date, with the endorsements effective then. Policy systems often show the latest renewal, so the task record should store form editions and endorsement effective dates explicitly.

Do these tasks need professional review?

Yes. An insurance operations reviewer should confirm the policy set, quoted wording and final dispositions, and a privacy or rights reviewer should confirm what may be shared. Coverage outcomes depend on contract wording and state law, so this structure is general information rather than coverage advice.

Sources

  • The NFIP Dwelling Form's other insurance condition prorates with non-NFIP flood insurance, makes the NFIP policy primary when the other policy is excess, sits in excess over condominium association insurance, and asks for details of other insurance with the proof of loss. Source
  • FEMA's April 2024 flood insurance manual allows only one NFIP policy with building coverage per building, keeps the earlier policy and pays damaged items under one policy only. Source
  • NAIC consumer guidance says homeowners policies do not cover flood damage, which requires a separate flood policy. Source
  • NAIC describes hurricane or named storm deductibles as applied separately from other deductibles and often set as a percentage of insured value. Source
  • TWIA policies cover only property damage caused directly by wind and hail and exclude flooding and storm surge. Source
  • The Texas Department of Insurance says coastal homeowners policies may not cover wind and hail, requiring a separate windstorm policy. Source
  • CMS explains that Medicare does not pay to the extent a no-fault or liability insurer or a workers compensation entity has paid or may reasonably be expected to pay, and that Medicare's earlier payments are conditional and must be repaid from a later settlement, judgment or award. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies