Captive Insurance
An insurer owned by the businesses it covers, the forms it takes, and what separates a captive from simply retaining the risk.
Glossary
Insurance Claims Cycle Time
Where the clock starts and stops on a claim, why the average hides the files that matter, and what a long cycle time usually indicates.
Insurance claims cycle time is the elapsed time between a defined starting event and a defined endpoint in the handling of a claim. A common measure runs from first notice of loss to claim closure. Other measures track shorter stages, such as the time to first contact, a coverage decision, or the first payment.
The starting and ending events determine what the number means. Two insurers can report different cycle times for the same sequence of events if one measures time to payment and the other measures time to administrative closure.
Where does the clock start and stop?
The start is often first notice of loss, when the insurer receives the initial report. Some systems instead use the date the claim file was opened. Those dates can differ if a report arrives before a handler creates the record.
The date of the incident is another useful timestamp, but it measures a different interval. Time from the incident to notification includes the reporting delay before the insurer begins handling the claim.
Common endpoints include:
| Endpoint | What the measure shows |
|---|---|
| First meaningful contact | How quickly the claims team responds to the person reporting the loss |
| Coverage or liability decision | How long the relevant assessment takes |
| First payment | How quickly an initial payment is made on claims that receive one |
| Final payment | When the last payment in the measured claim history occurs |
| Claim closure | When the claim reaches the insurer’s defined closed status |
Guidewire’s cycle-time documentation distinguishes claim opening, first payment, last payment, and closure. It also explains that the gap between payment and closure can reflect administration or recovery activity. Guidewire’s claim cycle-time definitions.
How to calculate claims cycle time
For an individual claim:
Claims cycle time = endpoint timestamp − starting timestamp
The result can be expressed in hours, calendar days, or business days. Reports should state the unit and apply it consistently. Business-day calculations also need a defined holiday calendar.
Consider a fictional property claim, with each event recorded at the same time of day:
| Event | Date |
|---|---|
| Incident occurs | 1 September |
| Insurer receives the claim | 3 September |
| First contact takes place | 4 September |
| First payment is made | 12 September |
| Final payment is made | 23 September |
| Claim is closed | 26 September |
Using elapsed calendar days, this claim has:
- A two-day reporting delay.
- One day from notification to first contact.
- Nine days from notification to first payment.
- Twenty days from notification to final payment.
- Twenty-three days from notification to closure.
The customer may be most concerned with payment, while an operations team also needs to understand the work remaining before closure. Reporting both measures makes that distinction visible.
Average, median, and longer-running claims
An average combines the total duration of the included claims and divides it by their number:
Average cycle time = sum of individual cycle times ÷ number of included claims
For five fictional claims closed after 5, 7, 8, 10, and 70 days, the average is 20 days. The median, or middle value, is eight days.
Both figures are correct. The average reflects the substantial effect of the 70-day claim, while the median shows that half the claims closed within eight days. Percentiles can provide additional detail. For example, the 90th percentile describes a duration within which approximately 90% of the measured claims fall, using the report’s chosen calculation method.
A useful report also shows claim counts. An apparent improvement based on five claims should not be read in the same way as a stable pattern across several thousand comparable claims.
What happens to claims that are still open?
A completed cycle time cannot yet be calculated for an open claim. Its current age can be measured, but that age is not its final duration.
This creates a potential distortion. Suppose ten claims open together and six straightforward cases close quickly. The average for those six can look excellent even though four difficult claims remain unresolved.
Guidewire’s descriptive metrics identify missing long-running claims as a potential source of incomplete comparisons. Guidewire’s explanation of claim populations and descriptive metrics.
Two views help explain the workload:
- Claims closed during a period: shows the duration of work completed, including older claims closed in that period.
- Claims reported during a period: follows a group from arrival, showing how many have closed and how old the remaining claims are.
For the second view, the closure percentage and open-claim ages should accompany the cycle time of completed claims. Recent groups have had less time to develop than older groups.
Reopened claims and multiple coverages
A claim can close and later reopen because new information or further work emerges. Reports need a consistent rule for this situation. They might preserve the initial closure measure and track reopening separately, or calculate a revised duration through the latest closure.
The chosen rule should be visible. Otherwise, a quick closure followed by repeated reopening could appear more efficient than a claim kept open until the remaining work was completed.
A single claim may also contain several coverages or exposures that progress at different speeds. Property damage might be resolved while an associated injury claim remains open. Measuring the whole claim and measuring one exposure answer different questions.
Comparing claims cycle time across insurance lines
There is no single useful target for every type of claim. A straightforward glass replacement and a disputed liability claim require different evidence and handling steps.
Comparisons become more meaningful when they account for coverage, severity, litigation, catastrophe involvement, and whether the claims received payments. The reporting period and the start and end definitions also need to match.
Even benchmark averaging methods can differ. Guidewire describes a company-level averaging approach for its comparisons, which serves a different purpose from combining every claim into one industry-wide average. Guidewire’s explanation of its benchmarking methodology.
What a long cycle time can reveal
Breaking the process into stages can show where claims wait: before assignment, while documents are requested, between inspection and assessment, or after payment approval.
Elapsed time also differs from active handling time. A file may take three weeks to close while receiving only a few hours of direct work. That gap can identify a queue or dependency, although some waiting is necessary to establish the claim correctly.
Changes should be judged alongside payment accuracy, complaints, reopening, and the outcome for the claimant. A shorter duration is useful when it reflects timely, complete handling. Closing a record before the work is finished only changes the reported number.
