---
title: "The claims process end-to-end: from FNOL to settlement"
description: "The claims process is a clock and a ledger running from FNOL to settlement. Map all eight stages, and see why investigation is the one still measured in weeks."
date: "2026-07-09"
lastModified: "2026-07-09"
author: "Pankaj Dhariwal"
tags: ["Guides"]
canonical: "https://gethesperai.com/blog/claims-process-end-to-end-fnol-to-settlement/"
---

# The claims process end-to-end: from FNOL to settlement

> **TL;DR** The insurance claims process runs through eight stages from First Notice of Loss to settlement, and two things run alongside it from the first minute: cycle time (the clock) and leakage (the ledger). Carriers have automated FNOL, triage, coverage checks, and estimating down to minutes. Investigation is the one stage still measured in 14+ days, so it is where the clock stalls and the ledger bleeds.
>
> - Eight stages: FNOL through settlement, every handoff adds time
> - Average auto repair cycle time is 22.3 days (J.D. Power 2024)
> - Investigation is the last stage still measured in weeks, not minutes

- **22.3 days** - Average auto repair cycle time (Down 1.0 day from 2023 (J.D. Power 2024))
- **$308.6B** - Annual US insurance fraud loss (~10% of P&C losses involve fraud (CAIF))
- **14%** - Of personal auto premium is leakage (Premium leakage estimate (III / Verisk))
- **14+ days → 2-4 hrs** - Investigation cycle time (Manual SIU vs Hesper (Hesper benchmark))

The insurance claims process runs through eight stages, but the way it is usually taught - as a linear checklist from First Notice of Loss to settlement - hides the two things that actually decide the outcome. From the moment a claim is reported, two meters start running at once: cycle time, which the customer watches and the reserve pays for, and leakage, which never shows up as its own line item but quietly erodes the loss ratio. This post maps all eight stages and shows where those two meters run fastest.

The structural argument is simple. Carriers have spent a decade automating the front of the process. Digital FNOL intake, automated triage, systematic coverage verification, and computer-vision estimating have collapsed those stages from days to minutes. But automation has not reached one stage - investigation - which is still measured in 14+ days per case. That is where the process stalls, and it is where the money leaks. You cannot compress the claims process end-to-end while one stage stays manual.

This is the operational reality behind the loss-ratio and cycle-time numbers a Claims VP reports up. For how automation maturity varies stage by stage, see our companion piece on [what is automated and what is still manual in 2026](/blog/insurance-claims-automation-2026-whats-automated). This post is part of our [claims fraud leakage](/blog/claims-fraud-leakage-pillar) cluster, which tracks where uninvestigated claims drain profitability.

## The claims process is a clock and a ledger, not a checklist

The claims process is best read as two meters running in parallel from FNOL: a clock measuring cycle time and a ledger measuring leakage. The clock is what the customer feels and what a Claims VP is measured on; every day a reserve sits open costs the carrier. The ledger is overpayment, missed exclusions, and un-investigated fraud that never surfaces as its own number. Both are set at intake and paid at settlement.

The clock is not abstract. Per the [J.D. Power 2024 U.S. Auto Claims Satisfaction Study](https://www.claimsjournal.com/news/national/2024/11/01/327168.htm), the average auto repair cycle time was 22.3 days, down 1.0 day from 2023, and "time to settle claim" is one of the eight dimensions the study uses to score satisfaction. Cycle time is a customer-satisfaction driver, not just an internal metric. Every stage in the process is a handoff, and every handoff adds days to that 22.3-day figure.

The ledger is the quieter meter. Per the [Coalition Against Insurance Fraud](https://insurancefraud.org/fraud-stats/), insurance fraud steals at least $308.6 billion a year from American consumers, and fraud occurs in about 10% of property-casualty losses. Beyond outright fraud, the [Insurance Information Institute](https://www.iii.org/article/background-on-insurance-fraud) notes that as much as 14 percent of all personal auto premium can be attributed to premium leakage. The clock and the ledger collide at exactly one stage - investigation - and that collision is the spine of this post.

## Stages 1-2: FNOL and triage set the clock in motion

First Notice of Loss (FNOL) is the moment the policyholder reports the claim, and triage is where that claim gets routed to the right handler and priority. Together they start the settlement clock and produce the first fraud signals. Every decision made here - severity, complexity, routing - sets the speed and the exposure for everything downstream, which is why intake quality compounds through the whole process.

Both stages are heavily automated now. Digital FNOL intake through web, mobile, or telematics captures the loss in minutes, and the J.D. Power study tracks "ease of starting claim" as one of its satisfaction dimensions precisely because carriers have invested there. Automated triage scores incoming claims for severity and routing, and for a full breakdown of how that routing works, see our [claims triage automation guide](/blog/claims-triage-automation-guide).

### The first fraud signals appear at intake, not investigation

Triage is also where suspicious claims get flagged. This is where the leakage ledger opens: a claim scored as low-risk and fast-tracked can be exactly the one that needed a second look. Rules-based flagging carries a real cost here - 60-85% of what a rules layer flags is not fraud unless the rules are heavily tuned - so triage generates noise that flows straight into the investigation queue. Hesper has built-in fraud detection, so it can surface signals at intake rather than depend entirely on a bolt-on scoring layer, though the deeper point is what happens to a flag once it is raised.

## Stages 3-4: coverage verification and reserving set the financial exposure

Coverage verification confirms the policy actually responds to the loss, and evaluation and reserving set the estimated exposure and open a reserve. These two stages fix the financial size of the claim. Coverage checks catch exclusions and policy limits; reserving is the carrier's first formal estimate of what the claim will cost, and it drives capital allocation across the book.

Automation has compressed this middle of the process hard. Systematic coverage verification runs against policy data in seconds, and computer-vision estimating tools assess damage in minutes rather than days. That is genuine progress - but it has a side effect. When the front of the process gets fast, the bottleneck does not disappear; it moves downstream. Automating coverage and estimating just relocates the drag to the one stage that stayed manual. For where that leaked money accumulates across stages, see our analysis of [how uninvestigated claims drain profitability](/blog/insurance-claims-leakage-reduce-losses).

> **Estimating is not investigation**
>
> A claim assessed by computer vision at $12,000 in damage can still be fraudulent. Estimating tools like the ones from Tractable and CCC compress the evaluation stage to minutes, but they measure legitimate damage - they do not test whether the loss happened as reported. Estimating sits upstream of investigation. A fast, accurate estimate on a staged loss is a fast, accurate payment of a fraudulent claim.

The exposure set here is where leakage first becomes measurable. The III attributes as much as 14 percent of personal auto premium to leakage, and the [Insurance Information Institute](https://www.iii.org/article/background-on-insurance-fraud) puts annual property and casualty fraud at $45 billion, workers compensation fraud at $34 billion, and auto theft fraud at $7.4 billion. Every dollar of that either gets caught at investigation or gets paid at settlement. The stage that decides which is the one still running on human time.

## Stage 5: investigation, the one stage still measured in weeks

Investigation is where a flagged or complex claim gets examined for fraud and validity - document forensics, statement cross-reference, timeline reconstruction, financial pattern analysis - and it is the one stage in the process still measured in weeks. A manual Special Investigations Unit review takes 14+ days per case, while every stage around it has been compressed to minutes. This is where the clock stalls and the ledger bleeds.

The bottleneck is structural, not a staffing accident. A human investigator works one case at a time because attention is the constraint, and a typical investigator already carries 200+ open cases. Because capacity is finite, only about 25% of flagged claims get fully investigated; the rest are paid, denied without full work, or queued indefinitely. With roughly 10% of P&C losses involving fraud and $308.6 billion lost annually, the un-worked 75% is the largest single leak in the process.

*Figure: The settlement clock and the leakage ledger run from FNOL. Every stage but one has been compressed to minutes. Investigation - 14+ days per case, ~25% coverage - is where both meters stall, and where a compressed 2-4 hour, 100%-coverage stage changes the whole process.*

Automating the investigation stage is what closes the loop. AI investigation agents run 15+ investigation phases in parallel on every flagged claim and return an audit-ready report in 2-4 hours instead of 14+ days. That is the difference between a partially automated process and an end-to-end one. It also changes the coverage math structurally: from about 25% of flagged claims to 100%.

| The investigation stage: manual SIU vs Hesper (Hesper internal benchmark) | Value | Share |
| --- | --- | --- |
| Manual cycle time (14+ days, indexed) | 14+ days | 100% |
| Hesper cycle time (2-4 hours, indexed) | 2-4 hrs | 2% |
| Manual flagged-claim coverage | ~25% | 25% |
| Hesper flagged-claim coverage | 100% | 100% |

The economics follow the coverage. Manual investigation runs about $2,500 per case; an AI-run investigation runs about $150. Throughput moves from roughly 10 investigations per investigator per month to 800+. The investigator's role shifts from execution to decision-making - reviewing an audit-ready report and handling exceptions instead of assembling every case by hand. This is the move from fraud detection to fraud resolution: Hesper has built-in fraud detection, not just a downstream position of other tools, so it takes a flag and resolves it end-to-end.

> Every stage of the claims process except one has been compressed to minutes. Investigation is still measured in 14+ days, so it is simultaneously the biggest cycle-time drag and the biggest source of leakage. You cannot claim an end-to-end automated claims process while the one stage that stops fraud stays manual.
>
> - Hesper AI product research

## Stages 6-8: what a compressed investigation unlocks at settlement

Negotiation settles the amount with the claimant, settlement pays the claim, and closure documents the outcome and closes the file. These final three stages are where the clock and the ledger get paid. Faster, fuller investigation changes all three - not just the SIU spend line - because it changes the information available before money goes out the door.

When investigation takes 14+ days, reserves sit open longer, settlement is delayed, and recovery windows narrow. Compressing investigation to 2-4 hours lets a carrier set more accurate reserves earlier, settle valid claims faster, and deny or pursue fraudulent ones before payment. Settlement speed and fairness are customer-facing: the J.D. Power study ranks "time to settle claim" and "fairness of settlement" among its core dimensions, and 48% of respondents reported a premium increase in the prior 12 months - a reminder that leaked loss cost eventually reaches the customer as price.

Closure quality also improves. An audit-ready investigation report flows back into the claims management system as a case attachment, so the documented-decision trail is complete when the file closes. Investigating 100% of flagged claims instead of 25% means fewer fraudulent claims settle by default simply because the SIU ran out of capacity to look. The compression at one stage propagates through every stage after it.

## Manual vs automation-augmented claims timeline

Laid out side by side, the eight stages make the bottleneck visible. Most stages have credible automated durations measured in minutes to hours; only investigation carries a hard, sourced gap on both sides - 14+ days manual versus 2-4 hours augmented - and the 22.3-day total cycle time anchors the whole table. The leakage column shows where money escapes at each handoff.

| Stage | What happens | Manual duration | Automation-augmented | Where leakage occurs |
| --- | --- | --- | --- | --- |
| FNOL | Policyholder reports the loss | Hours to days | Minutes (digital intake) | Incomplete or delayed first notice |
| Triage & assignment | Route to handler and priority | Hours to days | Minutes (automated scoring) | Mis-routing; missed early fraud signals |
| Coverage verification | Confirm the policy responds | Hours to days | Seconds to minutes | Missed exclusions and policy limits |
| Evaluation & reserving | Set exposure, open reserve | Days | Minutes (computer-vision estimating) | Over-reserving; inflated estimates |
| Investigation | Examine flagged claims for fraud | 14+ days per case | 2-4 hours per case | ~75% of flags never fully worked |
| Negotiation | Agree the amount with claimant | Days to weeks | Faster with earlier evidence | Overpayment without full facts |
| Settlement | Pay the claim | Days | Days (payment rails) | Paying fraudulent or inflated claims |
| Closure | Document outcome, close file | Days | Hours (audit-ready report) | Weak documented-decision trail |

Read the investigation row against the rest of the table. Every other stage has an automation-augmented duration in minutes to hours; investigation is the only row where the manual side is measured in weeks. That single row is why the 22.3-day average cycle time does not fall further even as intake and estimating get faster - the drag has concentrated in the one stage automation has not reached.

## Where each vendor sits in the claims process

Mapping the vendor landscape onto the stage model shows that the investigation stage is the layer no product occupies. Claims management systems own the workflow rails, estimating vendors own evaluation, and detection vendors own the flagging at and after FNOL. Investigation - taking a flag and resolving it end-to-end - has no incumbent except manual SIU teams.

Claims management systems like [Guidewire ClaimCenter](https://www.guidewire.com/products/claimcenter) and [Duck Creek Claims](https://www.duckcreek.com/products/claims/) run the FNOL-to-settlement workflow and increasingly automate intake and triage. Hesper integrates into those systems as the investigation stage: a flagged claim flows out, and an audit-ready report flows back as a case attachment. Hesper never replaces the claims management system.

Estimating vendors like Tractable and CCC compress evaluation to minutes for damage assessment; they sit upstream of investigation and are complementary, not competitive. Detection vendors like [FRISS](https://www.friss.com/), [Shift Technology](https://www.shift-technology.com/), and [Verisk](https://www.verisk.com/products/claimsearch/) flag suspicious claims at and after FNOL. Detection is upstream; investigation is downstream. Hesper takes the flag those tools raise and resolves it - complementary to FRISS, Shift Technology, and Verisk, not a replacement. Because Hesper also has built-in fraud detection, it can operate standalone if a carrier has no detection vendor on a given line.

## Key takeaways

- The claims process runs through eight stages from FNOL to settlement, and two meters - cycle time (the clock) and leakage (the ledger) - run alongside it from the moment of first notice.
- Carriers have automated FNOL intake, triage, coverage verification, and estimating down to minutes, which relocated the process bottleneck downstream rather than removing it.
- Investigation is the one stage still measured in weeks: a manual SIU review takes 14+ days per case and reaches only about 25% of flagged claims, so it is both the biggest cycle-time drag and the biggest leakage source.
- Compressing investigation to 2-4 hours at 100% coverage changes reserving accuracy, settlement speed, and closure quality across the stages that follow it - not just the SIU spend line.
- Fraud detection and investigation are different stages: detection flags at FNOL, investigation resolves the flag downstream, and Hesper occupies the investigation layer that no other vendor fills.

## Frequently asked questions

### What are the stages of the insurance claims process from FNOL to settlement?

The claims process runs through eight stages. It starts with First Notice of Loss (FNOL), when the policyholder reports the claim. Triage and assignment route the claim to the right handler and priority. Coverage verification confirms the policy responds. Evaluation and reserving set the estimated exposure and open a reserve. Investigation examines flagged or complex claims for fraud and validity. Negotiation settles the amount with the claimant. Settlement pays the claim, and closure documents the outcome and closes the file. Each stage is a handoff, and every handoff adds cycle time. Per the J.D. Power 2024 U.S. Auto Claims Satisfaction Study, the average auto repair cycle time was 22.3 days, and "time to settle claim" ranks among the top satisfaction drivers.

### Where does most delay happen in the claims process?

Delay concentrates at the investigation stage. Carriers have automated FNOL intake, triage, coverage checks, and damage estimating down to minutes, so the process bottleneck has moved downstream to investigation - the one stage still measured in weeks. A manual Special Investigations Unit review takes 14+ days per case, and one investigator typically carries 200+ cases. Because capacity is limited, only about 25% of flagged claims get fully investigated; the rest are paid, denied without full work, or queued. That backlog stalls the settlement clock on exactly the claims most likely to contain fraud. With roughly 10% of property-casualty losses involving fraud per the Coalition Against Insurance Fraud, the investigation bottleneck is both the biggest cycle-time drag and the biggest source of leakage.

### How much does insurance fraud and claims leakage cost carriers?

The Coalition Against Insurance Fraud estimates insurance fraud steals at least $308.6 billion every year from American consumers, and fraud occurs in about 10% of property-casualty losses. The Insurance Information Institute puts annual property and casualty fraud at $45 billion, workers compensation fraud at $34 billion, and auto theft fraud at $7.4 billion. Beyond outright fraud, leakage - overpayment, missed exclusions, and inflated invoices - erodes the loss ratio quietly; the III notes as much as 14 percent of personal auto premium can be attributed to premium leakage. The [NAIC](https://content.naic.org/insurance-topics/insurance-fraud) cites an FBI estimate that insurance fraud costs the average family between $4,000 and $7,000 in increased premiums over a 10-year period.

### How does automation compress claims cycle time?

Automation compresses cycle time by removing the manual handoffs between stages. Digital FNOL intake, automated triage and routing, systematic coverage verification, and computer-vision estimating each collapse a stage from days to minutes. But automating everything except investigation only relocates the bottleneck - the flagged-claim workflow still routes to a manual SIU queue measured in 14+ days. Closing the loop requires automating the investigation stage too. AI investigation agents run 15+ investigation phases in parallel on every flagged claim and return an audit-ready report in 2-4 hours instead of 14+ days, lifting coverage from about 25% to 100% of flagged claims. That is the difference between a partially automated process and an end-to-end one.

### Where does fraud detection fit in the claims process versus investigation?

Detection and investigation are different stages. Detection sits at and just after FNOL: tools like FRISS, Shift Technology, and Verisk score incoming claims and flag suspicious ones. Investigation sits downstream: it takes a flagged claim and resolves it - document forensics, statement cross-reference, timeline reconstruction, financial pattern analysis - and produces a documented conclusion. Detection tells you a claim looks suspicious; investigation tells you whether it is, and why, with an audit trail. Most carriers have automated detection but still run investigation manually, which is why flags pile up faster than the SIU can work them. Hesper AI sits at the investigation stage, complementary to detection vendors, with built-in fraud detection so it can also operate standalone. The shift is from fraud detection to fraud resolution.

### How does faster claims investigation affect settlement and reserving?

Faster investigation changes the economics of the stages after it, not just the SIU spend line. When investigation takes 14+ days, reserves sit open longer, settlement is delayed, and recovery windows narrow. Compressing investigation to 2-4 hours lets carriers set more accurate reserves earlier, settle valid claims faster, and deny or pursue fraudulent ones before payment goes out the door. Settlement speed and fairness matter to customers directly: the J.D. Power 2024 study ranks "time to settle claim" and "fairness of settlement" among its eight core satisfaction dimensions. Investigating 100% of flagged claims instead of 25% also means fewer fraudulent claims settle by default because the SIU ran out of capacity to look.