Writing a Winning Needs Statement for Federal Grants

The Section That Wins or Loses Applications

Ask any experienced federal grant reviewer what separates winning applications from losing ones, and most will point to the needs statement first. Not the project design. Not the budget. The needs statement — the section where you make the case that the problem you're proposing to address is real, significant, and urgent.

This sounds obvious. Every applicant knows they need to explain why their work matters. But most needs statements fail not because the need isn't real — it usually is — but because the applicant can't prove it to someone who doesn't already believe them.

What Reviewers Are Looking For

Reviewers evaluate your needs statement by asking three questions:

1. Is the problem real and significant — not just in your opinion, but evidenced?
2. Is the problem specifically present in the population and geography you're proposing to serve?
3. Does your organization have a unique connection to this problem that makes you the right entity to address it?

The third question is the one most applicants miss. It's not enough to document a problem that exists somewhere. You need to demonstrate that this problem exists for the specific people you serve, and that your organization is positioned to address it in a way that a generic organization couldn't.

The Structure That Works

Open With the Human Reality

Don't start with statistics. Start with a specific, concrete description of the problem as it exists for a real person in your service area. One person, one situation, described precisely. Then widen the lens to show that this person is not an exception — they're representative of a broader population facing the same challenge.

This is not manipulation. It's effective communication. Reviewers read dozens of applications in a sitting. An opening that makes the problem real and immediate is remembered; an opening that begins "According to the Centers for Disease Control and Prevention, 21 million Americans..." is not.

Document the Need With Data

After you've humanized the problem, prove it. Use data from credible sources — federal databases, peer-reviewed research, state health data, census data, community needs assessments. The more local the data, the better. County-level data is more compelling than national averages. Your own service data is more compelling than county-level data.

Be specific: "The diabetes hospitalization rate in our county is 47% higher than the state average, driven by food insecurity and limited access to primary care" is a statement that supports a specific intervention. "Diabetes is a major problem in rural America" is not.

Establish the Gap

Define what currently exists to address the problem, and then define what's missing. The gap — the difference between what exists and what's needed — is what your project fills. If you can't articulate the gap clearly, reviewers will wonder why your project is necessary.

Connect to Your Organization

End the needs section by establishing your organization's unique connection to this problem and population. How long have you been serving this community? What do you know about this problem that an outsider wouldn't? What relationships and trust do you have that make your approach possible? What does your data from serving this population tell you that the literature doesn't capture?

Common Mistakes

• National data for a local problem — Reviewers know that national averages don't describe your specific community. Always localize your data.
• The problem is your organization's lack of funding — The need you're documenting is the community need, not your organizational budget gap. "Our organization needs funding to continue" is not a needs statement.
• Too long — Needs statements that run four pages for a two-page section are common. Be relentless about cutting. Every sentence should earn its place by adding evidence, specificity, or urgency.
• Unsourced claims — Every data point needs a citation. "Studies show that..." without a citation is worse than no citation — it signals sloppiness to reviewers.
• The need is obvious — Reviewers read hundreds of applications. They've seen every obvious need statement. Find the specific, local, differentiated angle on your need that makes your application stand out.

A Note on Tone

Write needs statements in plain, direct language. The people who will read your application know the field. You don't need to educate them on the basics of poverty or mental illness or environmental contamination. You need to show them that this specific problem is present for these specific people in this specific place, and that your organization understands it deeply enough to address it effectively.