State filing requirements and checklists

Where requirements come from

Statutes

The insurance code sets the filing obligation itself (what must be filed, by whom and when), the rate standards, the content rules for policy forms, and line-specific mandates such as required coverages, cancellation and nonrenewal notice rules, and restrictions on rating variables. See Prior approval, file-and-use and use-and-file for how rating laws differ.

Regulations

Administrative rules implement the statute. They often define what a complete filing contains, set data and exhibit expectations for rate filings, prescribe readability or format standards for forms, and specify required notices.

Bulletins, circular letters and orders

Departments use bulletins and similar notices to announce new expectations, interpret a statute, require a certification or data call, or respond to an event. Bulletins can be issued, amended and withdrawn quickly, which makes them the layer most likely to be missed.

SERFF General Instructions and Filing Rules

Each participating state publishes instructions inside SERFF: General Instructions that apply to all of the state's filings, and Filing Rules that apply by type of insurance and filing type. The NAIC's state participation page notes that each state's submission requirements are in SERFF Filing Rules, which filers see after signing in. They translate the law into the submission itself: which filing types the state accepts, which attachments are required on which schedule, what goes in the filing description, which state-specific fields must be completed, and how filing fees are calculated and paid. Many states also publish general filing instructions on their own websites.

Review Standards Checklists and state forms

The NAIC's Uniform Review Standards Checklists were designed to help insurers verify a state's filing requirements before filing. They list the statutes, regulations, bulletins and case law that apply to a product, by line. The NAIC publishes 20 property and casualty checklists, from auto liability and homeowners to workers' compensation, plus one for life, accident and health, annuity and credit. Some states post completed checklists on their websites; others build the contents into their SERFF requirements. Some make the checklist itself a required attachment. New York, for example, says attaching the appropriate Review Standards Checklist is mandatory for every SERFF filing and requires a rate filing sequence checklist for rate and rating rule filings.

States also prescribe their own forms: certifications of compliance, actuarial certifications, rate filing summaries, and line-specific questionnaires.

Uniform transmittal fields and the Product Coding Matrix

The NAIC's uniform transmittal document fields are built into every SERFF filing, and the uniform Product Coding Matrix supplies the type of insurance and sub-type codes that decide which Filing Rules apply. Getting the code right is itself a requirement. See Rate, rule and form filings.

The NAIC Product Filing Review Handbook

The handbook is not a source of state requirements, but it explains how reviewers approach rate, rule and form filings: the rate standards, the data and adjustments a property and casualty rate review expects, and the purpose of form review. It is useful for anticipating what a reviewer will look for beyond the literal checklist.

Why missing items cause rejections and objections

The handbook describes a typical review sequence. At intake, a complete filing is assigned to a reviewer; an incomplete one may be rejected or met with a request for more information. The reviewer then checks the filing for completeness and compliance, and deficiencies come back to the filer in writing.

Missing items surface in a few predictable ways:

• Rejection at intake. Some states reject filings that do not follow their instructions instead of objecting. New York's guidelines say filings that do not conform to its general instructions or filing rules will be rejected, as will filings with attachments on the wrong schedule.
• Objections for missing support. A rate filing without the expected exhibits, or a form filing without a redline, draws an objection that adds a round of correspondence. In prior approval states, the review clock may not run, or may restart, until the information arrives.
• Content objections that trace back to a requirement. A form missing a mandated provision, or a rate filing using a restricted rating variable, is a requirement miss even though it shows up as a substantive objection.

Most of these objections are avoidable. A checklist built before the filing is drafted catches them earlier and more cheaply than a reviewer does. See SERFF objections.

Building a requirements checklist for a filing

Build the checklist per filing, not per state. The same state has different requirements for a homeowners rate filing and a commercial auto form filing.

1. Fix the filing's identity. State, type of insurance, sub-TOI, filing type (rate, rule, form or a combination), the companies filing, whether this is a new program or a revision, and whether it adopts or deviates from advisory organization material.
2. Pull the SERFF instructions. Read the state's General Instructions and the Filing Rules for that TOI and filing type. List every required attachment and schedule entry, every state-specific field and the fee rule.
3. Add the law. From the statute, regulations and the applicable review standards checklist, list the content requirements the filing must meet: mandated provisions, notice requirements, rating restrictions, data and exhibit requirements.
4. Add current guidance. Search the department's bulletins and notices for anything that applies to the line or filing type, including temporary requirements such as data calls or catastrophe-related moratoria.
5. Add filing-specific items. Some requirements are triggered by what the filing does: a new rating variable, use of a model, a rate change above a threshold, a coverage reduction, a change to credit-based insurance scores. Note each trigger and whether it applies.
6. Record a source for every row. Each item should cite the statute section, regulation, bulletin, Filing Rule or checklist it comes from, with the date you checked it. A row without a source cannot be verified later and is hard to defend in an objection response.
7. Assign and track. Mark each row with its owner, the document that satisfies it and its status. Before submission, every row should be satisfied, marked not applicable with a reason, or explained in the filing.

Keeping it current

Requirements drift. A checklist that was right last year may not be right this year.

• Re-pull SERFF instructions for every filing. States update General Instructions and Filing Rules without much notice. Check them at the start of each project, not from a saved copy.
• Watch the bulletin page. Subscribe to department notices where available, and check bulletins issued since the last filing in that line.
• Track the Product Coding Matrix. Updates to the matrix take effect January 1, which can change the sub-TOI a filing should use.
• Note platform changes. The NAIC is migrating states to a modernized SERFF in phases. A state's screens and instructions may change when it moves.
• Learn from objections. When a reviewer asks for something the checklist did not include, add it with the objection as its source. Recurring objections across filings are a sign that a requirement is missing from the checklist itself.
• Date-stamp the checklist. Keep the date each source was last verified, so the next filer knows what to recheck.