Software for humanitarian organisations

Field systems, beneficiary data and donor reporting, built by a team that has delivered for international humanitarian organisations.

Software for humanitarian organisations covers field data collection, beneficiary and case management, distribution tracking and donor reporting. It usually runs where connectivity is poor, and it always carries an unusual duty of care toward the people in the database. AMT (Advanced Millennium Technologies) has delivered systems for international humanitarian organisations and is ISO 27001:2022 certified.

Trusted by

// beneficiary_management

What beneficiary management software covers

What beneficiary management software covers
Stage	What the system handles
Registration	Capturing who needs help, offline, with only the fields the programme truly needs.
Eligibility and targeting	Applying programme rules consistently and recording why each decision was made.
Case management	Following a person or household over time, with record-level access control.
Distribution	What was delivered, to whom, where and when, and whether it reconciles.
Feedback and referrals	Complaints, feedback and referrals to partner organisations, handled safely.
Donor reporting	The numbers each donor requires, produced without a month of manual work.

// duty_of_care

Why humanitarian software is different: people cannot opt out

Commercial software collects data from people who chose to use a product. Humanitarian software often does not. Someone registering for assistance is not in a position to refuse the data collection, may not be able to read the consent language, and may be at real risk if the data reaches the wrong people.

That is a different obligation from GDPR compliance. Meeting the regulation is not the same as meeting the duty of care.

// data_protection

Six principles for protecting beneficiary data

Six principles for protecting beneficiary data
Principle	What it changes
Collect less	The most protective design choice is not collecting a field at all. Every field should justify itself against a real programme need.
Sensitive by default	Location, ethnicity, family structure and status are restricted from the very first database design.
Record-level access control	Who can see which beneficiary, from which office, in which situation. Role-based access alone is not enough.
Retention that really deletes	Deletion has to be real, scheduled and verifiable, including in backups.
Plan for lost devices	Encryption, remote wipe and minimal data on the device are the baseline.
All of this, offline	Every protection still has to hold when a device has been out of contact for a week.

Get the beneficiary data checklist

Six design decisions that protect people who cannot opt out, with the question to ask any vendor about each. One page, written for programme and IT teams to read together.

// proof

Proof

Legal aid platform for an international humanitarian NGO. A multi-tenant, multilingual platform that lets several organisations run their own legal counselling on one shared system, serving people displaced by conflict, disasters and climate change. It combines a legal content library that stays current as rules change, decision-tree guided counselling and a client portal. Built on Angular (PWA), Node.js and MongoDB, and supported by AMT under an SLA for more than six years, with the engagement still running.

// what_we_build

Humanitarian software we build

Humanitarian software AMT builds
Service	What it covers
Field data collection	Offline-first, on the devices field teams actually use.
Beneficiary and case management	With record-level access control designed in.
Distribution and programme tracking	What was delivered, to whom, and what reconciles.
Donor reporting	Reporting that produces the numbers donors require.
Integration	With the platforms the sector already runs on.

// budgets

A word on budgets

Humanitarian organisations work to restricted budgets with donor scrutiny on every line. We are not the cheapest engineering firm, and we do not pretend to be. The expensive failure in this sector is a system field teams work around because it does not function where they are, which means the programme data is wrong and the donor report is built on it. Our discovery is fixed price, and you own the output whether or not you continue.

// faqs

FAQs: software for humanitarian organisations

What is beneficiary management software?

Software that registers people who receive assistance, checks eligibility, tracks cases and distributions over time, and produces donor reports, while protecting data about people who often cannot opt out.

Is GDPR compliance enough for humanitarian data?

No. GDPR is the legal minimum. Humanitarian work adds a duty of care toward people who cannot refuse data collection and may be at risk if it leaks, which calls for collecting less and stricter access control.

Have you worked with humanitarian organisations?

Yes. We have delivered for international humanitarian organisations, so the sector's constraints around connectivity and beneficiary data are familiar to us.

Does it work without connectivity?

It has to. Our field systems are offline-first, and every protection still holds after a device has been offline for a week.

Can you meet donor reporting requirements?

Yes, and it is worth designing for from the start, so reports do not need a month of manual reconciliation every cycle.

What happens if a field device is lost?

Data is encrypted, the device can be wiped remotely when reachable, and very little is stored locally.

Talk to an engineer who has built for the field

30 minutes. Bring the programme and its constraints, including the budget, and we will tell you honestly what is achievable.

Not ready to talk? Read how we deliver. No form.