How to verify a parametric earthquake trigger with before and after satellite imagery

A seismic network says the magnitude cleared your trigger. The cedent says the damage footprint matches. The counterparty wants its own confirmation before it signs off on the number. This is the moment a parametric earthquake cover either pays cleanly or ends up in a month of back-and-forth about whose data to trust.
Before/after satellite imagery doesn't replace the seismic reading that fires the trigger in the first place. It gives both sides a second, independent layer to check the footprint against, so the payout decision isn't resting on one party's own account of what happened on the ground.
Why magnitude alone doesn't close the file
A ground station network tells you how big the event was at a point, or a few points, and a shake-map model interpolates the rest. That's fine for triggering the policy. It's thinner when the actual dispute is about footprint: did the shaking that cleared your magnitude threshold also produce damage inside the defined radius, or did the epicenter sit at the edge and the worst of it land somewhere outside your zone?
Gauge density varies a lot by region. Some basins have a station every few kilometers; others have one for a hundred-kilometer radius and a lot of inference in between. When a counterparty questions a payout, "the model says so" is a weaker answer than a dated image showing the ground before the quake and a dated image showing it after.
The actual before/after process
The verification itself is simple in concept, less simple to do well under time pressure:
- Lock a baseline scene before the event window opens. This is the "before" half of the read, and it has to predate the quake by enough margin that nobody can argue seasonal change or unrelated construction explains a difference.
- Define the trigger geometry up front. A radius around the epicenter, a fault trace buffer, or a grid tied to the parametric structure, whatever the contract actually specifies, has to be nailed down before an event happens, not negotiated after.
- Pull the post-event pass as soon as the trigger condition registers. This is where event-driven cadence matters: the imagery order fires off the seismic trigger itself, not a weekly or monthly schedule that might land the right pass three days too late or three days too early.
- Compare the two scenes inside the defined area. At 10 to 30 meter resolution across a wide swath, a multispectral read picks up footprint-level change: collapsed structures, shifted debris fields, blocked access roads, altered terrain. Changes visible in the pixel pattern even without resolving individual buildings.
- Hand over both dated scenes and the comparison, not just a conclusion. The adjuster, the cedent, and the counterparty are all looking at the same two images and the same AOI.
What this is not: a substitute for a structural engineer walking a single building. A 10 to 30 meter pixel won't tell you if one house's foundation cracked. It tells you whether the footprint inside your trigger zone shows a regional damage signature consistent with the event, which is usually the actual question a parametric contract needs answered to settle, not a building-by-building inspection.
Why independence is the point
The reason this works as a settlement tool and not just a nice-to-have is that neither party is grading its own homework. The cedent didn't fly the drone. The counterparty didn't pick the comparison dates. A third-party read, pulled from the same wide-swath source before and after, with the trigger geometry fixed ahead of time, is harder to argue with than either side's internal account, because nobody on either side of the contract controlled when the images were taken or how the AOI was drawn.
If your contract language already references satellite confirmation as a condition of payout, the gap to close is operational: who locks the baseline, who triggers the post-event pull, and who delivers the comparison in a form an adjuster can actually use. Trigger Verification is built around exactly that sequence, an independent before/after read tied to the event, not a dashboard you have to remember to check.
If you're drafting trigger language for the next renewal, put the baseline-scene date, the AOI geometry, and the post-event pull window into the contract text itself. That's three decisions a live dispute will otherwise force you to make on the fly, under a counterparty's clock instead of yours.