By Editorial — IT Researches

Disaster response is a problem of decisions made quickly, with incomplete information, by people under pressure. That makes it a domain where AI is both attractive and dangerous. Used well, it shortens the time between an event and an informed decision. Used carelessly, it adds confident-looking noise to a situation that already has too much of it.
The core approach
The most mature use is damage assessment from imagery. Satellite, aerial and drone images can be compared against pre-event baselines to flag collapsed buildings, flooded roads and blocked access routes. Computer-vision models do not replace field assessment teams; they tell those teams where to look first. The practical requirements are unglamorous: reliable baseline imagery, agreed damage categories, and a review step in which a trained analyst confirms what the model flags before it reaches a coordination map.
The second use is forecasting demand for relief supplies. Water, shelter, medical stock and fuel are needed in different places at different times, and the pattern changes as roads reopen and people move. Forecasting models built on population data, previous events and live logistics signals can help planners pre-position stock. The same lessons we see in commercial forecasting apply: measure bias, not only error, and keep prediction ranges visible rather than collapsing them into a single number.
The third use is triage of incoming messages. After a major event, emergency lines, social media and partner organisations produce large volumes of requests in many languages. Language models and classifiers can group, translate and prioritise those messages so that coordinators see urgent medical or rescue needs sooner. This is also where errors are most costly, so the system should route uncertain cases to people, record why each message was prioritised, and never silently discard anything.
Trade-offs and failure modes
Across all three, data protection matters. Location data, health information and messages from vulnerable people are sensitive by nature. Systems should collect only what the response needs, restrict access by role, set retention limits in advance, and be clear about which partners may receive which data.
Preparation decides whether any of this works on the day. Models, data agreements, imagery sources and escalation procedures need to be in place and rehearsed before an event, not assembled during one. Exercises that include the AI tooling — and its failure modes — reveal gaps that no evaluation report will.
The realistic future of AI in emergency relief is not autonomous decision-making. It is faster situational awareness, better-placed supplies and fewer missed requests, with accountable people making the calls. Organisations that approach it that way will get the benefit; those that expect the technology to make the decisions for them will be disappointed at the worst possible moment.

