The surprises always arrive late in the file
Every one of them was knowable at application. None of them were looked up, because looking them up took twenty minutes each.
Flood insurance requirement surfaces at closing because nobody checked the zone at intake
FEMA NFHL zone, BFE and SFHA status at application, from the address, in seconds
Open permits on the collateral discovered by the title company, not by you
Permit history and open-permit status from the county portal, returned with the property record
Age and construction questions answered from the listing rather than the county roll
Year built, living area, just and assessed value straight from the Florida Department of Revenue parcel data
Wind exposure treated as an insurance problem and never priced into the file
Design wind speed by risk category alongside elevation, so exposure is visible while the loan is still being structured
What lands on the file
Enough to flag the files that need attention, early enough that attention is still cheap. This is screening data — it is not a Standard Flood Hazard Determination and does not replace your determination vendor.
Sample Report Data
Flood zone
AE — SFHA
BFE
9 ft NAVD88
Ground elevation
8.4 ft
Year built
1974
Just value
$1,420,000
Living area
2,180 sqft
Open permits
2
Last sale
On record
County
Miami-Dade
Bring your own AI agent
Enrich the pipeline, not one file at a time
Underwriting is a queue. The value of this data is proportional to how early and how automatically it reaches the queue.
At application
Enrich the address the moment it enters your LOS. Flood, elevation and permit status arrive before an underwriter opens the file.
Portfolio review
Run an existing book through the API to find collateral sitting in an SFHA, or with an elevation gap against the BFE, that was never flagged.
Ask in plain language
Connect your assistant over MCP and ask which files in today's queue sit in a special flood hazard area. No report to run, no analyst to task.
For these 40 addresses: flood zone, BFE, ground elevation, and open permits. Flag any where elevation is below BFE.
How it works for you
Intake screening
Catch the flood-insurance conversation at application rather than at closing, when it is still a conversation and not a delay.
Collateral review
Year built, valuation and permit history from the county record, so the file reflects the parcel rather than the listing.
Portfolio exposure
Understand aggregate wind and flood exposure across a Florida book using the same design criteria an engineer would cite.
Questions we actually get
Is this a flood determination?
No. PropDocket returns FEMA NFHL zone, base flood elevation and SFHA status as screening data at application. It is not a Standard Flood Hazard Determination and does not replace your determination vendor or transfer any of that liability.
Can it run inside our LOS?
Yes, through the REST API. Addresses can be enriched on intake so flood, elevation and permit status are on the file before an underwriter opens it.
What does it tell me about the collateral itself?
Year built, living area, just and assessed value from the Florida Department of Revenue parcel roll, plus permit history including anything still open.
How does elevation relate to BFE?
Ground elevation and base flood elevation are returned together so the gap is visible. That gap is an estimate from published elevation data and is not an Elevation Certificate.
PUBLIC BETA
PropDocket is free during the beta. No card required. We'll email you before billing starts.
Usage-based, one balance per organization, no seats, nothing expires. See pricing →
Stop toggling between tabs.
Start making decisions.
Get instant property intelligence for any Florida address. Free during launch — no credit card required.