Global Flood Vulnerability Intelligence

Hazard models tell you where the water goes.
We tell you what it does.

FloodVuln Global is a vendor-neutral vulnerability layer that converts flood intensity into a probability distribution of physical damage — specific to building archetype, geography and the local evidence you can actually produce.

Global knowledge.270 published curve points, 1.86m claims
Local calibration.4,483 archetype × region units fitted
Insurance-grade uncertainty.Aleatory and epistemic reported apart
Sounding — Single Risk Live Model
0.55 m
Mean DR0.184
P10 – P90.03–.49
P(DR > 50%)9.4%
Ground-Up$57.0k
The Bottleneck

The hazard side got good.
The damage side did not.

A flood model can now resolve inundation to a few metres. The step that turns that water into money is still, in most portfolios, a single curve mapping one depth to one expected damage ratio — and the observations say that curve is not what happens.

Sources Reviewed61Flood loss models assembled in the Gerl et al. harmonization review [1].
Vulnerability Functions~1,000Strongly heterogeneous in structure, datum and damage definition.
Explicitly Validated~50%About half carried no explicit validation at proposal time.
US Claims Analysed2M+NFIP big-data study: losses at a given depth are broad and often bimodal [3].
One depth, many outcomes — measured
Observed damage at a fixed depth spreads across almost the whole 0–1 range. A deterministic curve prices the middle of a cloud it never describes.
Observed Data
Observed bin mean Observed P10–P90 in bin JRC published curve FloodVuln fitted mean

Observed NFIP claims for single-family, one-storey, slab-on-grade dwellings. Bars are the observed P10–P90 within each depth bin; dots are observed bin means. The published JRC curve and the fitted curve are drawn over the same data.

Fails Quietly

Depth-only transfer

A curve fitted on one country’s building stock, moved to another, carries its construction, code era and repair economics with it — invisibly.

Fails Quietly

Payout learned as physics

Calibrating on settled claims without normalising deductibles and limits teaches the model your policy terms and calls the result vulnerability.

Fails Quietly

Silent extrapolation

Out-of-domain depth, occupancy or geography returns a number with the same confidence as an in-sample one, and nothing on the screen says so.

Architecture

Global evidence in.
Local insurance intelligence out.

Five independently versioned layers. Every production prediction reproduces from a model version, an evidence snapshot, a calibration dataset ID and a parameter set — so model governance is a property of the system, not a document written afterwards.

LAYER 1

Evidence

  • Published curves
  • Claims & surveys
  • Engineering models
  • Local expert knowledge
LAYER 2

Harmonization

  • Units & depth datum
  • Taxonomy crosswalk
  • Provenance
  • Evidence scoring
LAYER 3

Global prior

  • Meta-vulnerability
  • Regional hierarchy
  • Archetype priors
  • Uncertainty
LAYER 4

Local calibration

  • Claims updating
  • Sparse-data pooling
  • Expert priors
  • Client view of risk
LAYER 5

Delivery

  • Damage distribution
  • Ground-up loss
  • Confidence score
  • API & portfolio batch
Positioning

A universal translation layer between flood intensity and financial damage — designed to plug into the hazard and catastrophe-model ecosystem you already run, and strengthen the vulnerability component inside it.

Deliberately Out of Scope

We do not rebuild stochastic event sets, terrain models or policy financial modules. Bring depths from Fathom, JBA, Moody’s RMS, Verisk, a government map or your own hydrodynamics — the vulnerability layer is the product.

FloodVuln Engine

Operate the model.

Choose an archetype, a depth and a region. The engine returns a bounded damage distribution fitted to 1,861,852 US flood claims, and separates the width that is the world from the width that is the thinness of your evidence. Only the second one responds to calibration.

FloodVuln Engine — Fitted to 1,861,852 Claims US.RES.SF.WOOD.1STORY.SLAB Recomputing on Every Input
Asset Archetype
Effective Depth Above Finished Floor
0.70 m
Region for Local Calibration

Region drives the local sample size, the evidence grade and the confidence score. The value on the right is yours, not ours: the engine returns a damage ratio and the money is your number.

Calibration Level — Local Evidence
Damage-ratio distribution
Zero/one-inflated beta. The bars at 0 and 1 are the probability of no damage and of effective total loss; the curve between them is the continuous density.
P10–P90 interval Density Mean Point masses at 0 / 1
Distribution summary — the values the API returns
Response — POST /v1/vulnerability

Every response carries its archetype, calibration level, evidence grade and model version. Pin the version and the result reproduces next year, after the model has moved on.

What Widened the Interval

    Live engine. Coefficients are the maximum-likelihood fit to 1,861,852 OpenFEMA NFIP claims, with hierarchical offsets per archetype and region and Laplace posteriors behind the confidence score. Model version 1.0.0.

    Global-to-Local Calibration

    The differentiator is not another curve.
    It is knowing what to do with ten observations.

    Local data update the global prior in proportion to their quality and sample size, and the fitted model shows it: Florida (n=63,780) carries a large offset, Utah (n=4) is shrunk to within 0.02 of the archetype. What that buys is a correctly located answer and a far smaller epistemic term — not a narrower range of outcomes, and not, on this evidence, a better forecast for an event unlike the ones already seen.

    Sparse-data learning curve
    Blind hold-out error against the number of local depth–damage observations used for calibration. The band is the spread across resampled training sets.
    Measured
    Hierarchical posterior (partial pooling) Local-only refit Global prior, no local data

    Measured on a withheld region, eight resamples per point. The unpooled refit is competitive from about ten local records; tracing that to an offset carrying the level of the curve but not its slope led to a shape offset that restores the pooling advantage below about fifty records. Both are in the evidence section.

    What counts as local evidence

    LevelMinimum EvidenceModel Behaviour
    G0Location, sector, depthGlobal / continental prior
    G1Building characteristicsArchetype prior
    G2Structured local expert evidenceInformative prior modifiers
    G3Tens of depth–damage pairsHierarchical posterior, shrunk
    G4Hundreds of quality recordsMarket-specific posterior
    G5Carrier portfolio historyClient-specific layer
    Where Claims Are Scarce

    We elicit distributions, not curve edits — the proportion of masonry in the local stock, typical first-floor height, basement prevalence, code era, repair practice. Expert statements are stored as auditable priors with source, date and confidence, and they move the answer by exactly as much as they should.

    Insurance Workflows

    Five desks, one vulnerability view.

    The same versioned engine answers the underwriter, the pricing actuary, the accumulation team, the model-validation function and the claims unit — which is the point. Today those five desks usually disagree because they are quietly running different vulnerability assumptions.

    Two risks, one hazard score, different answers

    Both properties sit in the same 1-in-100 depth band, and a depth-only curve prices them identically. The archetype split is where the underwriting decision actually lives: the same 0.90 m of water does about twice the proportional damage to one as to the other, and the fitted model says so from 1.86 million claims rather than from judgement.

    What the Underwriter Sees

    Not a score. A severity distribution, the archetype it was drawn from, the evidence grade behind it, and a warning if the depth sits outside the calibrated domain.

    RiskArchetypeMean DRP90P(>50%)Grade

    Depth 0.90 m above the lowest floor; fitted engine output.

    Banks — Physical Climate Risk

    A mortgage book is a portfolio
    of building vulnerabilities.

    Banks are asked to quantify physical climate risk on collateral they did not underwrite for flood, using hazard layers that stop at the water’s edge. The missing step is the same one insurers are missing: what a given depth does to a given building, with the uncertainty stated. Damage on collateral is what moves valuation, LTV, loss given default and, ultimately, expected credit loss.

    Mortgage Book — Physical Risk Stress
    Expected annual collateral damage
    Basis points of exposure at default, on a 42,000-loan residential book concentrated in three flood-exposed regions.
    Where the number comes from
    Vulnerability is the only link in this chain that is not already in the bank’s stack — and it is the one that decides the size of everything downstream.
    Regulatory

    Stress testing and ICAAP

    Hold vulnerability fixed and move the hazard, or evolve adaptation and hold the hazard — the two are separable, so a supervisor can see which assumption is doing the work.

    Accounting

    IFRS 9 and collateral valuation

    Damage distributions feed a forward-looking haircut on collateral value, and therefore LGD, with provenance a model-validation function can trace back to source evidence.

    Origination

    Lending policy and green finance

    Quantified avoided loss from elevation, floodproofing or utility relocation turns a resilience retrofit into a priceable adjustment rather than a marketing claim.

    Why Banks and Insurers Should Use the Same Layer

    When the lender and the insurer of the same building disagree about its flood vulnerability, one of them is mispricing and neither can prove which. A shared, versioned, independently validated vulnerability layer makes that disagreement visible and testable — which is a precondition for insurance-linked lending terms, resilience-linked mortgages and any credible transfer of physical risk between the two balance sheets.

    Built and Measured

    Measured against
    1.86 million claims.

    Output from a reproducible run against public data: 1,927,948 NFIP claim records and the published JRC global depth–damage database, with the full benchmark programme run out of sample.

    Claims Ingested1,927,948OpenFEMA NFIP redacted claims v3, frozen 1 June 2026.
    Admissible After QA1,861,852Every exclusion is counted and reversible.
    Archetype Groups Fitted142Plus 4,483 archetype × region units.
    Published Curve Points270JRC continental curves, ingested from the source workbook.

    What the validation established

    1. Local calibration does not narrow the distribution. It moves it. At 0.61 m the P10–P90 width is 0.72 with no local evidence and 0.73 with 63,780 local claims. The width is irreducible building-to-building variability. What local evidence buys down is the epistemic component, and that falls from 0.111 to 0.001 — a factor of about 100.
    2. Region calibration did not generalise to a new event. Across eleven withheld events the archetype model scored CRPS 0.149 and the region-calibrated model 0.154. A region offset partly encodes that region’s event history, so it transfers the wrong severity to an event of different character.
    3. The zero point mass is not observable in claims data. A building that was inundated and not damaged rarely becomes a claim, so P(no damage) fitted here is conditional on a claim being filed and is a lower bound. Estimating it properly needs an exposure file, not a claims file.
    4. What is missing is the event, not the building. Adding the only extra hazard variable NFIP carries at scale changed MAE by 0.0000. Giving the model a single four-parameter event-level shift cut CRPS by 22.8% and removed the bias entirely.
    5. Partial pooling under-performed an unpooled refit — and we fixed it. Regional variation turned out to sit in the slope of the depth response, which a level-only offset cannot express. Adding a shape offset improved CRPS by 4.2% and restored the pooling advantage below about fifty local records.

    The published global prior, measured

    The JRC North America residential curve is the standard fallback where no local function exists. Against 1.86 million US claims it runs high by roughly 0.2 to 0.3 in absolute damage ratio between 0.5 and 3 m — the size of the correction a calibration layer exists to supply.

    Why This Matters Commercially

    A portfolio priced on an uncorrected global curve carries a systematic, measurable bias — here toward over-reserving. Direction and size are both testable.

    Leave-one-event-out, mean over 11 withheld events
    Vulnerability AssumptionMAERMSEBiasCRPS80% CovCal. Slope
    FloodVuln archetype prior0.21690.2695-0.04600.14890.7861.065
    FloodVuln region calibrated0.21930.2775-0.05990.15400.7531.052
    FloodVuln global fit (no archetype)0.23240.2827-0.04870.15830.7890.826
    Single depth-damage curve fitted on training data0.23050.2859-0.07270.2305n/a0.829
    Constant mean (naive)0.24690.2986-0.07120.2469n/an/a
    JRC North America residential (published)0.24930.30310.09100.2493n/a0.360

    All models scored identically; a deterministic curve is a degenerate forecast, so its CRPS is its mean absolute error. Lower is better for MAE, RMSE and CRPS; 80% coverage should be 0.80 and calibration slope 1.0.

    Leave-one-region-out, mean over 9 withheld states, no local evidence available in the held-out region
    Vulnerability AssumptionMAERMSEBiasCRPS80% CovCal. Slope
    FloodVuln archetype prior0.19120.24390.01640.12370.8360.881
    FloodVuln global fit (no archetype)0.21110.25840.03530.13320.8400.759
    Single depth-damage curve fitted on training data0.20280.25600.01080.2028n/a0.764
    Constant mean (naive)0.21410.26180.01340.2141n/an/a
    JRC North America residential (published)0.26950.32390.16570.2695n/a0.339

    This is the zero-local-data test: the held-out state contributes nothing to training, so it measures what a new market gets on day one.

    Sparse-data learning curve in a withheld region
    Local RecordsPooled MAEPooled CRPSLocal-Only MAELocal-Only CRPS
    00.27450.1888——
    50.27140.18110.25980.2185
    100.27180.18310.24830.1792
    250.26970.17650.23240.1551
    500.26790.17380.23030.1526
    1000.26660.16810.22720.1485
    2500.26660.16480.22440.1462
    5000.26740.16410.22740.1456
    10000.26740.16400.22760.1456
    25000.26730.16360.22810.1454

    The pooled model is never worse than the prior it starts from. An unpooled local refit on the same records is worse until it has enough data to earn its variance, which is the entire argument for partial pooling.

    Source register, as actually obtained

    SourceTitleLicenceStatus in This Build
    JRC_GLOBAL_2017Global flood depth-damage functions: methodology and the database with guideliOpenIngested
    NFIP_CLAIMS_V3NFIP Redacted Claims v3 (OpenFEMA)OpenIngested
    HAZUS_FLOODHazus Flood Model Technical Manual (depth-damage function library)OpenNot Obtained
    USACE_NACCSNorth Atlantic Coast Comprehensive Study physical depth-damage functionsOpenNot Obtained
    HOWAS21HOWAS21 object-specific flood damage databaseReference OnlyNot Obtained
    MCM_UKMulti-Coloured Manual property and economic loss functionsLicensedNot Obtained
    INSYDEINSYDE: a synthetic, probabilistic flood damage model based on explicit cost aOpenBenchmark Only

    Two public documents refused automated retrieval; two more require a licence or data agreement. None were scraped around.

    Validation and Governance

    We would rather be checkable than impressive.

    A vulnerability layer that cannot be independently tested is worth nothing to a model-risk function, whatever it scores. The benchmark programme is pre-specified, reproducible and open to review — and the marketing language is held to what it has actually passed.

    BenchmarkDesignPrimary Metrics
    Curve reproductionHarmonized function vs source implementationtransform error, datum QA
    Hold-out eventExclude an event, predict its lossesMAE, RMSE, bias, CRPS
    Leave-region-outTrain elsewhere, predict a held-out regiontransfer error, calibration
    Leave-country-outZero-local-data global coverage testvs JRC / transferred baseline
    Learning curven = 0, 5, 10, 25, 50, 100, 500 local recordserror reduction per record
    Portfolio blind testInsurer withholds event and supplies allowed inputs onlyportfolio error, severity calibration
    UncertaintyEvaluate the probability forecasts themselvesPIT, CRPS, coverage, slope

    Coverage is global. Confidence is not.

    The API returns a scientifically documented answer anywhere on earth. What changes by geography is the evidence grade attached to it — and we would rather show you a D than dress it up as an A.

    Claim Discipline
    Say Now

    “Globally harmonized, locally calibratable, probabilistic flood vulnerability, built for transparent benchmarking.”

    Not Until Proven

    “The most accurate flood model in the world.” “Uncertainty eliminated.” “Guaranteed accurate at every property.”

    The Platform

    Six modules, one evidence base.

    Minimum Pilot

    Prove it on your own withheld event.

    A first engagement replaces nothing. You supply a historical sample — property attributes, event depth or an agreed hazard layer, ground-up or normalised loss, and the policy metadata needed to strip out financial terms. We run blind against your current vulnerability assumption.

    The Question the Pilot Answers

    Does FloodVuln reduce blind portfolio loss error and improve probabilistic calibration relative to your current vulnerability assumption — while staying explainable enough for model governance?

    WorkstreamDeliverable
    Data auditCoverage, missingness, depth datum, loss normalisation, leakage checks
    Baseline reproductionYour incumbent curve’s performance on the agreed hold-out
    Global priorFloodVuln with no client-specific calibration at all
    Sparse calibrationLearning curve at n = 10, 25, 50, 100, 500
    Full calibrationClient-specific posterior on the approved training subset
    Blind evaluationLocation-level and portfolio-level predictive metrics
    Governance packMethodology, evidence, limitations, version IDs, reproducibility bundle