Climate Risk in Underwriting: The Data Question Behind the ESG Slide

Climate risk has a permanent slot in every insurer's strategy deck, usually somewhere near the ESG commitments. What it rarely has is a coherent answer to the operational question underneath it: how does climate risk actually change the number an underwriter puts on a policy today? Between the boardroom ambition and the point-of-sale decision sits a data problem that most insurers haven't solved, and until they do, "we take climate risk seriously" is a statement about intent, not capability.

The gap between narrative and rating

At the strategic level, climate risk is well understood: perils are intensifying, historical loss experience is becoming a weaker guide to the future, and portfolios concentrated in exposed geographies carry risk that yesterday's models understate. All true, all in the deck. But an underwriter pricing a specific property in a specific location needs that macro truth translated into a concrete input — a forward-looking view of flood, wildfire, wind, or heat risk for this address, at a resolution and a time horizon the rating engine can use. That translation is where it breaks down.

Why it's hard, specifically

  • The past is a fading guide. Traditional pricing leans on historical loss experience; climate change is precisely the force making that history less predictive. So you need forward-looking climate data layered onto backward-looking loss data — two different worlds, joined.
  • Resolution mismatch. Climate projections often come at coarse grid resolutions; underwriting needs address-level precision. Bridging that gap without either overstating or washing out the signal is a real modeling-and-data challenge.
  • Exposure data quality. Forward climate risk is only as useful as the exposure it's applied to. If your property locations and characteristics are stale or imprecise, a sophisticated climate layer just produces confident nonsense — the same geocoding problem that plagues catastrophe modeling.
  • Time horizon. An annual policy and a 30-year climate trend operate on different clocks. Deciding how much of a long-term trend to price into a short-term contract is a judgment that needs the data to support it.

From slide to signal

Operationalizing climate risk means building the data pipeline that turns climate science into an underwriting attribute: sourcing credible forward-looking peril data, resolving it to the specific insured location, joining it to your own loss and exposure data, and delivering it into the rating decision at a resolution and horizon that make sense. None of that is the ESG story; all of it is the data foundation that makes the ESG story operationally real. And it rests on the same unglamorous prerequisites as everything else — precise exposure data, clean geocoding, the ability to join external data to your own at the right grain.

What it takes

  1. Source forward-looking peril data you can defend, not just historical averages.
  2. Resolve it to the insured location — address-level, with confidence — so it applies to the right risk.
  3. Join it to your own loss and exposure data so the climate view is grounded in your book, not a generic map.
  4. Deliver it into the underwriting decision at a horizon the business has consciously chosen, rather than as a report read after binding.

Climate risk will keep escalating whether or not your underwriting can see it, so the real question is operational: can you get a defensible, address-level, forward-looking risk signal into the decision? Building that pipeline — sourcing, resolving, joining, and delivering climate data into pricing — is the kind of data-foundation work we do with insurers at IntelliBooks.

The ESG slide says you take climate seriously. The underwriting data decides whether that's true.

Comments

Post a Comment

Popular posts from this blog

Why Your Insurance Data Warehouse Didn't Fix Anything

You built the data warehouse. It took eighteen months and cost more than planned. Policy data, claims data, billing — it's all in there. The project was declared a success and everyone moved on. And yet: underwriting still can't see the whole customer. The AI initiative is still stalled. Someone still asks for a report and waits three weeks. Nobody says it out loud, but the question hangs there — what exactly did we buy? You're not alone, and it isn't because you built it badly. It's because a warehouse solves a problem you didn't have. The problem a warehouse solves Warehouses solve location . Before: your data was in eight systems. After: it's in one place. That's genuinely valuable — you can run a query across policy and claims without begging two teams for extracts. But notice what that fixes: it fixes where the data is . It doesn't touch what the data means , whether it's trustworthy, or whether the records refer to who you think t...
Read more

Straight-Through Processing: From 10% to 90%

Straight-through processing is the number every insurance executive quotes and almost nobody achieves. The industry benchmark has moved from 10–15% to 70–90% at the carriers who've cracked it. That's not a marginal efficiency gain — it's a different cost structure. So why is your STP rate still stuck in the teens? Because STP gets treated as a workflow project. It isn't. It's a data problem wearing a workflow costume. What STP actually requires Straight-through means a quote, policy, or claim goes from submission to completion with zero human touches . For that to happen, every decision point in the chain has to be answerable automatically. Every single one. A chain of nine automated steps and one manual check isn't 90% straight-through — it's 0%. One human touch and the whole thing is a manual process with extra steps. That's the bar. And it means the constraint isn't the workflow engine — it's whether the data needed at each decisio...
Read more

Embedded Insurance: Why the API Is the Easy Part

Embedded insurance is the idea that coverage should be offered at the moment of need, inside someone else's product — travel insurance at checkout, device protection when you buy the phone, cover for the rental car in the booking flow. It's one of the fastest-growing distribution models in the industry, and every insurer has a strategy slide about it. Most of those strategies underestimate the same thing, and it isn't the partnerships or the product. It's the data plumbing. Everyone assumes the API is the hard part. The API is the easy part. What embedded insurance really demands The promise of embedded is speed and invisibility: a customer buys a flight and, in the same breath, is offered exactly the right travel cover at exactly the right price, and accepts with one tap. No forms, no friction. Deliver that and you've won. But "exactly the right cover at exactly the right price in one tap" makes brutal demands on your back end: You must price i...
Read more