Statement of Need: How to Write One That Wins

A statement of need is the section of a grant proposal that uses data and evidence to prove a specific problem exists for a defined target population. It establishes why funding is necessary and becomes the foundation that every goal, activity, and outcome later in the proposal must trace back to. If reviewers do not believe the problem is real and urgent, no amount of polish in the other sections will save the application.

This is the section that decides more proposals than any other, so it is worth getting exactly right.

Why the needs statement carries the proposal

Funders are buying a solution to a problem they believe matters. The needs statement is where you make them believe. A vague or unsupported version signals a vague program, while a precise, data-backed one earns the reviewer's trust for everything that follows.

The most damaging mistake is framing the need around your organization rather than the community. "We need funding to keep our doors open" describes your problem. "62 percent of third graders in our service area read below grade level" describes theirs. Funders respond to the second. For how this section fits the rest of the document, see our pillar on drafting a complete proposal.

Anatomy of a strong statement of need

A complete needs statement does four jobs in order:

1. Names the problem clearly and specifically.
2. Defines the target population affected, including who, how many, and where.
3. Proves the problem with data, pairing local evidence with external sources.
4. Shows the gap between the current reality and the desired outcome, then bridges to your solution.

Keep the four moves visible. A reviewer should be able to point to the sentence that names the problem, the figures that prove it, and the line that hands off to your goals.

Using data without drowning the reader

Strong statements pair two kinds of evidence. Local data (your waitlist, intake numbers, service-area statistics) proves proximity and shows the problem is yours to solve. External data from credible sources such as government agencies or research institutions proves scale and gives the figures authority. Cite the source and the year, for example "(U.S. Census Bureau, 2025)," so reviewers can trust the number.

Resist the urge to pile on statistics. Three well-chosen figures that build a single point beat a dozen that scatter. Each number should earn its place by advancing the argument, and a short human detail or quote can make the data land. The goal is a problem that feels both measurable and real.

Connecting need to everything downstream

The needs statement is not a standalone essay; it is the setup for the rest of the proposal. The problem you name becomes the goal you promise to address, which becomes the objectives you measure. If a later objective addresses something your need never established, the proposal loses coherence, and reviewers notice. Mapping that chain in a logic model for your grant makes the handoff explicit and easy to check.

Test the link directly. Read your goals and ask whether each one solves a part of the problem you proved. Then read your evaluation indicators and confirm each measures a change in the population you named. To build that chain, write tight SMART, testable objectives and an annotated grant proposal example shows the handoff in action.

A short worked example

Across the two schools we serve, 62 percent of third graders read below grade level, compared with 41 percent statewide (State Department of Education, 2025). Research links third-grade reading failure to a fourfold increase in the risk of leaving school without a diploma. Our 2025 fall assessments confirmed this gap locally, with 148 of 240 third graders below benchmark. Without intensive early intervention, these students enter fourth grade unable to read to learn.

Notice the structure: external data for scale, local data for proximity, a consequence that raises the stakes, and a closing line that points straight at the solution.

Need is not the same as demand

A subtle distinction separates the strongest statements from the merely competent: the difference between need and demand. Need is the measurable gap between the current condition and an acceptable one, the 62 percent reading below benchmark. Demand is the evidence that the affected population actually wants and will use the solution you propose. Reviewers increasingly look for both, because a real problem with no demonstrated demand produces empty programs and unspent funds. A literacy gap is a need; a waitlist of 90 families requesting tutoring is demand, and together they make a far more convincing case than either alone.

Show demand with concrete signals: waitlists, survey responses, attendance at a pilot, referrals from partner agencies, or letters from the community asking for the service. This is also where a brief, human detail earns its place, a single quote from a parent or a caseworker, because it converts an abstract statistic into a felt problem without sacrificing rigor. The pairing matters for sustainability too, since a program with proven demand is one a funder can believe will continue. When you document both the gap and the appetite to close it, you answer the quiet question behind every reviewer's evaluation: not just whether the problem is real, but whether your solution will be used.

Common mistakes to avoid

• Describing the organization's need for money instead of the population's need for change.
• Using no data, or only emotional appeals.
• Citing outdated or unsourced statistics.
• Listing a problem that your proposed methods never actually address.

Prove the problem, frame it around the people you serve, and hand off cleanly to your goals. When the stakes are high, our grant writing team helps you turn raw data into a needs statement reviewers act on.