View source for Friedland07.Development

'''Reading''': Friedland, J.F., Estimating Unpaid Claims Using Basic Techniques, Casualty Actuarial Society, Third Version, July 2010. The Appendices are excluded.

'''Chapter 7''': Development Technique''(or Chain Ladder Technique)''

==Pop Quiz==

If case reserve adequacy increases, will the paid-to-reported loss diagnostic triangle show increases or decreases when you look down the columns? <span style="background-color: lightblue; border-radius: 5px;"> ''[[Friedland07.Development#POP_QUIZ_ANSWERS |Click for Answer]]''&nbsp;</span>

==Study Tips==

[https://vimeo.com/1095256123 <span style="color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top:;">'''VIDEO: F-07 (001) Development Method &rarr; 4:00'''</span>] [https://www.battleactsmain.ca/battleacts5.ca/forum5/index.php?p=/categories/f-07-development<span style="font-size: 12px; background-color: lightgrey; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 0px;">'''Forum'''</span>]

This is a long chapter, almost 60 pages, but the <u>development method</u>, also called the <u>chain-ladder method</u>, is not hard. Once you practice it a few times, you'll get the hang of it. It might already be familiar to you anyway. The source text is organized like this:

: '''first 15 pages''': (page 84-98) <span style="color: green;">'''mechanics of the development method'''</span>
:* <span style="color: red;">''this is the <u>single most important</u> topic on the Exam 5 syllabus''</u>
:* source text explains the method in words but it's simpler just to look at examples ''(provided in this wiki article)''
: '''next 8 pages''': (page 98-105) <span style="color: green;">'''influences of a changing environment</span>
:* You need to understand how changes in the environment affect the accuracy of the development method ''(this is important)''
:* I have used my own policy & claims simulation software called ''SimPolicy'' to create illustrative examples
:* video explanations are provided for selected examples
: '''last 25 pages''': (page 106-130) <span style="color: green;">'''PDFs of Excel spreadsheet to illustrate the material</span>
:* these examples in the source text are very detailed ''(maybe a little <u>too</u> detailed)''
:* you can take a look at these if you'd like but make sure you look at my examples first

'''Note''': If you're reading this chapter as part of your first pass through the pricing material, you only need to know the first 15 pages on the mechanics of the method. If you're studying the reserving material, then you need to study the whole chapter.

'''Estimated study time''': 2-5 days depending on whether you're covering this material for pricing or reserving ''(not including subsequent review)''

==BattleTable==

Based on past exams, the '''main things''' you need to know ''(in rough order of importance)'' are:

* calculating ultimate / unpaid / IBNR using either the paid or reported development method
* considerations in combining or subdividing data for a reserve analysis

: {| class='wikitable' style='width: 1000px;'

|-
! style='width: 175px;' | reference !! style='width: 175px;' | part (a) !! style='width: 175px;' | part (b) !! style='width: 175px;' | part (c) !! part (d)

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2019_1-Spring)/(2019_1-Spring)_(13).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2019.Spring #13)'''</span>
|| '''combining data''': <br> - argue for
|| '''combining data''': <br> - argue against
|| '''rate recommendation''': <br> - provide comment
| style="background-color: lightgrey;" | 

|- style="border-bottom: 2px solid;" 
|| [https://www.battleacts5.ca/pdf/Exam_(2019_1-Spring)/(2019_1-Spring)_(16).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style="color: red;">'''(2019.Spring #16)'''</span>
|| '''ultimate claims''': <br> - rptd devlpt
|| '''industry data''': <br> - considerations
|| '''impact''': <br> - of operational change
| style="background-color: lightgrey;" |

|- style="border-bottom: 2px solid;" 
|| [https://www.battleacts5.ca/pdf/Exam_(2018_1-Spring)/(2018_1-Spring)_(20).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2018.Spring #20)'''</span>
|| [[Excel Practice Problems]]
|| 
||
||

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2017_2-Fall)/(2017_2-Fall)_(17).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2017.Fall #17)'''</span>
|| '''reserving data''': <br> - advantages of subdividing
|| '''reserving data''': <br> - disads. of subdividing
| style="background-color: lightgrey;" |
| style="background-color: lightgrey;" |

|- 
|| [https://www.battleacts5.ca/pdf/Exam_(2017_2-Fall)/(2017_2-Fall)_(19).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2017.Fall #19)'''</span>
|| '''ultimate claims''': <br> - rptd devlpt
|| '''diagnostic''': <br> - operational changes
|| '''accuracy issues''': <br> - unpaid claim data
| style="background-color: lightgrey;" |

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2017_1-Spring)/(2017_1-Spring)_(14).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2017.Spring #14)'''</span>
|| '''IBNYR''' <br> - AY & RY rptd development
| style="background-color: lightgrey;" | 
| style="background-color: lightgrey;" | 
| style="background-color: lightgrey;" | 

|- style="border-bottom: 2px solid;" 
|| [https://www.battleacts5.ca/pdf/Exam_(2017_1-Spring)/(2017_1-Spring)_(20).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2017.Spring #20)'''</span>
|| '''CY paid claim amounts''': <br> - uses development method
| style="background-color: lightgrey;" |
| style="background-color: lightgrey;" |
| style="background-color: lightgrey;" |

|-  
|| [https://www.battleacts5.ca/pdf/Exam_(2016_2-Fall)/(2016_2-Fall)_(25).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2016.Fall #25)'''</span>
|| '''ultimate claims''': <br> - rptd development
|| '''claims & ALAE''': <br> - combining data
|| '''ultimate ALAE''': <br> - development method
| style="background-color: lightgrey;" |

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2016_1-Spring)/(2016_1-Spring)_(14).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2016.Spring #14)'''</span>
|| '''ultimate claims''': <br> - paid development
|| '''ultimate claims''': <br> - using industry data
|| '''ultimate claims''': <br> - final estimate
| style="background-color: lightgrey;" |

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2016_1-Spring)/(2016_1-Spring)_(15).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2016.Spring #15)'''</span>
|| [[Friedland05.Triangles]]
|| [[Friedland03.Data]]
|| [[Friedland03.Data]]
|| '''combining data''': <br> - appropriate?

|- style="border-bottom: 2px solid;" 
|| [https://www.battleacts5.ca/pdf/Exam_(2016_1-Spring)/(2016_1-Spring)_(16).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2016.Spring #16)'''</span>
|| [[Friedland08.ExpectedClms]]
|| '''ultimate''': <br> - paid devlpt
|| [[Friedland09.BornFerg]]
| style="background-color: lightgrey;" |

|- 
|| [https://www.battleacts5.ca/pdf/Exam_(2015_2-Fall)/(2015_2-Fall)_(14).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2015.Fall #14)'''</span>
|| '''combining data''': <br> - argue for & against
|| '''combining data''': <br> - change in severity
| style="background-color: lightgrey;" | 
| style="background-color: lightgrey;" | 

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2014_1-Spring)/(2014_1-Spring)_(12).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2014.Spring #12)'''</span>
|| '''combining data''': <br> - volume & growth
| style="background-color: lightgrey;" | 
| style="background-color: lightgrey;" | 
| style="background-color: lightgrey;" | 

|- 
|| [https://www.battleacts5.ca/pdf/Exam_(2014_1-Spring)/(2014_1-Spring)_(13).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2014.Spring #13)'''</span>
|| '''ultimate claims''': <br> - rptd development
|| '''assumptions''': <br> - rptd development method
|| '''alternative''': <span style="color: red;"><sup>'''1'''</sup></span> <br> - if assumptions violated
| style="background-color: lightgrey;" |

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2013_1-Spring)/(2013_1-Spring)_(16).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2013.Spring #16)'''</span>
|| '''ultimate claims''': <br> - development method
|| '''accident half-years''': <br> - advantage over full years
| style="background-color: lightgrey;" |
| style="background-color: lightgrey;" |

|-
|| [https://www.battleacts5.ca/pdf/Exam_(2013_1-Spring)/(2013_1-Spring)_(20).pdf <span style='font-size: 12px; background-color: yellow; border: solid; border-width: 1px; border-radius: 5px; padding: 2px 5px 2px 5px; margin: 5px;'>E</span>] <span style='color: red;'>'''(2013.Spring #20)'''</span>
|| '''ultimate claims''': <br> - development method
| style="background-color: lightgrey;" |
| style="background-color: lightgrey;" |
| style="background-color: lightgrey;" |

|}

: <span style="color: red;"><sup>'''1'''</sup></span> To answer part (c) you need knowledge of reserving techniques from later material.

[https://www.battleacts5.ca/FC.php?selectString=**&filter=both&sortOrder=natural&colorFlag=allFlag&colorStatus=allStatus&priority=importance-high&subsetFlag=miniQuiz&prefix=Friedland07&suffix=Development&section=all&subSection=all&examRep=all&examYear=all&examTerm=all&quizNum=all<span style="font-size: 20px; background-color: lightgreen; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 10px;">'''Full BattleQuiz]'''</span> <span style="color: red;">'''You must be <u>logged in</u> or this will not work.'''</span>

==In Plain English!==

===Intro to Development Method===

Before getting to the first example ''Alice-the-Actuary'' wanted me to mention the different terms for a very important concept regarding the development method. These terms all mean the <u>same thing</u>:

* age-to-age factor
* development factor
* Loss Development Factor
* Claim Development Factor
* link ratio

Friedland uses both ''age-to-age factor'' and ''Loss Development Factor''. But the latter has a very nice abbreviation: '''LDF'''.

Here is a closely related concept that also has more than one label:

* age-to-ultimate factor
* Cumulative Development Factor

The nice thing about Cumulative Development Factor is that it has the simple abbreviation '''CDF'''. Be careful if you read the source text however. They sometimes also refer to a "Claim Development Factor" which is the same thing as "Loss Development Factor" and is <u>not</u> abbreviated by CDF.

{| class='wikitable' style='background-color: navajowhite;'
|-
|| The version of the development method discussed below is '''multiplicative'''. There is also an '''additive''' version that's discussed ''[[Friedland16.ALAE#Calculating_Ultimate_ALAE | here in Reserving - Chapter 16 - ALAE]]''.
|}

===Development Method - A Simple Example===

''You will never have a problem this simple on the exam or in real life. It's purely to teach you the mechanics of the method. Enjoy it while you can. :-)''

{| class='wikitable'
|-
|| '''Example''': calculate the <u>ultimate loss</u> for each AY using the given data
|}

'''Cumulative paid loss triangle:'''

:{| class='wikitable' 
|-
! AY !! 12 !! 24 !! 36 !! 48
|- 
! scope='row' |  2020	
|48	||140	||201	|| style='color: brown;' |'''240'''
|-
! scope='row' | 2021	
|48	||140	|| style='color: brown;' |'''201'''
|-
! scope='row' | 2022	
|48	|| style='color: brown;' |'''140'''
|-
! scope='row' | 2023	
| style='color: brown;' | '''48'''
|}

'''Method:''' paid loss development
: &rarr; Use historical patterns to predict future losses.
: &rarr; The text breaks this method into 7 steps but Alice likes to condense it into just 4 steps as follows:

'''Step A''': <u>calculate</u> age-to-age factors or LDFs

* This is incredibly simple:
** The 1<sup>st</sup> age-to-age factor ''(or LDF)'' for AY 2020 = 140/48 = <u>2.92</u>. ''(You just divide the 24-month value by the 12-month value.)''
** The 2<sup>nd</sup> age-to-age factor for AY 2020 = 201/140 = <u>1.43</u> ''(Divide the 36-month value by the 24-month value.)''
** The 3<sup>rd</sup> age-to-age factor for AY 2020 = 240/201 = <u>1.19</u> ''(Divide the 48-month value by the 36-month value.)''

:{| class='wikitable' style='text-align: center;'
|-
! AY !! 12-24 !! 24-36 !! 36-48 
|-
! scope='row' |  2020	
|2.92	||1.44	||1.19
|-
! scope='row' | 2021	
|2.92	||1.44
|-
! scope='row' | 2022	
|2.92
|}

* Now do the same thing for AY 2021 and AY 2022. For this very simple example the age-to-age factors are the same for each AY. We'll build to more complicated examples once we've covered the basic method. ''(There is no row for AY 2023 in the LDF triangle because AY 2023 has only 1 data point at age = 12. You would have to wait another year to get the next data point at age = 24 to be able to calculate the 12-24 LDF for AY 2023.)''
* Note how the <u>column labels changed</u>. Instead of ''12'' for the first column, we now use ''12-24''. That's because the value of 2.92 represents how the value at 12 months ($48) <u>develops</u> to get the value at 24 months ($140).

'''Step B''': <u>select</u> an age-to-age factor (or LDF) for each column

* This is potentially the most complex step because it requires actuarial judgment. The idea is to scan the column from top to bottom and <u>select</u> a representative value that according to Friedland:
::{| class='wikitable'
|-
|| ...represents the growth anticipated in the subsequent development interval
|}

* It's like an IQ-test. ''(Pick the next number in the pattern.)'' And actuaries tend to be very sensitive about selecting LDFs ''(age-to-age factors)''. But for certain high-volume, short-tail lines of business like auto insurance ''(fewer than 5 years can be considered short-tail)'' the computer can make pretty good selections for most development periods. That means the actuary can spend more time on the parts of the analysis that really do require human insight. Click for a ''[[Funny Story About Selecting LDFs]]''.

* Anyway, selecting the LDFs is very simple for this example because every value in each column is the same. ''(Remember, we will build to more complex examples once you understand the basic method.)'' Our selected LDFs are as follows: ''(Even Ian-the-Intern could have figured this out!)''

::{| class='wikitable' style='text-align: center;'
|-
!  !! 12-24 !! 24-36 !! 36-48 !! 48-ultimate<span style='color: red;'>'''<sup>*</sup>'''</span>
|-
! scope='row' | selected
| 2.92 || 1.44 || 1.19 || <span style='color: red;'>'''1.00'''</span> &nbsp; ''(tail factor)''
|}

:: <span style='color: red;'>'''<sup>*</sup>'''</span> Note the additional column for the tail factor LDF. We'll return to this later but for now just assume there is no development on claims past 48 months, or equivalently that all claims are settled and closed by 48 months. This would mean that every development period past 48 months ''(60, 72,...)'' would have paid loss equal to the 48-month value of 240. If you were then to calculate the LDFs for ''48-60, 60-72,...etc,'' they would all equal 1.00.

'''Step C''': <u>calculate</u> age-to-ultimate LDFs

* This step does not require judgment. It is just arithmetic.
* In Step B, we calculated ''age-to-age'' development factors. Now we multiply them together to get ''age-to-ultimate'' development factors, also called ''Cumulative Development Factors'' or ''CDFs''. Here's the result. ''(Explanation below.)''

::{| class='wikitable' style='text-align: center;'
|-
!  !! 12-ult !! 24-ult !! 36-ult !! 48-ultimate
|-
! scope='row' | selected
| 5.00 || 1.71 || 1.19 || <span style='color: red;'>'''1.00'''</span> &nbsp; ''(tail factor)''
|}

* To get these values, you have to work backwards, from right to left:
:: '''48-ult''': No calculation required in this example. Just copy the <span style='color: red;'>'''1.00'''</span> tail factor from Step B.
:: '''36-ult''': (selected age-to-age LDF) x (prior [age-ult])
::: = 1.19 x 1.00
::: = 1.19
:: '''24-ult''': (selected age-to-age LDF) x (prior [age-ult])
::: = 1.44 x 1.19
::: = 1.71
:: '''12-ult''': (selected age-to-age LDF) x (prior [age-ult])
::: = 2.92 x 1.71
::: = 5.00

* When you reproduce these calculations, you may see minor differences due to rounding because I'm only showing 2 decimal places. I didn't want to clutter the presentation with a bunch of extra decimals.

'''Step D''': <u>calculate</u> ultimate losses based on the latest diagonal of paid losses ''(the latest diagonal comprises the values in <span style='color: brown;'>'''brown font'''</span> from the original triangle)''

* Here's the result. I've reproduced the latest diagonal from the original paid loss triangle just for convenience but you don't technically have to do that.

::{| class='wikitable' style='text-align: center;'
|-
!  !! AY 2023 !! AY 2022 !! AY 2021 !! AY 2020
|-
! scope='row' | <span style='color: brown;'>diagonal</span>
| <span style='color: brown;'>48</span> || <span style='color: brown;'>140</span> || <span style='color: brown;'>201</span> || <span style='color: brown;'>240</span>
|-
! scope='row' | ultimate
| 240 || 240 || 240 || 240
|}

:: '''AY 2020''': <span style='color: brown;'>'''diagonal'''</span> x (age-ult)
::: = <span style='color: brown;'>240</span> x <span style='color: red;'>'''1.00'''</span>
::: = 240
:: '''AY 2021''': <span style='color: brown;'>'''diagonal'''</span> x (age-ult)
::: = <span style='color: brown;'>201</span> x 1.19
::: = 240
:: '''AY 2022''': <span style='color: brown;'>'''diagonal'''</span> x (age-ult)
::: = <span style='color: brown;'>140</span> x 1.71
::: = 240
:: '''AY 2023''': <span style='color: brown;'>'''diagonal'''</span> x (age-ult)
::: = <span style='color: brown;'>48</span> x 5.0
::: = 240

* Again, please ignore the minor rounding differences. Take a quick look at the following link, which lays out the solution to the above problem concisely. There are also a few extra comments included within the solution that might be worth looking at.

: [https://www.battleacts5.ca/pdf/Friedland.Ch07_(Demo_07.01)_Development.pdf <span style="color: black; font-size: 12px; background-color: yellow; border: solid; border-width: 2px; border-radius: 10px; border-color: yellow; padding: 1px 3px 1px 3px; margin: 0px;">'''''Demo F-07 (002): Development Method - Simple Example'''''</span>]

{| class='wikitable' style='background-color: navajowhite;'
|-
|| The version of the development method discussed above is '''multiplicative'''. There is also an '''additive''' version that's discussed ''[[Friedland16.ALAE#Calculating_Ultimate_ALAE | here in Reserving - Chapter 16 - ALAE]]''.
|}

===Development Method - The Key Assumption===

Notice that '''Steps A, C, D ''' in the development method were formula-based calculations: No actuarial judgment required. But '''Step B''' was different. The actuary had to <u>select</u> LDFs for each column that "fit the pattern" from previous years. And your final estimates of AY ultimates could vary greatly depending on what you selected. In the simple example from above, even ''Ian-the-Intern'' could select good LDFs. That's because the development pattern was consistent from year to year. In other words, the way losses ''(or claims)'' <u>developed</u> from one period to the next <u>was the same for every row or AY</u>.  Mathematically, that means the calculated age-to-age development factors were the same within each column.

:{| class='wikitable'
|-
|| '''Key Assumption:''' The development method assumes future loss development is <u>similar</u> to development in prior years
|}

* Mathematically, this means the LDFs within each column are roughly the same.
* Sometimes this is a matter of judgment and sometimes you can use ''[[Friedland06.Diagnostics | diagnostics]]'' to assist in determining whether this stability/consistency assumption holds.

{| class="wikitable"
|-
| style="background-color: darkslategrey; color: white; border: solid; border-width: 2px; border-radius: 10px;" | '''Pop Quiz A! &nbsp;&nbsp; :-o'''
|}

* Identify which of these triangles satisfy the key assumption of the development method. <span style="background-color: lightblue; border-radius: 5px;"> ''[[Friedland07.Development#Pop_Quiz_A_-_Answer |Click for Answer]]''&nbsp;</span>
: ''(You have to ask yourself whether the development from year to year is similar <u>enough</u>. It's never going to be exact.)''

{| class='wikitable' style="float: left; margin-left: 25px; text-align: right;"
|-
! <span style="background-color: coral; padding: 5px; border-radius: 5px;"> Triangle 1 !! 12 !! 24 !! 36 !! 48 !! &nbsp;&nbsp;&nbsp;
|- 
! scope='row' |  2020	
|48.1	||141.2	||200.7	|| style='color: brown;' |'''240.0'''
|-
! scope='row' | 2021	
|47.4	||140.5	|| style='color: brown;' |'''201.0'''
|-
! scope='row' | 2022	
|48.2	|| style='color: brown;' |'''139.6'''
|-
! scope='row' | 2023	
| style='color: brown;' | '''48.0'''
|}

{| class='wikitable' style="float: left;"
|-
! <span style="background-color: coral; padding: 5px; border-radius: 5px;"> Triangle 2 !! 12 !! 24 !! 36 !! 48 !! &nbsp;&nbsp;&nbsp;
|- 
! scope='row' |  2020	
|48.0	||140.4	||200.7	|| style='color: brown;' |'''240.0'''
|-
! scope='row' | 2021	
|43.6	||136.0	|| style='color: brown;' |'''198.6'''
|-
! scope='row' | 2022	
|40.0	|| style='color: brown;' |'''132.1'''
|-
! scope='row' | 2023	
| style='color: brown;' | '''39.6'''
|}

{| class='wikitable' style="float: left; float: clear;"
|-
! <span style="background-color: coral; padding: 5px; border-radius: 5px;"> Triangle 3 !! 12 !! 24 !! 36 !! 48
|- 
! scope='row' |  2020	
|42.4	||145.7	||202.3	|| style='color: brown;' |'''240.0'''
|-
! scope='row' | 2021	
|56.1	||144.0	|| style='color: brown;' |'''205.3'''
|-
! scope='row' | 2022	
|52.1	|| style='color: brown;' |'''137.2'''
|-
! scope='row' | 2023	
| style='color: brown;' | '''42.2'''
|}


<br>
<br>
<br>
<br>
<br>
<br>
<br>

{| class='wikitable' style="float: left; margin-left: 25px; text-align: right;"
|-
! <span style="background-color: coral; padding: 5px; border-radius: 5px;"> Triangle 4 !! 12 !! 24 !! 36 !! 48 !! &nbsp;&nbsp;&nbsp;
|- 
! scope='row' |  2020	
|46.8	||144.3	||196.9	|| style='color: brown;' |'''240.0'''
|-
! scope='row' | 2021	
|53.3	||145.4	|| style='color: brown;' |'''203.1'''
|-
! scope='row' | 2022	
|60.0	|| style='color: brown;' |'''151.2'''
|-
! scope='row' | 2023	
| style='color: brown;' | '''68.6'''
|}

{| class='wikitable' style="float: left; float: clear;"
|-
! <span style="background-color: coral; padding: 5px; border-radius: 5px;"> Triangle 5 !! 12 !! 24 !! 36 !! 48
|- 
! scope='row' |  2020	
|48.0	||140.0	||201.0	|| style='color: brown;' |'''240.0'''
|-
! scope='row' | 2021	
|52.0	||152.0	|| style='color: brown;' |'''217.0'''
|-
! scope='row' | 2022	
|56.0	|| style='color: brown;' |'''164.0'''
|-
! scope='row' | 2023	
| style='color: brown;' | '''60.0'''
|}

<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
* After you've looked at the quick answer under ''Pop Quiz Answers'', see if you can apply the development method to each of these triangles. Even if the key assumption doesn't hold, go ahead and do the calculations. Since these triangles were all created using my simulation software ''SimPolicy'' you can check your estimate of ultimate losses against the "real" ultimate losses. Use the link below to see the full solutions.
* There are also extra comments within the solutions that will help prepare you for upcoming material. The development method is a good basic method but it does have shortcomings. Some of those can be addressed by being a little more sophisticated in how it's applied, but others must be addressed by different methods entirely. Friedland covers several of those other reserving methods in subsequent chapters.

: [https://www.battleacts5.ca/pdf/Friedland.Ch07_(Demo_07.02)_Development_v03.pdf <span style="color: black; font-size: 12px; background-color: yellow; border: solid; border-width: 2px; border-radius: 10px; border-color: yellow; padding: 1px 3px 1px 3px; margin: 0px;">'''''Demo F-07 (004): Development Method - Full Solutions to Pop Quiz A'''''</span>]

Okay, that was a long pop quiz so I won't torture you too much more in this section. One last thing though: the source text mentions a '''second main assumption''' of the development method as follows:

* claims observed for an <u>immature period</u> provide information about claims yet to be observed

This is just another way of saying that history repeats itself, except there's specific reference to ''immature periods''. A set of claims at 12-months development would be considered immature ''(for many lines of business)'' but those claims become progressively more mature at each successive period. In general, estimates of ultimates based on immature claims will be less accurate than estimates based on mature claims. And you don't know for certain the ultimate value of a claim until it has been closed. ''(Even then it could be reopened, but that doesn't happen very often.)''

Friedland lists other ''"assumptions''" but they are all more or less implied by the ''Key Assumption''. Rather than ''"assumptions"'', I would describe these as situations where the ''Key Assumption'' is satisfied and where the development method is likely to work well.

:{| class='wikitable'
|-
|| '''Question:''' identify situations where the development method is likely to work well
|}

:* consistent claim processing
:* stable mix of types of claims
:* stable policy limits
:* stable reinsurance & retention limits
:* high frequency & low severity lines of business

You should give a little thought as to why these situations satisfy the ''Key Assumption'' although this might be easier once you've worked through more examples and understand better the mechanics of the method. It always comes back to the idea of <u>stability</u> & <u>consistency</u>. The reason the development method works well high frequency & low severity lines of business is that:

* high frequency means there will be more claims and therefore more credibility in the data ''(reduces noise in the triangle)''
* low severity reduces chance of large losses creating outlier data points in development triangle that could distort the development pattern

Consistent claims processing means ''(among other things)'' that claims are settled at roughly the same rate from one year to the next, and that the level of case reserves is consistent for similar types of claims. If either of those don't hold, the the development method could produce distorted results. The ''[[Friedland13.BerqSherm | Berquist-Sherman method]]'', discussed in a later chapter, is specifically designed to correct for this.

[https://www.battleacts5.ca/FC.php?selectString=**&filter=both&sortOrder=natural&colorFlag=allFlag&colorStatus=allStatus&priority=importance-high&subsetFlag=miniQuiz&prefix=Friedland07&suffix=Development&section=all&subSection=all&examRep=all&examYear=all&examTerm=all&quizNum=1<span style="font-size: 20px; background-color: aqua; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 10px;">'''mini BattleQuiz 1]'''</span> <span style="color: red;">'''You must be <u>logged in</u> or this will not work.'''</span>

===Development Method - LDF Selections===

The examples we've look at so far only had 4 AYs and 4 development periods. That made '''Step B''', where you had to select LDFs, pretty simple because you could just eyeball it. There are essentially only 3 possibilities in such a small triangle:

* if the LDFs in a column appear stable, your selected LDF could be be the average
* If there is a trend in a column, your selected LDF could reflect that trend
* if the LDFs <u>do not</u> appear stable and there is <u>no</u> trend, then the development method may not work ''(but you might just go ahead and select the average anyway then hope for the best!)''

We're going to look at a loss triangle with 12 AYs and 12 development periods, but the application of the development method to this triangle has an extra "sub-step" as part of Step B.

:{| class='wikitable'
|-
|| '''Step B (sub-step)''': calculate <u>candidate</u> LDF selections then select your LDF from among these candidates
|}

:: These candidate LDF selections often include:
::* average of all values in column
::* average excluding high and low values ''(source text calls this the "medial average")''
::* weighted average ''(where the loss dollars are the weights)''
::* median
::* average of last n values ''(where n can be anything from 1 to the number of values in the column)''
::* geometric average ''(nth root of the product of n LDFs from the column, although this is not common)''

:: Of course in the end you don't have to select one of your candidates:
::* you can use your own '''judgment'''
::* or you may conclude the development method isn't appropriate and use a different method entirely

Anyway, here's a short video explaining the Excel file given below. The Excel file has a lot going on so it's a good idea to watch the video first. ''(There will be a quiz so pay attention!)''

: [https://vimeo.com/1095256169 <span style="color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 100px;">'''VIDEO: F-07 (010) Candidate LDFs &rarr; 6:30'''</span>]

And here is the Excel file from the video with ''candidate'' LDFs for you to play with.
* See how changing the selected LDFs changes the estimates of ultimate loss. The great thing about creating triangles with a simulation is that you know the true ultimate loss. Experimenting with LDF selections teaches you how to make good selections in real-life situations where you don't know the answer in advance.

: [https://www.battleacts5.ca/Excel/Excel_F-07_(010)_candidate_LDFs.xlsx <span style="color: white; font-size: 12px; background-color: indigo; border: solid; border-width: 2px; border-radius: 10px; border-color: indigo; padding: 1px 3px 1px 3px; margin: 0px;">'''''Excel Demo F-07 (010): Development Method - Candidate LDFs'''''</span>]

:{| class='wikitable'
|-
|| &rarr; ''[[F-07 (010) Candidate LDFs: Improved LDF Selections]]'' 
|}

Here's a quick-vid for a web-based problem that comes up in quiz #2 which is much further down in this article. It might be an idea however to watch the video then skip ahead to the quiz so you can practice selecting LDFs before doing the assignment below.

: [https://www.battleacts5.ca/video/Quick-Vid_F-07_(010)_SelectLDF_easy.webm <span style="color: white; font-size: 12px; background-color: darkorange; border: solid; border-width: 2px; border-radius: 10px; border-width: 3px; border-color: steelblue; padding: 5px 10px 5px 10px; margin-top: 100px;">'''Quick-Vid: F-07 (011) Selecting LDFs ~ 1:00'''</span>]

'''Assignment''': The Excel file below has 5 examples of paid loss triangles with either 4 AYs or 6 AYs. I'd suggest solving the small triangles with pencil, paper, and calculator. Once the method is firmly embedded in your brain, you can solve the larger triangles by typing the appropriate formulas into Excel.

: [https://www.battleacts5.ca/Excel/Excel_F-07_(011)_candidate_LDFs_Qs.xlsx <span style="color: white; font-size: 12px; background-color: indigo; border: solid; border-width: 2px; border-radius: 10px; border-color: indigo; padding: 1px 3px 1px 3px; margin: 0px;">'''''Excel Assignment F-07 (011): Development Method - Calculate Ultimates'''''</span>]

{| class='wikitable'
|-
|| '''Something to keep in mind:''' One of the reasons I like math is that there is virtually always one correct answer. No arguments. But actuarial work is more than just math and when applying reserving methods, there is no such thing as "the" single correct answer. On the exam, as long as your method is correct and you choose your LDFs in a semi-intelligent way, you should get full credit. ''(Be sure to provide a <u>brief explanation</u> for your selection, like if you noticed an outlier and decided to exclude it.)''
'''About the triangles in the assignment:''' Since these triangles were created by ''SimPolicy'', we do in fact know the real ultimate losses, unlike in the real world, but you'll see there's a limit to how accurate your estimates can be if you're only given the triangle of losses. It's partly due to normal random variation but also because there are just too many moving parts in such a complex system for the human brain to handle. I always find it humbling when I think I've made really good LDF selections, but my estimates turn out to be less accurate than if I had just chosen the ''all-period average.'' It a good reminder to myself that I'm not as smart as I think I am. Remember that next time you're in a meeting and people are arguing about their LDF selections or trends or whatever. Don't take yourself too seriously. :-)
|}

===Development Method - Tail Factors===

In all the examples so far, the tail factor for the development triangle had been 1.000. That meant at least 1 accident year was <u>complete</u>: all its claims were paid and settled so there would be no more development past that point. In the very simple example at the top of this article, the oldest AY had all its claims settled by 48 months and we assumed the other AYs would also be complete by 48 months.

In the earlier video and spreadsheet example, we assumed development was complete after 12 years or t=12. The next example uses the same data but the simulation stops at t=6. That means we <u>do not</u> have any complete AYs. And recall the 6-ultimate CDF was something like 1.07 ''(depending on how you selected your LDFs)'' so if we didn't include this tail factor, we would be under-estimating by roughly 7%.

:{| class='wikitable'
|-
|| '''Step B (sub-step)''': identify methods for estimating the <u>tail factor</u> in a development triangle
|}

:* industry benchmarks
:* curve-fitting using existing LDFs to extrapolate the tail factors
:* use ''reported-to-paid ratios'' at the latest observed paid development period
::* works only for paid development triangles
::* requires the reported development triangle have at least 1 complete AY
::: &rarr; Friedland states this method is beyond the scope of the text so it should not appear on the exam

One simple way of using curve-fitting is to use a ''"square-root"'' pattern. If your latest LDF is 1.10, you can extrapolate to the next period with an LDF of 1.10<sup>1/2</sup> = 1.048, and so taking square roots on until you get values very close or essentially equal to 1.000. Something more sophisticated would be to use all your selected LDFs to fit an exponential curve that decreases to 1.00. That seems like it would work better but in practice you often gain very little from that extra work. It's largely a crap-shoot. You can try it out for yourself though in the spreadsheet to see if you can get a better SSE. ''(Remember, this is simulated data so we know the answer in advance. That means you can try methods for coming up with a tail factor and see right away which is best.)''

Note that sometimes tail factors can be less than 1.00. This may happen in physical damage coverages where salvage reduces the insurer's losses after the claim is settled. But the square root trick still works because successive square-roots of a number between 0 and 1 results in a bigger number and approaches 1.00 in the limit. Take a look at the video then download the spreadsheet so you can play around with creating the tail factor.

: [https://vimeo.com/1095256246 <span style="color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 100px;">'''VIDEO: F-07 (020) Tail Factors &rarr; 3:00'''</span>]

And here is the Excel file from the video with tail factor selections you can play with.
* Try setting the tail factor equal to 1.00, which is the same as not having a tail factor because you're assuming no further development. Then try fitting an exponential curve and using the regression to see if you can improve on the ''square root'' method that I inserted.

: [https://www.battleacts5.ca/Excel/Excel_F-07_(020)_tail_factors_v03.xlsx <span style="color: white; font-size: 12px; background-color: indigo; border: solid; border-width: 2px; border-radius: 10px; border-color: indigo; padding: 1px 3px 1px 3px; margin: 0px;">'''''Excel Demo F-07 (020): Development Method - Tail Factors'''''</span>] 

Here is Alice's solution to an exam problem involving tail factors and 4 similar practice problems:

: [https://www.battleacts5.ca/pdf/Friedland.Ch07_(17F.19)_v02.pdf <span style="color: white; font-size: 12px; background-color: orchid; border: solid; border-width: 2px; border-radius: 10px; border-color: orchid; padding: 1px 3px 1px 3px; margin: 0px;">'''''Solution: 2017.Fall #19'''''</span>]

: [https://www.battleacts5.ca/pdf/Friedland.Ch07_(17F.19)_practice_01_04_v02.pdf <span style="color: white; font-size: 12px; background-color: green; border: solid; border-width: 2px; border-radius: 10px; border-color: green; padding: 1px 3px 1px 3px; margin: 0px;">'''''Practice: 4 problems like 2017.Fall #19'''''</span>]

===Development Method - A Few Comments===

All the above examples of the development method used ''paid loss data'', but the development method works whenever you can organize data into a triangle. Most commonly, the development method is applied to:

* ''paid losses''
* ''reported losses''
* ''paid counts''
* ''reported counts''

Sometimes it's applied to ''ALAE'' or ''Salvage & Subrogation'' triangles but the data in those triangles is often sparse and there are other more reliable methods. We cover those in ''[[Friedland14.Recoveries]]'' and ''[[Friedland16.ALAE]]''.

Did you also notice that all the development method examples we looked used ''Accident Years''. The method applies equally well however to any of the following:

* ''Accident Year''
* ''Policy Year''
* ''Underwriting Year''
* ''Report Year''
* ''Fiscal Year''

And then there's the level of aggregation. We used ''year'' but you can just as easily group by ''quarter'' or even ''month.'' Do you think the development method would still work? Well, yes. Yes it does! As long as the ''Key Assumption'' holds:

* future loss development is similar to development in prior years.

If you need a quick review, click ''[[Friedland07.Development#Development_Method_-_The_Key_Assumption | Development Method - Key Assumption]]''. Of course if you aggregate data by ''accident quarter'' and ''development quarter'' you'll have less data in each cell which reduces credibility, but theoretically it can be done.

{| class='wikitable'
|-
|| '''Side story''': When I first started working as an actuary, we had auto claim data by ''accident month'' and ''development month''. For the larger states it worked very well, plus we could update our estimates every month so that any inaccuracies in initial estimates improved very quickly. Smaller states were aggregated into groups. The software, called the ''Triangle System'', was 100% automated so the results were available in just a few days after month-end. The system also included some basic AI that flagged specific segments for human analysis. The idea was to let the computer do the grunt work so humans like ''Alice-the Actuary'' could focus on the higher-order thinking. ''(Our trends and expected loss ratios were input in advance based on both industry and company data.)''
|}

<span id="EE_(F-07-010)"></span>
[[File: 020-easter-bunny.png | 50px | link=Easter_Egg_(F-07-010)]] &larr; <span style="color: red;">'''CLOSED''':</span> 2 correct answers received as of Jan 15, 2022, <span style="color: red;">'''BUT'''</span> you can still try to solve it for practice!

===Development Method - Estimating Unpaid Amounts===

So far we looked at estimating <u>ultimate</u> losses or claims. The real goal however is to estimate the <u>unpaid</u> losses, but that's easy once you have the ultimates. This next example is similar to Exhibit 1 in the source text, but it's smaller, only 6 AYs instead of 10. It shows 3 things:

# estimating ultimate loss ''(or ultimate claims)'' using <u>both</u> paid loss triangles and reported loss triangles
#* ''(the method is exactly the same for each but you often get different results &ndash; more on this below)''
# calculating Case O/S ''(case outstanding)''
#* ''(this is the amount on the books the claims adjuster expects is needed to settle the open claims &rarr; but often there's IBNR on top on that)''
# estimating unpaid loss, both IBNR and total amounts
#* ''(recall that IBNR is an amount on top of the case outstanding the actuary thinks is needed to fully settle the open claims)''

Item 1 above is just the plain old development method but we apply it to both a paid loss triangle and a reported loss triangle. Item 2 is a simple formula based on the given data. For item 3 you need to know the ultimate loss but once you do, it' simple. Here's the video:

: [https://vimeo.com/1095256284 <span style="color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 100px;">'''VIDEO: F-07 (030) Paid & Reported Development &rarr; 5:30'''</span>]

Here's the corresponding Excel file:

: [https://www.battleacts5.ca/Excel/Excel_F-07_(030)_paid_and_rptd_dev_v02.xlsx <span style="color: white; font-size: 12px; background-color: indigo; border: solid; border-width: 2px; border-radius: 10px; border-color: indigo; padding: 1px 3px 1px 3px; margin: 0px;">'''''Excel Demo F-07 (030): Development Method - Paid & Reported Development'''''</span>] &nbsp;&nbsp; 

And the formulas used to create the summary table shown:

:{| class='wikitable'
|-
|| '''Case''' || &nbsp; = &nbsp; (reported loss) &ndash; (paid loss) &nbsp; &larr; ''at the same evaluation date'' 
|-
|| '''IBNR'''     || &nbsp; = &nbsp; (ultimate loss) &ndash; (reported loss) 
|-
|| '''Total unpaid loss''' || &nbsp; = &nbsp; (ultimate loss) &ndash; (paid loss)
|}

These formulas are valid for separate AYs but also in total. An obvious implication of these formulas is:

:{| class='wikitable'
|-
|| '''Total unpaid loss''' || &nbsp; = &nbsp; Case + IBNR
|}

Let's return to the comment I made under Item 1. You can estimate ultimate losses using either paid or reported data but you often get different answers.

:{| class='wikitable'
|-
|| '''paid vs reported development''': why might you get <u>different</u> answers
|}

:* Recall the formula for the ultimate loss for each AY from '''Step D''' in ''[[Friedland07.Development#Development_Method_-_A_Simple_Example | Development Method - A Simple Example]]'':
::: &rarr; ultimate &nbsp; = &nbsp; <span style='color: brown;'>'''diagonal'''</span> x CDF

:* '''Difference 1''': The diagonal entry, which is just the raw data, is going to be different in the paid loss triangle versus the reported loss triangle
::: ''(paid loss should be &le; reported loss)''

:* '''Difference 2''': paid losses develop differently ''(longer tail)'' than reported losses, which means the paid CDF will generally be different from the reported CDF
::: ''(paid CDFs are generally &ge; reported CDFs)''

We often refer to paid and reported development as 2 different methods, but that isn't strictly accurate. It's the same method applied to different sets of data. The distinction isn't terribly important however.

:{| class='wikitable'
|-
|| '''paid vs reported development''': why is it good to use <u>both</u> methods
|}

:* each method is a check on the other
:: ''(since these methods only provide estimates, not exact answers, they are subject to distortion)''

: The <u>final</u> estimate of ultimate is often a judgment-weighted-average of the paid & reported development estimates.

A very important topic in reserving is why different methods produce distorted results in specific situations. We'll begin discussing this later in this wiki article and also in subsequent chapters from Friedland. A simple example is that the paid development method tends to ''over-estimate'' the true ultimate loss if claim settlement rates increase. The increase is sometimes an effect of hiring more claims staff. ''Many, many different things can distort the accuracy of reserving methods and we gotta learn how to cope with all that!''

===Development Method - Summary & Observations===

Here's a summary of the various steps in the development method. This isn't something you have to memorize. Once you've practiced the calculations several times, you won't have any trouble with it. Remember that '''Step B''' is the only step where you have to use judgment. The other steps are just formulas.

:{| class='wikitable'
|-
|| '''Step A''': <u>calculate</u> age-to-age factors or LDFs
|-
|| '''Step B''': <u>select</u> an age-to-age factor (or LDF) for each column <br> '''Step B (sub-step)''': calculate <u>candidate</u> LDF selections then select your LDF from among these candidates <br> '''Step B (sub-step)''': identify methods for estimating the <u>tail factor</u> in a development triangle
|-
|| '''Step C''': <u>calculate</u> age-to-ultimate LDFs ''(also called CDFs or Cumulative Development Factors)''
|-
|| '''Step D''': <u>calculate</u> ultimate losses based on the latest diagonal of paid losses
|}

Something Friedland mentions in chapter 7 is the '''cumulative % paid''' and '''cumulative % reported'''. It's easy but we won't spend much time on it now because it isn't really needed until later chapters. It's a very simple formula. If you have the CDFs from the development method then at each age i:

:{| class='wikitable'
|-
|| '''cumulative % paid<sub>i</sub>     || &nbsp; = 1 / (paid CDF<sub>i</sub>)
|-
|| '''cumulative % reported<sub>i</sub> || &nbsp; = 1 / (reported CDF<sub>i</sub>)
|}

In my mind, I just think: &nbsp; <span style="color: green;">'''1/CDF'''</span>. &nbsp; Let's use the same paid loss data as in our original ''[[Friedland07.Development#Development_Method_-_A_Simple_Example |  Simple Example]]''. The CDFs we came up are as listed in the table below.

:{| class='wikitable' style='text-align: center'
|-
! age (i) !! paid CDF<sub>i</sub> !! cumulative % paid   !! incremental % paid
|-
|| 12 || 5.00    || 1/5.00 = 0.200 or '''20.0%''' || (current row) &ndash; (prior row) = 20.0%
|-
|| 24 || 1.71    || 1/1.71 = 0.585 or '''58.5%''' || 38.5%
|-
|| 36 || 1.19    || 1/1.19 = 0.840 or '''84.0%''' || 25.5%
|-
|| 48 || 1.00    || 1/1.00 = 1.000 or '''100%'''  || 16.0%
|}

As the CDF approaches 1.00, the cumulative percentage approaches 100%. The cumulative % paid is a nice intuitive way of thinking about the development pattern. To say your losses for a particular AY are 84% paid is probably more understandable than just quoting the CDF of 1.19. And of course it works the same way for a reported loss triangle or any other type of development triangle.

It's useful also to keep in mind the corresponding formula for the '''% unpaid''' at age i: &nbsp; <span style="color: green;">'''1 &ndash; 1/CDF<sub>i</sub>'''</span>. &nbsp; If you think about it for just a moment, you can see why the formulas make sense. Anyway, let's move on. ''(I'll remind you when you need this later on.)''

Friedland goes on to make a couple of observations about loss development. The first one is pretty obvious. The second is a reference to a paper by Pinto & Gogol and is not discussed in any detail.

: '''Observation #1''':

:* If all selected LDFs are &ge; 1.00 then CDFs for less mature years are greater than CDFs for more mature years. This is because less mature years have further to go before they reach ultimate. Mathematically, if CDF<sub>i</sub> represents the ''age i-to-ultimate'' CDF then we have:
:::{| class='wikitable'
|-
|| if all selected LDFs &ge; 1.00 then CDF<sub>i</sub> &ge; CDF<sub>i+1</sub> for all i
|}

:* If any selected LDFs are < 1.00, then this relationship may not hold. A selected LDF of < 1.00 means there has been ''favorable/downward'' development within a cohort of claims.

: '''Observation #2''': ''(from Pinto & Gogol paper)''

:* Development varies by retention: Let's say you have a paid triangle with a retention level 100,000 and another with a retention of 500,000. Even if both triangles are based on the same underlying claim data, they will likely have different development patterns. Part of the reason is that the distribution for size of loss is different for different maturities. ''(The source text doesn't provide any examples.)''
:* This is discussed a little further in ''[[Friedland14.Recoveries#Tail_Factors_in_Reinsurance | Chapter 15 (Recoveries) - Tail Factors in Reinsurance]].''

In the next section, we're going to tackle a very, VERY important question:

:{| class='wikitable'
|-
|| '''Question''': When <u>does</u> the development method work and when <u>doesn't</u> it work
|}

:* We know the general answer to this from an earlier section of this wiki article: ''[[Friedland07.Development#Development_Method_-_The_Key_Assumption | Development Method - The Key Assumption]]'':

::: &rarr; The development method assumes future loss development is <u>similar</u> to development in prior years

But that answer, while perfectly valid, is not tremendously helpful in a real-life situation. We have to be more specific. This section of the source text provides a bunch of examples of situations where the development method works, and also where it doesn't work. I've summarized them below and you can skim it quickly but don't linger. This topic is covered in great detail in the remainder of chapter 7 and in most of the rest of the text.

:{| class='wikitable'
|-
|| '''Question''': identify 1 situation specifically related to <u>paid</u> development and 1 situation specifically related to <u>reported</u> development where the development method should likely <u>work</u> ''(produce accurate estimates of ultimate loss)''
|}

:* when using <u>paid</u> loss development:
:: &rarr; no significant changes in the speed of closing claims
:* when using <u>reported</u> loss development:
:: &rarr; no significant changes in the adequacy of case O/S ''(case outstanding)''

An obvious corollary is that paid development <u>will not work</u> if there's been a speedup or slowdown of claim closings or payments. Reported development <u>will not work</u> when there have been changes in the adequacy of case O/S. ''(This is also referred to case reserve adequacy.)'' Of course you have to able to recognize when these changes have occurred, either from the paid and reported loss triangles themselves, or other diagnostic triangles, or having spoken with management about relevant operational changes. Operational changes like hiring more claims staff could increase the speed of closing claims. Also, initial case reserves are often set using tables and if these tables are updated then levels of case reserve adequacy could change.

:{| class='wikitable'
|-
|| '''Question''': identify 3 general situations where the development method ''(either paid or reported)'' should likely <u>work</u>
|}

:# no significant operational changes
:# large volume of claims ''(large enough so that a large loss won't distort the development)''
:# high-frequency, low-severity lines of business ''(auto physical damage)''

:{| class='wikitable'
|-
|| '''Question''': identify some general situations where the development method ''(either paid or reported)'' might <u>not work</u>
|}

:# the opposite of the situations where the development method works ''(see above)''
:# tort reform ''(changes in the external environment like judicial decisions imposing caps on damages)''
:# new lines of business that may not have credible data 
:# long-tailed lines like WC ''(CDFs at early maturities can be highly leveraged)'' <span style="color: red">'''<sup>1</sup>'''</span>
:# uneven spread of claims over the year, often due to <u>seasonality</u> ''(snowmobile claims spike in winter, boat accidents spike in summer)''

:: <span style="color: red">'''<sup>1</sup>'''</span> ''Highly leveraged'' means a large CDF, like 10.0, where the estimate of ultimate would be very sensitive to the given loss amount. Applying a CDF of 10.0 to a loss amount would be magnify any estimation error by a factor of 10.0. ''(versus a situation where the CDF is something much smaller, like 1.05, which is <u>not</u> highly leveraged)''

Here is a selection of exam problems related to the development method:

[https://www.battleacts5.ca/FC.php?selectString=**&filter=both&sortOrder=natural&colorFlag=allFlag&colorStatus=allStatus&priority=importance-high&subsetFlag=miniQuiz&prefix=Friedland07&suffix=Development&section=all&subSection=all&examRep=all&examYear=all&examTerm=all&quizNum=2<span style="font-size: 20px; background-color: aqua; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 10px;">'''mini BattleQuiz 2]'''</span> <span style="color: red;">'''You must be <u>logged in</u> or this will not work.'''</span>

{| class='wikitable' style='background-color: gold;'
|-
|| '''''Alice-the-Actuary says:'''''
&nbsp;&nbsp; &rarr; ''If you're reading this material to understand the development method for the Werner '''pricing''' material, you can probably '''stop here'''.
<br>&nbsp;&nbsp; &rarr; ''If you currently studying the Friedland '''reserving''' material, then '''read on...'''''
|}

===Influence of a Changing Environment - Scenario 1 (Base Case)===

This is the most interesting part of reserving and is part of the reason I created ''SimPolicy''. The development method is simple to understand and apply but it has a lot of moving parts, too many for the human brain to keep track of. For example, in auto insurance, a summer storm with heavy rain could cause a spike in accidents. How would this event affect the accuracy of your reserving methods? Those higher than normal claim dollars would appear in the data triangles and propagate through your analysis, But how would that change your analysis? Would you have to make adjustments to maintain the accuracy of your results? There's no simple formula that can give you the answer but a simulation can help you better understand how all the moving parts fit together.

We'll start with a <u>base case</u> scenario that's roughly similar to ''Scenario 1'' from the source text. A reserving scenario can have many different relevant characteristics but the two we're focusing on here are:

* stability of the <u>AY Loss Ratios</u> ''(source text refers to Loss Ratios as Claims Ratios)''
* stability of the <u>case O/S strength</u> ''(case O/S or case outstanding is also often referred to as <u>case reserves</u>)''

In this base case, the development patterns are stable and our estimates of ultimate loss using the development method are 100% accurate. We will subsequently introduce ''destabilizing events'' as described further down, first separately, then together, to see the effect of these changes on our estimates.

: [https://vimeo.com/1095256295 <span style="color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 100px;">'''VIDEO: F-07 (041) Scenario 1: Base Case &rarr; 2:00'''</span>]

Here is the PDF version of the various scenarios: ''(Sometimes I find it helpful to have the spreadsheet printed out as a pdf)''

: [https://www.battleacts5.ca/pdf/F-07_(040)_scenarios_1-4.pdf <span style="color: black; font-size: 12px; background-color: yellow; border: solid; border-width: 2px; border-radius: 10px; border-color: yellow; padding: 1px 3px 1px 3px; margin: 0px;">'''''Demo F-07 (040): Development Method - Influences of a Changing Environment 1-4'''''</span>]

And here's the Excel version:

: [https://www.battleacts5.ca/Excel/Excel_F-07_(040)_scenarios_1-4.xlsx <span style="color: white; font-size: 12px; background-color: indigo; border: solid; border-width: 2px; border-radius: 10px; border-color: indigo; padding: 1px 3px 1px 3px; margin: 0px;">'''''Excel Demo F-07 (040): Development Method - Influences of a Changing Environment 1-4'''''</span>]

===Influence of a Changing Environment - Scenarios 2,3,4===

In this section, we change the base scenario in very specific ways by introducing ''destabilizing events'':

:: '''scenario 2''': increasing AY loss ratios
:: '''scenario 3''': increasing case O/S strength
:: '''scenario 4''': combining scenarios 2 & 3 and applying both changes simultaneously

Note that the first 2 changes are done in isolation. Everything else stays the same.

:{| class='wikitable'
|-
|| '''Question''': how do these <u>individual changes</u> in scenarios 2 & 3 affect the application of the development method
|}

:* The first thing to realize is that the effect on the <u>paid</u> development method may be different from the effect on the <u>reported</u> development method. The '''key''' is to know how ''(or if)'' these changes affect the underlying development patterns.

Before you watch the video for the answers, try it yourself. Maybe talk about it with someone at work to see what you come up with. If you'd like a print-out of the spreadsheets discussed in videos, the PDF is available in the yellow link at the end of the previous section and the Excel version is in the purple link. ''Alice-the Actuary'' says you'll learn better if you think about it before looking at the answer. ''Listen to her &ndash; she's smart!''

Anyway, once you understand these individual changes...

:{| class='wikitable'
|-
|| '''Question''': how does the <u>combination change</u> in scenario 4 affect the application of the development method
|}

:* Again, the '''key''' is understanding how the development pattern changes. Use the pdf or Excel for scenario 4 and try working it out on your own before watching the video.

Links to a PDF version and the Excel version of scenarios 1-4 were provided in the previous section, ''[[Friedland07.Development#Influence_of_a_Changing_Environment_-_Scenario_1_.28Base_Case.29 | Influence of a Changing Environment - Scenario 1 Base Case]].''

Here are the videos for scenarios 2,3,4. You can watch them without worrying about taking notes &ndash; Alice took notes for you further down. :-)

: <div style="width: 430px; color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 2px;">[https://vimeo.com/1095256404 <span style="color: black;>'''VIDEO: F-07 (042) Scenario 2: Increasing AY LR &rarr; 2:30'''</span>]</div>
: <div style="width: 430px; color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 2px;">[https://vimeo.com/1095256429 <span style="color: black;>'''VIDEO: F-07 (043) Scenario 3: Increasing Case Reserve Strength &rarr; 3:30'''</span>]</div>
: <div style="width: 430px; color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 2px;">[https://vimeo.com/1095256450 <span style="color: black;>'''VIDEO: F-07 (044) Scenario 4: Combination of 2 & 3 &rarr; 3:30'''</span>]</div>

====Alice's Video Notes (Scenarios 2,3,4)====

Here are some notes to help you out:

:{| class='wikitable' style='background-color: lightgreen;'
|-
|| '''Scenario 2''': ''Increasing AY LRs''
|}

:* If the only thing that changes from the base case is the AY LR then the development patterns remain completely stable and the development method will be <u>100% accurate</u>.
:* This result applies to <u>both</u> the paid & reported method.
:* This result also applies regardless of whether the AY LRs <u>increase</u> or <u>decrease</u>. ''(You <u>cannot</u> test this in the spreadsheet just by changing the real AY LRs. You would need access to the simulation software to rerun the simulation and get new triangles. There will be some exercises however so you can see how this works.)
:* Paid development patterns are generally <u>different</u> from reported development patterns.
:* Paid development patterns generally have a <u>longer tail</u> than reported development patterns. ''(This is because claims are paid at a later date from when they were reported)''
:* Paid data &le; reported data ''(This is true even if case reserves are inadequate because as soon as a claim is paid, the reported data will be adjusted upward to reflect the higher final payment.)''

:{| class='wikitable' style='background-color: lightgreen;'
|-
|| '''Scenario 3''': ''Increasing Case O/S Strength''
|}

:* Changing the case reserve strength changes the <u>reported</u> development pattern.
::: &rarr; ''It does <u>not</u> change the paid development pattern so paid development is still 100% accurate.''
::: &rarr; ''It does <u>not</u> change the ultimate &ndash; all it does is change case reserving practices but the final settlement amount is assumed to be the same
:* <u>Increasing</u> the case reserve strength causes reported development to <u>over</u>-estimate the true AY LR. Here's the reasoning:
::: &rarr; Historical LDFs had to be higher because they had to take claims at lower level of case strength <u>up</u> to the final settlement amount.
::: &rarr; If you apply those higher historical LDFs to more recent claims that already have a higher case reserve strength, your estimate will overshoot the mark.
:* Similarly, <u>decreasing</u> the case reserve strength causes reported development to <u>under</u>-estimate the true AY LR. ''(You should think through that before moving on.)''
:* Increasing case reserve strength is generally a <u>calendar year</u> event. That means it affects <u>diagonals</u> in the reported development triangle. ''(The previous scenario of an increase in AY LRs was an <u>accident year</u> event, meaning it affects successive accident years, or horizontal rows, in the triangle.)''
:* '''Side note''': In the <u>base case</u> scenario, the case reserve strength was set by the simulation to be 100%. That means the initial reserve for every claims was perfectly accurate. ''(This might happen for claims in aggregate but never consistently for individual claims.)'' In this <u>increasing case O/S strength</u> scenario, the case strength was set to be 120%, representing a 20% increase. This often happens once every few years when an insurer updates their tables of initial case reserves.
:* We'll learn how to handle reported triangles where the case reserves strength is changing in ''[[Friedland13.BerqSherm | Chapter 13 - Berquist-Sherman Method]]''.

:{| class='wikitable' style='background-color: lightgreen;'
|-
|| '''Scenario 4''': ''Increasing AY LRs & Increasing Case O/S Stength''
|}

:* Scenarios where two things change at the same time can be difficult to analyze but this one is <u>easy</u>! That's because the change in AY LR has no effect on the accuracy of the development method. It's only the change in case reserve strength that messes things up.
:* The paid loss triangle is exactly the same as in scenario 2. ''(And the paid development method produces accurate estimates of ultimate losses.)''
:* The reported loss data triangle has dollar values that are greater than in scenarios 2 & 3, but the reported development patterns in scenarios 3 & 4 are the same.
:* The true AY LRs are higher in scenario 4 ''(60%, 60%, 65%, 65%, 70%, 70%)'' than in scenario 3 ''(all 60%)'' but reported development in both scenarios 3 & 4 over-estimate the true AY LRs by a proportionately similar amount.

{| class='wikitable'
|-
|| '''More examples''': The <u>source text</u> has examples/scenarios similar to mine that you can look at for further study
|}

: '''Source text scenarios 1-4''': Changes in Claim Ratios and Case Outstanding Adequacy

:* Scenario 1 is a steady-state environment where claim ratios are stable and there are no changes from historical levels of case outstanding strength (U.S. PP Auto Steady-State)
:* Scenario 2 is an environment of increasing claim ratios and no change in case outstanding strength (U.S. PP Auto Increasing Claim Ratios)
:* Scenario 3 is an environment of stable claim ratios with an increase in case outstanding strength (U.S. PP Auto Increasing Case Outstanding Strength)
:* Scenario 4 is an environment where there are increases in both claim ratios and case outstanding strength (U.S. PP Auto Increasing Claim Ratios and Case Outstanding Strength)

: '''Source text scenarios 5-6''':  Changes in Product Mix ''(We'll cover scenarios 5-6 in the next section.)''

:* Scenario 5: U.S. Auto Steady-State (No Change in Product Mix)
:* Scenario 6: U.S. Auto Changing Product Mix

===Influence of a Changing Environment - Scenarios 5,6===

In each of scenarios 1-4, we had only 1 set of paid & reported data triangles. In other words, we were looking only at 1 product or 1 LOB ''(Line of Business).'' In scenarios 5-6, we have 2 separate LOBs and therefore 2 sets of paid & reported triangles.

When Alice has to do a reserve analysis for 2 lines of business, she likes to combine the data into a single set of triangles. That way she has more time to ''[https://www.battleacts5.ca/images/relaxing.jpg relax]'' because she only has to go through the reserving process once instead of having to do it separately for LOB 1 and then again for LOB 2. Great idea, but it doesn't always work. :-(

{| class='wikitable'
|-
|| '''Question''': describe a set of conditions where <u>combining LOBs</u> for estimating ultimate losses with the development method <u>is valid</u>
|}

* In general you can do this when the development triangles for the combined data are stable, but in scenario 5 ''(video below)'' we can be more <u>specific</u>:
: &rarr; development pattern for LOB 1 is stable
: &rarr; development pattern for LOB 2 is stable ''(even if it's different from LOB 1)''
: &rarr; relative proportions of premiums & losses for LOB 1 versus LOB 2 remain stable ''(will be true if growth rates for each LOB are the same)''

Below is the video for scenarios 5 & 6 showing an example of combining 2 LOBs. Each has a stable development pattern, and each has <u>premium growth</u> of 5%. That ensures the relative proportions of premiums remain the same over time. Also, the true AY LR for LOB 1 is 60% for all AYs, and for LOB 2, it's 80%. That ensures the relative proportions of losses also remain stable. ''(You might have to think about that for a moment.)''

: [https://vimeo.com/1095256467 <span style="color: black; font-size: 12px; background-color: aqua; border: solid; border-width: 2px; border-radius: 10px; border-color: aqua; padding: 5px 10px 5px 10px; margin-top: 100px;">'''VIDEO: F-07 (045) Scenarios 5 & 6: Combining LOBs &rarr; 8:00'''</span>]

And here's the Excel version:

: [https://www.battleacts5.ca/Excel/Excel_F-07_(045)_scenarios_5-6_wiki.xlsx <span style="color: white; font-size: 12px; background-color: indigo; border: solid; border-width: 2px; border-radius: 10px; border-color: indigo; padding: 1px 3px 1px 3px; margin: 0px;">'''''Excel Demo F-07 (045): Development Method - Influences of a Changing Environment 5-6'''''</span>]

Now that we know at least one situation where combining LOBs is valid, let's look at a situation where it isn't. In this case, your development method estimates will be inaccurate using the combined data triangles.

{| class='wikitable'
|-
|| '''Question''': describe a set of conditions where <u>combining LOBs</u> for estimating ultimate losses with the development method <u>is not valid</u>
|}

* In scenario 6 ''(video below)'' the development method works just fine on LOB 1 and LOB 2 separately ''(because individually they have stable development patterns)'' but when you combine the data, the results are <u>not</u> accurate

: &rarr; development pattern for LOB 1 is stable
: &rarr; development pattern for LOB 2 is stable but different from LOB 1
: &rarr; growth rates for LOB 1 and LOB 2 are different ''(so the relative proportions of premiums & losses for LOB 1 versus LOB 2 <u>change over time</u>)''

* See above for video of Scenarios 5 & 6.

====Alice's Video Notes (Scenarios 5,6)====

Here are some notes to help you out:

:{| class='wikitable' style='background-color: lightgreen;'
|-
|| '''Scenario 5''': ''Combining LOBs - Estimates are Valid''
|}

:* Each LOB has consistent AY LRs, consistent case O/S strength ''(same as scenario 1 &ndash; the base case scenario.)''
:* Each LOB has a stable development pattern for both paid & reported losses but the pattern is different for LOB 1 versus LOB 2
:* <span style="color: red;">'''Each LOB has a premium growth rate of 5%'''</span> ''(and because the AY LRs are the same for all AYs, the growth rate of losses is also 5%)''
:* If the data triangles for LOB 1 and LOB 2 are combined by summing, then the development patterns for the <u>combined</u> paid & reported triangles are <u>stable</u>.
:* The development method then <u>produces accurate estimates</u> of ultimate loss.
:: &rarr; ''The estimate of the combined ultimate AY LR is 70%, a simple average of the 60% LR for LOB 1 and the 80% LR for LOB 2''

:{| class='wikitable' style='background-color: lightgreen;'
|-
|| '''Scenario 6''': ''Combining LOBs - Estimates are <u>Not</u> Valid''
|}

:* <span style="color: red;">'''LOB 1 has a premium growth rate of 5%'''</span>, <span style="color: purple;">'''LOB 2 has a premium growth rate of 30%'''</span> ''(and the growth rates of the losses are also 5% and 30% respectively.)''
:* Each LOB has a <u>stable</u> development pattern for both paid & reported losses but the pattern is <u>different</u> for LOB 1 versus LOB 2
:* The development patterns for the <u>combined</u> paid & reported triangles <u>are not stable</u>. This is because
:: &rarr; ''The combined LDF triangles are essentially volume-weighted averages of the LDF triangles for LOBs 1 & 2.
:: &rarr; ''So if the lines are growing at different rates, then the weights are changing every year and that destroys the stability of the combined triangles.''
:* The development method <u>does not</u> produce accurate estimates of ultimate loss. Here our estimates are <u>too low</u> because:
:: &rarr; ''The LDFs show an upward trend as you go down the columns
:: &rarr; ''Therefore the historical LDFs will be <u>too low</u> for the more recent AYs''
:* Side note:
:: &rarr; ''LOB 2 has a true AY LR of 80% and since it's growing faster, the combined AY LR will <u>no longer be</u> the simple average (60% + 80%)/2 = 70%.'' 
:: &rarr; ''The true AY LR for the combined data will increase from 70% and move <u>steadily closer to 80%</u> with each successive year.''

{| class="wikitable"
|-
| style="background-color: darkslategrey; color: white; border: solid; border-width: 2px; border-radius: 10px;" | '''Pop Quiz B! &nbsp;&nbsp; :-o'''
|}

* If you combine data for LOB 1 and LOB 2 under the following conditions, can the development method still be accurate: <span style="background-color: lightblue; border-radius: 5px;"> ''[[Friedland07.Development#Pop_Quiz_B_-_Answer |Click for Answer]]''&nbsp;</span>
: &rarr; development pattern for LOB 1 is stable
: &rarr; development pattern for LOB 2 is stable and the same as LOB 1
: &rarr; growth rates for LOB 1 and LOB 2 are different ''(so the relative proportions of premiums & losses for LOB 1 versus LOB 2 <u>changes over time</u>)''

===Remaining Exam Problems===

These are the remaining exam problems back to 2016:

[https://www.battleacts5.ca/FC.php?selectString=**&filter=both&sortOrder=natural&colorFlag=allFlag&colorStatus=allStatus&priority=importance-high&subsetFlag=miniQuiz&prefix=Friedland07&suffix=Development&section=all&subSection=all&examRep=all&examYear=all&examTerm=all&quizNum=3<span style="font-size: 20px; background-color: aqua; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 10px;">'''mini BattleQuiz 3]'''</span> <span style="color: red;">'''You must be <u>logged in</u> or this will not work.'''</span>

These problems are from 2015 & earlier:

[https://www.battleacts5.ca/FC.php?selectString=**&filter=both&sortOrder=natural&colorFlag=allFlag&colorStatus=allStatus&priority=importance-high&subsetFlag=miniQuiz&prefix=Friedland07&suffix=Development&section=all&subSection=all&examRep=all&examYear=all&examTerm=all&quizNum=4<span style="font-size: 20px; background-color: aqua; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 10px;">'''mini BattleQuiz 4]'''</span> <span style="color: red;">'''You must be <u>logged in</u> or this will not work.'''</span>

And here are all the quizzes put together:

[https://www.battleacts5.ca/FC.php?selectString=**&filter=both&sortOrder=natural&colorFlag=allFlag&colorStatus=allStatus&priority=importance-high&subsetFlag=miniQuiz&prefix=Friedland07&suffix=Development&section=all&subSection=all&examRep=all&examYear=all&examTerm=all&quizNum=all<span style="font-size: 20px; background-color: lightgreen; border: solid; border-width: 1px; border-radius: 10px; padding: 2px 10px 2px 10px; margin: 10px;">'''Full BattleQuiz]'''</span> <span style="color: red;">'''You must be <u>logged in</u> or this will not work.'''</span>

==POP QUIZ ANSWERS==

* If case reserve adequacy increases then the <u>paid-to-reported</u> diagnostic triangle will show <span style="color: red;">'''decreases'''</span> down columns. ''(This is because reported losses for newly reported claims will be higher than historical values so the paid-to-reported ratio will show a drop starting along a CY diagonal.)''

: <html><a href="javascript:history.go(-1)">Go back</a></html>

==Pop Quiz A - Answer==

: To answer this question you have to do '''Step A''' of the development method where you calculate the LDFs ''(or link ratios or age-to-age factors or whatever you like to call them.)''
:* <u>Triangle 1</u>: <span style="color: green;">'''satisfies'''</span> stability/consistency assumption for loss development to work reasonably well
:* <u>Triangle 2</u>: <span style="color: red;">'''doesn't satisfy'''</span> stability/consistency assumption ''(LDFs are increasing significantly within columns)''
:* <u>Triangle 3</u>: '''hard to tell''' - the underlying development pattern is the same for each AY but the simulation introduced moderate random variation which confounds the data
:* <u>Triangle 4</u>: <span style="color: red;">'''doesn't satisfy'''</span> stability/consistency assumption ''(LDFs are decreasing in the 12-24 column)''
:* <u>Triangle 5</u>: <span style="color: green;">'''satisfies'''</span> stability/consistency assumption for loss development to work reasonably well ''(losses increased year-over-year, but the development pattern didn't change)''

{| class='wikitable' style="float: ; margin-left: 50px; text-align: right;"
|-
! <span style="background-color: lightgreen; padding: 5px; border-radius: 5px;"> Triangle 1 LDFs !! 12-24 !! 24-36 !! 36-48
|- 
! scope='row' |  2020	
|2.936	||1.421	||1.196
|-
! scope='row' | 2021	
|2.963	||1.430
|-
! scope='row' | 2022	
|2.897
|}

{| class='wikitable' style="float: ; margin-left: 50px;"
|-
! <span style="background-color: lightgreen; padding: 5px; border-radius: 5px;"> Triangle 2 LDFs !! 12-24 !! 24-36 !! 36-48
|- 
! scope='row' |  2020	
|2.924	||1.430	||1.196
|-
! scope='row' | 2021	
|3.116	||1.461
|-
! scope='row' | 2022	
|3.302
|}

{| class='wikitable' style="float: ; float: clear; margin-left: 50px;"
|-
! <span style="background-color: lightgreen; padding: 5px; border-radius: 5px;"> Triangle 3 LDFs !! 12-24 !! 24-36 !! 36-48
|- 
! scope='row' |  2020	
|3.436	||1.388	||1.186
|-
! scope='row' | 2021	
|2.568	||1.426
|-
! scope='row' | 2022	
|2.636
|}

{| class='wikitable' style="float: ; margin-left: 50px;;"
|-
! <span style="background-color: lightgreen; padding: 5px; border-radius: 5px;"> Triangle 4 LDFs !! 12-24 !! 24-36 !! 36-48
|- 
! scope='row' |  2020	
|3.085	||1.364	||1.219
|-
! scope='row' | 2021	
|2.726	||1.397
|-
! scope='row' | 2022	
|2.520
|}

{| class='wikitable' style="float: ; float: clear; margin-left: 50px;"
|-
! <span style="background-color: lightgreen; padding: 5px; border-radius: 5px;"> Triangle 5 LDFs !! 12-24 !! 24-36 !! 36-48
|- 
! scope='row' |  2020	
|2.924	||1.430	||1.196
|-
! scope='row' | 2021	
|2.924	||1.430
|-
! scope='row' | 2022	
|2.924
|}

: <html><a href="javascript:history.go(-1)">Go back</a></html>

==Pop Quiz B - Answer==

* Yes, the development method can produce accurate estimates because the development patterns are the same for LOB 1 and LOB 2. ''(If the development patterns are the same then it doesn't matter whether the LOBs are growing at different rates.)''

: <html><a href="javascript:history.go(-1)">Go back</a></html>