Scoped extract
A defined slice of the filing record, delivered once as files, with its definitions and dated scope statement.
Structured P&C filing facts and carrier analytics for teams that want to work in their own research tools, models and data environments.
Part of RateFileAI. A data delivery offering—not another application subscription.
RateFileAI Data Products turns public filing observations into normalized, joinable data. Use filing and company-level facts alongside documented calculations to study carrier activity, reported changes and regulatory review.
Built for product, pricing, actuarial, regulatory, competitive-intelligence and data teams. Use the RateFileAI application to explore filings, or discuss a bounded data package for analysis in your own environment.
A defined slice of the filing record, delivered once as files, with its definitions and dated scope statement.
The same package, refreshed monthly or quarterly and delivered as files or a data feed, for your internal use.
A defined analysis built on the licensed data, scoped and quoted for the engagement.
The Texas Personal Auto pilot below is one example of a scoped extract. Every form is priced by custom quote; there is no published price.
The prepared pilot pairs structured facts with definitions, measurement boundaries and reproducible examples.
Filing identifiers, classifications, carrier relationships, lifecycle dates, reported rate impact, program premium and affected policyholders where stated.
Company-level values stay aggregated at the company level.
Filing counts and mix, cadence, review timing, pending age, explicit approval outcomes, impact distributions and comparable-peer views.
Calculations retain observation counts and exclusions.
Typed Parquet tables, a data dictionary, field availability, methodology, limitations, a versioned manifest, checksums and 20 SQL examples.
Evaluation samples and delivery require an agreed scope.
The package contains facts and calculations—not PDFs, ZIP archives, policy wording, raw correspondence or personal contact details. It does not grant application, API or source-document access.
557 Texas Personal Auto filings, submitted Sep 1, 2024–Sep 21, 2026. Counts below describe the prepared Sep 22 copy, not all Texas filings or the full five-year dataset.
| Fact family | Observed | How to read it |
|---|---|---|
| Carrier relationship | 552 of 557 filings | 118 distinct writing carriers; a multi-company filing can relate to more than one carrier. |
| Reported overall rate impact | 438 of 557 filings | A carrier-stated filing value, not an independently confirmed approved rate. |
| Reported premium change | 437 of 557 filings | The signed premium change the carrier states in the filing. |
| Reported affected policyholders | 438 of 557 filings | A separate measure from premium change. People are not deduplicated across filings. |
| Form schedule facts | 215 observations · 83 filings | Form numbers, titles, types, editions and stated actions—not full policy wording. |
| Rule schedule items | 435 observations · 158 filings | Schedule references and actions. A replacement entry does not by itself prove a numerical rule change. |
| Dated review events | 1,820 observations · 493 filings | Explicitly dated objections, responses and supported dispositions; not a complete correspondence history. |
Non-rate and actuarial extraction is selective. Coverage-change facts, compatible exposure bases and requested-versus-approved rate comparisons are not yet populated in this pilot. Unprocessed attachments and unreadable pages remain; an empty field does not mean a change never occurred.
Basis: the prepared pilot, 557 accepted filing records, measured Sep 22, 2026. Availability is not extraction accuracy. Other states, lines, periods or update schedules require a separately confirmed scope.
Each release has a defined population and observation date. Unknown, not reported and not applicable are never silently changed to zero.
Bound the jurisdiction, line and submission period. Preserve stable filing and carrier identities; disclose acquisition and field-coverage gaps.
Read explicit source fields, schedules and dated events. Normalize units and classifications while retaining source provenance and the difference between stated and calculated values.
Keep denominators, eligible dates and exclusions alongside metrics. Separate explicit approvals from broader effective outcomes; do not label open review age as approval time.
Check schemas, joins, units, content boundaries and reproducibility. Report source-comparison work separately: technical checks alone do not establish population-wide extraction accuracy.
Reported premium and policyholder totals are filing observations, not a deduplicated insurance book. No market share, profitability, unique-customer count or carrier-quality rating is inferred.
Discuss the states, lines, time period, fields and intended use with RateFileAI. Coverage, delivery and pricing are confirmed for the agreed scope.
No published Data Products price or self-service checkout is active. A pricing inquiry is not an order, a subscription or immediate access. The current prepared pilot is a fixed copy; recurring feeds and service levels are not included by default.
The contact form opens ready for a Data Products question. Add the market, period and use case you need.
Compare with the application planNo. Data Products is part of RateFileAI. It supports analysis in your own tools; the application supports interactive Search, filing review and monitoring. Data delivery rights are agreed separately from an application subscription.
No. This offering is a structured facts-and-analytics package, not a public archive of source documents. The authenticated application's source-document access follows its own permissions and delivery rules.
No. The stated pilot is a bounded observed population. A represented carrier, a supported field or a processed document does not establish complete market or attachment coverage. Every agreed delivery must retain those limitations.
No. Explicit approval metrics use a stated decision denominator and remain separate from effective-disposition metrics. Neither establishes an approved-versus-requested rate comparison or an implemented customer price.