The difference between outputs and outcomes is the difference between what a program does and what changes for the people taking part. Outputs are the products of a program's activities: the number of sessions held, the number of people served, the hours of instruction delivered, or the materials distributed. Outcomes are the changes the program hopes to see in the people or conditions it serves, such as new knowledge or skills, different behavior, or improved circumstances, usually described as short-term, intermediate, and long-term. The distinction matters to funders because many invest in a program to support change, and output figures alone describe activity without showing whether anything changed. Outputs still matter, because they show what was delivered and to whom, and outcomes are difficult to interpret without them.
Sort what you currently report into two lists, what the program delivered and what changed for participants, and see which list is longer.
If the first list is longer, it shows where your reporting can move from describing activity to describing change.
For one outcome your program is designed to produce, identify what information would show whether it's occurring and for whom.
An output counts anything the program produces or delivers, and an outcome counts a change in the people or conditions the program is meant to affect. A useful test is to ask whether the figure would still be true if nobody's knowledge, skills, behavior, or circumstances had changed at all. If it would, it's an output.
| Outputs | Short-term outcomes | Intermediate outcomes | Long-term outcomes |
|---|---|---|---|
| 40 tutoring sessions held; 60 students enrolled; average attendance per student | Greater confidence and skill in the subject | Better course grades and higher course completion | Students continuing in their education |
The figures and outcomes in the table are invented for illustration. Your own program's outputs and outcomes will depend on what it's designed to accomplish. If you're building a logic model, where outputs and outcomes sit side by side with goals, inputs, and activities, What's a logic model, and does my proposal really need one? covers it.
Funders ask about outcomes, and not only how many people you served, because a funder supporting a program usually wants to know whether it's making a difference, and the number of people served doesn't show whether that change is occurring. Saying that a program served 200 people describes activity. Explaining who participated, what they experienced, what changed, why that change matters, and what the organization learned describes the program's progress toward what it set out to do.
That doesn't mean output figures are unimportant to funders. Many require them in reports, and they're often the first thing a funder checks to see whether a program reached the people it was designed to serve. What a particular funder requires is in your grant agreement or reporting template, so read those before deciding what to report.
Outcome figures can hide important differences between groups, the experiences of people who left the program early, and the role of influences outside the program. An overall average may show improvement while one group of participants made little progress, so looking at results by group, site, or level of participation often reveals more than the total. A survey given at the end of a program usually reaches only those who finished it.
Outcome figures also can't establish on their own that the program caused the change. Participants' lives are shaped by many influences, and positive outcomes don't automatically tell you what produced them. Being clear about what your evidence can and can't support makes an outcome report more credible to a funder.
Outputs still matter when funders care about outcomes, because outcomes are difficult to interpret without them. If an outcome falls short, output information helps you determine why: whether the program was delivered as planned, who participated, and how much of the program they actually received. Participants who attended two sessions and participants who attended twenty didn't receive the same program, and output records are often the only place that difference is documented. Are we collecting the right data to show that our program is working? explains why information about how a program is carried out belongs alongside its results.
Organizations doing meaningful work often know their programs are making a difference but struggle to demonstrate that difference. Anecdotes matter. Numbers matter. Participant voices matter. Outcomes matter. The strongest stories often combine them.
Evaluation can help an organization move beyond saying, "We served 200 people," to explaining who participated, what they experienced, what changed, why that change matters, what the organization learned, and what happens next. That's the difference between reporting activity and communicating impact. Numbers can show patterns and change, and participants' own accounts can help explain why a pattern may be occurring. Used together, they provide a much more complete picture.
The number of people you served is an output, because it describes the program's reach. It becomes more informative when you can also say who those people were and whether they're the people the program was designed to serve.
Participant satisfaction is useful information about how people experienced the program, but it usually isn't the change the program was designed to produce. Treat it as information about how the program is working for participants, and pair it with evidence about whether the intended changes are occurring.
A small program can report outcomes, as long as it's honest about what the information can show. With a small number of participants, describe what changed and for whom, and combine figures with participants' own accounts, instead of claiming more certainty than the numbers allow.
Explaining your outcomes to a funder or a board is a reporting question that starts once you know what changed. How do I turn program data into a report my funder actually reads? and How do I explain our results to a board that just wants numbers? cover it.