Notes ·

What is a peril footprint in a parametric contract?

A wind anemometer mounted on a pole against a clear blue sky, with trees below.

A peril footprint is the geographic extent of whatever the contract pays on: flood line, burn scar, wind swath, cyclone track. It's the shape of where the peril touched ground, separate from the administrative boundary used to price the deal and separate from whatever a single index station happened to read. Lay the footprint over the insured area and you see what the peril covered, not just what the deal was priced against.

Most parametric paper never asks "did the footprint touch the insured asset." It asks "did the index cross a threshold." That's a shortcut, and a defensible one when the index and the ground truth usually move together. The gap shows up on the claims nobody wants: a gauge reads just under trigger while the field two miles away is underwater, or a wind station clocks a lower gust than the roof damage three streets over suggests. When the index and the footprint disagree, whoever is writing the check needs something to point at besides the one sensor that happened to be nearby.

Peril footprint definition, in contract terms

In a parametric structure, the footprint is the evidence layer sitting between the trigger definition and the payout calculation. The contract says "pays if footprint overlaps insured polygon by X%" or "pays per km² of footprint within the defined area." Either way, somebody has to produce that footprint after the event, independent of the two parties who have a financial stake in its size.

That's the part that gets skipped at drafting time. Teams write careful language about thresholds and percentages, then leave the actual footprint source as "to be determined" or, worse, as whichever party's internal data happens to be fastest to produce. A counterparty's own loss estimate is not an independent footprint. A single ground station gives one point reading, and a point reading won't show you where an edge fell.

Where footprint disputes happen

The trigger reading gets argued about because it's the number everyone already agreed matters. The footprint gets argued about because nobody defined who draws it. That's backwards from a risk standpoint: the reading is usually a single value from a single source, easy to audit. The footprint is a shape with an edge, and the edge is exactly where marginal claims sit. If your book has any assets near a boundary, basis risk lives in that edge, not in the headline index number.

A before and after satellite read handles this the way an adjuster would if they could be everywhere at once. One pass before the qualifying event, one pass after, same sensor, same swath. The difference between the two images is the footprint: burned area, inundated area, downed canopy, whatever the peril leaves behind. It's multispectral, wide-swath imagery, so it covers the whole insured area in one look rather than sampling it from a handful of ground points. Nobody's loss estimate and nobody's station reading is in the loop. The read is the event footprint, full stop.

That's the piece a parametric trigger needs to settle cleanly: an observation nobody on either side of the contract produced themselves. Trigger Verification exists to be that observation, a before/after read triggered the moment a qualifying event occurs, built specifically to stand in as the independent footprint a contract pays against.

What this changes at drafting and at settlement

At drafting, it means you can write the trigger clause against a footprint source you name in the contract, instead of leaving "footprint" undefined and hoping the parties agree later. At settlement, it means neither side is handing the adjuster their own number and asking it to be trusted. The footprint comes from outside both balance sheets.

None of this replaces the index or the gauge data your pricing model already relies on. It sits next to it, as the layer that answers the question the index can't: not "did the threshold trip," but where did the peril actually go, and does that match the area this contract covers. For a book with enough geographic spread that edge cases are a when, not an if, that's the gap worth closing before the next event, not during the dispute that follows it.

If your contract language is still silent on who produces the footprint, that's the sentence worth fixing next.

Start a pilot

Photo: Lucy Meadows / Pexels