Build practical GI 101 skills through twenty original written exercises and sixty focused lessons on data preparation, ultimate claims, unpaid handling expenses, trend and pricing. Worked answers connect calculations to assumptions, diagnostics and defensible selections. This representative preview follows the supplied November 2026/March 2027/July 2027 syllabus, applicable to the next administration as of October 16, 2026; it does not represent a later syllabus version. Written exercises are a practice choice because the supplied evidence does not verify the examination's response format. The syllabus states that no case study is provided. Citations establish syllabus relevance; technical explanations use established actuarial knowledge rather than implying that the outline verifies every detail.
What this guide covers
Twenty original GI 101 exercises and 60 concepts covering claim development, trend, expenses and rates.
Introduction and Key Considerations
1. Ultimate, reported and unpaid claims reconcile
Ultimate claims estimate the total cost attributable to a defined exposure period after all relevant claims develop. Reported claims normally combine cumulative payments and current case estimates. Total unpaid claims equal ultimate less paid, while the provision beyond reported claims equals ultimate less reported. That additional provision can include both genuinely unreported claims and future changes on reported claims. Establish whether claim-adjustment expenses, recoveries and discounting are included before comparing amounts. These identities provide a control framework, but they do not establish whether the selected ultimate itself is adequate.
Worked example: A portfolio has $12 million paid, $5 million in case estimates and a selected ultimate of $21 million. Reported claims are $17 million, additional development is $4 million and total unpaid claims are $9 million, reconciling as $5 million plus $4 million.
Common mistake: Calling ultimate less reported the entire unpaid reserve omits outstanding case estimates and understates the remaining obligation.
Official syllabus reference: [2]
2. The actuarial control cycle tests a model against emergence
The actuarial control cycle links problem definition, model development, implementation and monitoring within the business environment. Define the decision, valuation basis and constraints before selecting a method. Translate assumptions into observable expectations, such as next-quarter payments or reported development. Compare actual results with those expectations and distinguish random variation from changes in data, operations or underlying risk. Feed justified findings into the next model iteration. Monitoring becomes informative when it can identify which assumption failed; merely replacing last quarter's figures does not complete the feedback mechanism.
Worked example: A paid projection anticipates $4 million of quarterly payments, but $6 million emerges after a settlement initiative. The actuary checks closure counts and remaining inventories before deciding whether payment timing changed or total claim costs actually increased.
Common mistake: Treating each valuation as an isolated calculation loses the connection between previous assumptions, observed departures and defensible revisions.
Official syllabus reference: [2]
3. Professional requirements depend on the assignment
Professional obligations arise from the actuary's applicable code, qualification requirements, standards of practice and assignment circumstances. Distinguish those requirements from textbook techniques and organizational preferences. The syllabus names U.S. ASOP No. 25 for credibility procedures, but that listing does not make every assignment subject to identical jurisdictional requirements. For a credibility application, identify the purpose, relevant experience, complement and limitations rather than treating a selected weight as self-justifying. Professional judgment operates within applicable requirements and evidence; a technically correct formula can still produce unsuitable advice when its intended use is misunderstood.
Worked example: An actuary estimating a small commercial portfolio's rate need identifies which professional framework governs the engagement, then explains the credibility procedure and complementary experience. The communication distinguishes the technical recommendation from any separate approval or implementation decision.
Common mistake: Assuming that a syllabus reference automatically creates the same legal or professional obligations for every actuary and jurisdiction.
Official syllabus reference: [2]
4. Data reconciliation establishes a usable analysis population
Data review starts with the population and accounting boundaries: covered business, origin periods, valuation dates, gross or net amounts, expenses and recoveries. Reconcile extracted totals to an independent control and explain material differences. Then test analytical consistency, including missing development cells, duplicate transactions, unusual negatives and changed claim identifiers. Reconciliation cannot prove every record is correct, but it detects omissions and incompatible bases before projection magnifies them. The actuary should understand relevant limitations and assess whether available data support the intended analysis, rather than equating successful file loading with data fitness.
Worked example: A transaction extract totals $24.6 million paid while the ledger shows $25 million. Investigation identifies $0.4 million of allocated expenses excluded from the extract. The actuary either adds them consistently or defines a claim-only analysis and handles expenses separately.
Common mistake: Forcing analytical totals to match a ledger without explaining basis differences can conceal genuine omissions or duplicate expenses.
Official syllabus reference: [2]
5. Segmentation trades homogeneity against statistical stability
Segmentation groups risks with comparable claim processes, coverage terms and development behavior. Greater homogeneity can reduce bias from mixing different risks, but smaller groups produce less stable estimates. Aggregation improves volume while potentially hiding differences in settlement speed, severity or exposure mix. Choose the level separately for the quantity being estimated: development patterns may be pooled while expected claim ratios remain segment-specific. Assess whether differences are persistent and decision-relevant, and consider partial pooling or credibility when neither complete separation nor complete aggregation uses the available evidence efficiently.
Worked example: Two liability classes have similar reporting patterns but different expected severities. An actuary pools their development-factor experience to improve stability, then applies class-specific expected claim costs rather than assuming that a common reporting pattern implies a common claim ratio.
Common mistake: Assuming that more granular data always improve estimates ignores the sampling variability created by dividing a limited portfolio.
Official syllabus reference: [2]
6. Credibility weights combine comparable estimates
A credibility procedure combines subject experience with another relevant estimate to balance responsiveness and stability. In a simple linear form, the result is Z times subject experience plus one minus Z times the complement. Both components must estimate the same target on consistent coverage, exposure and cost bases. Credibility is not merely a judgment that data are trustworthy: process variance, volume, relevance and structural differences matter. A large dataset can be precisely estimated yet unsuitable for the target. Select a procedure appropriate to the purpose and explain material assumptions behind the weight and complement.
Worked example: A small fleet's adjusted expected claim cost is $900 per vehicle, while a comparable broader portfolio indicates $750. With a selected credibility weight of 0.40, the combined estimate is $810, provided both figures represent the same prospective coverage and cost period.
Common mistake: Giving a large external dataset full influence without checking comparability confuses statistical volume with relevance to the insured risk.
Official syllabus reference: [2]
7. A decision trail makes judgment reproducible
Useful actuarial documentation connects the decision purpose to data definitions, adjustments, methods, assumptions and final selections. Record why important alternatives were accepted or rejected and identify sensitivities capable of changing the recommendation. Preserve enough calculation detail for a qualified reviewer to follow the estimate without reconstructing undocumented choices. Documentation should distinguish observations from assumptions and judgments from mechanical outputs. It also supports future comparison: when an estimate changes, the reviewer can separate new experience, methodological revisions and corrected errors instead of attributing the entire movement to one cause.
Worked example: An actuary selects a 1.08 tail although the latest single-year indication is 1.03. The record explains the longer historical evidence, treatment of one unusual recovery and the reserve impact of using tails from 1.05 through 1.10.
Common mistake: Saving only the final spreadsheet and selected reserve leaves material assumptions and rejected alternatives unavailable to later reviewers.
Official syllabus reference: [2]
Preparing Claims and Exposure Data for Actuarial Work
8. Transactions become incremental and cumulative triangles
A development triangle groups transactions by origin period and elapsed development age. Incremental paid cells contain payments occurring within a development interval; cumulative paid cells sum payments through that age. Construct reported triangles using payments plus case estimates at each valuation, or equivalent consistent incurred transactions. A case estimate is a balance, so adding successive case snapshots would duplicate the outstanding amount. Define interval endpoints and valuation cutoffs consistently. Reversals, recoveries and corrections may legitimately create negative increments and should be investigated rather than automatically removed.
Worked example: A claim pays $2,000 during its first year and $3,000 during its second, with case balances of $8,000 and $4,000 at those dates. Cumulative paid is $2,000 then $5,000; reported claims are $10,000 then $9,000, not the sum of case snapshots.
Common mistake: Adding case balances across development periods treats stocks as flows and overstates cumulative reported claims in the triangle.
Official syllabus reference: [2]
9. Claim-count definitions control frequency and closure measures
Reported, open, closed and reopened claim counts measure different events or states. Decide whether counts represent unique claims, coverage features, claimants or transactions, and whether zero-payment claims are included. A reopened claim can increase open inventory without adding a new unique reported claim. Closed counts may represent cumulative unique closures or closure events; those definitions behave differently when claims reopen. Consistency matters when deriving frequency, average severity and settlement rates because mismatched numerators and denominators can create apparent trends or impossible inventory reconciliations.
Worked example: A portfolio begins with 100 open claims, receives 30 new claims, reopens 5 previously closed claims and closes 25. Ending open inventory is 110. Unique reported count increases by 30, while treating reopenings as new reports would incorrectly increase it by 35.
Common mistake: Using closure-event counts with unique reported counts can distort settlement proportions when repeated reopenings and closures occur frequently.
Official syllabus reference: [2]
10. Accident, report and policy years answer different questions
Accident-year data group claims by occurrence date, report-year data by notification date, and policy-year data by the originating contract's inception period. These bases associate different timing patterns with exposure and premium. Calendar-year financial results combine transactions from many origin periods and may include revisions to old claims. Choose an origin basis aligned with the analysis, then match denominators and development ages accordingly. A report-year triangle cannot reveal the pre-report delay in the same way an accident-year triangle can, while policy-year experience requires time for the underlying policies to earn and claims to mature.
Worked example: A policy begins in November 2024, a covered accident occurs in February 2025 and notification arrives in January 2026. The claim belongs to policy year 2024, accident year 2025 and report year 2026, illustrating why the bases cannot be interchanged.
Common mistake: Matching report-year claims directly to accident-year exposures can create misleading frequency changes when reporting delays shift between periods.
Official syllabus reference: [2]
11. Written, earned and in-force exposure measure different time
Written exposure measures coverage committed during a period, earned exposure measures coverage provided during that period, and in-force exposure measures the portfolio active at a particular date. An annual vehicle-year exposure earns with time at risk, whereas an in-force vehicle count is a point-in-time stock. Unearned exposure represents remaining contracted coverage when that concept is useful. Select the measure consistent with claim occurrence and pricing purpose. A rapidly growing portfolio can have substantially different written, earned and year-end in-force quantities even when every contract has identical coverage terms.
Worked example: An insurer writes 100 annual vehicle policies on October 1 with no cancellations. By December 31, those policies contribute 25 earned vehicle-years, 100 written vehicle-years and 100 vehicles in force, with 75 vehicle-years of contracted coverage still unearned.
Common mistake: Dividing annual accident claims by a year-end in-force count can bias frequency when the portfolio grows or contracts materially.
Official syllabus reference: [2]
12. Premium earning follows the assumed risk pattern
Premium earning allocates written premium to the period in which insured risk is provided. Uniform earning is suitable only when the assumed risk pattern supports it; seasonal or project risks may require another allocation. Under consistent accounting, earned premium equals written premium plus opening unearned premium minus closing unearned premium, allowing for applicable adjustments. Exposure earning and premium earning need not follow identical patterns if premium includes components with different timing. Establish how cancellations, endorsements and retrospective adjustments affect the calculation before using earned premium as a claim-ratio denominator.
Worked example: A six-month seasonal contract charges $1,200, with an assumed 70% of risk in its first three months. At that point, risk-based earned premium is $840 and unearned premium is $360, rather than the $600 each produced by uniform earning.
Common mistake: Assuming every policy earns uniformly can misalign claims and premium when the insured risk is concentrated in particular months.
Official syllabus reference: [2]
13. Parallelogram on-leveling uses earned rate-level shares
The parallelogram method estimates the average rate level embedded in historical earned premium using rate-change dates, writing patterns and policy terms. Divide the desired current rate index by the historical average index to obtain an on-level factor. Annual policies written uniformly create triangular earned contributions immediately after a writing-date rate change because policies enter gradually and earn over time. Multiple changes require separate affected regions or an equivalent integration. The method assumes the portfolio structure used in the geometry is sufficiently representative; it does not automatically correct changing coverage, limits or risk mix.
Worked example: A 20% increase applies to annual policies written from July 1. With uniform writings and earning, only one-eighth of that calendar year's earned exposure carries the increase. Its average rate index is 1.025, giving a current-level factor of 1.20/1.025.
Common mistake: Weighting a midyear writing-date change by one-half of earned premium ignores the gradual earning of newly written annual policies.
Official syllabus reference: [2]
14. Extension of exposures isolates current pricing from mix
Extension of exposures applies a selected rating structure to detailed historical exposures, producing the premium those risks would generate under that structure. It can capture interactions among classification, limits, deductibles and rate changes more precisely than a broad average on-level factor. Its reliability depends on complete historical rating characteristics and consistent treatment of current rules. Changes in observed average premium can arise from rate revisions, exposure size, coverage or portfolio composition. Therefore, average premium growth alone is not an adequate measure of a rate-level change.
Worked example: A portfolio's average premium rises from $800 to $920 while the filed rate schedule is unchanged. Detailed repricing shows that larger insured values and a shift toward higher-hazard classes explain the increase, so treating the full 15% as a rate increase would misstate premium adequacy.
Common mistake: Using the change in average premium as an on-level adjustment confounds pricing actions with changes in insured risks and coverage.
Official syllabus reference: [2]
15. Ultimate premium includes later exposure and contract adjustments
Premium may continue developing after initial booking because exposure audits, endorsements, cancellations, reinstatements or contract-based adjustments change the final amount. Estimate ultimate premium on a basis consistent with the associated claim projection and intended analysis. Audit-sensitive business may require exposure-development assumptions, while retrospective premium arrangements require attention to contractual relationships with claims. Distinguish ultimate premium estimation from on-leveling: the former estimates the final amount attributable to the business, whereas the latter restates amounts to a chosen rate level. Both adjustments may be needed, but they address different mechanisms.
Worked example: Initially booked premium is $5 million for payroll-rated contracts. Expected audit adjustments add 8%, producing $5.4 million ultimate premium before any current-rate adjustment. Applying an on-level factor to only the original booking would leave the expected audit premium outside the analysis.
Common mistake: Assuming booked earned premium is final can overstate claim ratios when material favorable exposure audits are still expected.
Official syllabus reference: [2]
Projecting Ultimate Claims
16. Development-factor selection requires matched observations
An age-to-age factor compares cumulative values for the same origin period at successive development ages. A volume-weighted factor divides the sum of later-age values by the sum of corresponding earlier-age values. Only matched pairs belong in both sums. Simple averages, volume-weighted averages and selected recent-period averages emphasize different aspects of experience; none is automatically appropriate. Examine outliers, changes in volume and operational breaks before selection. A large year can dominate volume weighting, so its relevance matters as much as its size when forecasting the current portfolio.
Worked example: Two matched years develop from 100 to 150 and from 200 to 260. The volume-weighted factor is 410/300, or 1.3667, while the simple average of 1.50 and 1.30 is 1.40. The difference reflects greater weight on the larger year.
Common mistake: Including a recent year's early-age amount without its unavailable later-age partner biases the denominator and understates the development factor.
Official syllabus reference: [2]
17. Cumulative factors translate maturity into remaining development
A cumulative development factor multiplies all selected age-to-age factors from the current age through ultimate, including the tail. Its reciprocal is the implied emerged proportion when that interpretation is appropriate. A tail captures development beyond the latest explicitly modeled age and can materially affect unpaid liabilities even when close to one. Tail selection needs evidence suitable for the coverage's duration and changing conditions. Do not infer that a reported factor below one is automatically impossible: recoveries or case redundancy can produce downward development, although the usual positive-emergence interpretation then needs care.
Worked example: A 24-month amount has factors of 1.20 to 36 months, 1.05 to 48 months and a 1.02 tail. The cumulative factor is 1.2852, implying approximately 77.81% emerged under the selected pattern, with the rest still to develop.
Common mistake: Adding age-to-age percentages instead of multiplying factors omits compounding and misstates both ultimate claims and implied emergence proportions.
Official syllabus reference: [2]
18. Paid and reported development rely on different stability
Paid development assumes the relationship between payments at an observed age and ultimate cost remains representative. Reported development additionally reflects the strength and consistency of case estimates. Paid data avoid direct case-estimate changes but can be distorted by settlement initiatives, payment batching or litigation delays. Reported data may mature earlier but react immediately to reserving guidelines. Compare both with counts, average case estimates and payment diagnostics. Agreement is useful evidence, yet shared exposure changes or common data errors can make both methods wrong in the same direction.
Worked example: A claims team strengthens case estimates while payment behavior remains unchanged. Reported claims rise immediately, making unadjusted reported development potentially excessive. Paid projections may offer a useful comparison, provided historical settlement timing still represents the current claims process.
Common mistake: Calling paid data objective does not establish that historical payment timing remains suitable after a material operational change.
Official syllabus reference: [2]
19. Triangle diagonals reveal calendar-period effects
Rows of an origin-development triangle follow cohorts, columns compare equal maturities, and diagonals generally correspond to common calendar valuations or transaction periods. A change affecting several origin years on the same diagonal suggests a calendar-period influence such as inflation, case strengthening, system conversion or settlement activity. Contrast paid and reported amounts, counts and average severities to identify the likely mechanism. A diagonal pattern is a diagnostic clue rather than proof of causation. Origin-year changes and development effects can overlap, requiring qualitative information and additional investigations.
Worked example: Several accident years show unusually high reported increments in the same calendar quarter, while payments and reported counts remain ordinary. A simultaneous increase in average case estimates directs investigation toward a reserving-guideline change rather than a sudden increase in accident frequency.
Common mistake: Attributing every unusual triangle cell to its accident year overlooks calendar changes that affect many cohorts at the same valuation.
Official syllabus reference: [2]
20. Frequency-severity development separates claim volume from cost
The development-based frequency-severity method projects ultimate claim counts and ultimate average claim costs, then multiplies them to estimate ultimate aggregate claims. It can distinguish a reporting-count change from a severity change that aggregate development conceals. Ensure that both projections refer to the same population, including treatment of zero claims, reopened claims and late reports. Average severity can change as the claim population matures because larger claims report or settle at different speeds. Therefore, severity development is not simply inflation, and an assumption suitable for currently reported claims may not describe all ultimate claims.
Worked example: An accident year has 500 reported claims averaging $4,000. Selected count and average-severity development factors are 1.20 and 1.15. Ultimate count is 600, ultimate severity is $4,600 and ultimate aggregate claims are $2.76 million, assuming consistent populations.
Common mistake: Multiplying developed counts by an average severity defined only for closed claims can combine incompatible claim populations and distort ultimate cost.
Official syllabus reference: [2]
21. The expected method projects costs from an exposure benchmark
The expected method estimates ultimate claims by applying an expected claim ratio to suitably adjusted premium or an expected cost per unit to exposure. It is useful when current emergence is sparse or unrepresentative, but its accuracy depends on the benchmark and adjustment basis. Align rate level, trend, coverage and portfolio mix before transferring experience from another period or book. Unlike development, the basic expected method does not automatically respond to current reported or paid amounts. That stability is beneficial only when the independent expectation remains relevant to the target business.
Worked example: A new segment has $12 million of comparable on-level premium and a selected expected claim ratio of 65%. The expected method gives $7.8 million ultimate claims, even if early reported claims fluctuate, unless new evidence justifies revising the benchmark itself.
Common mistake: Using an old claim ratio with premium after a major rate increase can overstate expected claims unless the ratio is adjusted.
Official syllabus reference: [2]
22. Bornhuetter-Ferguson fixes the expected unobserved component
Bornhuetter-Ferguson ultimate equals observed claims plus expected ultimate multiplied by the selected unobserved proportion. For reported data, the added amount is expected future reported development; for paid data, it is expected unpaid claims. When the emerged proportion is p, the estimate can also be written as p times development ultimate plus one minus p times expected ultimate. This algebra explains its maturity-dependent responsiveness, without establishing a formal statistical credibility model. The method reduces amplification of early deviations but remains sensitive to the expected-cost benchmark and selected emergence pattern.
Worked example: Reported claims are $6 million, the selected reported proportion is 40% and expected ultimate is $14 million. Bornhuetter-Ferguson gives $6 million plus 60% of $14 million, or $14.4 million, compared with development ultimate of $15 million.
Common mistake: Subtracting actual reported claims from expected ultimate to obtain the unreported component forces the estimate back to the expected method.
Official syllabus reference: [2]
23. Benktander iteration increases reliance on observed emergence
A Benktander update replaces the original expected ultimate in a Bornhuetter-Ferguson calculation with the preceding Bornhuetter-Ferguson result. This moves the estimate toward development ultimate while retaining part of the original expectation. With emerged proportion p and unobserved proportion q, the first repeated update gives development ultimate weight one minus q squared and original expected ultimate weight q squared. Further iterations continue reducing the prior's influence when the pattern permits convergence. Specify the iteration convention explicitly, since an instruction to use Benktander should identify the intended update rather than silently applying an arbitrary number.
Worked example: Observed claims are $20 million, emergence is 50% and expected ultimate is $50 million. Bornhuetter-Ferguson gives $45 million. Replacing the expectation with $45 million gives a Benktander update of $42.5 million, between development's $40 million and the first result.
Common mistake: Treating repeated iteration as new evidence confuses a change in weighting with the arrival of additional independent claim information.
Official syllabus reference: [2]
24. Cape Cod estimates an expectation from used-up exposure
Cape Cod commonly estimates an expected claim ratio by dividing aggregate observed claims by aggregate premium multiplied by corresponding emerged proportions. The denominator is often called used-up premium because it measures the portion associated with observed emergence. Apply the resulting ratio to each year's unobserved premium-equivalent amount and add actual claims. Premium and claims must be placed on comparable rate, trend and coverage bases. The method pools information across years and therefore assumes their adjusted expected ratios are sufficiently related; a structural change in profitability can make unrestricted pooling misleading.
Worked example: Two years have on-level premiums of $10 million each, emerged proportions of 80% and 20%, and reported claims totaling $7 million. Used-up premium totals $10 million, giving a 70% expected ratio for estimating each year's remaining development.
Common mistake: Dividing reported claims by full premium rather than used-up premium understates the expected ratio when part of the experience remains unreported.
Official syllabus reference: [2]
25. Generalized Cape Cod calibrates expectations with target-specific weights
A Generalized Cape Cod approach can assign different experience weights when estimating the expected claim ratio for a particular target year. In the specified weighted variant, divide weighted reported claims by weighted used-up premium, applying identical weights to both sums. Used-up premium equals comparable on-level premium multiplied by the reported proportion. Apply the resulting ratio to the target year's unused premium, then add its reported claims. Weights can emphasize experience considered more relevant to the target. They require justification and sensitivity testing; they do not replace adjustments for differences in coverage, rate level or claim-cost level.
Worked example: In $000, reported claims are 60, 48 and 24; used-up premiums are 100, 60 and 20. Weights are 0.25, 0.50 and 1.00. The weighted ratio is 63/75 = 0.84. For target premium 80 with 25% reported, ultimate is 24 + 0.84 × (80 − 20) = 74.4.
Common mistake: Weighting claims while leaving used-up premiums unweighted distorts the calibrated ratio. Apply each year's selected weight consistently to both components.
Official syllabus reference: [2]
26. Berquist-Sherman case adjustment restates reserve strength
A Berquist-Sherman case-adequacy adjustment seeks a historical reported triangle consistent with the current level of case-estimate strength. Analyze average outstanding case estimates per open claim, allowing for ordinary severity trend and differences in claim maturity or composition. Restate historical case balances to the selected comparable level and add unchanged paid claims. Derive development patterns from the restated history for use with a compatible current diagonal. The procedure does not assert that higher average case estimates always mean strengthening: changing open-claim mix or selective closures can create the same observed increase.
Worked example: A historical cell contains 100 open claims, $1 million of case estimates and $2 million paid. A justified comparable case level is $12,000 per open claim. Restated reported claims become $3.2 million, rather than increasing the entire original reported amount by 20%.
Common mistake: Scaling total reported claims for case strengthening incorrectly changes historical payments, which the case-adequacy adjustment is intended to preserve.
Official syllabus reference: [2]
27. Berquist-Sherman settlement adjustment matches closure progress
A settlement-speed adjustment restates historical payments to a common settlement pattern using claim-count development and the relationship between payments and closures. Estimate ultimate counts, identify target closure proportions and determine payments associated with equivalent settlement progress. The adjusted paid triangle can support development factors less distorted by changing closure speed. Assumptions include sufficiently stable claim definitions, ultimate-count estimates and payment relationships after relevant cost adjustments. Closing cheap claims first, changing partial-payment practices or altering reopening behavior can break the link between closure counts and cumulative payment progress.
Worked example: Historical payments are $4 million at 400 closures and $7 million at 700 closures. Under a specified linear approximation, a target of 550 closures corresponds to $5.5 million. That adjusted point represents comparable settlement progress rather than the original elapsed-age payment.
Common mistake: Assuming closure percentage equals paid percentage ignores partial payments and differences in the costs of claims settled at different times.
Official syllabus reference: [2]
28. Large-claim separation must preserve expected excess cost
A few large claims can dominate aggregate development factors and obscure the ordinary portfolio pattern. Possible approaches include individual review, separate large-claim projections or capping claims for the attritional analysis and adding an expected excess component. Match the threshold's cost level over time and define whether catastrophe claims are treated separately. A cap changes the quantity being modeled: developed capped claims estimate capped ultimate cost, not unrestricted cost. The excess provision should reflect the relevant exposure and tail behavior, rather than simply deleting inconvenient historical observations from the estimate.
Worked example: An actuary develops claims capped at $250,000 to an estimated $8 million and separately estimates $1.5 million of ultimate excess. Total ultimate is $9.5 million. The capped triangle provides stability, while the excess component preserves the expected cost removed by the cap.
Common mistake: Removing large claims from factor selection and forgetting their expected excess component produces a stable-looking but incomplete ultimate estimate.
Official syllabus reference: [2]
29. Method influence should change with maturity and reliability
Method selection balances the information in observed emergence against the reliability of independent expectations and development patterns. Very immature years may need substantial expected-method influence, while mature stable years often support more direct development. Maturity alone is insufficient: a late operational disruption can reduce the relevance of historical patterns even for older years. Compare assumptions and sensitivities before combining outputs. Several methods using the same triangle and factors are correlated, so their numerical agreement does not provide the same evidence as genuinely different information sources.
Worked example: A recent year has only 10% reported and volatile development ultimate, while older years have 95% reported with stable case practices. The actuary gives greater expected-cost influence to the recent year and greater observed-experience influence to the mature years.
Common mistake: Taking an unweighted average of every available method assigns influence by spreadsheet layout rather than by evidence and assumption reliability.
Official syllabus reference: [2]
30. Case strengthening affects methods through different channels
Stronger case estimates increase current reported claims without necessarily changing ultimate loss cost. Unadjusted reported development can overreact by multiplying the strengthened balance by factors derived from weaker historical reserves. Reported Bornhuetter-Ferguson still includes the current increase directly, but does not multiply it through the entire development factor when the prior and pattern stay fixed. Paid methods avoid the immediate case change, although other operational effects may remain. Expected methods are unchanged mechanically. Compare these responses to distinguish genuine economic deterioration from a changed measurement basis.
Worked example: Reported claims rise from $20 million to $24 million solely through case strengthening. With a fixed factor of 1.50, development ultimate rises $6 million. With an unchanged prior and reported proportion, reported Bornhuetter-Ferguson rises $4 million, illustrating different mechanical sensitivity.
Common mistake: Assuming Bornhuetter-Ferguson is unaffected by case strengthening overlooks that its observed reported component enters ultimate directly, dollar for dollar.
Official syllabus reference: [2]
31. Reporting acceleration can mimic higher claim frequency
Faster notification increases reported counts and amounts at a given accident-year age even if ultimate claim frequency and cost are unchanged. Investigate report-lag distributions, cumulative reported counts per exposure and the relationship between report-year and accident-year experience. Historical reported-development factors may overstate future development when applied to an accelerated current diagonal. A reported Bornhuetter-Ferguson estimate can also be biased if its selected emerged proportion remains too low. Distinguish increased ultimate incidence from earlier observation, then revise the reporting pattern or use methods less dependent on the disrupted lag assumption.
Worked example: An online reporting portal moves many notifications from the second quarter after an accident into the first. First-quarter reported frequency rises, but cumulative frequency at twelve months is unchanged. Applying the old early-age count factor would incorrectly project additional ultimate claims.
Common mistake: Interpreting every increase in early reported counts as worsening ultimate frequency ignores changes in how quickly existing claims become visible.
Official syllabus reference: [2]
32. Payment acceleration changes both development and BF patterns
Payment acceleration raises cumulative paid claims at a given age while reducing the amount remaining, without necessarily changing ultimate cost. Historical paid-development factors may then overproject ultimate. Paid Bornhuetter-Ferguson reduces direct amplification but still adds an expected unpaid component based on its selected payment pattern; retaining an obsolete unpaid proportion can overstate that component. Examine closure rates, partial payments, payment batching and paid-to-reported relationships. A timing change may warrant adjusted triangles or revised proportions, whereas higher settlement amounts may require revising the expected ultimate as well.
Worked example: A year expected to be 40% paid is actually 55% paid after faster settlements. If expected ultimate remains $10 million, using the old pattern adds $6 million of expected unpaid claims instead of $4.5 million, potentially overstating the remaining obligation.
Common mistake: Assuming paid Bornhuetter-Ferguson fully solves settlement-speed changes overlooks its dependence on a representative expected unpaid proportion.
Official syllabus reference: [2]
33. Actual-versus-expected emergence localizes projection error
An actual-versus-expected analysis compares observed payments, reported movements or counts with forecasts implied by the previous valuation. Preserve the prior assumptions so that the comparison is not contaminated by hindsight. Decompose differences by origin year, maturity, segment and component to distinguish random volatility from systematic departures. Separately reconcile ultimate revisions as payments plus the change in unpaid liability on a consistent basis. An emergence difference does not necessarily equal the ultimate revision because later expectations can offset or amplify current departures, particularly when methods use independent expected costs.
Worked example: The prior model expected $3 million of payments, but $4 million occurs. If the remaining liability falls by an additional $1 million because payments merely arrived earlier, ultimate need not change. If it falls only as expected, the extra payment may indicate adverse development.
Common mistake: Equating every dollar of excess payment emergence with a dollar of ultimate deterioration ignores revisions to the remaining payment expectation.
Official syllabus reference: [2]
34. A selected ultimate needs a component and sensitivity bridge
A final ultimate selection should reconcile to paid claims, case estimates and the additional development provision, while explaining how reliable method indications inform the choice. Quantify sensitivities to influential assumptions such as tails, expected ratios and settlement patterns. A range of method outputs is not automatically a probability interval, particularly when the methods share inputs or assumptions. Distinguish central selection, alternative scenarios and any separately required margin. The objective is a coherent estimate supported by the claim process and intended use, rather than a number chosen solely because it lies near the middle.
Worked example: A selected ultimate of $40 million consists of $25 million paid, $10 million case estimates and $5 million additional development. A tail sensitivity adds $2 million, while a higher expected ratio adds $1 million; these are identified scenarios rather than independent amounts to add automatically.
Common mistake: Calling the minimum and maximum method results a confidence interval assigns probabilistic meaning that the calculations have not established.
Official syllabus reference: [2]
Financial Reporting
35. ULAE classification defines the liability being estimated
Unallocated loss adjustment expenses represent claim-handling costs not assigned to individual claims under the analysis's chosen classification. They may include shared claims salaries, systems and management costs, while claim-specific costs may be treated separately. Establish the organization's definitions because expense classifications can differ across datasets and reporting bases. An unpaid ULAE estimate concerns future handling work for existing claim obligations, not every future expense of the claims department. Separate costs attributable to future business and avoid duplicating expenses already included in claim projections or another liability component.
Worked example: A claims department budget includes $2 million for servicing existing claims and $1 million for claims from next year's policies. An unpaid-expense analysis for the current liability starts with the existing-claim work, while the future-business portion belongs in prospective pricing or funding.
Common mistake: Reserving the entire future claims-department budget for existing claims includes work arising from future exposure and can duplicate prospective expense allowances.
Official syllabus reference: [2]
36. Paid ULAE-to-paid claim ratios can reflect mismatched activity
Historical paid ULAE divided by paid claims can provide an expense-ratio benchmark, but the numerator and denominator respond to different operational drivers. Opening work may occur before substantial claim payments, while settlement payments can arrive long after much administrative effort. Growth, shrinking inventories, wage inflation and changing average claim size can therefore distort calendar-period ratios. Review multiple periods and relevant operations before selecting a ratio for unpaid work. A high paid ratio may indicate higher handling cost, lower claim severity or payment timing rather than a stable increase in lifetime expense intensity.
Worked example: A growing insurer hires handlers and opens many claims before large indemnity payments occur. Paid ULAE rises faster than paid claims, temporarily increasing the ratio. Applying that single-year ratio without examining growth may overstate the expense rate for the existing inventory.
Common mistake: Treating a calendar-year paid expense ratio as an unchanged lifetime cost relationship ignores differences between administrative activity and indemnity payment timing.
Official syllabus reference: [2]
37. Ratio reserves need an explicit remaining-work allocation
A common ratio approach multiplies a selected ULAE-to-claim ratio by a weighted claim-liability base. Different weights represent how much associated handling work is assumed to remain for reported and unreported claims. A half-weight for case estimates and full weight for unreported claims is an assumption-driven model, not a universal rule. Broad IBNR may include development on reported claims, whose opening work is already completed. Identify that composition and any exceptional claims before applying weights. The resulting reserve should represent future handling effort, not simply a fixed percentage of an undifferentiated balance.
Worked example: With a 10% ratio, $8 million case estimates and $3 million genuinely unreported claims, specified weights of 40% and 100% give unpaid ULAE of $620,000. Changing the reported-claim remaining-work assumption to 60% increases the estimate to $780,000.
Common mistake: Applying full unreported-claim handling assumptions to all IBNR can overstate work when much of IBNR relates to already reported claims.
Official syllabus reference: [2]
38. Count-based ULAE models price future handling activities
A count-based ULAE model estimates remaining claim activities and multiplies them by expected unit costs. Separate opening, maintenance, closure and reopening when those stages have meaningfully different costs. Existing open claims usually require a different activity mix from currently unreported claims. Maintenance may depend on future open-claim years rather than just ultimate count, especially for long-duration claims. Estimate future unit costs at the relevant payment levels and ensure completed work is excluded. This structure can respond to workflow changes more directly than a claim-dollar ratio, but requires reliable operational counts and cost allocation.
Worked example: An inventory contains 500 open claims requiring $80 each to complete, plus 100 unreported claims requiring $150 each over their full lives. Expected unpaid handling cost is $55,000, before any separately modeled reopening work or future unit-cost changes.
Common mistake: Applying a full lifetime handling cost to every open claim charges the unpaid estimate for opening and maintenance work already performed.
Official syllabus reference: [2]
39. ULAE selection must separate productivity from claim severity
A ratio model links handling expenses to claim dollars, while a count model links them to activities or inventory. Evaluate which relationship better represents the operation. Rising claim severity can reduce an expense-to-claim ratio even when handlers perform the same work at the same cost. Automation may reduce opening effort but leave complex maintenance unchanged. Expense inflation can offset productivity improvements. Explain differences between methods using these drivers, and allow for implementation costs or changing workloads where relevant. Neither a lower ratio nor fewer staff necessarily means proportionately lower unpaid handling obligations.
Worked example: Average indemnity cost increases 20% while cost per handled claim stays constant. The ULAE-to-claim ratio falls, although the future cost of processing 1,000 comparable claims is unchanged. A count model helps distinguish this denominator effect from genuine administrative savings.
Common mistake: Projecting a falling ULAE ratio as productivity improvement can understate expenses when the decline is caused only by higher claim severity.
Official syllabus reference: [2]
Trending
40. Frequency and severity trends combine multiplicatively
Frequency is claim count per exposure, severity is claim amount per claim, and pure premium is their product. Annual pure-premium trend therefore equals the product of the frequency and severity growth factors, less one. Adding component percentages omits their interaction. Use consistent claim populations, development levels and exposure definitions before estimating the components. Changes in zero-claim treatment or claim counting can shift frequency and severity in opposite directions without changing aggregate pure premium. The decomposition is valuable because operational, behavioral and inflationary forces can affect the two components differently.
Worked example: Frequency decreases 3% while severity increases 8%. The pure-premium factor is 0.97 × 1.08 = 1.0476, giving 4.76% growth. A historical pure premium of $300 becomes $314.28 after one year under those assumptions.
Common mistake: Adding component trend percentages produces an approximation that can become materially inaccurate when trends or projection periods are large.
Official syllabus reference: [2]
41. Trend periods connect representative cost dates
A trend factor translates costs between representative dates for the experience and target periods. For accident-year claim costs, average accident dates are often appropriate under a specified exposure pattern. Prospective policies may generate accidents after their inception dates, so a rate implementation date is not automatically the target cost date. Determine the expected distribution of writings, policy terms and earning before selecting a midpoint. Development moves a cohort toward ultimate; trend moves its cost level through time. Keep these dimensions separate to avoid omitting or duplicating an adjustment.
Worked example: Experience represents accidents averaging July 1, 2024. Rates apply to annual policies written uniformly during 2027, whose accidents average approximately January 1, 2028 under uniform earning. The illustrative trend period is three and one-half years, rather than simply three calendar labels.
Common mistake: Trending only to the first rate-effective date can omit the later accidents covered by policies written during the prospective period.
Official syllabus reference: [2]
42. Inflation-sensitive exposures change the per-unit trend
Some exposure measures, such as payroll or insured values, increase with inflation even when physical risk volume is unchanged. When both claim amounts and the exposure denominator grow, claim cost per exposure follows the ratio of their growth factors. This is distinct from a vehicle-year measure whose units do not automatically increase with wages or prices. Align the exposure basis used in premium and claims analysis, and distinguish nominal exposure growth from real growth in activity. Otherwise an analyst can overstate the necessary rate change by applying full claim inflation to an already inflation-sensitive premium base.
Worked example: For unchanged operations, claims increase 7% and payroll increases 4%. Claim cost per payroll dollar grows by 1.07/1.04 − 1, or approximately 2.885%, rather than 7%. Additional workforce growth would require a separate exposure-volume adjustment.
Common mistake: Applying full nominal claim inflation to a payroll-based rate ignores the premium growth already generated by inflation in the exposure denominator.
Official syllabus reference: [2]
43. Standardization separates portfolio mix from within-group change
Observed aggregate frequency or severity reflects both subgroup experience and the proportions represented in the portfolio. Standardization holds selected weights constant while substituting each period's subgroup measures. For frequency, exposure weights usually provide the appropriate aggregation; for severity, claim-count weights matter. Choose a reference mix relevant to the diagnostic or forecast and explain it. Standardized change can differ from actual portfolio change without either calculation being wrong. Future pricing requires both a view of underlying subgroup trends and the expected prospective mix, rather than an automatic adoption of either historical aggregate.
Worked example: Low-risk frequency remains 0.05 and high-risk frequency remains 0.20, but the high-risk exposure share rises from 20% to 40%. Aggregate frequency rises from 0.08 to 0.11 despite no within-class deterioration. Constant-weight standardization reveals the unchanged underlying class frequencies.
Common mistake: Using exposure weights to standardize average severity can misrepresent the result because severity is averaged across claims, not exposure units.
Official syllabus reference: [2]
44. Log-linear trend regression estimates compound growth
A log-linear trend model fits the logarithm of a positive measure against time. If the fitted slope is b per year, the implied annual growth factor is exp(b), and the trend rate is exp(b) minus one. This models proportional rather than constant-dollar change. Review development completeness, mix shifts, residual patterns and sensitivity to the selected period before using the fitted slope prospectively. A statistically neat historical fit does not establish that the same economic regime will continue. Zero or negative observations also require a different treatment rather than taking an undefined logarithm.
Worked example: A fitted annual log-severity slope is 0.04. The implied compound trend is exp(0.04) − 1, approximately 4.081%, rather than exactly 4%. A two-year factor is exp(0.08), approximately 1.08329, if the fitted relationship remains applicable.
Common mistake: Interpreting the log slope as the exact percentage trend overlooks the exponential transformation needed to recover compound growth.
Official syllabus reference: [2]
45. Piecewise trend handles different historical and future regimes
A piecewise trend applies different growth assumptions over distinct intervals when one constant rate is unsuitable. Multiply the factors for each interval, using fractional years where appropriate. Historical adjustment can normalize experience through an observed inflation episode, while prospective trend reflects a separate forecast. Keep the boundary dates explicit and avoid overlapping or skipping time. A change in the selected trend should have an economic or empirical rationale rather than merely improving fit. Scenario testing is useful when the duration of an inflation regime is uncertain.
Worked example: A $1,000 severity is trended for one year at 8% and another eighteen months at 4%. The target estimate is $1,000 × 1.08 × 1.04^1.5, approximately $1,145.44. Each interval contributes only its own elapsed time.
Common mistake: Averaging two trend percentages without weighting their durations and compounding their factors can misstate the target cost level.
Official syllabus reference: [2]
46. Deductibles and limits make insured-cost trend nonlinear
Inflation in ground-up claim severity does not necessarily translate proportionately into insurer-paid severity when deductibles or limits remain fixed. For a simple per-claim deductible d and limit L above it, payment is the smaller of the positive excess over d and L. Inflation can push claims across the deductible and increase insurer payments faster than ground-up costs, while limits can suppress growth at the upper end. Analyze the relevant payment layer and distribution. Do not transfer an unlimited ground-up severity trend directly to a limited or deductible-adjusted portfolio without considering these interactions.
Worked example: A ground-up claim grows from $1,500 to $1,650 under 10% inflation. With a fixed $1,000 deductible and no binding limit, insurer payment grows from $500 to $650, or 30%. The layer's growth exceeds the underlying claim inflation.
Common mistake: Assuming insurer-paid severity always grows at the ground-up inflation rate ignores claims moving through fixed deductibles and policy limits.
Official syllabus reference: [2]
Ratemaking
47. Pure-premium pricing balances dollars per exposure
The pure-premium method starts with prospective claims and claim expenses per exposure, adds fixed expenses per exposure, and divides by the premium share available after variable expenses and selected margins. If L is claim cost, F fixed expense, v variable expense ratio and q profit plus contingency ratio, indicated premium is (L + F)/(1 − v − q). Every component must describe the same prospective coverage and exposure unit. Compare the indicated premium with current average premium on a consistent portfolio mix to derive the rate-change indication.
Worked example: Prospective claims cost $360 per vehicle-year, fixed expenses are $40, variable expenses are 20% of premium and the selected margin is 5%. Indicated premium is $400/0.75, or $533.33. Against comparable current premium of $500, the indication is a 6.67% increase.
Common mistake: Adding premium-based expense percentages directly to claim dollars applies the loading to the wrong base and fails the premium balance.
Official syllabus reference: [2]
48. The claim-ratio method uses current-level premium as its base
The claim-ratio method compares prospective adjusted claims with historical premium restated to an appropriate current rate and exposure basis. Add a fixed-expense ratio measured against that same premium, then divide by one minus variable expense and margin ratios. The result is a required premium factor, so subtract one for the percentage change. On-leveling, premium trend and claim trend address different effects and should be separately justified. A denominator left at obsolete rates can create a spurious indication even when the claim projection itself is sound.
Worked example: Adjusted claims are $7 million and current-level premium is $10 million. With fixed expenses of $0.5 million, variable expenses of 20% and margin of 5%, the required factor is (0.70 + 0.05)/0.75 = 1.00, indicating no overall change.
Common mistake: Using unadjusted historical premium after substantial rate increases can overstate the indicated increase by ignoring premium already generated at current rates.
Official syllabus reference: [2]
49. Fixed and variable expenses require different projection bases
Fixed expenses are expressed relative to an appropriate exposure or activity base, while variable expenses are commonly modeled as a proportion of premium. The labels describe the model's behavior over the relevant planning range, not an immutable property of every expense. Trend fixed dollar costs to their expected payment period using suitable cost drivers, and consider volume effects on unit expense. A commission ratio may remain stable while salary cost per policy changes with wage inflation and productivity. Avoid both treating all expenses as premium-proportional and assuming total fixed expenses remain constant under major operational changes.
Worked example: A $50 fixed expense per policy increases 6% through wage and systems costs, becoming $53. A commission remains 15% of premium. At a $600 indicated premium, those components are $53 and $90; applying wage inflation again to the commission would require separate justification.
Common mistake: Trending every expense ratio by wage inflation mixes dollar-cost inflation with expenses whose modeled amounts already vary automatically with premium.
Official syllabus reference: [2]
50. Profit and contingency provisions have a specified denominator
A selected underwriting profit or contingency provision must be interpreted on its stated base. When expressed as a proportion of premium, it reduces the premium share available to fund claims and expenses and therefore enters the denominator of the indication. A percentage markup on cost produces a different premium and cannot be substituted without conversion. The appropriate margin depends on the assignment and supporting analysis; the syllabus does not establish a universal percentage. Keep expected claim costs separate from any explicit margin so that uncertainty allowances are not unintentionally duplicated.
Worked example: Expected claims and fixed expenses total $800, variable expenses are 15% of premium and profit is 5% of premium. Required premium is $800/0.80 = $1,000. A 5% markup on the $800 cost would not provide the specified premium-based profit after variable expenses.
Common mistake: Treating a 5% premium margin as a 5% markup on costs changes the intended profit provision and understates required premium.
Official syllabus reference: [2]
51. Catastrophe loading replaces volatile experience with expected cost
Catastrophe claims are often separated because a short experience period may contain too few events to estimate their long-run expected cost reliably. Remove the defined historical catastrophe component from ordinary experience and add a prospective expected catastrophe provision on a compatible exposure, coverage and cost basis. Consider changes in location concentrations, insured values and policy terms when evaluating the loading. Distinguish the expected annual cost from any separately selected risk or contingency margin. The replacement approach requires consistent event definitions and treatment of recoveries to avoid duplication or omissions.
Worked example: Ordinary developed claims excluding catastrophes are $9 million. A selected prospective annual catastrophe allowance is $1 million for the target exposure. The expected claim provision is $10 million before other adjustments, even if the latest year happened to have no catastrophe claims.
Common mistake: Adding an expected catastrophe allowance while retaining the same catastrophe claims in ordinary experience double counts the component being normalized.
Official syllabus reference: [2]
52. Large-claim caps require prospective excess-loss loadings
Capping individual claims can stabilize an ordinary pure-premium estimate, but the prospective rate still needs the expected amount above the cap. Estimate that excess using relevant experience or an appropriate severity model, adjusted for trend, limits, deductibles and exposure changes. Maintain a consistent cap basis over time, especially when inflation changes how many claims exceed a nominal threshold. Distinguish noncatastrophe large-claim excess from catastrophe allowances when both are used. A capping threshold is an analytical choice and should not be presented as a universal professional requirement.
Worked example: Prospective capped claims are estimated at $4.2 million and expected noncatastrophe excess is $0.6 million. For 8,000 exposures, capped pure premium is $525 and excess loading is $75, giving $600 total before catastrophe, expense or margin provisions.
Common mistake: Keeping a nominal cap unchanged without reviewing inflation can shift growing amounts into the excess component and distort historical comparisons.
Official syllabus reference: [2]
53. A ratemaking credibility complement must share the target basis
Credibility in ratemaking may combine pure premiums, claim ratios or indicated rate-change factors, but each combination must use comparable quantities. A complement based on broader experience needs adjustments for coverage, cost level, exposure mix and current premium level. When blending rate-change factors, one represents no change; when blending percentage changes, zero represents no change. Consistent linear blending gives equivalent answers, but mixing a factor with a percentage does not. Select the complement for relevance and independence of information, and avoid applying trend twice when it is already embedded in the complementary estimate.
Worked example: The experience factor is 1.20 and the comparable complementary factor is 1.05. With credibility 0.40, the blend is 0.40 × 1.20 + 0.60 × 1.05 = 1.11. Equivalently, blending increases of 20% and 5% gives an 11% increase.
Common mistake: Blending a rate factor of 1.20 with a percentage change of 0.05 combines incompatible representations and produces a meaningless indication.
Official syllabus reference: [2]
54. Pure-premium and claim-ratio methods reconcile algebraically
The pure-premium and claim-ratio methods should produce equivalent overall indications when they use the same claims, expenses, exposures and current premium basis. Divide dollar totals by exposure for the pure-premium formulation or by current-level premium for the claim-ratio formulation. Differences usually reveal inconsistent bases, expense treatment, mix adjustments or rounding rather than a fundamental disagreement between the methods. Reconciliation is especially useful when separate teams prepare exposure and premium exhibits. It does not remove model uncertainty, but it detects avoidable mechanical differences before the final recommendation.
Worked example: Claims plus fixed expenses are $6 million, exposures are 10,000 and current premium totals $8 million. With 25% variable expenses and margin combined, indicated premium is $800 per exposure. The ratio method gives (6/8)/0.75 = 1.00, matching current average premium.
Common mistake: Averaging conflicting indications before reconciling their bases can hide a premium, exposure or expense inconsistency that should be corrected.
Official syllabus reference: [2]
Analyze and Evaluate Real-Life Scenarios
55. Self-insurer retention transforms ground-up claim cost
A self-insurer's retained liability depends on the applicable retention, excess protection and recovery arrangements, not only ground-up ultimate claims. For a simple per-occurrence retention R without complications, retained cost for each occurrence is the smaller of ground-up cost and R. Apply the transformation at the contractual unit, since capping an annual aggregate is generally different from capping individual occurrences. Estimate expenses and recoveries on consistent terms and identify whether excess reimbursements create separate receivables. Changed retentions can invalidate direct comparisons of historical retained development and prospective funding costs.
Worked example: Three occurrences have ultimate ground-up costs of $100,000, $400,000 and $900,000. With a $250,000 per-occurrence retention, retained claims total $600,000. Applying the retention once to the $1.4 million aggregate would incorrectly produce only $250,000.
Common mistake: Applying a per-occurrence retention to total annual claims ignores the contractual unit and can substantially understate retained expected cost.
Official syllabus reference: [2]
56. Expected-cost funding differs from a cash-payment budget
Expected-cost funding for new exposure recognizes the ultimate claims and expenses attributable to that exposure, whereas a cash budget estimates payments occurring during a particular period. Cash payments may include old claims and only part of the new year's ultimate cost. A reserve measures unpaid obligations at a valuation date and is therefore a third quantity. Define whether the decision concerns incurred-cost funding, liquidity or total asset sufficiency before combining amounts. Discounting, margins and investment assumptions should be included only on an explicitly stated basis rather than inferred from the word funding.
Worked example: Next year's new claims are expected to cost $5 million ultimately, but only $2 million will be paid that year. Another $3 million will be paid on older claims. The claims cash budget is $5 million, yet its composition differs entirely from the new year's $5 million expected cost.
Common mistake: Using next year's total expected payments as the new year's ultimate funding requirement confuses payment timing with the period generating the liability.
Official syllabus reference: [2]
57. Sparse new-business experience needs adjusted external benchmarks
A new book may lack enough emergence to support stable development or a credible internally estimated expected ratio. Build an initial expectation from relevant external or adjacent experience, adjusting explicitly for coverage, limits, deductibles, exposure mix, distribution and cost level. Distinguish a lack of volume from a lack of comparability: more data do not correct structural differences. Use early experience diagnostically and increase its influence as it becomes informative. State which assumptions can be tested soon, such as reporting counts, and which require longer maturity, such as large-claim severity.
Worked example: A new liability product uses an established book's expected cost after adjusting for higher limits and a different industry mix. Early reporting frequency is checked against that benchmark, while the actuary avoids interpreting six months of sparse payments as a reliable ultimate severity pattern.
Common mistake: Borrowing a large comparison portfolio's unadjusted claim ratio can import pricing, coverage and mix differences into a new book's reserve or rate.
Official syllabus reference: [2]
58. System conversions require a triangle movement bridge
A claims-system conversion can change identifiers, expense allocation, transaction dates or balance definitions without changing economic obligations. Build a bridge between old and new extracts at a common valuation date before interpreting development. Reconcile paid, case and count totals separately, then examine movement by origin year and component. Preserve genuine historical transactions while avoiding duplicate migrated balances or artificial closure and reopening events. An accounting-total match alone may conceal origin-period misallocation that distorts development factors. Resolve the data mechanism before changing actuarial assumptions in response to an apparent experience break.
Worked example: After migration, total reported claims reconcile, but older accident years fall while recent years rise. A record review finds that some migrated claims received conversion dates as accident dates. Correcting origin assignments removes the apparent recent-year deterioration without changing total liability.
Common mistake: Accepting an aggregate reconciliation as sufficient can miss origin-year reallocations that materially distort triangle development while leaving total claims unchanged.
Official syllabus reference: [2]
59. An inflation regime shift needs both reserve and rate analysis
A new inflation regime can affect unpaid existing claims and prospective new claims through different durations and coverage layers. Identify which costs remain exposed to future inflation, which case estimates already incorporate revised expectations and how settlement timing distributes remaining payments. Avoid applying the same blanket multiplier to paid claims, current case estimates and prospective costs. Develop coherent alternative scenarios for inflation level and persistence, then trace them through ultimate claims, unpaid liabilities and indicated rates. Scenario results describe conditional outcomes unless a probability model separately supports a distribution.
Worked example: Repair inflation accelerates after the valuation date. The actuary leaves completed historical payments unchanged, reviews whether open-claim estimates reflect revised repair costs and trends next year's expected claims over its own cost period. A longer inflation scenario increases long-duration liabilities more than quickly settled claims.
Common mistake: Applying one inflation percentage to the entire historical ultimate can inflate already paid claims and duplicate inflation embedded in revised case estimates.
Official syllabus reference: [2]
60. Reserve and rate selections share evidence but target different periods
Reserving estimates ultimate cost for exposure already incurred, while ratemaking estimates cost and premium needs for prospective exposure. Both may use the same selected historical ultimates, but pricing additionally requires future trend, mix, coverage and expense adjustments. A reserve strengthening can alter the historical cost base without translating into an equal percentage rate increase. Build a bridge from selected historical ultimate to prospective claim cost, then add pricing expenses and margins on consistent bases. Explain differences between the two decisions rather than forcing identical assumptions where their time horizons or exposure populations differ.
Worked example: A historical ultimate increases from $10 million to $11 million, but the future book has lower-risk mix and higher deductibles. Pricing starts with the revised $11 million base, then applies those documented differences and prospective trend instead of mechanically recommending a 10% rate increase.
Common mistake: Translating a reserve strengthening percentage directly into a rate change ignores prospective exposure, existing rate level, expenses and coverage differences.
Official syllabus reference: [2]
Official syllabus sources
- GI 101 Ratemaking and Reserving
- Syllabus with Learning Objectives/Outcomes and Readings – Nov 2026/Mar 2027/Jul 2027