The Needs or Problem statement might be the most misunderstood section in a grant proposal. It's often the first substantive section a reviewer reads, which means it's doing a lot of work. And yet it's also one of the sections where organizations most consistently undermine themselves — making one persistent, fixable mistake:
They write about what their organization needs instead of what the community needs.
That distinction sounds small. It isn't.
Why the Needs Statement Is the Foundation Your Whole Proposal Rests On
A grant proposal is, at its core, a logical argument. You're asking a funder to invest in a solution. Before they can evaluate your solution, they have to agree that the problem is real, significant, and worth addressing.
The needs statement is where you make that case.
If a reviewer doesn't come away from your needs statement believing that the problem is serious and that it's actually affecting the community you serve, the rest of the proposal loses its foundation. You can have a beautifully designed program and credible evaluation plan, but neither of them will land the way you intend if the need behind them hasn't been established clearly.
This is why The Grantsmanship Center teaches the needs statement as a community-facing argument, not an organizational one. The question you're answering isn't "What do we need funding to do?" It's "What is happening in this community that justifies intervention, and what does the evidence tell us about it?" Remember: the absence of your program is not the need.
What a Needs Statement Is Not
Before getting into what makes a strong needs statement, it helps to name the patterns that weaken one.
It is not a history of your organization. Funders are not investing in your past. They're deciding whether your plan addresses a real problem. Background on your organization belongs in the Introduction to the Organization.
It is not a description of your program. The needs statement outlines the problem. The methods section specifically describes how you'll address it with your program. Many proposals blur this line, and reviewers notice.
It is not a list of services you wish you could offer. Statements like "our organization needs additional staff to serve more clients" describe an organizational gap, not a community need. The community need is what is happening to people because services are insufficient or because of a systemic flaw. That's a different framing, and it matters.
It is not a request. This one seems obvious, but proposals routinely include language in the needs section that slides into making the ask early. Hold that for later. The needs statement earns the ask by establishing that the problem is real.
What Makes a Needs Statement Credible
Credibility in a needs statement comes from evidence and specificity. A credible needs statement should make a logical connection to your program.
Use data that reflects the specific community you serve. National statistics can orient a reviewer, but they don't establish local need on their own. A funder evaluating a proposal for a program in a specific county or neighborhood wants to see that the problem exists in that same place. Census data, local health department reports, school district data, state agency statistics, and community assessments are all stronger than national figures when the work is local.
Be specific about who is affected and how. Vague need statements tend to gesture at broad social problems without connecting them to actual people in an actual place. "Mental health challenges affect millions of Americans" is true. "In [County A], 1 in 4 adults reported experiencing symptoms of depression or anxiety in the past year, yet only 34% sought treatment" is more relevant. The first one tells the reviewer a problem exists in the world. The second, tells them it exists in the community you serve.
Connect the data to your program's design. The needs statement shouldn't just establish that a problem exists. It should set up the logic of your intervention. If your program addresses employment barriers for formerly incarcerated people, the needs statement should document what those barriers are and what happens when they go unaddressed. The data you choose should support the solution you're proposing.
Use current sources and cite them. Funders notice when data is out of date. A study from 2014 in a proposal submitted in 2026 raises questions. Prioritize recent data wherever possible and cite your sources clearly. It signals that your organization is engaged with current conditions in the field.
How to Build the Case Without Overloading the Reader
One of the more common problems in needs statements is not lack of evidence but too much of it. Some proposals stack statistic after statistic in a way that starts to feel like padding rather than argument. More data doesn't equal more persuasion.
Think about the needs statement the way you'd think about any compelling argument you're making to a skeptic. You need enough evidence to establish the claim, enough specificity to make it credible, and a clear logical through-line so the reviewer can follow where you're going.
A useful test. After reading your needs statement, could a reviewer accurately describe:
- the problem,
- who it affects,
- the number of people involved,
- why existing resources aren't enough, and
- why this community specifically needs this intervention?
If the answer to any of those questions is unclear, the section needs more work.
The Difference Between Community Need and Organizational Aspiration
This is worth returning to because it's the single most common thing that weakens a needs statement.
Organizational aspiration sounds like: "We believe every child deserves access to quality after-school programming, and our organization is committed to making that vision a reality in our community."
Community need sounds like: "In [City B], 62% of school-age children are unsupervised after school. Research consistently links unsupervised after-school hours with increased risk of academic disengagement, juvenile justice involvement, and substance abuse."
Both organizations might be doing the same work. But only one of those statements gives the funder a reason to fund it that doesn't depend on simply taking the organization's word for things.
Funders are not evaluating how much your organization cares. They're evaluating whether the problem is real, whether the scale justifies investment, and whether your proposed solution is logically connected to the need.
A Framework Worth Following
If you're not sure where to start, The Grantsmanship Center's approach to the needs statement offers a clean framework:
Establish what the problem is. Use local data to show that it exists in the community you serve. Describe who is affected and at what scale. Explain what happens when the problem goes unaddressed. Document why current resources or services are insufficient. Connect the documented need directly to the program you're proposing.
That's not a formula to follow mechanically. It's a logic chain. Your needs statement should be able to hold up to the question "So what?" at every step. The problem exists, so what? It affects this many people, so what? Existing resources don't cover it, so what? Your program addresses the specific gap, and that's the bridge into the rest of the proposal.
A strong needs statement doesn't argue for your organization. It argues for the community. Funders who believe the problem is real and serious are already halfway to agreeing that your solution is worth funding.
That's the work the Needs or Problem statement is there to do.
The Grantsmanship Center has been training nonprofit professionals in the fundamentals of grant proposal writing since 1972. Learn more about our training programs at tgci.com.
Get Funding. Create Change.
