Tutorials › CAS Exam 8 - Advanced Ratemaking › The Rate Filing Lifecycle

CAS Exam 8 · Rate Regulation and Filings · Tutorial 892 of 989

The Rate Filing Lifecycle

Learn how to manage a rate filing as a controlled sequence of actuarial decisions, supporting documentation, regulatory responses, and implementation actions.

Intermediate 12 min read

What You'll Learn

  • Distinguish a filing’s proposed change from the analysis supporting it and the final regulatory disposition
  • Organize the decisions and records needed as a filing moves through its lifecycle
  • Reconcile a proposed portfolio change using premium-weighted segment changes
  • Manage regulatory questions with traceable responses and controlled document versions
  • Translate a disposition into implementation and post-filing controls

Why the Filing Lifecycle Matters

A rate filing is not just a rate indication or a set of exhibits. It is a documented process that connects an insurer’s proposed action to its supporting analysis, the regulator’s review, and the rates ultimately implemented. Each stage should leave a clear record of what was decided, by whom, on what basis, and in which version of the filing.

This tutorial follows that process at a general level. Specific filing pathways, jurisdictional requirements, and the detailed construction of actuarial exhibits vary and should be addressed for the relevant filing. The lifecycle framework helps an actuary keep those distinct decisions connected without treating a proposal, a submission, and an approval as interchangeable.

Definition: The rate filing lifecycle is the controlled sequence in which an insurer defines a proposed rate action, assembles and validates its supporting materials, submits them through an applicable pathway, responds to regulatory review, records the disposition, and implements the resulting rates subject to the applicable requirements.

The Main Stages and Their Records

The stages are related but not identical. For example, an indicated change is an analytical result; a proposed change is a business and actuarial recommendation; a filed change is what is submitted; and the disposition is the regulator’s decision or other formal outcome. A sound filing record makes each transition visible.

1
Define the proposed action.
State the product and business covered, the intended change, the proposed effective timing, and the decision owner. Record the reason for proposing the action and how it relates to the supporting analysis. Do not imply that an analysis result automatically determines the proposal.
2
Prepare and validate the filing materials.
Assemble the required forms, exhibits, explanations, and supporting records for the applicable pathway. Check that totals, labels, assumptions, and versions agree across the package. Identify any difference between the analytical result and the proposal and explain it in the filing support.
3
Submit and preserve the record.
Record what was submitted, when it was submitted, the applicable tracking identifier, and the exact document versions. Preserve a reproducible copy of the package. Submission is a procedural milestone; it is not itself a decision on whether the proposal may be used.
4
Manage regulatory review.
Log each question or request, its due date when specified, the responsible owner, and the response status. Prepare responses that answer the question directly, identify affected material, and supply revised support when needed. Keep the original and revised versions distinguishable.
5
Record the disposition and control implementation.
Document the outcome and any conditions or revisions, then compare it with the proposal and the submitted version. Ensure implementation uses the rates and timing permitted by the applicable disposition. Retain evidence of the final system configuration and any required follow-up.

A practical filing register can make these transitions auditable. It commonly identifies the filing owner, product and scope, filing pathway, submission date, current status, outstanding questions, response deadlines, version identifiers, disposition, and implementation status. These are management controls, not substitutes for the requirements that apply to a particular jurisdiction and line.

Connecting the Proposal to the Exhibits

One important lifecycle control is to verify that the proposed portfolio-level change is consistent with the segment changes shown in the supporting materials. If segment \(j\) has baseline premium \(P_j\) and a proposed percentage change \(g_j\), the static premium-weighted change is:

$$ g_{\text{portfolio}} = \frac{\sum_j P_j g_j}{\sum_j P_j} $$

Here, \(P_j\) is the baseline premium for segment \(j\), expressed on a consistent basis, and \(g_j\) is the proposed proportional change for that segment. This is a reconciliation of the changes against the stated baseline; it is not, by itself, a forecast of future written or earned premium. It assumes the stated baseline weights are the weights being used for the calculation and does not account for changes in mix or policyholder behavior.

The formula follows from a direct roll-up. The baseline total is \(\sum_j P_j\). Under the stated percentage changes, the static premium change for segment \(j\) is \(P_jg_j\), so the total change is \(\sum_j P_jg_j\). Dividing that change by the baseline total gives the overall percentage change. Since \(P_j\) can differ by segment, taking an unweighted average of the segment percentages generally does not produce this result.

Worked Example: Reconciling Segment Changes to the Proposal

A hypothetical filing covers three segments. The baseline premiums are $2,000,000, $3,000,000, and $1,000,000. The proposed changes are increases of 6%, 2%, and a decrease of 1%, respectively. The filing summary states an overall increase of 3%. Check whether the summary agrees with the segment changes on this static baseline.

Method. Calculate each segment’s dollar change, sum the changes, and divide by total baseline premium.

Segment 1 changes by \( \$2{,}000{,}000 \times 0.06 = \$120{,}000 \). Segment 2 changes by \( \$3{,}000{,}000 \times 0.02 = \$60{,}000 \). Segment 3 changes by \( \$1{,}000{,}000 \times (-0.01) = -\$10{,}000 \).

The total baseline premium is \( \$2{,}000{,}000 + \$3{,}000{,}000 + \$1{,}000{,}000 = \$6{,}000{,}000 \). The total static change is \( \$120{,}000 + \$60{,}000 - \$10{,}000 = \$170{,}000 \).

Therefore, the implied overall change is \( \$170{,}000 / \$6{,}000{,}000 = 0.028333\ldots \), or 2.8333% to four decimal places. The stated 3% summary does not exactly reconcile: at 3%, the implied static dollar change would be \( \$6{,}000{,}000 \times 0.03 = \$180{,}000 \), which is $10,000 higher.

Check. The segment changes sum to $170,000, and dividing by the $6,000,000 baseline reproduces 2.8333%. The filing team should investigate whether the summary is rounded, uses different weights, or contains an error, and document the resolution. The common mistake is to average 6%, 2%, and −1% equally, obtaining 2.3333%; that ignores the unequal baseline premiums.

Preparing a Submission as a Controlled Package

Before submission, the filing team should be able to answer three questions: What action is being requested? What evidence supports it? Can a reviewer reproduce the important connections between the proposal and its exhibits? These questions apply regardless of the specific actuarial methods used in the supporting analysis.

  • Make the requested action explicit. State the proposal in a consistent location and ensure the narrative, exhibits, and implementation materials refer to the same action.
  • Keep support traceable. Identify data sources, selections, assumptions, and material calculations in a way that permits review. A short explanation of a choice can be more useful than an unexplained number.
  • Run cross-document checks. Compare totals and labels across exhibits. Confirm that the proposal described in the narrative matches the changes represented in the supporting materials.
  • Control versions. Mark drafts, submitted materials, responses, and revised materials so that no one mistakes a working copy for the version on record.
  • Separate status from conclusion. “Submitted,” “under review,” and “disposed” describe different states. Do not treat a filing receipt or a reviewer’s question as the final outcome.

Worked Example: Checking the Proposed Change Before Submission

A hypothetical insurer is preparing materials for a portfolio with baseline premium of $15,000,000. The actuarial analysis supports an indicated increase of 7%, while management proposes a 4% increase. The draft summary says the proposed change produces a static premium increase of $600,000 and describes the proposal as equal to the indicated change. Identify what must be corrected or documented before submission.

Step 1: Verify the static amount. The proposed 4% change gives \( \$15{,}000{,}000 \times 0.04 = \$600{,}000 \). Thus, the stated static dollar increase is arithmetically consistent with the proposal and baseline.

Step 2: Compare proposal and indication. The proposal is 4% and the indication is 7%, a difference of \(7\%-4\%=3\) percentage points. The statement that the proposal equals the indicated change is incorrect.

Step 3: Resolve the documentation issue. Correct the draft wording so it distinguishes the 4% proposal from the 7% indication. The filing support should state the reason for proposing less than the indicated amount and identify the decision basis and approval record. The actuary should also check whether the stated $15,000,000 baseline is the same basis used for the static amount and the proposal’s supporting exhibits.

Step 4: Recheck the package. Confirm that every occurrence of the proposal shows 4%, that the static amount remains $600,000 on the stated baseline, and that no narrative says the proposal is 7%. Record the reviewed document version.

Check. The math supports $600,000, but it does not support describing the proposal as equal to the 7% indication. The common mistake is to treat an indicated result and a selected proposal as the same decision.

Regulatory Questions and Disposition

Regulatory review can lead to questions, requests for clarification, revised materials, or a disposition. A response should be complete enough to make the issue reviewable: restate the question, provide a direct answer, cite or attach the relevant support, and identify any changed material. If a response changes an exhibit or proposal, the team should assess which other documents must also be updated.

A disposition must be read as a decision with its actual terms, not as a general signal that the original submission is ready for use. The team should record what was permitted or required, what version controls, and any applicable timing or conditions. Where a response or disposition is ambiguous, the responsible filing team should obtain appropriate clarification rather than infer a broader authorization.

Worked Example: Responding to a Change in the Requested Amount

A hypothetical filing proposes a 5% increase on a $20,000,000 baseline, a static increase of $1,000,000. During review, the regulator asks the insurer to revise its request to 3.5%. The insurer decides to submit revised materials using that amount. Calculate the revised static increase and the reduction from the original proposal, then identify the lifecycle controls needed.

Step 1: Calculate the revised amount. The revised increase is \( \$20{,}000{,}000 \times 0.035 = \$700{,}000 \).

Step 2: Calculate the change from the original proposal. The original static increase was \( \$20{,}000{,}000 \times 0.05 = \$1{,}000{,}000 \). The reduction is \( \$1{,}000{,}000-\$700{,}000=\$300{,}000 \), equivalent to \(5.0\%-3.5\%=1.5\) percentage points of the baseline.

Step 3: Control the response. The response should identify the requested revision, submit or identify the revised materials, and explain any resulting changes to the package. The filing register should record the request, response date, responsible owner, and revised version. The team should retain the original submission so the change remains traceable.

Step 4: Control the disposition and implementation. The insurer must evaluate the actual formal disposition and its terms; the request alone should not be treated as the disposition. If the 3.5% version is ultimately the version permitted for use, implementation controls should verify that the configured rates and applicable timing match that version.

Check. The revised static increase is $700,000, which is $300,000 below the original $1,000,000. The common mistake is to calculate the reduction as 3.5% of the original $1,000,000; the change is 1.5 percentage points of the $20,000,000 baseline.

Common Lifecycle Traps

  • Confusing the indication with the proposal. An indicated change is analytical support. A selected proposal may differ and should be clearly identified and explained.
  • Assuming submission means acceptance. A submission record proves that materials were sent; it does not establish the final disposition or permission to implement.
  • Using inconsistent versions. A response can change the proposal or exhibits. Keep each version identifiable and use the controlling version for any subsequent action.
  • Answering a question without tracking its consequences. A revised figure may require changes to the narrative, calculations, or implementation materials. Recheck linked documents rather than editing only the page named in a question.
  • Ignoring the basis of a reconciliation. A percentage change depends on its stated baseline and weights. Label the basis and do not present a static calculation as a forecast that accounts for mix or behavior.
Key takeaway: Treat a filing as a traceable chain of decisions and records: define the proposal, validate the support, preserve the submission, manage review, record the disposition, and verify implementation against the controlling outcome. This process orientation is aligned with the CAS Exam 8 (Advanced Ratemaking) syllabus.

Check Your Understanding

For each hypothetical situation, identify the relevant calculation or lifecycle control. Answers are provided for checking.

  1. A filing has baseline premiums of $2,000,000, $6,000,000, and $4,000,000, with proposed changes of 4%, 3%, and −1%. Calculate the portfolio-weighted static change and its dollar amount. (Answer: dollar change \(=\$80{,}000+\$180{,}000-\$40{,}000=\$220{,}000\); weighted change \(=\$220{,}000/\$12{,}000{,}000=1.8333\%\).)
  2. A proposal is 5% on a $20,000,000 baseline, while the supporting analysis indicates 8%. A draft says the proposal equals the indication. What static dollar increase does the proposal imply, and what documentation issue must be resolved? (Answer: $1,000,000; correct the statement and document the reason and decision basis for proposing 5% rather than the indicated 8%.)
  3. A regulator requests a revised proposal of 2.5% on a $12,000,000 baseline, replacing a 4% proposal. Calculate both static increases and their difference, then name one version-control action. (Answer: revised increase \(=\$300{,}000\); original increase \(=\$480{,}000\); reduction \(=\$180{,}000\); retain and distinguish the original submission from the revised response version.)
  4. A filing response changes one exhibit total from $900,000 to $840,000, but the narrative still cites $900,000. What should the filing team do before treating the response package as complete? (Answer: reconcile the narrative and any linked materials to the revised $840,000 exhibit, verify the calculation and version consistency, and preserve the original and revised packages as distinct records.)
  5. A filing has been submitted and has an assigned tracking identifier, but regulatory review is ongoing and no disposition has been recorded. What status is established, and what status is not established? (Answer: submission is established; approval or other final disposition and authority to implement are not established.)
Clinical Biostats