USGS PAGER alerts vs site-level damage checks for supply chain teams
USGS PAGER alerts are the first thing a lot of control towers see after a big earthquake. A yellow, orange, or red banner lands in your inbox within half an hour, sometimes faster, and someone on the team pulls the alert into the incident channel and asks what it means for the three named sites you have in that province. That question is where PAGER stops being useful and a site-level check has to start.
What PAGER actually tells you
PAGER (Prompt Assessment of Global Earthquakes for Response) is a USGS product built for humanitarian response and government triage, not supplier risk. Within minutes of a quake it estimates:
- The shaking intensity across the affected region, reported as MMI (Modified Mercalli Intensity), from instrument readings and ground-motion models
- A population exposure count at each MMI band, built from census and population-density layers
- A color alert (green, yellow, orange, red) tied to modeled fatality and economic loss ranges for the whole event
None of that is site-specific. PAGER doesn't know where your tier-2 connector plant sits, and it can't, because it was never built to. It's a regional severity estimate, generated from a model of shaking propagation and population density, not an inspection of any particular building. Two sites five kilometers apart, one on bedrock and one on fill, can see very different shaking and PAGER's regional bands won't separate them.
That's fine for what it's for. A disaster-response agency deciding how many search-and-rescue teams to mobilize to a province doesn't need per-building detail. A control tower deciding whether to activate a backup supplier for one named facility does.
Ground shaking estimate vs confirmed site damage
This is the real gap, worth naming plainly: PAGER gives you a ground shaking estimate. It does not give you confirmed site damage. Those are two different kinds of fact.
A shaking estimate says: at this location, the model predicts MMI 7, which is "very strong" shaking, the kind that can crack plaster and topple unsecured objects. It's a prediction, derived from seismic sensor networks and attenuation models, before anyone has looked at the building.
Confirmed site damage says: this specific roof is visibly intact, or this specific loading dock has collapsed debris in front of it, based on something that actually looked at the site after the event, imagery, an aerial pass, a person on the ground.
A site can sit inside a red PAGER zone and come through with no visible damage because of how it was built or where it sits on the ground. A site can sit inside a yellow zone and still take a direct hit from a secondary effect like liquefaction or a landslide that the regional shaking model doesn't resolve at that scale. Allocation decisions and claims desks both need the second kind of fact, not the first, and PAGER was never designed to supply it.
Where this leaves a control tower or claims desk
The honest sequence most teams end up running is: PAGER tells you an event happened and roughly how severe it is regionally, so you know whether to even open an incident. Then you still need, for each named site on your supplier list, a separate answer to "is this one inside the footprint, and is there visible damage." That second step is traditionally the slow part, a call to the supplier's plant manager who may not answer for a day, or a field adjuster booking a drive-out that takes longer than that.
Supplier Impact Assessment is built for exactly that second step: a per-site check against the confirmed damage footprint of a flood, quake, or cyclone, run when the event happens rather than on a reporting schedule, so you get an inside-or-outside call and a damage-or-no-damage read for each named location while allocation and claims decisions are still being made.
If PAGER is telling you an event just happened near your supplier base, the next question is which of your named sites sat inside its footprint, and that's worth checking before you wait on a supplier's own report.