Nonprofit Grant Writing Tips That Actually Win Funding

Most nonprofits that struggle with grant writing have the same problem: they treat each grant application as a standalone transaction rather than as part of a long-term relationship and a coherent organizational story. Funders — especially foundation funders — don't just fund projects, they fund organizations and the people running them. Understanding how grant-making actually works from the funder's perspective is the first step toward writing proposals that consistently get funded. This guide covers the elements of grant writing that separate funded organizations from those collecting rejection letters.

Building Funder Relationships Before You Apply

The most important thing you can do to improve your grant success rate has nothing to do with writing — it's relationship-building. Program officers at foundations are the gatekeepers between your organization and their grant dollars. They read hundreds of proposals, attend dozens of site visits, and develop strong opinions about which organizations in their portfolio are worth long-term investment. Getting on their radar before you submit is a significant competitive advantage.

Start with research. Before contacting any program officer, review the foundation's 990-PF to understand what organizations they have funded, at what amounts, and in what program areas. Review the foundation's website for published priorities, strategic plans, and recent grantee spotlights. You should be able to articulate, in one sentence, why your organization is a strong fit for their specific priorities — not grant funding generally.

Then make contact appropriately. Most foundations accept brief introductory emails from nonprofit leaders. A two-paragraph email explaining your organization's work, its alignment with the foundation's priorities, and a specific question — "Is this a program area you're currently prioritizing? Would you be open to a brief call?" — is standard practice and well-received. Cold calls to program officers are generally not appropriate; emails are the norm.

When you do get a call or meeting with a program officer, listen more than you speak. Ask about their current priorities, what they're seeing across their grantee portfolio, and what gaps they wish more organizations were addressing. This intelligence is invaluable and will shape every proposal you write to that funder.

Building a Logic Model That Works

A logic model is a visual or narrative representation of how your program works — the chain of causation from inputs to outputs to outcomes. Many funders require logic models explicitly; even those that don't expect the same logical structure to be present in your narrative. A clear logic model is the foundation of a competitive grant proposal.

The standard logic model has five components:

• Inputs: Resources you invest in the program — staff, volunteers, facilities, equipment, partner relationships, funding.
• Activities: What your program does — specific services, training sessions, events, interventions.
• Outputs: Countable units of activity — number of people served, sessions delivered, hours of training provided.
• Short-term outcomes: Changes in knowledge, attitude, skills, or behavior among participants, typically measurable within 1–2 years.
• Long-term outcomes: Broader changes in conditions or systems, typically taking 3–5 years to materialize — reduced poverty, improved health outcomes, increased employment.

The most common logic model mistake is treating outputs as outcomes. "We will train 200 people" is an output. "80% of trained participants will gain employment within 90 days" is an outcome. Funders care about outcomes because outputs without outcomes don't demonstrate that their investment changed anything.

Build your logic model before you write any narrative. It will structure your proposal, ensure your budget aligns with your activities, and make your evaluation section much easier to write.

Writing a Compelling Needs Assessment

The needs assessment (or statement of need) answers the question every funder is asking: "Why does this problem need to be solved, and why can't it wait?" A weak needs assessment is the most common reason proposals score poorly at the narrative stage.

Strong needs assessments share three characteristics. First, they are data-driven. Every claim about the severity or scope of the problem is backed by specific, sourced data from credible sources — government datasets, peer-reviewed research, local surveys, or needs assessments conducted by respected regional organizations. "Many families struggle with food insecurity in our county" is not a needs statement. "27.3% of households in Riverside County experienced food insecurity in 2024, compared to a national average of 13.5%, according to the USDA's Economic Research Service" is a needs statement.

Second, strong needs assessments are local. National statistics establish context; local data establishes the specific need your organization is positioned to address. Funders who operate in your region will be familiar with the local landscape — local data demonstrates that you are too.

Third, they establish your organization's unique position. Once you've proven the problem is real, explain why your organization is the right one to address it — your community relationships, your track record, your specific expertise, your partnerships with other organizations that give you reach no single entity could achieve alone.

Evaluation Plans and Sustainability Sections

These two sections are where many grant proposals fall apart even when the project design is strong. Reviewers read them carefully because they reveal whether the organization has thought seriously about accountability and long-term viability.

A strong evaluation plan answers four questions: What will you measure? How will you measure it? Who will conduct the evaluation? What will you do with the findings? Address all four explicitly. Most funders expect both process evaluation (are you doing what you said you'd do?) and outcome evaluation (are participants achieving the outcomes you projected?). If you have the resources for an external evaluator, say so — it signals methodological rigor. If not, describe your internal data collection systems and who is responsible for them.

Common evaluation pitfalls include proposing to measure too many outcomes (five measurable outcomes are more credible than fifteen vague ones), relying entirely on self-reported data without objective measures, and not explaining what you'll do if outcomes fall short of targets. Funders know programs don't always work exactly as planned — describing your adaptive management approach demonstrates organizational maturity.

The sustainability section addresses what happens after the grant period ends. Funders invest in organizations they believe will continue doing good work — a project that dies when the grant runs out is a poor return on their investment. Describe your sustainability plan honestly: which components will be institutionalized in your operating budget, which will be funded by other grants you are pursuing, which may be absorbed by government contracts, and which may not continue if new funding isn't secured. Honesty here is more persuasive than claiming every element of the project will magically continue without new resources.

Letters of Support and Budget Narratives

Letters of support are often treated as an afterthought — collected at the last minute, generic in content, and providing little real value to the application. Done well, they can meaningfully strengthen a proposal. Done poorly, they add bulk without substance.

An effective letter of support does three things. It describes the author's organization and its relationship to your work. It specifies the concrete support being offered — not just endorsement, but actual commitments: referrals, shared facilities, co-facilitation, data sharing, in-kind services. And it connects those commitments to the outcomes your project is trying to achieve. A letter from a hospital system that commits to referring 50 patients per month to your health program is worth far more than a letter from the same hospital saying "we support this important initiative."

Request letters from partners at least three weeks before your deadline and provide a one-page brief explaining your project, the specific ask, and the outcome you're trying to achieve. Most partners are willing to write strong letters if you make the process easy for them.

The budget narrative should function as a defense of every line item in your budget. For each line, explain the calculation methodology, the connection to project activities, and why the cost is necessary and reasonable. Personnel lines should show the calculation (FTE × annual salary = total cost). Consultant lines should reference the market rate you're paying and the specific deliverables. If you're including indirect costs, confirm the funder's policy and apply your rate accurately.

Following Up After Rejection

• Request feedback immediately. Most foundations will provide feedback if you ask within 30 days of the rejection. Federal agencies are generally required to provide reviewer comments on request. This feedback is the most valuable data you'll receive about your proposal's weaknesses.
• Read feedback systematically. Categorize each comment: is it a fundamental concern about fit, a fixable narrative weakness, a budget issue, or a data/evidence problem? Each category requires a different response.
• Distinguish between fixable problems and fundamental misalignment. If the funder's comments suggest your project doesn't fit their current priorities, no amount of rewriting will change that. Accept the misalignment and redirect your energy to better-aligned funders. If the feedback identifies specific gaps in your evidence or weaknesses in your logic model, those are fixable.
• Reconnect with the program officer. A brief, professional follow-up call after a foundation rejection — "Thank you for your feedback. I wanted to clarify one point and ask whether a revised proposal might be appropriate for a future cycle" — keeps the relationship open and sometimes reveals opportunities the written feedback didn't mention.
• Track your win rate and refine your targeting. If you're applying to 20 foundations and winning 1, your targeting is the problem more than your writing. Apply to fewer funders with higher confidence of fit rather than blanketing every foundation in your field.

Grant writing is a craft that improves with deliberate practice, honest feedback, and long-term relationship investment. Organizations that build strong funder relationships, tell a coherent and data-driven story, and treat every rejection as a learning opportunity consistently outperform those that treat grants as a lottery. Browse available grants on GrantLocate to find open opportunities and build the pipeline your organization needs to thrive.