The Flood Insurance Transparency Act of 2025 amends the National Flood Insurance Act of 1968 to require the Administrator of the National Flood Insurance Program (NFIP) to publish the program’s data, models, assessments, tools, and related information used to assess flood risk and set premiums. It specifies the types of data to be released (including loss ratios, limited policy and claims fields, pre/post‑map construction status, mitigation status, and identification of multiple‑loss properties) and requires an open‑source data system for immediate electronic access.
The bill also directs FEMA to build and maintain a publicly searchable community database within one year listing community compliance status with NFIP requirements and concrete community‑level metrics (numbers of pre‑ and post‑map properties in hazardous areas, claims outside flood zones, multiple‑loss properties, and the portion of community in special flood hazard areas). The statute requires data at ZIP code or census‑block granularity, names of community and State, and disclosure formats that protect personally identifiable information under the Privacy Act (5 U.S.C. 552a).
This creates a single federal source of NFIP operational data intended to support research, private-sector risk modeling, mitigation targeting, and public accountability.
At a Glance
What It Does
The bill requires the NFIP administrator to make publicly available all data, models, assessments, analytical tools, and other information the program uses to assess flood risk, set elevations, and calculate premiums, and to host that material in an open‑source data system accessible electronically. It also creates a searchable community database with specific community metrics and compliance information, to be operational within one year of enactment.
Who It Affects
FEMA/NFIP will carry the primary operational burden and must curate, redact, and publish the materials. Insurers, reinsurers, risk model vendors, climate researchers, real‑estate market participants, and local governments will be direct users of the published data. Property owners and prospective buyers will be affected indirectly as the information filters into pricing, disclosures, and local reputational dynamics.
Why It Matters
By forcing a federal standard and central repository for NFIP data and models, the bill lowers barriers for independent research and private actuarial work, changes how flood risk is discovered and priced, and gives communities and markets new visibility into NFIP exposure and compliance. That transparency can improve mitigation targeting but also creates new legal, privacy, and market risks for owners and local governments.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The core obligation the bill creates is straightforward: FEMA must stop treating much of its flood‑risk work as internal and publish the raw inputs and tools it uses to assess flood hazard and price NFIP policies. That includes data tied to individual properties (at ZIP code or census block level), the program’s computed loss ratios, and the actual models and assessments FEMA relies on.
The statute narrows certain fields for public release — for policies, only amount and term; for claims, only date and amount paid — but otherwise calls for broad disclosure to support research and product development.
The bill defines a ‘‘loss ratio’’ (claims paid divided by premiums received for a fiscal year) and ‘‘multiple‑loss property’’ (including repetitive loss and severe repetitive loss under existing NFIP definitions) so readers can interpret the published metrics consistently. It also requires the published data to flag whether a property predates the community’s first Flood Insurance Rate Map (FIRM) and to indicate whether mitigation actions—elevation, buyouts, or other measures—have been taken, plus identify multiple‑loss properties where mitigation has not occurred.To make the material usable, FEMA must set up an open‑source data system enabling immediate electronic access; the community database must be searchable and populated with specific metrics (compliance findings, number of pre/post‑map properties in special flood hazard areas, claims outside hazard areas, multiple‑loss counts, and the share of community area in SFHAs expressed both as square miles and percent).
The statute requires compliance with the Privacy Act so the release avoids revealing individually identifiable owner information, but it leaves technical choices—how to aggregate, redact, and update—largely to FEMA’s implementation.
The Five Things You Need to Know
The bill requires FEMA to publish the NFIP’s data, risk models, assessments, analytical tools, and other materials used to assess flood risk and set premiums.
Policy-level public disclosures are limited to policy amount and term only; claims disclosures are limited to the date of loss and amount paid.
The statute defines loss ratio as claims paid divided by premiums received for the NFIP in a fiscal year and requires FEMA to make that information publicly available.
FEMA must establish an open‑source electronic data system for immediate public access and a searchable community database that must be available within one year of enactment.
All published data must be at least ZIP Code or census block level, include the community and State name, and be disclosed in a format that protects personally identifiable information under 5 U.S.C. 552a.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
This single line designates the statute as the ‘‘Flood Insurance Transparency Act of 2025.’
Definitions for public metrics
Subsection (a) supplies working definitions that the rest of the section uses to standardize disclosures. It defines ‘‘loss ratio’’ as claims paid over premiums for the program in a fiscal year — a simple ratio but one that can be computed at multiple aggregates — and it adopts existing NFIP categories for ‘‘multiple‑loss property’’ (repetitive and severe repetitive losses). That choice forces comparability with current NFIP reporting but also imports existing definitional edge cases that FEMA will need to clarify when publishing the data.
Flood‑risk materials to be published and open‑source system requirement
Subsection (b) lists the categories of materials FEMA must publish: property‑level risk data and loss ratios, current and historical policy information (amount and term only), current and historical claims (date and amount only), pre/post‑FIRM construction indicators, mitigation status, and identification of multiple‑loss properties lacking mitigation. It also requires FEMA to establish an open‑source data system for immediate electronic public access. Practically, that compels FEMA to ingest, standardize, redact, and host large administrative datasets and the models used to generate NFIP maps and pricing assumptions.
Searchable community database and required community metrics
Subsection (c) creates a separate, searchable repository of community‑level information to be operational within one year. Required fields include community compliance status (including findings of noncompliance, enforcement actions, and counts of days of continuing noncompliance), counts of pre‑ and post‑FIRM properties located in special flood hazard areas, total claims outside SFHAs, counts of multiple‑loss properties, and the percent and square‑mile share of the community in SFHAs. That timeline is ambitious; building accurate historical tallies across NFIP communities will test FEMA’s data integration and validation processes.
Geographic granularity and identification requirements
Subsection (d) requires data to be anchored geographically at the ZIP Code or census block level and to include the community and State names for each property. That degree of granularity supports detailed analysis but raises nontrivial privacy and standardization issues: ZIP codes cross municipal boundaries, census blocks sometimes change between decennial censuses, and reconciling different locational conventions will be an operational hurdle for FEMA.
Privacy Act compliance for personally identifiable information
Subsection (e) mandates that disclosures must not reveal individually identifiable owner information and must comply with 5 U.S.C. 552a (the Privacy Act). The bill leaves the technical means and thresholds for redaction or aggregation to FEMA, but it makes clear that transparency cannot be achieved by publishing unredacted owner names or other PII.
This bill is one of many.
Codify tracks hundreds of bills on Finance across all five countries.
Explore Finance in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Climate and flood‑risk researchers — they gain access to NFIP models, historical claims and policy data (in usable fields), and loss‑ratio metrics that enable independent validation of federal hazard estimates and improved forecasting models.
- Insurers and reinsurers — receiving FEMA’s models and standardized loss data lowers barriers to building competitive private pricing, reinsurance placement, and portfolio risk analysis for properties previously opaque or reliant on proprietary inputs.
- Local planners and mitigation managers — the searchable community database provides concrete, comparable metrics (pre/post‑map building counts, multiple‑loss properties, SFHA area) that let localities prioritize buyouts, elevations, and enforcement interventions against clearly visible NFIP exposures.
- Real‑estate and mortgage market participants — buyers, lenders, and appraisers can use standardized community and parcel risk signals to inform disclosures, underwriting, and valuation decisions, reducing information asymmetry in property transactions.
Who Bears the Cost
- FEMA/NFIP — must devote funding and staff to extract, standardize, validate, redact, host, and maintain large datasets and modeling artifacts; building an open‑source system and meeting a one‑year deadline will create immediate implementation costs.
- Local governments — public publication of compliance findings and days of continuing noncompliance will increase reputational and political pressure, potentially forcing municipalities to spend on code enforcement, map appeals, or mitigation without concurrent federal funding.
- Property owners in high‑risk areas — greater transparency can accelerate market corrections (higher premiums, harder sales) as private actors and lenders reprice risk based on new, accessible data.
- Proprietary model vendors and some private data firms — the release of FEMA’s models and underlying data may reduce the commercial value of certain proprietary products or require business model adjustments to compete with or complement public datasets.
Key Issues
The Core Tension
The central dilemma is transparency versus the practical and privacy costs of publishing granular government risk data: making NFIP data and models public improves market functioning, research, and mitigation planning, but it also risks revealing sensitive information, undermining proprietary contracts, imposing significant technical and financial burdens on FEMA and communities, and accelerating market adjustments that can harm property owners and local tax bases. There is no tidy legislative choice that fully preserves all those interests.
The bill resolves the question of availability but leaves numerous implementation choices that will determine real world impact. The statutory limits on disclosed fields (policy amount and term; claims date and amount) strike a compromise between usefulness and privacy but omit details that underwriters and researchers often need — for example, occupancy type, building elevation, deductible structure, and coverage endorsements — which could blunt the usefulness of the disclosures for some analytical tasks.
The Privacy Act compliance requirement controls for direct identification but does not mandate specific aggregation thresholds or disclosure avoidance techniques, so the balance between granularity and privacy will be set by FEMA rulemaking and technical decisions rather than statute.
Another tension arises around data provenance and proprietary rights. The bill directs publication of ‘‘models’’ and ‘‘analytical tools’’ but provides no guidance on distinguishing FEMA‑owned modeling materials from third‑party models obtained under contract with licensing or confidentiality terms.
Vendors that supply model components may claim intellectual property or contractual limitations; resolving those claims will affect what FEMA can actually publish. Finally, the bill does not appropriate funds or specify a funding mechanism for the one‑year community database timeline or the ongoing costs to maintain an open‑source system, creating practical risk that the mandate will outpace available resources and delay implementation or reduce data quality.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.