Most nonprofits write grant proposals that technically answer every question, and completely miss the point. Here's what program officers are actually evaluating in 2025, and how to write the proposal that gets funded.
I've worked with nonprofits ranging from community health centers to national advocacy organizations on federal, state, and private foundation grants. Across hundreds of proposals, the organizations that consistently win funding have one thing in common: they write for the program officer, not for the RFP.
That distinction sounds subtle. It isn't. An RFP is a compliance document. A funded proposal is a persuasive argument made by human beings to other human beings: people who read dozens of applications, who are trying to find the proposal that gives them confidence that the work will actually happen, and who are acutely aware of the risk of funding the wrong organization.
What Program Officers Are Actually Evaluating
Every grant reviewer has a set of explicit scoring criteria (the ones in the RFP). They also have a set of implicit questions they're answering as they read. The implicit questions are often more important than the explicit ones.
Do these people actually understand the problem?
Not "do they describe the problem accurately" (that's the explicit question). The implicit version is "do they demonstrate the kind of granular, lived understanding that comes from being close to this issue?" Generic statistics don't convey that. Specific community examples, nuanced subgroup data, and frank acknowledgment of what doesn't work do.
Is this organization capable of executing what they're proposing?
The work plan and budget are evaluated explicitly. Implicitly, reviewers are scanning every paragraph for signs of operational realism: specific timelines, named personnel, honest capacity constraints, realistic risk acknowledgment. Vague plans with inflated confidence get rated lower than specific plans that acknowledge uncertainty.
Will this money actually produce the outcomes they're claiming?
Logic models are required. What's evaluated implicitly is whether the theory of change is coherent: whether the activities genuinely lead to the outputs, and whether the outputs genuinely lead to the stated outcomes. A lot of proposals have beautiful logic models that don't match the program description.
Do I trust this organization with our grant dollars?
Trust is built through specificity, honesty, and evidence. It's destroyed by hyperbole, vague language, and claims that can't be verified. "We are uniquely positioned to address this need" is a trust-destroyer. "We have served 847 participants in this specific population over the past four years, with documented outcomes in X and Y" is a trust-builder.
The 7 Grant Writing Mistakes Nonprofits Make in 2025
1. Writing the needs assessment like a Wikipedia article
The needs assessment section is where many proposals die. Organizations fill it with national statistics that have no connection to their local population, cite studies that are 8 years old, and produce a narrative that could have been written by anyone about any community.
Winning proposals lead the needs assessment with hyper-specific local data: your own client data, community needs assessments from your county health department, demographic information specific to your service area. National statistics provide context. Local specificity provides credibility.
2. Burying your organization's credentials
Many nonprofits are almost apologetic about stating their qualifications. They list their history in one paragraph, mention a few programs in passing, and move on. Meanwhile, a reviewer who hasn't encountered your organization before is trying to answer the central question: "Can these people actually do this?"
Your organizational capacity section should be a confidence-building argument. Name the specific staff members who will lead the project and their relevant credentials. Describe past programs with similar populations and documented outcomes. If you've managed federal grants before, say so explicitly and describe your compliance track record.
3. Proposing programs that don't match your track record
One of the fastest ways to lose reviewer confidence is to propose a program type that doesn't match your organization's documented history. If your entire track record is in emergency food assistance and you're applying for a workforce development grant, that disconnect needs to be bridged explicitly, through partnerships, staff credentials, or a very clear rationale.
Reviewers are trained to look for organizational fit. If you've never run the type of program you're proposing, you need to address that directly, not hope they don't notice.
4. Using passive voice everywhere
"Participants will be served." "Outcomes will be measured." "Services will be provided." Passive voice in grant writing makes it impossible to hold anyone accountable for anything, which is exactly the signal a concerned reviewer doesn't want to see. "Our case managers will conduct weekly check-ins with each participant." "The program director will compile quarterly outcome reports." Active voice, named roles, specific commitments.
5. Setting targets you can't document
"We will serve 500 participants and improve their outcomes by 40%." Where did those numbers come from? Optimistic targets that aren't grounded in your actual capacity and past performance are a red flag. Reviewers know the difference between a target derived from capacity analysis and a target that was reverse-engineered from what sounded impressive.
Set targets you can defend. "Based on our current capacity and staff-to-client ratios, we project serving 120 participants in Year 1." That's a smaller number, and a far more credible application.
6. Ignoring the funder's theory of change
Every major foundation has a strategic framework: a theory about how their grantmaking leads to the outcomes they care about. Reading the funder's annual report, strategic plan, and recent grantee list before you write a word of the proposal is not optional. It's the research that tells you how to frame your proposal.
A funder whose theory emphasizes systems change wants to see how your program contributes to something larger than direct service delivery. A funder whose theory emphasizes community voice wants to see your community engagement process. If your proposal doesn't reflect the funder's priorities in its framing and language, it reads like a generic proposal, because it is one.
7. Letting the sustainability section be an afterthought
"We plan to sustain this program through future grants and fundraising." This is the sustainability section equivalent of "we'll figure it out." Funders, especially federal funders, are acutely aware that they're often asked to fund programs that disappear the moment the grant period ends.
A credible sustainability section identifies specific funding sources you're already pursuing, describes earned revenue potential if applicable, explains how this program fits into your organization's long-term financial strategy, and demonstrates that your board and leadership have thought seriously about what happens after the grant.
Case Study: Federal Health Center Grant
After restructuring a community health center's HRSA New Access Point proposal (previously denied twice):
Funded
3rd submission result after full rewrite
$850K
Award amount (3-year period)
94/100
Reviewer score (previous: 67/100)
2x
Specificity of needs data used
The Storytelling Dimension: What Most Grant Guides Miss
Technical grant writing (compliance, formatting, structure) is learnable. What separates the proposals that reviewers remember from the ones they score adequately and move on from is storytelling.
This doesn't mean fabricating emotional narratives. It means understanding that even the most analytical program officer is a human being responding to human stories. A single specific, permission-appropriate client story in the needs assessment does more to convey the urgency of your work than three pages of statistics.
"In the last 12 months, 34% of the participants who completed our workforce training program secured employment within 90 days" is data. "Maria came to us after her second layoff in three years. She had been told she had the wrong skills for the current job market. Eighteen months after completing our training program, she's now a medical billing specialist making twice her previous salary and training other participants herself." That's a story. Both belong in a competitive grant proposal.
This is the same principle behind nonprofit storytelling that actually drives donations: data tells people what to think; stories make them feel something. In grant writing, as in fundraising, you need both.
Federal vs. Private Foundation: Key Differences in 2025
Federal Grants (HRSA, HHS, DOJ, etc.)
- Strict compliance with page limits, formatting requirements, and required sections (violations can disqualify)
- Reviewers often have academic or policy backgrounds and respond to evidence-based program models
- Logic models and evaluation plans are rigorously scored; vague M&E plans are heavily penalized
- Sustainability and scalability are major scoring criteria
- Prior successful federal grants significantly strengthen your application
Private Foundation Grants
- More flexibility in narrative structure and length, but more variation in expectations across funders
- Relationship and cultivation often matter more than the written proposal
- Theory of change and funder alignment typically weighted more heavily than in federal applications
- Letters of inquiry (LOIs) are your first filtering layer; LOI quality often determines whether you're invited to apply
- Budget flexibility varies significantly; some foundations fund indirect costs, many don't
Related Reading
If your organization is preparing a grant application and needs a writer with actual experience in federal health and human services grant writing, book a free discovery call to see what a proposal partnership with documented outcomes looks like.
