Claims Cycle Time: How to Measure It and Where the Days Actually Go

Key Takeaways

• Claims cycle time is elapsed calendar days from first notice of loss to closure. How you measure it changes the answer: calendar or business days, closed-claim cohort or all  open claims, mean or median.

‍

• Median beats mean. A small number of catastrophe claims pulls the average away from a typical file.

‍

• There is no credible public benchmark. Statutory deadlines set a ceiling, and vendor ranges are observations rather than measured data.

‍

• The days accumulate across five stages, and payment gets blamed for delay that happened upstream.

‍

• An aggregate number cannot show variance between adjusters, rework loops, or work that happens between systems. An internal baseline segmented by claim type beats any industry average.

‍

‍

‍What Is Claims Cycle Time?

‍

Claims cycle time is the elapsed time from first notice of loss to final settlement and closure, measured in calendar days across every stage the claim moves through, from intake and triage to investigation, approval, and payment before the file closes.

‍

The answer sits in five stages: intake, triage, investigation, approval, and payment. Each one can add days for a different reason, and almost none of that shows up the same way twice across adjusters, claim types, or claims systems.

‍

Two claims that both close in 20 days on average might have gotten there through very different paths, one moving steadily, the other stalling for a week before catching up. That difference matters more than the average, because it points at where the process is inconsistent.

‍

How to Calculate Claims Cycle Time

‍

The formula: total cycle time across settled claims, divided by the number of claims settled. Three decisions made before that division change the result.

‍

The first is calendar days versus business days. Calendar days count every day a claim sits open, weekends included, which is closer to what a policyholder actually experiences. Business days flatter the number by excluding weekends and holidays, which can make a slow process look faster than it is.

‍

The second is which claims get counted. A closed-claim cohort measures only settled files, showing how long claims took once they were finished. Including all open claims pulls in files still in progress, which understates cycle time for anything still moving through investigation or approval.

‍

The third is mean versus median. The mean gets pulled upward by a small number of catastrophe claims that take far longer than anything else in the book. The median is the more honest number, since it reflects a typical claim rather than getting distorted by the tail that CAT events create.

‍

What Is a Good Claims Cycle Time?

‍

There's no credible public benchmark for P&C claims cycle time. What exists instead are three kinds of numbers, each answering a different question.

‍

Start with regulation. Every state has some version of an Unfair Claims Settlement Practices Act setting outer limits on how long an insurer can take. California's version, the Fair Claims Settlement Practices Regulations under 10 CCR 2695.5 and 2695.7, requires acknowledgment within 15 days, a decision within 40 days of proof of claim, and payment within 30 days of settlement, an 85-day outer limit from start to finish. These are ceilings, not targets. A carrier operating well inside them can still be losing days it doesn't need to lose.

‍

Then there is survey data. A December 2022 Five Sigma survey of 100 senior P&C claims executives found that 82% said closing a claim takes more than 30 days. That's a survey of claims executives describing their own experience, not a measured industry benchmark, but it's the closest thing to real-world consensus that exists.

‍

Last are the vendor-observed ranges. Assured, a vendor in this space, published ranges in June 2026 from its own market observations: personal auto claims running 15 to 30 days, property 20 to 40, and CAT events 30 to 90 or more. Assured describes these as observations from their own client base, not measured industry data, and that's the right way to read them.

‍

None of these three numbers tells a carrier whether its own cycle time is good. Cross-carrier comparison is weak anyway, since mix, line, and CAT exposure differ too much between books of business to compare cleanly. An internal baseline, segmented by claim type, beats any industry average.

‍

Where the Days Actually Go: The Five Stages

‍

A claim moves through five stages between first notice of loss and final payment, and each one can add days for a different reason. Breaking cycle time down by stage is what separates a genuinely complex claim from one that's simply been sitting.

‍

‍

FNOL and Intake

‍

An incomplete or inconsistent first capture forces follow-up before investigation can start. A missing policy number, an incomplete loss description, or a detail that needs a callback all push the real start of the claim later than the date it was actually reported.

‍

Triage and Assignment

‍

A claim routed to the wrong adjuster, or one that turns out to be more complex than its initial classification suggested, loses days before anyone starts real work on it. Complexity mismatch is common: a claim tagged as simple that turns out to need a specialist sits until someone notices. Accurate claims triage at intake prevents the misroute entirely.

‍

Investigation and Estimate

‍

This is where re-inspections, supplemental estimates, and waiting on third parties tend to add the most time. A contractor's estimate that arrives late, or a re-inspection triggered by new damage, can stall a file for days without anyone actively working it.

‍

Approval and Negotiation

‍

Approval queues and authority thresholds create their own delay. A settlement that exceeds an adjuster's authority has to wait for a supervisor's review, and back-and-forth negotiation over the amount can add multiple rounds before both sides agree.

‍

Payment and Closure

‍

Payment processing and administrative closure lag get blamed often, but they're rarely the real cause. By the time a claim reaches this stage, most of the actual delay has already happened upstream. This stage just makes the total visible.

‍

Why Your Cycle Time Dashboard Cannot Tell You Where the Days Went

‍

An aggregate cycle time number is a real measurement, but it's missing three things a dashboard was never built to show.

‍

One is variance between adjusters handling the same claim type. Two adjusters working identical claim types can produce meaningfully different cycle times, and a single average hides which one. If one adjuster consistently closes files faster with the same outcome quality, that's a process worth understanding and standardizing, not just a number to average away. In process intelligence terms, those different routes are process variants: one claim type, several real paths through it.

‍

Another is rework loops that leave no timestamp in the system of record. A supplemental estimate gets requested, a file gets reopened after being marked ready to close, a step gets redone because the first pass missed something. None of that shows up as its own event. It just looks like the claim took longer than expected, without showing why.

‍

The third is work that happens between systems. A file waiting in an adjuster's inbox for review, a spreadsheet kept for supplemental estimates outside the claims system, a phone call to a third-party vendor that never gets logged: all of it adds real days, and none of it appears anywhere a dashboard reads from.

‍

A cycle time dashboard tells you the number is bad. It does not tell you where the days went.

‍

Cycle time and claims leakage are related but different problems. Cycle time is elapsed days. Leakage is money paid that shouldn't have been. The two tend to move together, since the same process breakdowns that stretch out a claim often create the conditions leakage needs. OpsDog, which defines the metric as first notice of loss to formal settlement in calendar days, draws the same link between extended cycle time and leakage. Claims leakage, the money side of the same problem, is its own subject.

‍

Seeing past the aggregate number takes process intelligence: measuring the process itself rather than the timestamps at either end of it. How process and task mining actually capture the work differs: one reads system logs, the other captures activity at the desktop. For a process mining visualization background, a worked example is easier to follow than an abstract description.

‍

How to Reduce Claims Cycle Time

‍

You reduce claims cycle time by fixing the stage that is losing the days, which means measuring by stage before changing anything. Claims process automation only works once you know which steps are worth automating, and that has to come from measurement, not assumption. Claims processing efficiency is the sum of smaller corrections at each stage losing days, not a single fix. These are the patterns that show up most often once cycle time is broken down by stage. Stage-level work moves real days. McKinsey's account of Aviva's claims transformation reports routing accuracy up 30% and liability assessment time on complex cases down by 23 days, both gains landing at specific stages rather than spread across the book.

‍

Fix Intake Quality at First Capture

‍

Most downstream delay traces back to an incomplete or inconsistent first capture. A required field, a standard checklist, or a validation step at intake catches the gap before it turns into a callback three days later. Catching a missing detail at the point of intake costs a few extra minutes. Catching it during investigation costs a phone call, a delay, and a claim that now looks more complex than it actually is.

‍

Cut the Rework Loop

‍

If a claim type shows a high rate of reopened files or supplemental estimates, that's the highest-leverage place to start. Rework inflates cycle time twice: once for the original pass, and again for the redo. It also eats adjuster capacity that never shows up on a workload report, since a reopened file competes for the same hours as a brand-new one. Fixing the reason a step gets redone usually improves cycle time more than any single downstream change.

‍

Standardize on the Path Your Best Adjusters Already Take

‍

When the same claim type shows wide variance between adjusters, the fastest fix is often already inside the organization. This is process adherence, not performance management: the goal is finding which version of the workflow produces the best outcome, then making that the standard, not ranking individuals against each other.

‍

Automate Only the Steps You Have Measured

‍

Straight through processing insurance can work well for simple, high-volume claims once the steps are stable and well understood. It works badly on a process nobody has actually mapped. Automating a process you haven't measured doesn't remove the problem. It makes the same process fail faster, at scale, with less visibility into why. The risk is documented. CIO Dive reported in April 2026, drawing on a study from AI vendor Simplifai, that insurers' finance teams cannot tie AI investment to returns, which is what keeps projects stuck in pilot.

‍

Measure Your Claims Cycle Time in 14 Days

‍

Everything above depends on having real, stage-level data instead of a single aggregate number. That is what process intelligence produces. Workflow Optimization gives claims operations teams that baseline directly from how claims are really worked, not from a workshop or a self-reported estimate.

‍

Workflow Optimization is built for teams running claims through Salesforce Service Cloud. Over 14 days, it captures cycle time by stage, rework rate, and variance between adjusters handling the same claim type, the same measurements covered throughout this piece, applied to your own claims data rather than an industry range.

‍

Request beta access to see where your own claims cycle time is actually going.

‍

Frequently Asked Questions

‍

What is claims cycle time?

Claims cycle time is the elapsed time from first notice of loss to final settlement and closure, measured in calendar days. It covers every stage a claim moves through, including intake, triage, investigation, approval, and payment. Measured by stage instead of as a single average, it shows where the delay accumulates.

‍

How do you calculate claims cycle time?

Claims cycle time is calculated by dividing total cycle time across settled claims by the number of claims settled. Three decisions change the result: calendar days versus business days, a closed-claim cohort versus all open claims, and mean versus median. Median is the more defensible choice, since a small number of catastrophe claims can pull the mean upward without reflecting a typical file.

‍

What is the average claims cycle time in P&C insurance?

There's no reliable industry average, since claim mix, line, and CAT exposure vary too much between carriers to compare cleanly. Statutory deadlines set an outer limit: California requires acknowledgment within 15 days, a decision within 40, and payment within 30 of settlement, an 85-day ceiling. Vendor-published ranges exist but reflect one vendor's own client base, not measured industry data. An internal baseline, segmented by claim type, is the more useful number.

‍

What is the difference between claims cycle time and claims leakage?

Claims cycle time measures elapsed days from first notice of loss to closure. Claims leakage measures money paid that shouldn't have been. The two are related since the same process breakdowns that stretch out a claim often create the conditions leakage needs, but a longer cycle time doesn't always mean money was lost, and leakage doesn't always show up as a slower claim.

‍

How can you reduce claims cycle time without replacing your claims system?

Most claims systems are purpose-built for the processes they already run, so replacing one isn't usually the right fix. Insightful already integrates with insurance-specific tools such as Xactimate, so connecting to a claims system isn't a new integration category. The approach adds process data on top of the existing system rather than replacing it, showing where the days go without disrupting what's already running. From there, a scoped call can map out what that looks like for a specific claims operation.

‍

‍

‍