The distinction between outputs and outcomes is one of the most important concepts in grant reporting — and one of the most frequently confused.
Most grant reports are full of outputs. Most funders say they want outcomes. The gap between what's asked for and what's actually useful is one of the persistent frustrations on both sides of the grants table.
Here's what the distinction means in practice and how to build reporting requirements that capture outcomes without creating impossible burdens for grantees.
Outputs are what you did. The number of workshops run, the people who attended, the resources produced, the services delivered. Outputs are countable, observable, and usually available shortly after the activity happens.
Outcomes are what changed as a result. The knowledge participants gained. The behaviours that shifted. The relationships that formed. The problems that got solved. Outcomes take longer to manifest and are harder to measure, but they're what the grant was actually trying to achieve.
An example:
| Activity | Output | Outcome |
|---|---|---|
| Financial literacy workshops for job seekers | 12 workshops, 180 participants | Participants report greater confidence managing household budgets; 40% open a savings account within 6 months |
| Environmental restoration planting programme | 3,000 native plants planted across 8 sites | Native bird populations increase at two of the sites within 18 months |
| Grants management training for community foundations | 6 training sessions, 45 staff trained | Trained staff report improved confidence; participating foundations reduce average processing time by 30% |
Outputs tell you that activity happened. Outcomes tell you whether it mattered.
Outputs are easier to count. Funders know how to ask for them. Grantees know how to report them. They're available quickly, don't require follow-up measurement, and look impressive ("we reached 3,000 people").
Outcomes require more effort on both sides. They require thought about what change you're trying to create, how you'd know if it happened, and how you'd measure it. They often require follow-up contact with beneficiaries, which takes time and sometimes raises privacy considerations.
The path of least resistance is outputs. But a grant programme that only measures outputs doesn't know whether it's achieving anything.
Good outcome reporting doesn't require sophisticated research methodology. It requires clarity about what change you're trying to create and a proportionate approach to measuring whether it happened.
For a small community grant ($5,000–$25,000): Short participant feedback (a simple survey or structured conversation) plus grantee reflection on what changed for participants. This can be two or three questions. It doesn't need to be a research study.
For a mid-range grant ($25,000–$100,000): Pre-defined outcome indicators agreed at the grant offer stage, with data collection built into the project design. Grantees report against these indicators at acquittal.
For a large grant ($100,000+): A defined theory of change or outcomes framework, with agreed indicators, data collection methods, and timeline for measurement. May include independent evaluation for the largest grants.
The most common mistake is asking for outcomes in the acquittal report, for work that only finished last month, when any real change would take a year to manifest. You're asking grantees to report on something that can't be known yet.
Practical design principles:
Match your timeline to the type of change you're measuring: If you're funding a six-month programme targeting behaviour change, you won't have reliable outcomes data at the end of six months. Design a light-touch acquittal at grant close, and a follow-up check-in at 12 months to capture actual outcomes.
Agree indicators at grant offer, not at acquittal: The time to have a conversation about what change you're trying to create and how you'll know it happened is when you're offering the grant — not when you're asking the grantee to write a report. This also helps grantees build measurement into their project design rather than trying to reconstruct it afterwards.
Accept proxy measures where direct measurement isn't feasible: Not all outcomes can be directly measured. Participant confidence is hard to observe; a self-reported change on a five-point scale is a reasonable proxy. Behaviour change in a community is hard to attribute; increased engagement with a service is a reasonable indicator. Be willing to accept proportionate evidence, not just rigorous research.
Distinguish between contribution and attribution: For most community grants, grantees are contributing to change alongside many other factors. It's unreasonable to ask them to prove that their programme caused the outcome. Asking them to describe how their work contributed to change, and what evidence supports that view, is a much more realistic expectation.
Grantees who are used to reporting outputs will sometimes push back on outcomes requirements — not because they don't care about outcomes, but because they're not sure what's being asked or how they'll gather the evidence.
The conversation shifts when you frame it as: "We're trying to understand what changed for the people you worked with. You probably know more about this than we do — what have you seen or heard that tells you the programme made a difference?"
That question produces more useful information than any standard reporting form. And it positions the outcomes conversation as genuine curiosity about impact, not an accountability trap.
This article is part of the complete guide: Grant Reporting Templates: What Funders Actually Need from Grantees.