The loss development method, also known as the chain ladder method, is the most widely used approach for estimating healthcare IBNR reserves. It works by observing how past claims developed over time and projecting that pattern onto more recent periods.
This page covers the technical steps of the loss development method in detail.
Here’s the process at a high level:
Step 1. Build a Lag Triangle
Organize paid claims into a matrix of incurred months and paid months.
Step 2. Compute the Cumulative Triangle
Sum across each incurred month to create running totals, showing how much has been paid through each lag period.
Step 3. Compute Development Factors
Calculate the ratio between consecutive cumulative columns to measure how claims grow from one period to the next.
Step 4. Select an Average Method
Choose how to average those development factors to smooth out noise.
Step 5. Calculate Age-to-Ultimate Factors
Multiply the selected averages together to project each lag all the way to ultimate.
Step 6. Calculate Completion Factors
Invert the age-to-ultimate factors to express how “complete” each lag period is as a percentage.
Step 7. Determine IBNR Reserves
Divide total paid claims by the completion factor to estimate ultimate cost, then subtract what’s already been paid.
Step 1: The Lag Triangle#
Two dates are central to reserving: the incurred date (i.e. service date) and the paid date. The incurred date is when the medical service was provided to the member. The paid date is when the insurer paid the corresponding claim. For example, a surgery performed in January may not result in a payment until May.
This time difference between the incurred date and the paid date is what creates the need for IBNR reserves.
The difference, typically measured in months, between the incurred date and the paid date is called the lag. Conventionally, the lag can start at either 0 or 1. When using IBNR.net, the lag starts at 0, as we feel that this definition more intuitively aligns with the definition of months between the paid date and incurred date. In some other models, the lag can start at 1 when the incurred date is equal to the paid date.
A lag triangle is the foundation of the loss development method. It arranges claims data into a grid where one axis represents the incurred date and the other axis represents the paid date. A lag triangle does not need to be a square matrix. If there are more paid dates than incurred dates, the difference between the most recent paid date and the most recent incurred date is called the run-out. For example, if incurred dates range from January 1st, 2025 to December 31st, 2025, and paid dates range from January 1st, 2025 to March 31st, 2026, the run-out is 3 months.
For standardization purposes, on IBNR.net, the data is stored such that:
- Rows represent when the claim was incurred.
- Columns represent when the claim was paid.
Triangles can also be represented with the paid date on the rows and the incurred date on the columns. Triangles uploaded in this format will automatically be inverted as part of the standardization process.
Let’s take a look at an example of a lag triangle.
| Incurred | 1/1/2025 | 2/1/2025 | 3/1/2025 | 4/1/2025 | 5/1/2025 | 6/1/2025 | 7/1/2025 | 8/1/2025 | 9/1/2025 | 10/1/2025 | 11/1/2025 | 12/1/2025 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1/1/2025 | 2,140 | 1,552 | 589 | 375 | 75 | 43 | 21 | 21 | 11 | 21 | 5 | 2 |
| 2/1/2025 | 0 | 3,424 | 963 | 963 | 482 | 64 | 54 | 21 | 11 | 21 | 21 | 3 |
| 3/1/2025 | 0 | 0 | 3,531 | 1,017 | 1,017 | 428 | 86 | 32 | 21 | 32 | 11 | 11 |
| 4/1/2025 | 0 | 0 | 0 | 3,317 | 696 | 963 | 482 | 43 | 32 | 32 | 11 | 11 |
| 5/1/2025 | 0 | 0 | 0 | 0 | 2,782 | 1,177 | 910 | 428 | 43 | 43 | 32 | 11 |
| 6/1/2025 | 0 | 0 | 0 | 0 | 0 | 3,210 | 963 | 856 | 428 | 64 | 43 | 21 |
| 7/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 2,461 | 1,231 | 963 | 482 | 64 | 43 |
| 8/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2,889 | 1,070 | 1,017 | 428 | 75 |
| 9/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3,638 | 856 | 910 | 482 |
| 10/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2,996 | 1,391 | 963 |
| 11/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2,461 | 1,070 |
| 12/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1,926 |
Notice how the grid is split along the diagonal, creating a triangle shape. Claims cannot be paid before they are incurred, so the values in the lower-left corner are all zeros.
Observing this particular triangle, we see that most claims are paid in the same month as they’re incurred (lag 0). Paid amounts slowly decrease in the following lags, until they eventually reach a negligible amount.
A triangle that approaches zero more quickly is described as “completing fast” or having a “short tail.” Conversely, a triangle that takes longer to approach zero is said to “complete slowly” or have a “long tail.” The tail length is important because it directly affects how much uncertainty exists in the IBNR estimate. Longer tails mean more unpaid claims remain outstanding at any given point, making the reserve estimate less certain.
In general, healthcare claims complete fast, typically over the course of months rather than years, so advanced statistical models designed for analyzing long-tailed exposures are rarely necessary.
Different service categories complete at different speeds. For example:
- Pharmacy claims tend to complete the fastest. Prescriptions are typically adjudicated electronically at the point of sale, so the lag between incurred and paid dates is very short, often within the same month.
- Outpatient claims (e.g. office visits, lab work, imaging) complete at a moderate pace. These claims require submission and processing but are generally straightforward, with most payments settling within one to three months.
- Inpatient claims (e.g. hospital stays, surgeries) tend to have the longest tails. These involve higher dollar amounts, more complex billing, and often require additional review or negotiation before payment is finalized. It is not uncommon for inpatient claims to take several months or longer to fully settle.
Because of these differences in completion speed, actuaries typically build separate triangles for each service category rather than combining all claims into a single triangle. Mixing fast-completing and slow-completing categories would obscure the underlying development patterns and reduce the accuracy of the resulting IBNR estimate.
Different populations may also complete at different speeds. For these reasons, actuaries often build separate triangles for distinct populations, such as by line of business, plan type, or region, to ensure that each triangle reflects a homogeneous development pattern. Combining populations with materially different completion speeds into a single triangle can distort the development factors and produce unreliable IBNR estimates.
Ultimately, the choice of triangle cuts is a judgment call based on the available data and the needs of the analysis. Fortunately, IBNR.net simplifies the process by allowing for the immediate generation of triangles by uploading a single column-wise dataset, with the first three columns representing the incurred date, paid date, and paid amount, and each column representing an additional triangle filter, such as service category, population, or other relevant criteria.
Step 2: The Cumulative Triangle#
The cumulative triangle converts the incremental lag data from Step 1 into running totals. Each cell equals the sum of all incremental values in that row up to and including that column, representing the total amount paid through each subsequent period.
| Incurred | 1/1/2025 | 2/1/2025 | 3/1/2025 | 4/1/2025 | 5/1/2025 | 6/1/2025 | 7/1/2025 | 8/1/2025 | 9/1/2025 | 10/1/2025 | 11/1/2025 | 12/1/2025 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1/1/2025 | 2140 | 3692 | 4281 | 4656 | 4731 | 4774 | 4795 | 4816 | 4827 | 4848 | 4853 | 4855 |
| 2/1/2025 | 0 | 3424 | 4387 | 5350 | 5832 | 5896 | 5950 | 5971 | 5982 | 6003 | 6024 | 6027 |
| 3/1/2025 | 0 | 0 | 3531 | 4548 | 5565 | 5993 | 6079 | 6111 | 6132 | 6164 | 6175 | 6186 |
| 4/1/2025 | 0 | 0 | 0 | 3317 | 4013 | 4976 | 5458 | 5501 | 5533 | 5565 | 5576 | 5587 |
| 5/1/2025 | 0 | 0 | 0 | 0 | 2782 | 3959 | 4869 | 5297 | 5340 | 5383 | 5415 | 5426 |
| 6/1/2025 | 0 | 0 | 0 | 0 | 0 | 3210 | 4173 | 5029 | 5457 | 5521 | 5564 | 5585 |
| 7/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 2461 | 3692 | 4655 | 5137 | 5201 | 5244 |
| 8/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2889 | 3959 | 4976 | 5404 | 5479 |
| 9/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3638 | 4494 | 5404 | 5886 |
| 10/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2996 | 4387 | 5350 |
| 11/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2461 | 3531 |
| 12/1/2025 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1926 |
Consider the January 2021 row. The first cell is 2,140, the amount paid in the same month claims were incurred. By the second column, the cumulative total reaches 2,140 + 1,552 = 3,692, reflecting all payments for January 2021 claims through February. By the final column, the total reaches 4,855, the full amount paid for that incurred month across the entire year.
The critical observation is that older rows (such as January) are nearly complete, with the vast majority of claims already paid. More recent rows (such as December) remain in the early stages of development. The cumulative triangle provides a clear view of each incurred month’s maturity, allowing for easier comparison and set-up for the next steps.
Step 3: Development Factors#
Development factors, also called age-to-age factors or link ratios, quantify the rate at which claims grow from one period to the next. Each factor is calculated by dividing a cumulative value by the immediately preceding cumulative value in the same row.
For example, in the January 2021 row:
- Lag 1 = 3,692 / 2,140 = 1.72523, meaning claims grew by approximately 72.5% between the first and second periods.
- Lag 2 = 4,281 / 3,692 = 1.15953, reflecting an additional 16.0% growth in the subsequent period.
As claims mature into later lags, the factors converge toward 1.0, reflecting the diminishing volume of remaining unpaid claims.
| Incurred | Lag 1 | Lag 2 | Lag 3 | Lag 4 | Lag 5 | Lag 6 | Lag 7 | Lag 8 | Lag 9 | Lag 10 | Lag 11 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1/1/2025 | 1.72523 | 1.15953 | 1.08760 | 1.01611 | 1.00909 | 1.00440 | 1.00438 | 1.00228 | 1.00435 | 1.00103 | 1.00041 |
| 2/1/21 | 1.28125 | 1.21951 | 1.09009 | 1.01097 | 1.00916 | 1.00353 | 1.00184 | 1.00351 | 1.00350 | 1.00050 | |
| 3/1/21 | 1.28802 | 1.22361 | 1.07691 | 1.01435 | 1.00526 | 1.00344 | 1.00522 | 1.00178 | 1.00178 | ||
| 4/1/21 | 1.20983 | 1.23997 | 1.09686 | 1.00788 | 1.00582 | 1.00578 | 1.00198 | 1.00197 | |||
| 5/1/21 | 1.42308 | 1.22986 | 1.08790 | 1.00812 | 1.00805 | 1.00594 | 1.00203 | ||||
| 6/1/21 | 1.30000 | 1.20513 | 1.08511 | 1.01173 | 1.00779 | 1.00377 | |||||
| 7/1/21 | 1.50020 | 1.26083 | 1.10354 | 1.01246 | 1.00827 | ||||||
| 8/1/21 | 1.37037 | 1.25688 | 1.08601 | 1.01388 | |||||||
| 9/1/21 | 1.23529 | 1.20249 | 1.08919 | ||||||||
| 10/1/21 | 1.46429 | 1.21951 | |||||||||
| 11/1/21 | 1.43478 |
Note the triangular shape. Each row has one fewer factor than the row above it, since two consecutive cumulative values are required to compute a ratio.
The development factors along each column (lag) are of primary interest. Lag 1 factors indicate how much claims typically grow between the first and second periods, Lag 2 factors capture growth between the second and third periods, and so on. The degree of consistency within each column reflects the stability and predictability of the underlying runoff pattern.
Note that Lag 0 is not included in the development factors, as there is no denominator for the Lag 0 calculation. This naming convention may also explain why some models define the lag as starting at 1 instead of 0, with the “1” representing the denominator of the ratio rather than the numerator.
Development factors can inform the user about the suitability of the loss development method for the data in question.
- If age-to-age ratios are highly variable for a given lag, that could indicate that the loss development method is not a suitable method for the population in question.
- If later lags don’t converge to 1, that can indicate that claims have not yet settled, and the historic data may not be suitable for the loss development method.
In either of these cases, other methods may need to be used, either in conjunction with the loss development method, or separately altogether.
Step 4: Selecting an Average Method#
Individual development factors can exhibit volatility; a single large claim or a processing delay can distort a given period’s ratio. To produce a more stable estimate, the factors within each lag column are averaged.
Several averaging approaches are available. A simple average assigns equal weight to every factor in the column. A medial average excludes the highest and lowest values before averaging, reducing the influence of outliers. The sample can also be restricted to a specified number of recent periods (e.g., last 6) to place greater emphasis on recent experience.
Below are three different averaging methods, each with a different sample size and different approach to handling outliers.
| Method | Lag 1 | Lag 2 | Lag 3 | Lag 4 | Lag 5 | Lag 6 | Lag 7 | Lag 8 | Lag 9 | Lag 10 | Lag 11 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Simple Average Last 6 | 1.3842 | 1.2291 | 1.0914 | 1.0114 | 1.0074 | 1.0045 | 1.0031 | 1.0024 | 1.0032 | 1.0008 | 1.0004 |
| Medial Average 4 of 6 | 1.3924 | 1.2278 | 1.0900 | 1.0115 | 1.0075 | 1.0044 | 1.0031 | 1.0024 | 1.0032 | 1.0008 | 1.0004 |
| Simple Average Last 3 | 1.3781 | 1.2263 | 1.0929 | 1.0127 | 1.0080 | 1.0052 | 1.0031 | 1.0024 | 1.0032 | 1.0008 | 1.0004 |
We observe that all three methods yield similar results, indicating that the data could be relatively stable and predictable. For this example, a Simple Average of the Last 6 periods is selected.
The choice of averaging method represents one of the most significant actuarial judgment decisions in the reserving process, especially when anomalies are present. Different methods can yield materially different IBNR estimates, and actuaries typically evaluate multiple approaches before applying professional judgment to select the most appropriate one.
Step 5: Age-to-Ultimate Factors#
Age-to-ultimate factors indicate the total expected growth from a given lag period to the point at which all claims are fully settled. They are calculated by multiplying the selected average factors from the current lag through the final lag.
For Lag 1, the age-to-ultimate factor is the product of all selected average factors:
1.3842 × 1.2291 × 1.0914 × 1.0114 × 1.0074 × 1.0045 × 1.0031 × 1.0024 × 1.0032 × 1.0008 × 1.0004 = 1.9192
For Lag 2, the age-to-ultimate factor is the product of the selected average factors from Lag 2 onward:
1.2291 × 1.0914 × 1.0114 × 1.0074 × 1.0045 × 1.0031 × 1.0024 × 1.0032 × 1.0008 × 1.0004 = 1.3865
This indicates that claims at Lag 1 are expected to grow by a factor of 1.92 before reaching their ultimate value. At Lag 11 (the most mature), the factor is 1.0004, indicating that those claims have essentially completed their development.
| Lag 1 | Lag 2 | Lag 3 | Lag 4 | Lag 5 | Lag 6 | Lag 7 | Lag 8 | Lag 9 | Lag 10 | Lag 11 | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Age-to-Ultimate Factors | 1.9192 | 1.3865 | 1.1281 | 1.0336 | 1.0219 | 1.0144 | 1.0099 | 1.0068 | 1.0044 | 1.0012 | 1.0004 |
Step 6: Completion Factors#
The completion factor is the reciprocal of the age-to-ultimate factor (1 / age-to-ultimate). It represents the proportion of ultimate claims that have been paid at each lag.
For Lag 1: 1 / 1.9192 = 0.5211, indicating that approximately 52.1% of claims have been paid after one period. For Lag 11: 1 / 1.0004 = 0.9996, indicating that claims are virtually fully developed.
| Lag 1 | Lag 2 | Lag 3 | Lag 4 | Lag 5 | Lag 6 | Lag 7 | Lag 8 | Lag 9 | Lag 10 | Lag 11 | |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Completion Factors | 0.5211 | 0.7212 | 0.8865 | 0.9675 | 0.9785 | 0.9858 | 0.9902 | 0.9933 | 0.9956 | 0.9988 | 0.9996 |
Completion factors provide an intuitive measure of maturity. A completion factor of 0.62, for instance, indicates that approximately 62% of the ultimate cost for that incurred period has been paid, with the remaining 38% outstanding as IBNR.
Step 7: Determining IBNR Reserves#
The final step brings all prior calculations together. For each incurred month, the total amount paid to date is divided by the completion factor to estimate the ultimate cost, and the paid amount is subtracted to derive the IBNR reserve.
The formula is:
Ultimate = Total Paid / Completion Factor
IBNR Reserve = Ultimate - Total Paid
| Incurred Date | Total Paid | Age (Lag) | Completion Factor | Ultimate | IBNR.net Reserve |
|---|---|---|---|---|---|
| 1/1/21 | 4,855 | 12 | 1.0000 | 4,855 | 0 |
| 2/1/21 | 6,027 | 11 | 0.9996 | 6,029 | 2 |
| 3/1/21 | 6,186 | 10 | 0.9988 | 6,193 | 7 |
| 4/1/21 | 5,587 | 9 | 0.9956 | 5,612 | 25 |
| 5/1/21 | 5,426 | 8 | 0.9933 | 5,463 | 37 |
| 6/1/21 | 5,585 | 7 | 0.9902 | 5,640 | 55 |
| 7/1/21 | 5,244 | 6 | 0.9858 | 5,320 | 76 |
| 8/1/21 | 5,479 | 5 | 0.9785 | 5,599 | 120 |
| 9/1/21 | 5,886 | 4 | 0.9675 | 6,084 | 198 |
| 10/1/21 | 5,350 | 3 | 0.8865 | 6,035 | 685 |
| 11/1/21 | 3,531 | 2 | 0.7212 | 4,896 | 1,365 |
| 12/1/21 | 1,926 | 1 | 0.5211 | 3,696 | 1,770 |
| TOTAL | 61,082 | 65,422 | 4,340 |
To illustrate, consider claims incurred in September 2021. A total of $5,886 has been paid through the valuation date. That month is at Lag 4, with a completion factor of 0.9675, indicating that approximately 96.8% of claims have been paid. Dividing $5,886 by 0.9675 yields an estimated ultimate of $6,084. The difference, $198, represents the IBNR reserve for that month.
Older incurred months carry small or zero IBNR, as the majority of claims have already been paid. More recent months carry larger IBNR reserves, as they remain in the earlier stages of development. December 2021 has the largest IBNR at $1,770, with only 52.1% of its expected claims paid after one month.
In aggregate, $61,082 has been paid, while the estimated ultimate cost is $65,422, resulting in a total IBNR reserve of $4,340. This amount must be recognized on the balance sheet to cover claims that remain in the payment pipeline.
Wrapping Up#
The loss development method derives its strength from a straightforward premise: observe how claims have developed historically, average those patterns, and project them onto more recent periods. However, the apparent simplicity of the framework should not be mistaken for a lack of complexity in its application. The actuarial judgment required at each stage (selecting the averaging method, determining the number of periods to include, and deciding whether to adjust for anomalies) is what distinguishes a mechanical calculation from a well-reasoned reserve estimate.
Although IBNR.net automates the mechanical calculations for you, it is still important for the user to understand the process and the assumptions behind the loss development method. Understanding the foundations of the reserving process will allow for more informed decisions.
This guide has covered the foundational concepts. In practice, actuaries typically incorporate additional considerations such as seasonality, trend calculations, credibility weighting, margin, and other refinements. Each of these techniques builds upon the framework presented here.
Disclaimer: This article is a work in progress and reflects the opinions of Jeff Yang, FSA at IBNR.net. It is intended for educational purposes only and should not be relied upon as the sole basis for professional decisions. Readers should exercise independent judgment when making actuarial or financial decisions. Please contact support@ibnr.net if you have feedback or identify any mistakes on this page.