The Monitoring, Evaluation and Learning System Nonprofits Actually Need
Here is a scene that will be familiar to many people who work for small or resource-constrained non-profits.
It’s December. Time for the funder report scramble.
Someone opens a spreadsheet that was last updated in March. A program manager pulls numbers from memory, or from emails, or from a stack of sign-in sheets that have been sitting in a folder since June. Or from a haphazardly created database by someone who doesn’t actually know how the work works so pulling together useful data is difficult and the result is suspect. The report gets written. It sounds fine. Nobody is sure how much of it is accurate.
This is not a failure of commitment. The tracking and measuring is secondary to implementation. Almost everyone in this situation cares deeply about their work and wants to be accountable for it, but not at the expense of producing more impact. But there is the rub. How do you know if you’re producing more impact if the monitoring, evaluation and learning system — if there is one — was built for someone else? Does it answer questions the funder asked rather than what the team is actually trying to answer? Perhaps it requires more maintenance than anyone has capacity for or it produces information too late to use. Is it created for a team with full time MEL staff but there isn’t enough funding to pay for that?
The result is a system that creates reporting burden without creating learning. That is the opposite of what monitoring and evaluation is supposed to do.
What a useful MEL system actually does
A MEL system that works for a small nonprofit does three things.
First, it answers questions your team is already arguing about. Not hypothetical questions, not questions a consultant decided were important, not questions lifted from a logic model template. The questions that actually come up in staff meetings. Are we reaching the people we said we would reach? Is this program component worth the time it takes? Are things getting better for the people we serve, or are we just busy?
Second, it is light enough for someone to maintain without a dedicated data person. If your MEL system requires a database administrator, a data analyst, or more than a few hours a week of staff time, it will not survive contact with reality in a small organization. They don’t have that capacity, and building a system that assumes they do guarantees it will be abandoned.
Thirdly, it produces information when decisions need to be made, not just when it’s report-writing time. A report that arrives six months after a program ends cannot improve that program. Data that lives in a spreadsheet nobody knows how to read cannot inform a staffing decision. Useful MEL is timely, accessible, and connected to the moments when it can actually change something.
Having an external person come in and build a dashboard doesn’t usually solve the problem.
The difference between outputs and outcomes
This is the distinction that matters most, and it is the one most small nonprofits get wrong — not because they do not understand it, but because outputs are much easier to count.
Outputs are what you do. Number of people served. Sessions held. meals distributed. Hours of training delivered. These are real and worth tracking. They tell you whether your program is operating as designed. They are necessary for funder reporting. They are not, by themselves, evidence that anything changed.
Outcomes are what changes as a result of what you do. A parent who attended twelve parenting workshops is an output. A parent who reports feeling more confident and less overwhelmed three months later is an outcome. A child placed in stable housing is an output. That child still in stable housing a year later, with improved school attendance, is an outcome.
The difference sounds obvious when stated plainly. In practice, the pressure to count things that are easy to count pushes organizations toward output-heavy systems. Outputs are available immediately. Outcomes require follow-up, often long after the program interaction has ended. Outcomes require asking people how they are doing, which takes time and trust and sometimes feels intrusive.
But a MEL system built entirely on outputs cannot answer the question funders and boards and communities actually want answered: is this working? It can tell you how much you did. It cannot tell you whether it mattered.
A useful MEL system tracks both, with a deliberate ratio. For most small nonprofits, a handful of outcome indicators — three to five — anchored to your core theory of change, combined with the output tracking you are already doing, is enough. You do not need twenty outcome measures. You need a small number of good ones, collected consistently, over enough time to see whether anything is moving.
What to track and what to leave out
The discipline of a good MEL system is not addition. It is subtraction.
Every indicator you add is a commitment to collect that data, clean it, store it, and use it. Most organizations add indicators because a funder asks for them, or because they seem important in the abstract, or because a consultant recommended them. Very few organizations ask the harder question: will we actually use this?
A reasonable target for a small nonprofit is no more than 20 indicators total, across all programs. Fewer is better. If no one explain in one sentence why you are tracking something and what decision it would inform, it probably does not belong in your system.
The other discipline is alignment. Your indicators should connect directly to your theory of change. Not the theory of change you wrote for a grant proposal, but the actual logic of why you believe your program produces the results it does. If your theory of change says that building relationships between youth and trusted adults leads to better decision-making, your outcome indicators should measure something about those relationships and something about decision-making.
Tools that are actually usable
For most small nonprofits, the right tool is the simplest one that does the job.
Google Sheets works for organizations with modest data volume and limited technical capacity. It is free, familiar, and accessible to everyone on your team. Its limitations are real — it is not a database, it does not handle relational data well, and it breaks down at scale — but for a small program tracking a few hundred participants across a handful of indicators, it is often enough.
Airtable sits one step up in sophistication. It handles relational data, supports multiple views of the same information, and has a low enough learning curve that non-technical staff can use it after minimal orientation. It is worth considering when your data has more complexity — multiple programs, multiple sites, data that needs to connect across tables.
Neither tool requires a data team. Both require someone with enough ownership of the system to keep it maintained and updated. That person does not need technical expertise. They need time, clarity about what the system is supposed to do, and organizational support to actually use it.
A reasonable starting point
Do not build your MEL system from a template. Do not start with a logic model and work backward to indicators. Start with questions.
Ask your program staff: what do you argue about? What do you wish you knew? What would help you make better decisions next month? Write those questions down. Then ask: what data would actually answer them?
Build your system around three questions. Collect that data for six months. See whether it gets used. Expand only when you have evidence the system is working — meaning people are looking at the data and it is changing how they think.
A good MEL system is not impressive. It does not have dashboards nobody reads or indicator libraries that run to forty rows. It is used. Someone looks at it before a program decision. Someone brings it to a board meeting and it changes the conversation. Someone says: we thought this was working, but the data says otherwise, so we changed it.
That is the whole goal.
Anthralytic is a strategy and evaluation studio helping mission-driven teams clarify and amplify their impact. If someone in your network makes decisions about resources in the social sector, this newsletter is for them.
