Insurance Verification

Questions & Answers / Clarifications

This document provides responses to questions submitted by vendors regarding FEMA RFI # 70FA4026I00000004, which seeks information on insurance validation and consumer-permissioned data sharing services.

• Identity Resolution: FEMA will collaborate with vendors to determine confidence levels for identity resolution, routing cases for manual review if identifiers are incomplete or inconsistent.
• Matching Metrics: FEMA collects Sensitive Personally Identifiable Information (SPII) and Personally Identifiable Information (PII) to support data matching with high confidence and will work with vendors to set confidence thresholds.
• Automation of Determinations: The extent of automation for eligibility or duplication-of-benefits determinations will depend on the information received from vendors and will likely fall into one of three categories: completely automated, automated with human-in-the-loop review, or manual.
• Data Freshness: FEMA looks to insurance coverage that is in force and effective at the time of loss, generally validating presence or absence of insurance at the time of registration.
• System of Record: Salesforce is expected to be the System of Record for Individual Assistance.
• Coverage Verification: FEMA's preference is for coverage verification to occur during survivor registration.
• Duplication-of-Benefits Logic: This logic is anticipated to reside within Salesforce rules engines.
• Architecture Preference: FEMA is open to various integration methods but generally prefers aggregator-based access to limit technical debt.
• Underinsurance Methodologies: FEMA has not yet committed to publishing standardized methodologies for calculating underinsurance.
• Pilot Rollout & Acquisition Strategy: FEMA will determine its approach for pilot rollouts and acquisition strategy (single award vs. modular procurements) following a review of submitted RFI responses.
• Data Access: FEMA's initial presumption is to use APIs to pull insurance data, but the RFI seeks recommendations on viable approaches.

The RFI due date has been extended to March 11, 2026, at 3:00 PM EST. The RFI is seeking insurance validation and consumer-permissioned data sharing services, with the expectation that selected vendors will collaborate with FEMA staff and system integrators for necessary integrations.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding Request for Information (RFI) # 70FA4026100000004 issued by the Federal Emergency Management Agency (FEMA).

• Page Limitation: The 25-page limitation for addressing topic area statements/questions is not a hard requirement. FEMA is open to reviewing additional details if helpful.
• Requirement Status: This RFI represents a new requirement, not a follow-on to previous services. Incumbent contract and vendor information will not be provided.

Vendors should note that the page limitation is flexible, and the requirement is new. This clarification may influence how vendors structure their responses and assess their ability to meet the new requirements.

Request for Information (RFI)

This RFI is issued by the Federal Emergency Management Agency (FEMA) to conduct market research for insurance verification and data-sharing services for its Individual Assistance (IA) Program. FEMA is seeking information on industry capabilities to validate insurance coverage for disaster survivors and enable survivor-permissioned digital connectivity with insurance carriers to streamline the process of obtaining verified policy, coverage, and claims information. This RFI is for planning purposes only and does not constitute a commitment to award a contract.

FEMA is seeking information on services and technical solutions that can:

• Securely validate survivor insurance coverage for various types of policies (homeowners, renters, flood, auto, etc.) using survivor-authorized data sharing, complying with regulations to prevent duplication of benefits.

• Allow survivors to authenticate and link their insurance accounts to FEMA's Disaster Assistance Portal (DAP), enabling FEMA to receive verified insurance data directly from insurers.

• Integrate with FEMA's IA systems, including the Individual Assistance Processing System (Salesforce-based), to support automated checks for duplication of benefits and underinsurance calculations.

• Ensure secure handling of Personally Identifiable Information (PII) and Sensitive PII (SPII), complying with Federal privacy and security requirements.

• Anticipated Period of Performance Start Date: Beginning in FY27.

• Anticipated Acquisition Strategy: FEMA has not yet determined the acquisition strategy and is considering options such as existing Government-wide Acquisition Contracts (GWACs), full and open competition, small business set-asides, or a phased approach.

• Responses are due no later than 3:00 PM EST on March 4, 2026.

• Questions are due no later than February 25, 2026.

• Responses should be submitted electronically to the Contracting Officer and Contract Specialist.

• FEMA recommends a maximum of 25 pages for the response, excluding the cover page and appendices.

• FEMA is considering various acquisition strategies, including potential small business set-asides if appropriate based on market research.

• Respondents are encouraged to provide feedback on acquisition approaches, contract types, and performance structures.

• The RFI includes detailed topic areas for responses, covering corporate capabilities, technical approaches for insurance verification and survivor-permissioned data sharing, integration with FEMA systems, security, privacy, compliance, performance, scalability, reliability, implementation, operations, support, pricing models, risks, constraints, and recommendations.

• NAICS Code: 518210 – Data Processing, Hosting, and Related Services.

• PSC Code: DA10 – IT and Telecom – Business Application/Application Development Software as A Service.