Skip to main content

Now booking discovery calls · weekdays, 9am–4pm EasternBook a time (opens Google Calendar in a new tab)

AI in practice

Checking flood insurance policies against the loan file with AI

Lenders have to confirm that every loan in a flood zone carries enough flood insurance, for as long as the loan runs. Here's what that check involves, why it's slow by hand, and how AI can do the reading while a person makes the call.

By the Sixth Wave team4 min read

The requirement

Under the Flood Disaster Protection Act of 1973 and the National Flood Insurance Reform Act of 1994, flood insurance is mandatory when a building in a Special Flood Hazard Area secures a loan from a federally regulated lender. FEMA describes the Special Flood Hazard Area as the area on its flood maps where the mandatory purchase of flood insurance applies.

The federal banking regulators' rules spell out what that means. The FDIC's version is typical: a supervised institution may not make, increase, extend or renew a designated loan unless the building, and any personal property securing the loan, is covered by flood insurance for the term of the loan. The amount must be at least the lesser of the loan's outstanding principal balance or the maximum coverage available for that type of property under the National Flood Insurance Program.

  • One- to four-family homes: the NFIP maximum for the building is $250,000, or the building's insurable value if that is lower.
  • Other residential and non-residential buildings: the NFIP maximum is $500,000.
  • Lenders can require more than the legal minimum, and many do.

The obligation doesn't end at closing. If the lender or its servicer finds at any point during the loan that coverage is missing or too low, it must notify the borrower. If the borrower hasn't obtained enough insurance within 45 days, the lender must buy it on the borrower's behalf, known as force placement, and may charge the borrower for it.

This is a summary, not legal advice: your compliance team and your investors' guidelines set the exact requirement for each loan. The point is that every policy, at origination and at every renewal, has to be read and compared with the loan.

What a reviewer actually checks

Most of the work happens on the policy's declarations page, the summary page every flood policy carries. A reviewer typically confirms:

  • Building coverage is at least the amount the loan requires.
  • The deductible is within the limit the lender or investor allows.
  • The policy period covers the loan, with no gap between the closing or renewal date and the effective date.
  • The named insured matches the borrower on the loan.
  • The property address matches the collateral, unit number included.
  • The lender is listed as mortgagee, so it's notified if the policy changes or lapses.
  • Contents coverage, where personal property also secures the loan.

Why it's slow by hand

Each check is simple. Doing them reliably, at volume, is not. Declarations pages differ between the NFIP and private carriers and change from year to year. Many arrive as scans or photos of a printout. The figure that matters may be on page two, next to three figures that look like it. And the work never stops: policies renew every year, so a portfolio's worth of policies has to be read again and again.

Done by hand, that means keying figures into a spreadsheet or a servicing system and comparing them by eye. A missed shortfall isn't a paperwork problem. It can mean a flooded building with too little cover behind the loan, a borrower who should have been notified and wasn't, and a finding the next time examiners look at the file.

How an AI check works

This is the problem we built FloodCaliber to solve. It reads flood insurance policies, pulls out the figures that matter and checks them against the loan, so a reviewer sees any shortfall and the page it came from. In practice:

  1. It reads the declarations page, scanned or digital, and turns it into checked, structured data.
  2. It links every value to the place on the page it came from, so nothing is a number without a source.
  3. It checks the coverage against the loan's requirements, including the building limit and the policy period.
  4. It shows a shortfall and its evidence side by side on a review screen, for a person to decide.

What stays with people

Software should never decide that a borrower is underinsured on its own. The reading, the arithmetic and the comparison are what a machine does well and people find tedious. The decision, the borrower notice, any force-placement and every exception stay with your team, with the evidence one click away. That division is what lets the check run faster without weakening it: reviewers spend their time on the policies that need judgment, not on re-keying the ones that don't.

Getting started

Every lender's requirements, investors and systems are a little different, so we start with your own files. In discovery, which is free, we gather a sample of the policies your team reviews today, including the messy ones, write down the rules each loan has to meet, and test the check on them before anything is built. You can read more about our work for insurance and for banking and lending, or book a free discovery call (opens in a new tab) and bring a few real declarations pages.

Common questions

Quick answers.

Does it make the decision on its own?

No. It reads, checks and flags. A person on your team decides on every shortfall, with the figure and the page it came from side by side.

Does it replace our flood zone determinations?

No. Whether a building is in a Special Flood Hazard Area comes from your flood zone determination. The check reads the policy and compares it with what the loan requires.

Can it read scanned policies?

Yes. It turns a scanned or digital policy into checked, structured data. We test it on your own files during discovery before anything is built.

Work with us

Have something like this in mind?

A free discovery call, then a written recommendation with one agreed price.