Skip to main content
Start with a Filing ID from discovery and use connection setup. These reads inspect stored extraction results; they do not start extraction, recalculate rates, or acquire documents.

​
Establish what is available

Florida IRFS currently has unsupported forms/rate extraction. An IRFS filing can still have stored PDFs. A SERFF filing can have stored PDFs while its supported forms endpoint returns no rows and its rate aggregate is null. These states are consistent: document storage and extraction coverage are separate. The file inventory’s textAvailability and downloadAvailability can be unknown. Use the corresponding content operation to learn whether the requested representation is available. An unknown flag is neither permission nor denial.

​
Follow a form to evidence

Forms return a schedule with form numbers, names, editions, actions, and replacement references where stored. Follow nextCursor with the same Filing ID and limit until it is null. The list is live; re-extraction can replace row IDs, so a form-row ID is not cross-filing form lineage. A nullable file contains a fileId and a current versionId when known. The match is inferred from form number and filename. Verify the document contents; the reference is not authoritative evidence of the version used for extraction. A null file does not invalidate the form metadata. Previous filing numbers remain native source references: resolve them through source-qualified lookup, rather than using them as Filing UUIDs.

​
Interpret the aggregate

Rate impact is one filing-level aggregate. Percent fields use percentage units: 7.5 means 7.5%, not a ratio of 7.5. Dollar fields are decimal strings; preserve that precision rather than converting them to binary floating-point values. Null is unknown, while zero and negative values retain their ordinary numerical meaning. The aggregate combines available company data. Percentages are weighted by known positive premium where possible and otherwise averaged; premiums and policyholder counts sum, and minimum/maximum changes are extrema. Source coverage may be partial, and the stored aggregate can lag extraction. It is not a per-company breakdown or a quote for an individual policy. For example, a filing description could discuss a surcharge while the stored aggregate contains zeros. Report both observations, then inspect the relevant memorandum or rate document. Do not conclude “no premium consequences” from the zeros alone, or replace them with an invented estimate. Filed rate information does not prove regulatory approval. Use Filing detail for source status, normalized outcome, and dates, and retain their distinctions. FILED, isClosed, and a non-null disposition date are not synonyms for APPROVED.

​
Keep the evidence boundary visible

In a comparison, state the filing IDs and source references, observation time, which extracted fields were present, and whether originals were read. Follow Read and cite document evidence for source verification. Keep unsupported, absent, unknown, and zero values distinct across filings; a complete inventory traversal does not prove complete regulatory-source coverage.