From filing to rater: building pricing models from US rate filings

Ask a pricing team where to find the most detailed rating information in US property and casualty insurance and many will point to the state filing systems. Before an insurer can use a new rate or rating rule, most states expect it to be filed with the department of insurance. Once filed, much of that material becomes public.

So the base rates, the factor tables, the eligibility rules and often a set of worked premiums are already written down. The hard part has always been getting them out of the documents and into something that can price a quote.

Anatomy of a filing

No two filings look quite the same. The state, the line and the carrier all shape the package. Most rate and rule filings carry some mix of these parts:

  • Rate pages. The base rates plus every relativity table: territory, age, construction, protection class, deductible, limit and so on.
  • The rule manual. How the factors combine, who is eligible, how rounding works, and where minimum premiums, fees and surcharges come in.
  • The actuarial memorandum. The carrier's case for the change: the overall rate level effect and the analysis that produced it.
  • Exhibits. Loss history, trend and development, expense loads and the working behind each factor.
  • Sample premium calculations. Step-by-step examples for named risks. These are gold, because they show the order of operations and give you exact answers to check against.
  • Regulator correspondence. Objection letters and the carrier's replies. Rates sometimes change during review, and this is where you see it.

Plenty of filings also lean on a rating bureau such as ISO, NCCI or AAIS, adopting its loss costs or rules by reference instead of printing them in full.

Where to look

Most states take filings through SERFF, the System for Electronic Rate and Form Filing run by the NAIC. Many publish them through SERFF Filing Access or their own department website. What you can search, and what you can download, differs by state, and some exhibits may be kept confidential.

Rebuilding the rater, step by step

  1. Trace the lineage. One filing rarely holds the whole rating plan. Usually it amends an earlier one. Walk back to the filing that launched the programme, then forward through every change to the version in force.
  2. Lift the tables. Get every rate table into structured rows, keeping band edges and values exactly as filed.
  3. Work out the algorithm. The rule manual and the sample calculations together tell you which factors apply, in which order, and where rounding and minimums sit.
  4. Write the rules. Eligibility becomes declines and referrals.
  5. Prove it. Turn every sample calculation into a test. When the model matches all of them to the cent, it is done.
  6. Keep the paper trail. Note which filing each table and rule came from, so any number in the model can be traced to a page.

In Swallow, steps 2 to 5 map straight onto the model format. Tables become collections, the algorithm becomes a run of calculation steps, rules become exclusions and refers, and the filing's examples become the tests saved on the version.

Where AI earns its keep

A single programme can span hundreds of pages across several documents. Tables are split over page breaks, some PDFs are scans and the rules are scattered. That is exactly the kind of reading AI is good at:

  • Finding and structuring tables, including ones that run across pages, from PDFs and spreadsheets.
  • Mapping the chain, by spotting which earlier filings a document refers to and which pages it replaces.
  • Drafting the order of calculation from the rules and examples, for a person to check.
  • Reconciling the model to the filing by running every sample premium as a test and explaining any gap, such as rounding in the wrong place or a factor that never got applied.

This is the work behind Swallow's filings platform. It has ingested every California filing since 2005 and can turn a filing into a structured rating model in Swallow's JSON format, then check that model against the worked examples in the source filing. The result runs on the same Swallow engine as any other model.

AI drafts. People still check. Every table and rule should be reviewed against the filing, and any decision the filing leaves open should be made by someone who understands the product.

Know the gaps before you start

Filings are rich, but they are not always the full story:

  • Bureau content. If a carrier adopts bureau loss costs or rules by reference, the bureau manuals usually aren't in the filing. They are copyrighted and normally need a licence.
  • Confidential sections. Some states let carriers withhold parts of a filing, such as proprietary scoring models.
  • Third-party scores. Insurance scores, credit-based scores and other external data feed factors whose models are often not in the filing.
  • Filed is not always approved. Check the correspondence and the final disposition so you build the rates that were actually approved.
  • State by state. Each state has its own filing and effective date, and the same programme can differ across states.

None of these stops a build. They just need to be spotted early, then filled from the right source or covered by a written assumption.

What teams use it for

  • Moving your own filed rates onto a new engine. Your approved filing is the right reference to build and test against.
  • Entering a new state, starting from filings you already have and adjusting for local rules.
  • MGA programmes written on a carrier's filed rates.
  • Understanding the market: which factors competitors rate on, how they structure discounts and how their rate levels compare.

When you study other carriers' filings, use them to inform your own work. Your rating plan should rest on your own analysis and be filed in your own name, and bureau material should only be used under licence.

Next steps

See what a finished model looks like on our model building page, or how testing proves it prices like the source. If you have a filing you want to build from, talk to our team.

Continue reading

Swallow compared: enterprise pricing platforms, core system raters and AI newcomers

Where Swallow sits against established insurance pricing and rating platforms and newer AI-led options, on model format, testing, approvals, AI and distribution.

Building pricing models with Claude and ChatGPT: what works, what doesn't

A practical look at building insurance pricing models with Claude and ChatGPT over MCP: where AI clients help, where they trip up and how to keep people in charge.

AI in insurance pricing: closing the gap between rating guide and live model

Pricing design is rarely the bottleneck. Implementation is. How AI shortens the path from signed-off rating guide to a tested, live pricing model.

Fair value under Consumer Duty: the evidence your pricing should leave behind

What the FCA's Consumer Duty and pricing rules ask of insurance pricing teams, and the records that make fair value something you can show, not just claim.

When the customer is an AI agent: getting your pricing ready

AI assistants are starting to shop for insurance on people's behalf. Here's what your rating engine has to give them to quote your products properly.

How to connect the Swallow MCP server to Claude

Connect Claude to your Swallow pricing infrastructure using MCP to analyse models, inspect rating logic and interact with your tools using natural language

Regression testing insurance pricing: why every rate change needs a test suite

How to build a regression test suite for an insurance pricing model, from worked examples and band edges to declines, refers and real quotes.

A safer rate change: eight steps from analysis to monitoring

A repeatable process for insurance rate changes, from the change statement and draft version to tests, approval, release and monitoring, and where AI helps.

Readable by design: pricing models people can check, even when AI writes them

When AI drafts pricing logic, review becomes the slow step. Why a declarative, readable model format is faster to check and audit than generated code.

Moving off a spreadsheet rater without changing a single price

How to tell when an Excel rater has outgrown its job, what keeping it really costs, and a migration plan that uses the spreadsheet's own answers as the tests.

Starting an MGA: from rating guide to first live quote

A practical route for a new MGA's first product: agreeing terms with capacity, building and testing the model, picking channels and watching rates after launch.

AI and insurance distribution: one price, every channel

Aggregators, embedded journeys, chat, voice and AI agents all need the same thing from pricing. Why one explainable rating engine should sit behind them all.

AI in regulated industries: why explainability has to come first

Insurers can get real gains from AI and still meet what the FCA, the EU and US regulators expect, provided every decision can be explained, reproduced and signed off.

Swallow vs Earnix

Swallow and Earnix Price-It compared for insurance pricing and rating: who each is for, how models are built, tested and released, how AI is used, and distribution.

Swallow vs Guidewire PricingCenter

Swallow and Guidewire PricingCenter compared: who each suits, how each relates to PolicyCenter, how models are built, tested and released, AI and distribution.

Swallow vs Duck Creek Rating

Swallow and Duck Creek Rating compared: who each suits, suite and standalone use, how rates are built, tested and released, deployment, AI and distribution.

Swallow vs Oracle Insbridge

Swallow and Oracle Insurance Insbridge Enterprise Rating compared: architecture, how rates are built and changed, testing, integration, AI, and how to migrate.

Swallow vs Akur8 Deploy

Swallow and Akur8 Deploy compared: where each rating engine fits, how rates reach production, testing and sign-off, how AI is used and when to pick which.

Swallow vs hyperexponential (hx Renew)

Swallow and hyperexponential's hx Renew compared: who each suits, Python models versus readable JSON, testing and approvals, AI and the Guidewire deal.

Swallow vs WTW Radar

Swallow and WTW Radar compared for pricing and real-time rating: who each suits, how models are built and changed, testing and approvals, and AI features.

Swallow vs building a rating engine in house

Build or buy? A fair look at writing your own insurance rating engine versus using Swallow: testing, versioning, audit, serving at volume and rate changes.

How to connect the Swallow MCP server to ChatGPT

Connect ChatGPT to your Swallow pricing infrastructure using MCP to analyse models, inspect rating logic and interact with your tools using natural language

Swallow Data: Live insight into your pricing performance

See how Swallow’s Data area gives you real-time visibility over quotes, performance, and customer behaviour across your entire pricing model

Swallow Tests: Validate your pricing with real-world scenarios

See how Swallow’s Tests area lets you simulate quotes, inspect calculations, and perfect your pricing model before publishing

Swallow Build: Bring your pricing model to life

A quick look at how Swallow’s Build area lets you edit, test, and publish pricing models with complete control and instant feedback

Swallow Overview: Core features at a glance

See how the AI actuary inside Swallow turns a simple prompt into a fully tested and deployable insurance pricing model for electric vehicles in just a few clicks

Why Modern Insurers Are Moving to AI-Powered Enterprise Pricing Engines

A look at how AI is transforming insurance pricing, from spreadsheet-based models to enterprise-grade rating engines built for speed, consistency, and control

Swallow / MGT

How MGT use Swallow to power AI-driven pricing, accelerate model updates and support fast, reliable commercial insurance quoting.

AI Agent for Insurance Products

Sam talks through our new AI Agent for Insurance products. Get a new Insurance product built and live within a couple of minutes.

Swallow / Ouch!

How Ouch! used Swallow to launch digital takaful products faster, with transparent pricing, audit readiness and seamless model updates.

Pricing Pain Point #4 - Slow deployment

Whilst the modelling process is where pricing strategy begins, getting changes in front of customers is where the rubber hits the road and new pricing is tested with real customers. Moving quickly to make changes to live pricing offers pricing teams an opportunity to respond to the market, test and iterate, and roll out new products.

Pricing Pain Point #3 - Testing concerns

With pricing critical to growth and profitability, businesses must understand the impact of any price changes, as well as ensure what goes live to customers is identical to that modelled. With pricing driven by complex financial models, this is particularly true - a percentage point error in the code deployed could easily lead to a significant financial impact.

Swallow / Open

How Open used Swallow to launch embedded insurance in the UK faster, with flexible pricing, rapid updates and lower operational cost.

Pricing Pain Point #2 - Lengthy process

In any fast moving business, having a clear record of decisions, changes and their impacts is key to operating efficiently and successfully. For regulated industries, a clear governance process is a requirement and critical to ensuring compliance with local regulations.

Pricing Pain Point #1 - Data issues

Underlying all pricing strategy is data, whether it be on the market and competition or a company’s own quote, sales and cost data. Collecting this data and using it to inform future pricing decisions is one of a pricing team’s key objectives.

Swallow / Rivr

How Rivr uses Swallow to deliver pricing models faster, with better governance, smoother client handovers and one-click deployment.

What we've learned about pricing

Over the past few months, we've talked to over 100 pricing and technology professionals from a range of industries. From our conversations, many pricing pain points have emerged, helping us to better understand the challenges businesses face and inform the direction of our platform.

Why I created Swallow

Financial pricing models (think insurance, credit, mortgages, financing, leasing, memberships) have, and continue to be, designed in spreadsheets and published through in-house custom code or legacy enterprise software. Pricing changes can take weeks instead of hours.

We feel you, pricing is hard...

Dynamic pricing is hard to create and serve to your customers. Because it is hard, it can become a technical concern rather than a business concern. Here be where the dragons lie.