M&E software for NGOs: what to look for

Good M&E software for an NGO does four jobs well: it holds your results framework, takes data in from the field with little effort, keeps indicators current between reports, and turns them into donor and board reports. Choose by the jobs you need, not the longest feature list.

Milestra team · 26 October 2026 · 8 min read

Start with the jobs, not the tools

Most NGOs start looking for M&E software after a bad reporting cycle. Three funders asked for slightly different numbers, the master spreadsheet had four versions, and the programme manager spent a week reconciling them. The temptation is to buy the tool with the longest feature list. A better starting point is to write down the jobs you need the software to do.

For most organisations, those jobs are:

  1. Hold the results framework. Goals, outcomes, outputs and indicators, with baselines, targets, owners and reporting periods. For many teams this is a logframe per grant plus an organisational strategy.
  2. Take data in. From mobile surveys, partner reports, registers, finance systems and the occasional photo of a paper form.
  3. Keep indicators current. Someone, or something, has to turn raw data into this month's number and flag what is off track.
  4. Produce reports. Donor reports in each funder's format, board reports, internal reviews and sometimes a public impact page.
  5. Keep the evidence. Attendance sheets, photos, case studies and verification documents, linked to the results they prove.

Very few tools do all five equally well. Knowing which two or three matter most to you is the single most useful thing you can bring to a software search.

The main types of M&E tool

The market is easier to understand if you sort tools by what they were built to do.

TypeBuilt forExamplesWatch out for
SpreadsheetsFlexible tables anyone can openExcel, Google SheetsVersion sprawl, broken formulas, no history of who changed what
Mobile data collectionSurveys and forms in the field, often offlineKoboToolbox, ODK, SurveyCTO, CommCareGreat at collecting, not designed to manage targets or write reports
Health and government information systemsRoutine national or district reportingDHIS2Powerful but usually needs specialist set-up and support
Dedicated M&E platformsIndicator tracking across projects and grantsActivityInfo, DevResults, and othersSet-up effort; check they fit how your team actually works
Business intelligenceDashboards on top of existing dataPower BI, Tableau, Looker StudioNeed clean data underneath and someone to maintain them
Goal and results trackingLinking strategy, indicators, owners and regular check-insMilestra and othersNot a replacement for a survey tool or a case management system

Many NGOs end up with a combination: a mobile data collection tool in the field, and one system that holds the indicators and produces reports. That is fine. The mistake is having four systems that each hold a slightly different version of the same number.

What to look for: a practical checklist

Results framework fit

  • Can it hold your structure as it really is? Organisational goals, programme outcomes and grant logframes often overlap. Look for a way to link one indicator to several funders without entering it twice.
  • Does each indicator carry a definition, unit, baseline, target, frequency and owner? If not, you will end up rebuilding your indicator reference sheets somewhere else.
  • Can you report by period (quarter, grant year, financial year) without restructuring everything?

Getting data in

  • Does it connect to the data collection tool you already use, or will someone retype numbers every month? Our guide to tracking programme KPIs from KoboToolbox data shows what a good connection looks like.
  • Can partners and field staff submit updates without a full licence or a long training session?
  • Does it work on a low-bandwidth connection, or offline? Test this from the field office, not from headquarters.
  • Can you import a spreadsheet to get started, so last year's data is not lost?

Keeping numbers current

  • Does it show progress against target and flag what is off track, or does it just store numbers?
  • Is there a light, regular routine (a weekly or monthly check-in) that keeps owners updating, or does everything happen the week before a report is due?
  • Can you see who changed a figure and when?

Disaggregation

Many funders ask for results by sex, age, disability, location or other groups. Check that the tool can hold disaggregated data properly, rather than as a pile of separate indicators that nobody can add up.

Reporting

  • Can it produce a donor report from the live indicators, with baseline, target, actual and a short narrative?
  • Can you filter to one grant, one country or one programme?
  • Does it export cleanly to Excel or PDF for funders who insist on their own template?

Evidence and verification

  • Can you attach evidence to a result, and can a manager sign it off?
  • Will it help in an audit or a funder verification visit, or will you still be searching email?

Data protection and security

  • Where is the data stored, and can you get it all back out in a standard format?
  • Are roles and permissions granular enough to keep personal data away from people who do not need it?
  • Involve your data protection lead early; they will have questions of their own.

People and cost

  • Who will own the system day to day? A tool that only one consultant understands will not survive their contract.
  • What does it cost for the number of people who need to update results, and for people who only need to view them? Check whether board members and donors can see reports without a paid seat.
  • What does set-up really involve: days, weeks or months?

A worked example: a multi-country WASH and health programme

Imagine an NGO running water, sanitation and hygiene (WASH) and maternal health programmes in three countries, funded by five institutional donors and a foundation.

Today the field teams collect household surveys and water point checks in KoboToolbox. Each country office keeps its own indicator spreadsheet. Every quarter, the regional M&E officer copies numbers into five donor templates, and the board gets a separate slide deck built by hand.

When this NGO writes its requirements, the list is short and specific:

  • Must have: one place for every indicator, linked to each donor's logframe; an automatic link from KoboToolbox so "% of water points functional" updates itself; reports filterable by donor and by country; disaggregation by sex and district.
  • Should have: a weekly check-in so country managers update the indicators that are not in KoboToolbox, such as "health facilities with trained staff"; evidence attached to results; a board-ready summary.
  • Nice to have: a public impact page; SMS updates from partners with poor connectivity.

With that list, the NGO can test three or four tools in a fortnight rather than sitting through a dozen demos. It also knows what it is not buying: it does not need a new survey tool, because KoboToolbox already works well in the field.

How to run a fair trial

  1. Use your own data. Load one real programme with its real indicators, not the vendor's demo data.
  2. Involve the people who will update it. A country programme manager and a field M&E officer will spot problems that headquarters will not.
  3. Produce one real report. Pick last quarter's donor report and try to reproduce it. If you cannot, find out why before you buy.
  4. Test the awkward cases. An indicator shared by two donors, a target revised mid-grant, a partner with intermittent internet.
  5. Time it. Note how long a monthly update and a quarterly report take, compared with the current process.

Two to four weeks is usually enough. Longer trials tend to lose momentum.

Common mistakes when choosing M&E software

  • Buying for the evaluation, not the monitoring. Evaluations happen once or twice in a programme's life. Monitoring happens every month. Choose for the routine.
  • Expecting software to fix an unclear framework. If your indicators are vague, a tool will store vague indicators very efficiently. Sort out your M&E plan first.
  • Ignoring the people who enter data. If updating takes too long, people stop doing it and the system quietly dies.
  • Replacing tools that work. If your field team is happy with its survey tool, connect to it rather than replacing it.
  • Forgetting the exit. Make sure you can export everything if you change provider later.

Where Milestra fits

Milestra is a results and reporting layer. It holds your goals, key results and indicators with owners and targets, keeps them current through short weekly check-ins and nightly syncs from KoboToolbox, ODK and Google Sheets, and produces board and donor reports from the live numbers. It is not a survey tool or a case management system: it sits alongside the tools that collect your data. You can see the details on the features page, and how it handles logframes, indicators and donor reports on the OKR software for nonprofits page.

Frequently asked questions

What is the difference between M&E software and a data collection tool?

A data collection tool such as KoboToolbox or ODK is built to gather survey responses and forms, often offline. M&E software is built to hold your indicators and targets, track progress over time and produce reports. Many NGOs use both and connect them.

Can a small NGO manage M&E in spreadsheets?

Yes, for a while. A well-structured indicator tracking table in Excel or Google Sheets works for one or two programmes and a small team. The strain usually shows when several people update the same file, or when you report to more than two or three funders.

How long does it take to set up M&E software?

It depends far more on how clear your results framework is than on the tool. If your indicators, baselines and targets are already written down, a first programme can usually be set up in days. If they are not, expect to spend most of the time agreeing them.

Should M&E software replace our logframes?

No. The logframe is the agreement with a funder about what you will achieve. M&E software should hold those logframe indicators and keep them up to date, so that reporting against the logframe becomes easier. Our logframe template is a good place to start.

What should we ask vendors about data protection?

Ask where data is hosted, who can access it, how permissions work, whether data is encrypted, how long it is kept, and how you can export or delete it. If you collect personal data about programme participants, involve your data protection lead before signing.

Try Milestra for free

Put this guide into practice in 10 minutes

  • Goals, key results and indicators in one place
  • Two-minute weekly check-ins with reminders
  • Donor and board reports from live numbers
  • Free for up to 5 people · 50% off for nonprofits

Keep reading