Renata's declined proposal came back with feedback so brief that she read it for a week. The program was strong, the reviewers said, but the application described what the organization would do rather than what would change. She went back through her draft and counted: every paragraph in the project description was a verb attached to a volume. Hours delivered. Youth served. Workshops held. Not one sentence said what would be different about a young person's life at the end of it. The proposal was accurate, well written, and answering a question funders had stopped asking.

The Shift: From Activity To Impact

Ten years ago, grant proposals focused on activities. A typical sentence read: "We will provide 200 hours of mentoring to 50 youth." Today's funders want outcomes, and the equivalent sentence reads: "As a result of mentoring, 80% of participants will improve school attendance by an average of 15 percentage points." The difference is not stylistic. The first sentence describes an expenditure of effort and asks the funder to assume it produces something. The second describes a change in the world and commits you to measuring whether it happened.

This shift reflects funder accountability demands rather than a change in taste. Nonprofits receive tax deductions, and funders are scrutinized by their own boards and by the IRS, so they need proof that their grants work. Your grant proposal is the first place they look for that proof, before any site visit, reference call, or financial review. That is worth sitting with, because it reframes the outcomes section from a compliance exercise into the part of the document that does the persuading.

Outcome Versus Output: The Critical Distinction

An output is what you do, measurable in volume: "We served 150 students in 2026." An outcome is what changes as a result, measurable in impact: "Of those 150 students, 89% graduated high school, compared to 76% district average." The second statement contains the first, and adds the thing the funder is buying. Notice also that it carries a comparison, because a graduation rate with no benchmark beside it tells a reviewer nothing about whether your program made the difference.

Both belong in your proposal. Outputs justify efficiency, showing that you can deliver volume for the money. Outcomes justify impact, showing that the volume mattered. Your narrative should lead with the outcome and then explain the outputs that produce it, which is the reverse of the order most nonprofits write in, because most nonprofits write from the inside of their own operations outward. The reviewer is reading from the outside in.

The Logic Model: Your Roadmap

A logic model shows the if-then chain: if we do X, then Y will happen, leading to Z. Written out, it forces you to be explicit about a causal claim you are otherwise making silently. Here is a simple one for a youth mentoring program.

Your proposal should articulate this entire chain rather than the ends of it. Funders want to see that you have thought through cause and effect, and the question they are asking as they read is a simple one: why will this activity produce this outcome? A chain with a missing link, where an activity is followed by an ambitious outcome with nothing between them, reads as hope rather than as design, and reviewers who fund programs for a living recognise the difference immediately.

Theory Of Change: The Deeper Story

Where the logic model shows the chain, the theory of change explains why the chain holds. It is grounded in research or in proven practice, and it is the part of the proposal that distinguishes a program someone designed from a program someone assembled. A model paragraph, with the bracketed placeholders you fill in from your own evidence base, runs like this: "Our mentoring program is based on decades of research showing that consistent adult relationships improve educational outcomes for at-risk youth. Specifically, studies by [Smith, 2020] and [Jones, 2019] demonstrate that students with mentors show 15-20 percentage point improvements in school attendance. We have adapted this evidence-based model for our local context by [specific adaptations]."

A strong theory of change answers five questions in order. What problem are you addressing, stated as a root cause rather than a symptom? How does your solution address that root cause? What evidence supports your approach? What assumptions are you making, for instance that consistent mentor availability is critical to success? And what could go wrong, for instance that you cannot recruit enough mentors and outcomes suffer? The last two questions are the ones nonprofits skip, and they are the ones experienced reviewers weight most heavily, because a proposal that names its own assumptions and risks is written by someone who has thought about failure.

Measurable Outcomes: The SMART Framework

Funders expect outcomes that are Specific, with a clear definition of what will change; Measurable, quantifiable with a named metric; Achievable, realistic given your resources and your population; Results-Oriented, focused on actual change rather than on activity; and Time-Bound, with a clear deadline for measurement. The framework is not bureaucratic decoration. Each letter closes a specific gap a reviewer would otherwise have to fill with an assumption, and reviewers do not fill gaps generously.

Compare the two versions. A weak outcome says: "Improve educational attainment." A SMART outcome says: "By June 2027, 80% of program participants will improve school attendance to 90%+ days present, from a baseline average of 75%." The second version tells the reviewer what will change, for whom, by how much, from what starting point, and by when, and it does so in one sentence. It also does something braver: it makes the grant report writeable in advance, because everyone now knows exactly what will be checked.

Setting Outcome Targets That Are Credible

Your outcome targets must be ambitious but realistic, and there are four legitimate places to get them. Peer organizations give you a working range: if similar programs achieve 70% completion, aim for 68-75%. Research tells you what the literature says a program like yours should achieve. Your own history tells you what you have actually delivered before. And population characteristics adjust all of it, because if your participants are the hardest-to-reach group in your community, your expectations should reflect that rather than quietly borrowing a number from a program serving an easier population.

The strategic point is easy to state and hard to follow: funders prefer a 75% outcome target you achieve over a 95% target you miss. Credibility compounds across a funder relationship and inflated targets destroy it in a single reporting cycle, because in your final report you will be measured against exactly the numbers you wrote here. Every ambitious target you set today is a promise a colleague will have to explain at reporting time.

Evaluation Plan: How You Will Measure Outcomes

Your proposal must explain how you will measure the outcomes you have promised, and that explanation is your evaluation plan. It has five components. The data source names where the information comes from: student records, surveys, interviews, or third-party data. The collection method explains how you will gather it systematically rather than opportunistically. The timeline sets when you collect, typically at baseline, mid-point, and end of program. The analysis states how you will interpret results, whether that is simple percentage comparison or something more statistically involved. And responsibility names the person who owns data collection and analysis.

Written out, a plan for the mentoring example reads: "School attendance data will be collected from school records at program baseline in September, mid-point in February, and program end in June. We will compare each participant's attendance before and after the program. Success will be measured as: X% of participants show at least 10 percentage point improvement in attendance. Results will be analyzed by demographic subgroup to identify equity gaps. Our Program Coordinator will manage data collection with support from our community school partner." Everything a reviewer needs is there, including who to hold accountable, and the subgroup analysis is doing double duty as an equity commitment.

Where Outcomes Belong In The Narrative

Outcomes are not a section, they are a thread that runs through the document. The Executive Summary should lead with your headline outcome, as in "students served by our program show 22% higher graduation rates." The Statement of Need shows the baseline problem with data: "only 64% of students in our district graduate on time." The Project Description explains what you will do and how it produces the outcomes. The Outcomes Section lists every outcome with its target and measurement method. The Evaluation Plan details how each will be measured. And the Budget Narrative justifies the budget items that make outcome achievement possible, such as a data manager or an evaluation consultant, which is where many proposals quietly undermine themselves by asking for evaluation rigour they have not funded.

Equity And Outcomes: The 2026 Imperative

Modern funders want to know whether your outcomes vary by race, gender, disability status, or other demographics, and whether your program is perpetuating disparities or closing them. An aggregate success rate can conceal a program that works well for its easiest participants and not at all for its hardest, and funders have become good at spotting proposals that report only the aggregate. Your proposal should say how you will serve marginalized populations disproportionately, how you will measure outcomes separately by demographic group, what your plan is if outcomes vary significantly between groups, and how you will ensure equitable access as well as equitable results.

Concretely, that reads: "We expect to serve 40% students of color, 25% students with disabilities, and 30% low-income students, reflecting district demographics. We will measure outcomes separately by these groups and adjust program components if any group shows significantly lower outcomes." The second sentence is the one that matters, because it commits you to acting on a disaggregated finding rather than merely reporting it.

Anti-Patterns

• Focusing on activity instead of change. Weak: "We will provide 300 hours of literacy tutoring." Strong: "Participants in our literacy program will improve reading proficiency by 1.5 grade levels on average, as measured by the DIBELS assessment."
• Writing unmeasurable outcomes. Weak: "Youth will have greater confidence." Strong: "80% of youth will report increased confidence on our confidence scale, measured pre and post-program."
• Claiming outcomes unrelated to your activities. Running a mentoring program and measuring housing stability, with no causal connection to mentoring, invites the reviewer to doubt the whole chain. Mentoring should measure academic engagement, school attendance, and college readiness.
• Setting unrealistic targets. Weak: "100% of at-risk youth will graduate high school", from an organization that works with dropouts. Strong: "80% of youth will graduate or complete GED", which is realistic for that population.
• Leaving the causal link unstated. An activity followed by an ambitious outcome with no theory of change between them reads as hope. Name the mechanism and the evidence for it.
• Skipping the assumptions and risks. Proposals that never say what they are assuming, or what could go wrong, look less rigorous than ones that do, not more confident.
• Reporting only aggregate results. Without disaggregation, a program that fails its most marginalized participants looks identical on paper to one that serves everyone well.

Practice Prompts

• Take your most recent proposal and mark every sentence in the project description as either an output or an outcome. Note the ratio.
• Build the full logic model for one program, from inputs through to long-term outcomes, and identify the link in the chain you would find hardest to defend to a reviewer.
• Write your theory of change as a single paragraph, then answer the five questions it should address, particularly the assumption and the failure mode.
• Rewrite one weak outcome from an old proposal into SMART form, including the baseline you would have to go and find.
• For one outcome target, write down which of the four sources it came from: peers, research, your own history, or population characteristics. If it came from none of them, that is the finding.
• Draft the five components of an evaluation plan for a program you currently run, and name the person responsible by name.
• Take one program's results from last year and disaggregate them by demographic group. Decide what you would do if the gap were large.

Reflection Exercise

Think about the last final report you submitted to a funder, and ask whether the targets in the original proposal made that report easier or harder to write. If they made it harder, look at where the ambition came from: a real estimate, or a fear that a modest number would not compete. Then take the question one layer down. Outcome-focused writing is uncomfortable because it commits you in public to a claim about the future, and the discomfort is the point, since a target nobody could fail to hit tells the funder nothing and a target you cannot hit costs you the relationship. Where, honestly, is your organization on that line, and who at your organization is allowed to say a proposed target is too high?

Glossary

• Output: What you do, measured in volume, such as students served or hours delivered. Outputs justify efficiency.
• Outcome: What changes as a result of what you do, measured in impact, such as a graduation rate compared against a district average. Outcomes justify impact.
• Logic model: The if-then chain from inputs through activities and outputs to short, medium, and long-term outcomes, making a causal claim explicit.
• Theory of change: The research-grounded explanation of why your activities produce your outcomes, including the assumptions you are making and what could go wrong.
• SMART outcome: An outcome that is Specific, Measurable, Achievable, Results-Oriented, and Time-Bound, stating what will change, for whom, by how much, from what baseline, and by when.
• Evaluation plan: The five-part description of data source, collection method, timeline, analysis, and responsibility that shows how each promised outcome will be measured.
• Disaggregation: Reporting outcomes separately by demographic group to reveal whether a program closes or perpetuates disparities that an aggregate figure would hide.

Related Lessons

• Budget Narratives for Grant Proposals: What Funders Want to See
• Grant Reporting Best Practices: Building Trust Through Transparency
• The Letter of Inquiry (LOI): Templates and Best Practices
• The Grant Lifecycle: From Discovery to Closeout
• Multi-Year Grants: How to Apply, Manage, and Report
• Building Funder Relationships Beyond the Ask
• The Grant Compliance Toolkit: Monitoring, Reporting, and Closeout

Closing

Renata's rewritten proposal was not longer than the one that was declined, and it described the same program run by the same staff for the same young people. What changed was the direction the sentences pointed. Every paragraph that had described effort now described a change, with a number attached, a baseline behind it, and a plan for checking it. Outcome-focused writing is not a technique for winning grants. It is the discipline of knowing, before you spend the money, what would count as having succeeded.

Key Takeaways

• Funders have moved from activities to outcomes because they answer to their own boards and to the IRS, and your proposal is the first place they look for proof.
• Outputs are what you do, outcomes are what changes. Include both, but lead with the outcome and present outputs as what produces it.
• A logic model makes the causal chain explicit from inputs through activities and outputs to short, medium, and long-term outcomes.
• A theory of change explains why the chain holds, and must name your evidence, your assumptions, and what could go wrong.
• Write outcomes in SMART form, with a baseline and a deadline, as in 80% of participants reaching 90%+ days present by June 2027 from a 75% baseline.
• Set targets from peers, research, your own history, and your population. Funders prefer a 75% target you achieve to a 95% target you miss.
• Every promised outcome needs an evaluation plan naming data source, method, timeline, analysis, and the person responsible, with results disaggregated by demographic group.

Frequently Asked Questions

Can we have too many outcomes in a proposal?

Yes. Stick with 3-5 primary outcomes that are central to your mission. Any more dilutes focus and complicates measurement. Secondary outcomes can be mentioned, but they should not be heavily emphasized or formally evaluated.

What if we have not run this program before and have no historical data for targets?

Use research benchmarks. If research says similar programs achieve a given rate, use that as your target, slightly adjusted for your population, and be transparent about it: "This is our first year implementing this program. Our outcome targets of 75% X are based on peer organizations running similar youth programs in comparable communities."

How do we measure outcomes for programs with long-term impact?

Measure both short-term and long-term. Short-term means immediate post-program results such as graduation rates. Long-term means 1-3 years later, such as college enrollment or job placement. Show in the proposal that you will track both. Long-term tracking requires data-sharing agreements with schools or employers and follow-up surveys, so budget for it.

Should we include negative findings in reports if outcomes are not met?

Yes, absolutely. If you targeted 80% but achieved 60%, report it, explain why, and propose adjustments. Funders respect transparency more than perfection, because they are investing in learning as well as in outcomes.