Skip to content

How to Write a Grant Needs Statement That Scores Well

Updated 6 official sources

Quick Answer: A grant needs statement is a data-driven section, typically 2-3 pages, that proves the problem your project addresses is real, urgent, and specific to your target population.

Full answer and how we checked it

It should include local and national statistics, cite at least 3-5 credible data sources, and connect the gap directly to your proposed solution. How many points it's worth varies by program, so check the review criteria in the NOFO you're applying to.

Data note: Amounts may shift with annual appropriations.

In this guide

If you're a grant writer trying to make a strong case for funding, this guide shows you how to write a needs statement that scores well with federal and foundation reviewers.

The needs statement is where reviewers decide whether your project matters. It goes by several names - Statement of Need, Problem Statement, or Statement of the Problem - but its function is the same across agencies: convince reviewers that the problem you're addressing is real, urgent, and affects real people in a specific place.

Learning how to write a grant needs statement that scores well means understanding what reviewers are actually evaluating, how to structure the argument, and where most applicants lose points unnecessarily. Each NOFO lists how many points this section carries, so check the review criteria before you draft. Those points come from a section that's primarily a matter of research and structure, not creative writing. For the full proposal structure and how all sections fit together, our guide to writing a grant proposal covers every component from SF-424 to budget justification.

Source Review by Grantsights

Checked June 2026.

Grantsights rechecked federal data sources, NOFO scoring patterns, reviewer guidance, and needs-statement examples in the Grantsights database. According to the U.S. Census Bureau (opens in a new tab), ACS tables provide local poverty, housing, education, and population data. According to CDC WONDER (opens in a new tab), public health data can be queried by geography, cause, and population group. According to BLS (opens in a new tab), labor-market data supports workforce and economic need claims. According to Grants.gov (opens in a new tab), each NOFO controls the exact scoring language, attachments, and deadline for a federal application.

A common mistake is a needs statement that cites national data but never proves the local gap. For example, a county mental-health proposal should pair national prevalence data with county provider ratios, waitlists, school referrals, or emergency department use.

Decision checklist:

Needs-statement claimEvidence to attach
Who is affectedLocal population count and subgroup data.
How severe it isRate, trend, benchmark, or waitlist data.
Why current services fall shortProvider capacity, geography, cost, language, or access gap.
Why this project fitsDirect link from need to activities and outcomes.

What Official Sources Don't Tell You

Official data sources give you statistics, but they do not build the review argument. The practical gap is alignment: every data point must explain why this applicant, this place, this population, and this intervention belong together. Use the Grantsights database to pull up the notice you're targeting and read its review criteria before you draft the needs statement.


Looking for your next grant?

About once a week, we email a short list of open grant calls with real deadlines from different funders. It lists open calls only.

No spam. Unsubscribe anytime.

What the Needs Statement Is Actually For

Before writing a single sentence, get clear on what this section is and isn't supposed to do.

The needs statement's job is to document that a problem exists, that it's serious enough to warrant federal investment, and that it affects the specific population in the specific geography your project will serve. That's it. This section is not the place to describe your organization, your track record, or your proposed solution.

That last point causes more confusion than anything else in grant writing. Applicants who have been working in their field for 20 years want to start every section by establishing their credibility. But the needs statement isn't scored on your organization's history. It's scored on the strength of the documented need. Keep the focus on the problem.

Your organization's track record, relevant experience, and capacity belong in the Organizational Capacity section. Your proposed solution belongs in the Project Narrative. The needs statement is exclusively about the problem.


The 4-Part Structure

Needs statements for SAMHSA, DOJ, ED, and ACF programs can follow the same underlying structure, even if the specific section names vary.

Part 1: State the Problem Clearly

The first paragraph of your needs statement should state the problem directly. What is it? Who is affected? How severely?

Don't ease into it with five sentences of background. Reviewers are reading dozens of applications. A needs statement that doesn't state the problem in the first paragraph is already working against itself.

Weak opening: "Mental health is a growing concern in the United States, affecting millions of people across all demographics. Research shows that access to care remains a challenge in many communities, particularly those facing economic hardship."

Stronger opening: "In Lakeview County, 1 in 4 adults reported a mental health condition in the 2024 county health assessment, yet only 38% of those adults accessed any mental health treatment in the past year. The county has 2 licensed therapists per 10,000 residents, a fraction of the statewide rate."

The second version states the problem, names the geography, cites specific figures, and immediately establishes why federal investment is warranted. The reviewer can evaluate it. The first version can't be evaluated because it says nothing specific.

Part 2: The Evidence

Every claim you make needs data behind it. Reviewers are trained to note when a statement is asserted without evidence. Unsupported claims don't score points.

Primary data sources for needs statements:

National government sources:

  • U.S. Census Bureau (census.gov) - poverty rates, housing, education, demographic data
  • CDC WONDER database - mortality, disease prevalence, health outcomes by county
  • SAMHSA National Survey on Drug Use and Health (NSDUH) - substance use data
  • Bureau of Labor Statistics (bls.gov) - employment and workforce data
  • Office of Justice Programs statistical databases - crime, recidivism, juvenile justice data

State-level sources:

  • State health department data portals
  • State education agency data
  • State criminal justice statistics offices
  • State SNAP and public assistance data

Local sources:

  • County public health agencies
  • Local hospital community health needs assessments (required by nonprofit hospitals under the ACA every 3 years)
  • Local United Way community assessment reports
  • Your own client intake data (with appropriate privacy protections)

Always cite the source and the year of the data: "According to the 2024 CDC WONDER database..." or "The 2023 Lakeview County Community Health Needs Assessment found..."

Prioritize recent data. For most programs, data older than 3 years weakens your case. For fast-moving issues like opioid overdose rates, data from 2022 in a 2026 application may already be outdated and reviewers will notice. Use 2024 and 2025 data wherever available.

Part 3: The Population and Geography

Describe exactly who is affected and where. The more specific the better.

Generic population descriptions ("low-income adults," "at-risk youth") are weaker than specific ones ("adults ages 18-45 with Medicaid or uninsured status in Lakeview, Millbrook, and Crestwood counties," or "youth ages 12-17 who have been involved in the juvenile justice system in the past 24 months").

Specificity does two things. It shows reviewers that you know your target population - you've done the analysis, not just described a category. And it connects your proposed services to the people who will actually receive them.

Include relevant demographic data about your target population: racial and ethnic composition, income levels, language access needs, geographic distribution (urban vs. rural, specific zip codes if relevant).

Part 4: The Gap

The gap section is where most needs statements fall short. After establishing that the problem is serious and well-documented, you need to explain why existing services and resources aren't solving it.

Reviewers in Washington see communities with high need all the time. What they need to know is why your project is necessary given what already exists. What gap does your program fill that isn't currently being filled?

Gap analysis questions to address:

  • What services currently exist for this population in this geography?
  • Why are they insufficient? (Capacity limitations? Geographic barriers? Cultural or linguistic barriers? Eligibility restrictions? Waitlists?)
  • How many people are unserved or underserved?
  • What happens to people who can't access existing services?

Example gap statement: "Lakeview County has one community mental health center (LCMHC) serving the entire population. LCMHC currently operates with a 90-day average wait time for new patients and does not offer services in Spanish, leaving the county's 8,400 Spanish-speaking residents without accessible mental health services. Our project will establish a bilingual outpatient mental health clinic specifically serving Spanish-speaking adults, directly addressing the access and language gap that LCMHC is not positioned to fill."

This tells reviewers: the existing provider exists but has specific limitations. Your project fills a specific gap the existing provider doesn't cover. That's the logic reviewers need.


Data SourceBest ForUpdate Frequency
ACS 5-Year EstimatesDemographic and economic dataAnnual release (2-3 year lag)
County Health RankingsHealth outcome comparisonsAnnual
BLS Unemployment DataLocal labor market conditionsMonthly
USDA Food Access AtlasFood desert identificationPeriodic; check USDA ERS for the latest data year
CDC WONDERMortality and disease dataAnnual
SAMHSA NSDUHSubstance use prevalenceAnnual

The Local Data Advantage

Local data beats national data for community-based grants. This is one of the most consistent patterns across federal grant programs, and it's one most applicants don't fully exploit.

A reviewer in Washington reading your application knows that opioid overdose deaths are a national crisis. What they don't know is that your county's overdose death rate is 3.8 times the national average, that the rate increased 42% between 2021 and 2024, and that 73% of those deaths occurred among adults with no prior treatment contact.

That specificity - local, recent, and precise - does more work than any amount of national statistics.

The structure that works: lead with national context to establish that the problem is real and recognized, then pivot to local data to establish the need in YOUR community.

Example: "Nationally, drug overdose deaths reached 105,007 in 2023 (CDC National Center for Health Statistics, Data Brief 522 (opens in a new tab), 2024). In Greendale County, overdose deaths increased from 34 per 100,000 in 2021 to 58 per 100,000 in 2024 - a rate 2.4 times the national average (Greendale County Health Department, 2025 Health Statistics Report). Despite this, the county has no licensed opioid treatment program within its borders. The nearest methadone clinic is 47 miles from the county seat, inaccessible to the 62% of residents who don't own a vehicle (U.S. Census Bureau American Community Survey, 2023)."

That's a needs statement that scores points. Every claim is supported. The national context is established. The local severity is documented. The access barrier is specific and evidence-based.


How to Cite Data Correctly

Citation format in grant narratives isn't formal academic citation, but it needs to be specific enough that a reviewer could locate the source:

  • "According to the 2024 SAMHSA National Survey on Drug Use and Health..."
  • "The U.S. Census Bureau's 2023 American Community Survey (5-year estimates) reports..."
  • "Lakeview County's 2024 Community Health Needs Assessment found..."

Don't cite unattributed statistics. "Studies show that..." without a citation is a flag. "Research indicates that..." with no source isn't evidence. Reviewers are trained to notice unsupported assertions.

Don't use sources that can't be independently verified - competitor websites, advocacy organization reports without methodology, press releases, informal community surveys without documented methodology.

Your own organizational data (client intake records, service utilization reports, community surveys you conducted) can be cited, but it should supplement published data, not replace it. Reviewers view organizational self-reported data with appropriate skepticism unless it's accompanied by external validation.


Common Mistakes That Cost Points

These are the patterns reviewers flag most often. They're all avoidable.

Being too broad. "Poverty is a major issue in America" isn't a needs statement. It's a truism. You need to narrow it to a specific population, geography, and condition with documented severity.

Spending too many pages on the problem, too few on the gap. The gap section - why existing services don't solve the problem - is where your project's rationale lives. Applicants often spend 4 pages documenting the need and half a page on the gap. Flip that ratio if you're running short on space.

Using outdated data. A 2026 application citing 2018 statistics raises questions about whether the applicant is current with the literature and the field. Use the most recent available data. If a certain data source only publishes every 5 years, note that and supplement with more recent proxy measures.

Making it about your organization. "For 20 years, our organization has served..." doesn't belong in the needs statement. There's a section for that. Reviewers know where to look for capacity information, and frontloading it in the needs statement suggests the applicant doesn't understand the purpose of each section.

Confusing correlation with causation. "Areas with higher poverty have higher rates of substance use disorder" requires explanation, not just assertion. Why does that relationship exist? What mechanisms connect poverty to substance use? Showing that you understand the causal factors makes your proposed intervention more credible.

Not connecting the need to your solution. The needs statement ends where the project narrative begins - but the transition must be explicit. Your final paragraph should state directly: here is the specific gap in the documented need that our proposed project addresses. Don't make reviewers infer the connection.


Writing for a New Organization Without Track Record

If your organization is new or doesn't yet have a documented track record with similar populations, the needs statement is your strongest section. Here's why: the needs statement is about the problem, not you. A well-documented need is equally compelling whether it comes from a 30-year-old institution or a 2-year-old one.

What new organizations can do:

Strengthen community data. If you can't demonstrate your organization's impact, demonstrate the community's need with exceptional specificity. Local data, recent data, and data specific to your exact target population carries weight.

Document partnerships with established organizations. Letters of support from established community partners - providers who are at capacity, schools documenting student need, health departments endorsing your approach - add credibility that partially substitutes for organizational track record.

Be transparent about your stage. Don't overclaim. If you're a new organization, don't imply you've been doing this for years. Reviewers will notice inconsistencies between your claimed history and your organizational documents. What you can do is document why existing organizations aren't filling the gap, and why your organization is positioned to address it specifically.

Cite national evidence for your program model. If you can't cite your own outcomes, cite outcomes from similar programs elsewhere. "Programs using this model have achieved 65% 90-day employment rates in comparable populations (citation)" tells reviewers that the model is evidence-based, even if you don't yet have your own outcome data.


Length and Format

Most needs statements run 3-5 pages in a 20-25 page proposal. Some agencies specify page limits for individual sections - always check the NOFA before you start drafting.

Use headers to organize the section. Sub-headers like "The Problem," "The Population," and "The Gap" help reviewers find information quickly and locate the information they're scoring. Bullet points work well for presenting multiple data points or listing barriers without dense prose.

Don't exceed the page limit. More data doesn't mean more points. A concise, tightly documented needs statement with strong local data outperforms a sprawling one that pads evidence with national statistics available in every other application.


Alignment with Your Evaluation Plan

Whatever problem you document in the needs statement is the problem your evaluation must measure. This is a rule, not a preference.

If your needs statement establishes that 65% of youth in your county are reading below grade level, your evaluation must include a reading assessment measuring reading proficiency gains. If it establishes that only 38% of adults with mental health conditions access treatment, your evaluation must measure treatment engagement rates.

Reviewers explicitly check for this alignment. Disconnect between the need you document and the outcomes you measure is a consistent critique in federal grant reviews. It signals that the needs statement and evaluation plan were drafted independently rather than as parts of a unified proposal logic.

For the full evaluation plan breakdown, see how to write a grant evaluation plan.


What Federal Grant Reviewers Doesn't Tell You

National statistics don't win points if your project is local. Reviewers want to see data about your specific service area. A needs statement citing nationwide poverty rates for a program serving one county in rural Georgia tells the reviewer you didn't do the research.

Census data older than 5 years gets flagged. ACS 5-year estimates are acceptable, but citing 2010 Census data in a 2026 proposal signals outdated research. Use the most recent ACS release and note the survey years.

Needs statements that only describe problems without quantifying gaps lose points. Saying "there aren't enough mental health providers" is weaker than giving the county's counselor-to-resident ratio next to the state or national ratio, with the source and year for each. Specificity drives reviewer scores.

The Needs Statement Technique That Wins: Compare, Don't Just Describe

One structural technique does a lot to separate funded from unfunded applications: the comparison framework.

Every data point needs a benchmark, and most applicants skip this. Organizations often cite their own community data in isolation. "Our county has a 22% poverty rate." So what? Is that high? Reviewers in Washington, D.C. reviewing 200 applications don't know your county. What works: "Our county's 22% poverty rate is nearly double the state average of 12% (American Community Survey 2020-2024 5-year estimates)." One comparison sentence does more than three paragraphs of description.

Local voice data can lift a Need score. Federal reviewers see Census data and HRSA data area profiles all day. What they rarely see is qualitative data from the community itself. Include 2-3 direct quotes from community members, needs assessment surveys, or focus groups. Reviewers can score Need higher when the application includes evidence that the community itself identified the issue as a priority, not just the applicant organization.


Sources


FAQ: Common Questions

How long should a grant needs statement be?

Typically 3-5 pages in a 20-25 page proposal. If the FOA specifies page limits for individual sections, follow them exactly. Don't assume you can use your entire word count for one section. Check the NOFA for section-specific page limits before you outline.

What data sources should I use for a grant needs statement?

Primary sources: U.S. Census Bureau (census.gov) for demographic and poverty data, CDC WONDER for health outcome data, SAMHSA's National Survey on Drug Use and Health, Bureau of Labor Statistics for employment data, and state health department data portals. For local data: county public health agencies, local hospital community health needs assessments, and state agency reports. Always cite the source name and year. The CDC WONDER database is publicly available at wonder.cdc.gov (opens in a new tab) and is one of the most useful free data tools for local health needs documentation.

Can I use my own organization's data in a needs statement?

Yes, but treat it as supplementary evidence rather than primary evidence. Organizational data - client intake records, service utilization reports, community surveys you conducted - can add valuable local specificity, but reviewers view it with some skepticism because it's self-reported. Back it up with published data from government or peer-reviewed sources. If you conducted a community survey, describe your methodology briefly so reviewers can assess its validity.

What's the difference between a needs statement and a problem statement?

They're the same thing with different names. Different agencies and different FOAs use different terminology - Statement of Need, Problem Statement, Statement of the Problem, Needs Assessment. The function is identical: document that the problem exists, is significant, affects a specific population, and isn't being solved by existing resources. The structure described in this guide applies regardless of what your specific FOA calls the section.

How do I write a needs statement when my organization is new?

Focus on the strength of the community data rather than organizational history - the needs statement scores on problem documentation, not organizational track record. Partner with established organizations and reference their letters of support. Cite national evidence for your program model. Document specifically why existing organizations in your area aren't filling the gap your project addresses. For your organizational track record and capacity, that goes in the capacity section of the proposal, not here.


If you're building a full proposal alongside the needs statement, see how to write a federal grant proposal for the complete section breakdown and agency-specific scoring criteria.

For building the program logic that connects your documented need to your proposed intervention, see what is a logic model for grants.

For structuring the outcomes that flow from your needs statement into a scoreable evaluation plan, see how to write a grant evaluation plan.

The needs statement is almost always the section where applicants leave the most points on the table. The data exists. The structure is learnable. With strong local data, a clear gap analysis, and tight organization, this section is one of the most reliably improvable parts of a federal grant proposal.

Last updated October 13, 2026. Corrected October 13, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.