Why Filing Requirements Must Be Checked by Jurisdiction and Line
A rate filing is not governed by one universal checklist. Requirements can vary by jurisdiction, insurance line, type of change, filing pathway, and the date on which a filing is made. One authority may require advance review for a rate change but allow certain form changes to take effect after filing. Another may require a separate submission for each line, or additional exhibits for a particular type of change. A requirement that applied to one filing therefore cannot safely be assumed to apply to another.
For an actuary, the practical task is to identify the rules that govern the particular submission and verify them before preparing or scheduling it. This tutorial is aligned with the CAS Exam 8 (Advanced Ratemaking) syllabus. The examples use invented jurisdictions and rules solely to demonstrate the verification process; they do not describe actual regulatory requirements.
Identify the Requirement Before Building the Package
Start by describing the filing precisely enough to find the applicable rule. At a minimum, identify the jurisdiction, line of insurance, kind of change, affected forms or rates, and intended effective date. The required pathway may depend on those distinctions. For example, a rule for a rate change does not automatically establish the procedure for a form revision, even when both changes are part of the same business initiative.
Check requirements as separate questions rather than treating “the filing rules” as a single item:
- Pathway: Must the submission receive approval before use, may it be used after a stated waiting period, or does another process apply?
- Forms: Are forms submitted with the rate materials, in a separate filing, or only when forms are changed?
- Timing: What event starts the clock, which days count, and is the stated period a deadline, a waiting period, or a review target?
- Supporting materials: Which exhibits or explanations are required for this line and this type of change?
- Review procedure: How are objections, requests for additional information, amendments, and approval communicated?
These categories can interact. A filing may have one pathway for rates and another for forms; a required exhibit may depend on the type of change; and a completeness review may affect when a review period begins. The Rate Filing Lifecycle provides the general sequence of filing and review. Here the emphasis is on checking which specific requirements apply within that sequence.
How to Verify Applicable Requirements
Use current, authoritative materials for the relevant jurisdiction and line. Depending on the regulatory system, useful sources may include statutes or regulations, current regulator instructions, official filing manuals, submission-system guidance, and written communications from the regulator. A secondary summary, old checklist, or prior submission can help locate a requirement, but should not substitute for checking the current controlling source.
Record enough detail to make the verification reproducible: the source and version or date, the section or instruction relied upon, the jurisdiction and line, the filing type, and any unresolved interpretation. Confirm that the source is current as of the planned submission, not merely as of the last time a similar filing was made. If sources appear inconsistent, do not choose the more convenient rule by assumption. Check for updates, determine which source controls, and obtain clarification from the appropriate compliance, legal, or regulatory contact when needed.
Write down the jurisdiction, line, change type, affected rate or forms, filing pathway if known, and planned effective date. Avoid searching using a broad label such as “rate filing” alone.
Check current official rules and instructions for the identified jurisdiction and line. Confirm that each source addresses the filing type in question.
Record the required submission method, documents, applicable dates, review steps, and conditions for use. Mark whether each item applies to rates, forms, or both.
Check what starts each clock, how days are counted, whether an incomplete submission affects timing, and whether a line-specific or change-specific exception applies.
Save the source and verification date with the filing workpapers. Recheck if the submission date, effective date, filing content, or applicable instructions change.
Deadlines, Waiting Periods, and Review Targets
Similar-looking time periods can have different meanings. A rule may require filing a specified number of days before use. A separate rule may state a review target, which describes an expected process rather than guaranteeing approval by that date. A waiting period may allow use after time has passed only if the applicable conditions are met. Do not treat these as interchangeable.
For a requirement expressed as “at least \(L\) calendar days before the effective date,” the minimum lead time is the calendar-date difference between the filing date and the effective date, under the counting convention specified by the authority. If the rule excludes the filing date and measures the interval up to the effective date, the test is:
This relation follows directly from the requirement: the filing must precede the planned use date by no fewer than \(L\) calendar days. It does not establish how a different rule counts days. If the instructions use business days, count business days; if a receipt timestamp, completeness determination, or other event starts the clock, use that stated event instead. When the rule does not specify an important counting detail, verify it rather than silently supplying a convention.
| Item to verify | Why it matters | Common assumption to avoid |
|---|---|---|
| Filing pathway | Determines whether approval, a waiting period, or another process applies | Every rate or form change follows the same pathway |
| Clock start and day count | Determines the earliest or latest permissible date | All stated days are calendar days or start on the same event |
| Required exhibits | Determines whether the submission contains line- and change-specific support | A prior filing’s exhibit list is universally complete |
| Review procedure | Clarifies how completeness, questions, amendments, and decisions are handled | A review target guarantees a decision by that date |
Worked Example: Separating Rate and Form Pathways
A carrier plans a hypothetical 6% rate change for personal auto in the invented jurisdiction of Delta. It does not plan to change any policy form. Delta’s fictional current instruction sheet says: rate changes require prior approval; a stated 30-calendar-day review target is not a guaranteed decision date; and a form submission is required only when forms change. Rate submissions go through the jurisdiction’s electronic portal and include an actuarial memorandum and a policyholder impact summary. Determine the applicable package and what can be concluded about timing.
Step 1: Classify the change. This is a personal auto rate change. No form is changing, so the form-submission condition in the hypothetical instruction sheet is not triggered.
Step 2: Select the pathway. Delta specifies prior approval for rate changes. Therefore, the carrier must not treat submission alone, or passage of a set number of days, as permission to use the rates.
Step 3: Identify the specified package. The submission must use the electronic portal and include the actuarial memorandum and policyholder impact summary. The invented rules given in the problem do not require a form submission when forms are unchanged.
Step 4: Interpret the review period. The 30-calendar-day period is a review target, not a guaranteed decision date. It cannot be used to promise approval or to set an effective date on the assumption that approval will arrive on day 30. The carrier must plan for the required approval and confirm any other applicable timing instructions.
Check. The result uses the rate pathway, not a form pathway; includes both listed exhibits; and does not convert a review target into permission to use the rates. The common mistake is to assume that a 30-day review target creates automatic approval after 30 days.
Worked Example: Testing a Minimum Filing Lead Time
In a separate invented jurisdiction, Cedar’s hypothetical instruction for a specified commercial property rate filing requires submission at least 45 calendar days before the planned effective date. The rule counts the date difference in calendar days. A carrier submits on August 20, 2027, and proposes an October 1, 2027 effective date. Does the filing meet the stated lead-time requirement?
Step 1: State the test. The required date difference must be at least 45 calendar days:
Step 2: Count the interval. From August 21 through August 31 there are 11 days. September contributes 30 days, and October 1 contributes 1 day. The total is \(11+30+1=42\) calendar days.
Step 3: Compare with the requirement. The filing has 42 days of lead time, which is 3 days short of the required 45. It does not meet the stated condition.
Step 4: Find the latest compliant date. October 1 minus 45 calendar days is August 17, 2027: August 18–31 contributes 14 days, September contributes 30, and October 1 contributes 1, for \(14+30+1=45\). Under the stated counting convention, an August 17 submission meets the minimum; August 20 does not.
Check. The date arithmetic and comparison agree: 42 is less than 45, and the proposed filing is 3 days late relative to the minimum lead time. The common mistake is to count only the remaining days in August and overlook all 30 days of September and the effective date when calculating the interval.
Line-Specific Exhibits and Completeness
Supporting materials are not interchangeable across lines. A jurisdiction may require a particular explanation or exhibit for one line or change type but not another. A checklist from a prior filing is useful as a starting point, not proof that the current package is complete. For each requested item, verify that it applies to the filing at hand and that the submitted material actually addresses it.
Completeness is also a procedural question. Some systems distinguish receipt of a submission from acceptance as complete, and a request for missing information may affect the review process. Do not assume that filing a package starts every applicable clock or that a missing item can be supplied without procedural consequences. Check the instructions for how deficiencies, responses, amendments, and revised submissions are handled.
Worked Example: Checking a Line-Specific Exhibit List
A carrier in the invented jurisdiction of Mesa proposes a hypothetical homeowners rate change that includes a change to its catastrophe provision. Mesa’s fictional checklist for this type of homeowners filing requires an electronic transmittal, an actuarial memorandum, a county-level policyholder impact summary, and an exhibit supporting the changed catastrophe provision. It requires a form submission only if policy forms change. The carrier has submitted the first three items but has not changed policy forms and has not included the catastrophe exhibit. Determine whether the package meets the stated checklist.
Step 1: Match the rule to the filing. The line is homeowners and the change includes the catastrophe provision. The stated special exhibit condition therefore applies under the invented checklist.
Step 2: Check each listed item. The electronic transmittal is present. The actuarial memorandum is present. The county-level policyholder impact summary is present. The catastrophe-support exhibit is absent.
Step 3: Evaluate the form condition separately. Forms are unchanged, so the checklist’s conditional form-submission requirement is not triggered. This does not excuse the missing catastrophe exhibit.
Conclusion and action. The package does not meet the stated checklist because one required exhibit is missing. The carrier should obtain and submit that exhibit, following the applicable instructions for supplementation and review. The common mistake is to treat a generally complete package—or a form submission—as a substitute for the line- and change-specific support explicitly required.
Check. Three unconditional items are present, the conditional form requirement does not apply, and the required catastrophe exhibit is absent. The completeness conclusion follows from the missing exhibit alone.
Common Traps in Jurisdictional Verification
- Copying a prior filing checklist without checking its scope. The earlier filing may have involved a different jurisdiction, line, change type, or version of the instructions.
- Combining rate and form rules. A rate pathway does not automatically determine the form pathway; verify each separately.
- Confusing a review target with an approval deadline. An expected review period does not necessarily authorize use when it expires.
- Counting days using an unstated convention. Calendar days, business days, receipt dates, and completeness dates can produce different results.
- Relying on an old secondary summary. Use current official materials to verify the applicable rule and record the source date.
- Assuming that all required exhibits apply to every filing—or that none do. Determine whether each item is universal, line-specific, change-specific, or conditional.
The practical standard is not “use the last checklist that worked.” It is “verify the applicable requirements for this filing, record the basis, and recheck if the facts or instructions change.” This disciplined approach reduces avoidable delays and helps ensure that a filing is not scheduled or assembled on the basis of a rule that does not apply.
Check Your Understanding
For each invented scenario, use only the rules stated in the question. Each rule is hypothetical and is not a statement of any actual jurisdiction’s requirements.
- An invented jurisdiction requires prior approval for a homeowners rate change and lists a 20-day review target that is explicitly not an automatic-use period. The carrier has filed and 20 days have passed without a decision. What can it conclude about using the new rates? (Answer: It cannot conclude that the rates may be used; prior approval is still required.)
- An invented rule requires submission at least 30 calendar days before use, counting the date difference. A filing is submitted on May 6 for a June 4 effective date. The interval is 25 days from May 7–31 plus 4 days in June, or 29 days. Does it comply, and what is the latest compliant filing date? (Answer: No; it is 1 day short, and May 5 is the latest compliant date.)
- A fictional commercial auto checklist requires a transmittal and actuarial memorandum for every rate filing, plus an impact summary only when the proposed change affects policyholder premiums. The proposed change affects premiums. The submission includes the transmittal and memorandum but not the impact summary. Is the listed package complete? (Answer: No; the conditional impact-summary requirement applies and the summary is missing.)
- A fictional jurisdiction uses separate rate and form submissions. A carrier changes rates but not policy forms. Its old checklist includes a form submission, but the current instruction says forms are submitted only when changed. What should the carrier do, and what should it verify before finalizing the package? (Answer: Do not include a form submission solely because the old checklist did; verify the current rate-submission requirements, including the applicable materials and timing.)
- A fictional rule says a 15-business-day review period begins only after the regulator accepts a submission as complete. The initial package is received on Day 0, and the regulator identifies a missing exhibit before accepting it as complete. Has the 15-business-day clock necessarily started at receipt? (Answer: No; under the stated rule, it begins only after acceptance as complete, so the carrier must follow the deficiency and completion procedure.)