Workflow FoundationsChapter 3522 min read

Claims Workflow, FNOL to closure, where claims and underwriting share data and where they don't.

Claims handling is structurally distinct from underwriting but operationally entangled. Every commercial claim follows a consistent path: first notice of loss, coverage analysis, liability and damages investigation, reserving, defense management, settlement, and (if applicable) subrogation. Claims data eventually flows back into underwriting through loss runs, but the two functions operate on different timelines, with different systems, and with different incentives.

§ 01

The mental model

A claim is the carrier's payment obligation under a policy. Claims handling is the operational process that determines whether the obligation exists, how much it is, and when it gets paid. The function combines coverage analysis, fact investigation, financial reserving, vendor management, negotiation, and (when needed) litigation management.

For commercial claims, the work is more involved than personal lines because the policies are larger, the wordings more bespoke, the counterparties more sophisticated, and the disputed issues more frequent. A typical commercial GL claim may run for years before resolution. A complex D&O securities class action may run a decade. Workers compensation claims with permanent disability components may stay open for the claimant's lifetime. Each open claim consumes adjuster attention, defense costs, and reserve capital. The discipline of claims handling determines whether the carrier recovers its expected loss ratio or surprises itself with adverse development. The function is also the primary operational interface between the carrier and the insured during the policy period; underwriters issue the policy, claims people deliver on it.

Anchor concept

Claims is where insurance actually delivers (or doesn't). The underwriter's pricing assumes claims will be paid efficiently and reserved accurately. When claims handling drifts (delays, over-reserving, under-reserving, missed defenses, missed subrogation), the underlying economics of the policy degrade. Strong claims operations are a competitive advantage that shows up in loss ratios over time.

§ 02

FNOL and intake

First Notice of Loss (FNOL) is the moment the carrier learns about a claim. Speed and accuracy at intake matter for everything that follows.

How FNOL arrives

  • From the insured directly. The insured calls a 1-800 number, submits through a portal, or emails the carrier or broker.
  • From the broker. The broker forwards a claim notice received from the insured. Most commercial claims still flow through the broker.
  • From a third party. A claimant attorney, a third-party administrator, or a court filing arrives at the carrier directly.
  • From a regulatory body. An EEOC charge, a state agency notice, an OSHA citation, or a similar regulatory communication.
  • From a counterparty. A subpoena, a tender from another carrier, or a contractual indemnity demand.

What gets captured

  • Date and time of loss.
  • Date of report.
  • Location of loss.
  • Description of loss event.
  • Persons or property involved.
  • Estimated severity.
  • Reporting party and contact information.
  • Police report, incident report, or other source documentation.

Initial routing

FNOL data routes the claim to the appropriate adjuster. Routing criteria typically include line of business, severity tier, geography, and (for some lines) class of business. A simple workers comp medical-only claim goes to a high-volume adjuster; a complex commercial property fire goes to a senior adjuster with property expertise; a securities class action goes to a senior litigation specialist.

The 24-hour rule

Most carriers have internal SLAs requiring acknowledgment of FNOL within 24 hours and substantive contact with the insured within a defined initial period (often 24-72 hours). Delayed first contact is a recurring source of insured friction and is closely tracked as a service metric.

§ 03

Coverage analysis

Before the carrier investigates the underlying facts, the adjuster confirms that coverage applies. This is the gatekeeping step that determines whether the claim is the carrier's obligation in the first place.

What coverage analysis covers

  • Policy in force. Was a policy in force on the date of loss, with sufficient remaining limit?
  • Insured under the policy. Is the party seeking coverage a named insured, additional insured, or otherwise covered party?
  • Triggering event. Did the alleged event meet the policy's trigger (occurrence, claims-made, discovery)?
  • Bodily injury / property damage. Does the loss qualify under the policy's covered injury or damage definition?
  • Exclusions. Does any exclusion apply? Pollution, cyber, war, employer's liability, owned property, automobile-related events.
  • Conditions. Did the insured comply with conditions (timely notice, cooperation, suit limitations, prior consent for settlement)?
  • Other insurance. Are other policies involved (primary, excess, contributing, OCIP, project-specific)?

The reservation of rights

If the carrier has uncertainty about coverage but wants to proceed with defense or investigation, it issues a reservation of rights letter. The ROR preserves the carrier's right to deny coverage later if facts develop that reveal an excluded event. RORs are a routine feature of complex commercial claims and are not necessarily a signal of denial.

Coverage opinions and outside counsel

For high-dollar or unusually complex coverage questions, the adjuster often engages coverage counsel for a formal opinion. The opinion analyzes the policy language, the facts, the applicable case law, and the recommended carrier position. Coverage opinions are working documents that inform the claim handling decision.

Denial

When coverage clearly does not apply, the carrier issues a denial. Denial letters cite the specific policy provisions and the facts on which the denial is based. Insureds frequently challenge denials, and the denial letter must be defensible against a bad-faith claim. Denials require senior review and (for many carriers) management sign-off.

§ 04

Liability and damages investigation

Once coverage is confirmed, the substantive investigation begins. This is where most adjuster time and most external vendor expense are concentrated.

Liability investigation

  • Document collection. Police reports, incident reports, OSHA recordables, contracts, service agreements, work orders.
  • Witness interviews. The insured, employees, witnesses, claimant.
  • Site inspection. Where applicable, physical inspection of the loss location.
  • Expert engagement. Engineers, scientists, accident reconstructionists, medical professionals.
  • Subpoena and discovery. When litigation is filed, formal discovery to obtain relevant evidence.
  • Surveillance. For workers compensation and disability-related claims, surveillance may be appropriate.

Damages investigation

  • Medical records review. For bodily injury claims, evaluation of the medical history, treatment, and prognosis.
  • Economic loss analysis. Lost wages, lost earning capacity, future treatment costs.
  • Repair estimates. For property damage, contractor estimates, salvage values, replacement cost analysis.
  • Business interruption analysis. For BI claims, accountants and forensic accountants quantify the lost income and continuing expenses.
  • Comparable verdict and settlement research. Understanding what similar cases have resolved for in the relevant venue.

The defense team

For litigated claims, the carrier engages defense counsel from a panel of approved firms. The defense attorney reports to the adjuster, develops the litigation strategy, and represents the insured. The relationship is a tripartite one: the attorney's client is the insured, but the attorney is paid by and reports operationally to the carrier.

§ 05

Reserving

The reserve is the carrier's estimate of the ultimate cost of the claim. Reserves drive financial reporting, reinsurance reporting, and capital allocation. Accurate reserving is the financial discipline of the claims function.

Reserve components

  • Indemnity reserve. Estimated amount the carrier will pay the claimant or the insured.
  • Allocated loss adjustment expenses (ALAE). Defense counsel fees, expert fees, court costs, mediation fees, vendor expenses tied directly to this claim.
  • Unallocated loss adjustment expenses (ULAE). Internal claims handling costs allocated through expense factors.

Reserve methodology

  • Stair-step. Reserves set at defined milestones in the claim's life: initial reserve, post-investigation, post-discovery, post-summary judgment, pre-trial. Each step reflects new information.
  • Most-likely outcome. The reserve reflects the adjuster's estimate of the most probable resolution amount.
  • Mean expected outcome. The reserve reflects the probability-weighted average of possible outcomes.
  • Multiple-scenario reserving. For complex claims, multiple scenarios are quantified and reserved separately.

Reserve adequacy

Carriers track reserve adequacy through several lenses: reserve-to-paid development (how reserves change relative to ultimate payments), case-by-case audit, and aggregate reserve studies by line and accident year. Adequate reserves develop favorably or neutrally; inadequate reserves develop adversely as claims close above expectations.

The IBNR component

Beyond case reserves, carriers maintain an IBNR (incurred but not reported) reserve at the portfolio level for losses that have occurred but not yet been reported. IBNR is set actuarially based on historical reporting patterns. IBNR is consequential at financial reporting time but does not flow directly into individual claim handling.

§ 06

Settlement and litigation management

Most claims resolve through settlement. Litigation through trial is the exception, not the rule, even for claims that file suit.

Settlement strategy

  • Direct negotiation. Adjuster-to-claimant or adjuster-to-claimant-attorney negotiation. Used for clear-liability claims with manageable damages.
  • Mediation. Voluntary or court-ordered facilitated negotiation. Used for many commercial claims, particularly bodily injury claims with serious damages.
  • Mandatory pre-trial settlement conferences. Court-imposed settlement discussions before trial.
  • Structured settlements. Periodic-payment settlements (typically funded through annuities) for catastrophic injury claims.
  • High-low agreements. Used in litigation where parties agree to a defined settlement range regardless of trial outcome.

The hammer clause and settlement consent

For lines with insured consent provisions (D&O, professional liability, EPLI), the policy specifies how the carrier and insured handle settlement disagreements. The hammer clause (covered in Chapter 16) governs the consequences when one side wants to settle and the other does not.

Litigation management

  • Litigation budgeting. Defense counsel provides budgets at the case level, updated as the case progresses.
  • Litigation guidelines. Carriers maintain guidelines on staffing levels, billing practices, settlement authority levels, and reporting cadence.
  • E-billing. Defense bills are submitted electronically and reviewed against guidelines before payment.
  • Settlement authority. Adjusters operate within defined settlement authority levels; settlements above the authority require management approval.

Trial

Cases that go to trial are a small fraction of filed cases. Trial outcomes can be substantially different from settlement values, particularly in bodily injury cases where venue, judge, and jury composition matter. The "nuclear verdict" trend (Chapter 02) has shifted some carrier strategies toward more aggressive pre-trial settlement to avoid trial risk.

§ 07

Subrogation and recovery

When the carrier pays a claim, the carrier may have rights to recover all or part of the payment from a third party.

Subrogation

Subrogation is the carrier's right to step into the insured's shoes and pursue the third party who actually caused the loss. Common subrogation scenarios:

  • Auto liability. Insured rear-ended; carrier pays the insured's deductible and the property damage; carrier subrogates against the at-fault driver's insurer.
  • Workers compensation. Employee injured at a third-party site; carrier pays WC benefits; carrier subrogates against the third party responsible for the unsafe condition.
  • Property damage. Insured's property damaged by a contractor's negligence; carrier pays the property damage; carrier subrogates against the contractor's GL.
  • Product liability. Insured supplied a component that failed; carrier pays the resulting claim; carrier subrogates against the upstream manufacturer.

Salvage

For first-party property losses where the carrier has paid a total loss, the carrier takes the property and may sell it for residual value. Auto total losses, fire-damaged equipment, and inventory write-offs are common salvage scenarios.

Recovery and the loss ratio

Net of subrogation and salvage, the carrier's actual loss is lower than gross paid. Loss ratios are reported on a net basis, and the recovery function is consequential to net underwriting results. Strong subrogation programs can recover 5-15% of paid losses on lines with material third-party exposure.

§ 08

Where claims and underwriting share data

The two functions are organizationally separate but operationally connected.

The shared dataset: loss runs

Loss runs (Chapter 33) are the primary information bridge between claims and underwriting. The underwriter receives loss runs from the broker (or directly from prior carriers) at submission and renewal. The data on those loss runs comes from the prior carrier's claims system.

What underwriters see

  • Date of loss.
  • Description of loss.
  • Reserves.
  • Paid amount.
  • Status (open, closed, denied, in litigation).
  • For some lines: incident class, location, severity tier.

What underwriters do not see

  • The claim file, including coverage analysis and reservation of rights letters.
  • Confidential settlement terms.
  • Internal carrier reserve methodology.
  • Litigation strategy and defense counsel work product.
  • Adjuster notes.

The internal data flow

Within a single carrier, claims data flows back to underwriting through several channels: loss runs at renewal, portfolio reports, large-loss notifications, and (for some lines) integrated risk management dashboards. Carriers with strong claims-underwriting feedback loops adjust pricing, appetite, and policy language faster than those with siloed functions.

The reinsurance reporting

Material claims trigger reinsurance reporting on a defined cadence. The reinsurance report includes coverage status, reserves, paid amounts, and significant developments. Reinsurers monitor cedant reporting closely and may engage on disputed coverage or settlement strategy on large claims.

§ 09

Where IDP earns its keep

The claims function is document-heavy in a different way than underwriting. Claims documents are operational, time-sensitive, and frequently come from external sources (medical providers, courts, opposing counsel, third-party administrators). The volume per claim is moderate but the frequency of new documents per claim per week is high. The claims operation has long been a target for document automation.

1
Intake
FNOL packets arrive with police reports, incident reports, photos, contracts. Auto-extract metadata.
2
Classify
Identify line, severity tier, geography. Match to policy in force.
3
Extract
Date of loss, description, claimant info, alleged cause, alleged damages.
4
Validate
Verify policy in force, compare reported event against coverage triggers, flag potential exclusion issues.
5
Triage
Score severity, route to adjuster tier, generate initial reserve recommendation.
6
Underwriter
Adjuster receives a structured FNOL package with coverage flags and recommended next steps.
Indico use cases for the claims workflow

The most common high-value extraction is FNOL itself: turning incoming claim notices into structured records that match against policies and route to adjusters. Beyond intake: medical record summarization (for bodily injury claims), legal pleadings extraction (for litigated claims), defense bill review automation, settlement document categorization, subrogation opportunity flagging from incident descriptions. The claims operation also benefits from internal-document automation: policy-in-force confirmation, prior loss matching, related-claim aggregation across the same policyholder.

Chapter 35 · Workflow Foundations · 22 min read

Claims Workflow — Cheat Sheet

Claims handling is structurally distinct from underwriting but operationally entangled. Every commercial claim follows a consistent path: first notice of loss, coverage analysis, liability and damages investigation, reserving, defense management, settlement, and (if applicable) subrogation. Claims data eventually flows back into underwriting through loss runs, but the two functions operate on different timelines, with different systems, and with different incentives.

The mental model: Claims is where insurance actually delivers (or doesn't). The underwriter's pricing assumes claims will be paid efficiently and reserved accurately. When claims handling drifts (delays, over-reserving, under-reserving, missed defenses, missed subrogation), the underlying economics of the policy degrade. Strong claims operations are a competitive advantage that shows up in loss ratios over time.

Key terms

FNOL · First Notice of Loss
ROR · Reservation of Rights letter
ALAE · Allocated Loss Adjustment Expense
ULAE · Unallocated Loss Adjustment Expense
IBNR · Incurred But Not Reported reserves
Subrogation · Carrier's third-party recovery right
Salvage · Carrier's residual property rights

If you remember three things

Claims handling is structurally distinct from underwriting but shares the same insured and the same policy, with loss runs as the dominant data bridge between the two functions. Coverage analysis is the gatekeeper, reserves drive financial discipline, and most claims resolve through settlement rather than trial. The claims operation generates time-sensitive, externally sourced documents at high frequency, which makes it a natural target for document automation.