Many need statements go wrong in one of two directions. Some pile up statistics until the reviewer can't tell which ones matter. Others tell a moving story about one family and never show that the problem reaches beyond that family. Either way, the reviewer finishes the section without knowing the one thing it was supposed to prove.
A need statement isn't proof that the world has problems. It's proof that this problem, in this place, has a gap your project fills. This article covers what reviewers check for, where to find numbers that carry weight, how to explain each one and how to describe a community's needs without casting its people as the problem.
Know the four things a reviewer is checking
Before you choose a single figure, be clear about what the section has to establish. Reviewers are usually looking for four things:
- A specific population. Not "youth" but "students in grades 6 through 8 at the county's three middle schools."
- A specific place. A county, a school district, a set of census tracts or a tribal service area. The more precise, the better.
- A specific gap. What exists now, what's needed and the distance between them.
- A credible link to your project. The gap you describe should be the gap your activities close.
The fourth point is where many drafts slip. A need statement that documents food insecurity across a whole state, attached to a project that runs one weekend backpack program, leaves the reviewer to make the connection. Don't make them. If the scoring criteria describe what the need section must cover, answer in their terms and in their order. Reading the notice closely before you write keeps you from documenting a need the funder never asked about.
Choose data from three places
Strong need statements usually draw on three kinds of evidence.
Public data
The Census Bureau's American Community Survey (ACS) is the workhorse for income, housing, language, disability and household data. Two things are worth knowing before you pull from it:
- Pick the right estimate. According to the Census Bureau, 1-year estimates are published only for areas with populations of 65,000 or more. The 5-year estimates cover all areas, down to census tracts, and are the most reliable, though the least current. For a rural county or a single neighborhood, the 5-year estimate is usually the one that exists.
- Check the margin of error. The ACS publishes a margin of error at the 90 percent confidence level for each estimate. For small areas it can be wide. If the margin of error is nearly as large as the difference you want to highlight, choose a different figure.
Beyond the ACS, look at your state health department's county data, your state education agency's school and district reports and any datasets published by the agency offering the grant. Agencies often publish the data behind their own priorities, and quoting it back shows you're working from the same picture.
Your own service data
Your waitlist, intake counts, referral sources and outcomes are often the most persuasive numbers you have, because nobody else has them. Say a family shelter tracks how many families it turns away when it's full. A line like "We turned away 140 families between November and March" says more about the gap than a statewide poverty rate.
Keep these numbers in one place and update them on a schedule. Reconstructing the previous year's intake counts from email the week of a deadline is how errors get in.
Comparisons
A local figure on its own means little to a reviewer from another state. Put it next to a state or national figure and the gap becomes visible. Compare like with like: the same source, the same measure and the same period. A county's 5-year ACS estimate set against a national 1-year estimate mixes two methods, and a careful reviewer will notice.
Use fewer numbers and explain every one
Three to five well-chosen figures beat a table of twenty. Each extra statistic dilutes the ones that matter, and tired reviewers skim tables.
The habit that makes this work is simple: every number gets a "so what" sentence immediately after it. The number shows the condition. The next sentence says why it matters to this project.
Here are two versions of the same hypothetical paragraph.
Weaker:
Thirty-one percent of households in the county have no vehicle. The county is 40 miles across. The nearest specialty clinic is in the county seat.
Stronger:
Nearly a third of households in the county have no vehicle, and the only specialty clinic is in the county seat, up to 40 miles away. For a patient without a car, a specialist referral means a full day of travel, which is why missed specialty appointments, not a lack of referrals, are the gap this project closes.
The second version uses the same facts and ends by pointing at the project. Repeat that move for every figure.
A few habits that help:
- Cite every number in the format the notice asks for.
- Use the most recent release of each dataset, and say which year or period it covers.
- Round sensibly. "Nearly a third" reads faster than "31.4 percent" and is just as honest when the margin of error is a few points.
- Cut any number you can't explain. If you can't write the "so what" sentence, the figure doesn't belong.
Describe conditions, not people as problems
How you frame need shapes how reviewers see the community, and how the community sees your proposal if they read it. Deficit language describes people as the problem: "at-risk youth," "broken families," "a community plagued by addiction." It reduces people to their hardest circumstances and implies the fix is to change them.
Describe conditions and systems instead:
| Instead of | Try |
|---|---|
| At-risk youth | Young people in schools with no after-school programs |
| Families who can't manage their money | Families whose rent takes more than half their income |
| A community that lacks leadership | A neighborhood with no meeting space large enough for its tenant association |
Name strengths alongside need. A trusted clinic, an active tenant association or a network of congregations are assets your project can build on, and reviewers often read them as evidence the work will take hold. Naming them also makes the section more accurate. Few places are only their problems.
Build the section in this order
Once you've gathered your material, this order works for most need statements:
- The population and place, in one or two sentences.
- The condition, with two or three figures and their "so what" sentences.
- The gap: what's available now and why it isn't enough. Name existing services honestly, because reviewers often know them.
- Strengths and assets the project will build on.
- The bridge: one or two sentences on how your activities address the gap you've just shown.
The bridge sets up the goals and objectives that follow. If your outline built from the notice puts the need section ahead of the project design, that sentence is what carries the reviewer from one to the other. And because reviewers read for fit as much as for need, it helps to know what funders are really looking for before you decide how much space each part gets.
Your next step
Open the need paragraph you paste into most applications. After every statistic, add one sentence explaining why that number matters to this specific project. If you can't write that sentence for a figure, delete the figure. You'll likely end up with a shorter section that does more work.
If your service data is scattered across old reports and spreadsheets, SoliContraX keeps it in one place and drafts from it, so your need statement starts from your numbers rather than generic ones. Get started with SoliContraX.