AI for Humanitarian Organisations

Last updated: 2026-08-15

Humanitarian AI is the use of artificial intelligence in aid operations, covering registration, feedback, targeting, forecasting, and service delivery for people affected by crisis. Humanitarian AI succeeds or fails on conditions that rarely appear in a demonstration: intermittent connectivity, many low-resource languages, sensitive personal data, and people who cannot appeal a wrong decision.

A practitioner guide to adopting artificial intelligence in humanitarian organisations, written from delivery rather than from policy. It covers the use cases that survive contact with the field, the risks that matter most when the people in the data are displaced, and the governance that keeps a human accountable for consequential decisions.

What humanitarian AI actually means

Humanitarian AI covers the systems an aid organisation runs on behalf of people in crisis: registering them, scheduling their appointments, hearing their complaints, forecasting where they will move, and deciding who receives assistance first. The subject is not the model. The subject is a person who cannot choose another provider, cannot easily appeal, and carries the cost when a system is wrong.

That asymmetry is what separates humanitarian AI from commercial AI. A recommendation engine that misfires loses a sale. A targeting model that misfires removes a family from an assistance list. The engineering is similar; the tolerance for error, and the obligation to explain it, is not.

Where AI holds in humanitarian operations

Four categories have repeatedly worked in practice. Access and scheduling: voice and messaging systems that let people reach a service without an app or a data plan. Feedback and accountability: transcribing and classifying what affected people say, so complaints reach the team that can act rather than dying in a spreadsheet. Data integrity: finding duplicates, gaps, and errors in registration data that quietly degrade every service built on top of it. Staff productivity: retrieval over project documents and policy so officers stop rediscovering the same answer.

What these share is that the AI sits behind an operational process with a named owner, not in front of a beneficiary making an unreviewable decision. See the AI for refugee operations hub for the delivered examples, including an interactive voice response appointment system used by more than 700,000 refugees.

Where it fails

Most humanitarian AI failures are not model failures. They are delivery failures: the system assumed connectivity that was not there, a language it did not support, a governance step that was skipped, or a user context it never accounted for. That pattern is set out in full in the Last-Mile AI Framework, which treats those constraints as design inputs rather than deployment surprises.

Three failure modes recur. A pilot proves a model and never confronts the operating environment. A chatbot is placed in front of crisis-affected people without a route to a human. And a system is procured rather than built, so nobody inside the organisation can explain how it decides or switch it off.

The governance that has to come with it

Governance in this sector is not a statement of principles. It is a set of answers to operational questions: who may approve a model for production, who can switch it off, how risk is tiered by consequence rather than by technology, and what observable condition brings a system down. Those answers are set out in the AI governance playbook, with a model register and approval gate you can use unchanged.

Data responsibility carries the same weight. Humanitarian data describes people who may be at risk from the state they fled, so data minimisation, retention limits, and access control are protection measures rather than compliance paperwork. For the wider institutional view, see AI governance in the United Nations.

How to decide whether a use case is suitable

Four questions settle most cases. What happens to a person if the system is wrong, and can they appeal? Does the organisation hold data of sufficient quality to support the task at all? Is there a named owner who will carry the decision, not a committee? And is there a channel to a human at the point where the system stops being confident? A use case that cannot answer all four is a research project, not a deployment. The use case discovery playbook turns those questions into a scoring sheet.

For related work, see agentic AI in humanitarian operations, the delivered project portfolio, and AI security and assurance.