AI Does Not Prevent Disasters. It Buys Time.

The brief for this cycle was "how AI can prevent/help natural disaster from happening." Half of that sentence is wrong.

AI does not stop a river, a cyclone, or a fault. It can, in a growing set of places, buy time — hours for a flood, days for a storm track, seconds for a quake if you are not at the epicenter — and then map what broke so the next truck is not a guess. Whether anyone spends that time is still a human job: cash, sandbags, a bus, a closed road.

On 7 July 2026 the ITU, UNDRR, WMO and IFRC published Leveraging AI to Enhance Multi-Hazard Early Warning Systems, a practical annex to the UN's Early Warnings for All (EW4All) push since COP27. Google's crisis-resilience write-up of the same day is the most concrete public inventory of what is actually in production. This post is a map of those jobs. It is not a product roundup, and it is not a claim that models "prevent" weather.

Four jobs, not one slogan

Lump "AI for disasters" into one slide and you get hype. Split it and you can audit a pitch.

1. Forecast the hazard. Rain, river stage, cyclone track, fire weather, flood extent. This is the grown-up layer: hydrology models, nowcasts, WeatherNext-class atmosphere models. It is also where local gauges still beat a global prior.

2. Get the warning to a phone that can act. Common Alerting Protocol (CAP) feeds into Search, Maps, and Android. Public Alerts from national services. This is dissemination, not meteorology. A perfect forecast that dies in a PDF is not an early warning system.

3. Spend the lead time. Anticipatory action: cash before the water, sandbags, pre-positioned shelter. This is the part vendors skip. GiveDirectly paying families in Kogi State, Nigeria, before a forecast flood is the honest success story — not because a model is magic, but because someone wired money while shops were still open.

4. Map the damage. Satellite plus building footprints plus a damage classifier, so UNOSAT is not hand-tracing 400,000 roofs. This is response, not prevention. It starts after the event.

If a vendor mixes 1–4, ask which job they actually run, on whose authority, and what happens when the model is wrong.

A December 2025 SAPEA evidence review for EU science advice said the same thing in plainer language: AI is strongest on standard, data-heavy, frequent hazards — floods, wildfires, droughts — and weakest where events are rare, labels are thin, or physics does not give you a precursor. That is a product constraint, not a temporary bug.

Floods: the operational case

River floods are where AI early warning has left the demo.

Google Flood Hub is the public face: coverage on the order of two billion people across more than 150 countries in basins with significant flood risk. UN OCHA stood up a Floods Anticipatory Action Programme in Adamawa, Nigeria, on those river forecasts. When the model crosses a threshold, the programme is supposed to trigger early interventions (shelter, not a tweet). GiveDirectly used the same class of forecast in Kogi State to send cash transfers before the water, so households could leave and buy sandbags.

That is "help." It is not "prevent the flood." The river still comes. The difference is whether the household still has a working ATM.

Two caveats belong next to the coverage number:

• Ungauged basins still need local data. A WMO pilot with hydrological services in Czechia, Nigeria, Uruguay and Vietnam found that stuffing local streamflow into a global AI model materially improves forecasts where gauges are sparse. Google open-sourced a hydrology modeling framework and a Groundsource dataset for urban flash floods so agencies can keep their own observations. The lesson is not "delete the hydrologist." It is "the global prior is a starting weight."
• Urban flash floods are a different product from large-river stage. Do not sell a basin model as a storm-drain model.

If you run a city: buy the forecast only if it is wired into a playbook with a budget. A dashboard is not anticipatory action.

Cyclones: days, if the track is the question

During the 2025 Atlantic season the US National Hurricane Center used Google's WeatherNext model. For Hurricane Melissa (October 2025) it had a historic Jamaican landfall about five days out, which Jamaica's Met Service could actually put on air. Five days is a lot of time for a small island. It is not a guarantee of a quiet week, and it does not move the storm.

Treat track skill and intensity skill as different products. A landfall call that is early and a wind-field call that is late are not the same win. Do not quote one as the other.

Wildfires: see it sooner, not put it out

The operational AI job on fire is detection and perimeter, not suppression.

Google tracks fire boundaries from satellite imagery in Search and Maps in 34 countries. FireSat, with the Earth Fire Alliance and Muon Space, is a purpose-built constellation aimed at faster detection before a start becomes a run. Additional FireSat birds launched from Vandenberg on the day of the UN report (7 July 2026). That is a sensor program. It does not rain.

If you sell "AI will prevent wildfires," you are selling weather control. If you sell "the duty officer sees a start in minutes instead of hours," you are in the real market. Fuel, wind, and crews still decide the rest.

Earthquakes: seconds, not days

Earthquakes are the clean counter-example, and they should stay in every brief so the flood story does not colonize the whole category.

Nobody has a reliable earthquake prediction product. What exists is early alerting after the rupture has started: P-waves, dense sensors, a few seconds to tens of seconds for people away from the epicenter. Google's Android Earthquake Alerts treat phones as a seismometer network. When earthquakes hit Venezuela in June 2026, the system alerted millions of users outside the epicenter so they could take cover before the strong shaking arrived. That is real. It is also not a forecast you can evacuate a city on.

Do not put "earthquake prediction" on a platform list next to "flood forecast." They are not the same maturity, and pretending they are gets people killed.

After: maps that save weeks

Once the water or wind has happened, the bottleneck is counting damage fast enough for logistics.

UN Global Pulse's DISHA workflow, with Google Open Buildings and a building-damage model, is in use with UNOSAT. Google says it has been deployed 11 times. On Hurricane Melissa it assigned preliminary damage scores to more than 385,000 buildings. After the February 2026 floods in Colombia, UNOSAT crossed AI building maps with radar flood extent so humanitarian agencies had a picture instead of a backlog.

This is not early warning. It is the fourth job. Keep it in the stack because it is where computer vision actually earns its keep — and because it is the job most "prevention" decks quietly skip when they need a pretty map.

A short test for any disaster-AI pitch

1. Which of the four jobs is this? Forecast, alert, anticipatory action, or damage map. If the answer is "all of them," it is a brochure.
2. What is the lead time, in the hazard's own units? Days for a basin flood. Hours for flash flood. Seconds for a quake. "Real time" is not a unit.
3. Who is allowed to spend the warning? A finance ministry, a Red Cross cash programme, a fire duty officer. If there is no spender, the model is a screensaver.
4. What happens when it is wrong? False alarm fatigue is how you lose the next real event. A review budget — like cricket's DRS — is the grown-up design. Fully automatic alerts with no human-call band will be ignored or, worse, trusted.

What to steal if you build software

You are probably not a met service.

• Steal the anticipatory cash lesson, not the globe. Wire the forecast to a payment or a ticket, with a human threshold.
• Steal the local gauge lesson: a global model plus your own stream is better than either alone. Keep the observations.
• Steal the seconds vs days lesson: product maturity is lead time, not model size. Do not ship earthquake-prediction copy.
• Steal the damage map lesson: computer vision on a known building layer beats a chatbot summarizing tweets.

If you are a board or a ministry: buy a forecast only with a CAP feed, a playbook, and a budget line that can move before the crest. If the analyst cannot query what the public just saw, you paid for a cartoon.

What not to do

Do not say AI prevents natural disasters. Do not equate Flood Hub coverage with "the world is warned." Do not sell wildfire detection as suppression. Do not put earthquake prediction in a 2026 roadmap. Do not skip false-alarm cost. Do not treat a satellite damage score as a cadastral survey.

A simple map

Job	What exists in 2026	What it is not
Forecast floods / some storms	Flood Hub-class rivers; WeatherNext tracks	Weather control
Alert	CAP → Search / Maps / Android	A substitute for a siren network
Spend the time	OCHA / GiveDirectly-style anticipatory cash	Automatic
Detect fire	Perimeters, FireSat	Putting the fire out
Quake	Seconds outside epicenter	Prediction
After	UNOSAT / DISHA building scores	Prevention

The UN report is useful because it is boring in the right way: pillars, not miracles. AI helps where the data is dense and the action is already funded. Everywhere else it is a prototype with a keynote.

If you only remember one line: the model buys time; a human still has to spend it.

More at amtocbot.com.