Your statement of need decides more of a grant’s fate than almost any other section, yet most applicants write it like an opinion essay. Reviewers do not read it that way. They score it against published criteria, paragraph by paragraph, and they subtract points for gaps the writer thought were minor. The fastest way to raise your odds is to stop treating the statement of need as persuasion and start treating it as the scored section it actually is.

Why the Statement of Need Is a Scored Section, Not an Essay

Generic advice tells you to “balance data with emotion.” That is not wrong, but it misses how funding decisions are made. A panel of reviewers reads your application against a published scorecard and assigns numbers. The needs statement is where the problem’s importance gets rated, and that rating is rarely a matter of taste. A weak score here is hard to recover elsewhere, because a reviewer who is unconvinced the problem matters will read the rest of your application looking for reasons to agree.

Look at the federal mechanics. NIH moved most research project grant applications to a simplified peer review framework for due dates on or after January 25, 2025. It folds the long-standing Significance criterion into “Factor 1: Importance of the Research,” which reviewers score on a 1-to-9 scale where 1 is exceptional and 9 is poor. Significance — the documented importance of the problem you propose to address — carries its own number that follows the application all the way to council. The CDC runs a parallel logic: its merit review process scores applications against criteria and point values published in each notice of funding opportunity, and a single CDC competition might weight approach, evaluation, and organizational capacity at 25, 25, and 50 points respectively. The takeaway is simple: before you write a sentence, find the scorecard.

Foundations are less formal but not different in spirit. A program officer is still asking whether the need is real, urgent, and the right fit for the funder’s mission. It is your evidence brief on that question, and a brief that reads like a feelings essay loses to one that reads like a case.

The Mistake That Costs the Most Points: Organizational Need vs. Problem Need

Here is the failure that sinks more needs statements than any grammar slip or formatting error: the applicant describes what the organization lacks instead of what the community or field lacks. “We need funding to hire two case managers” is an organizational need. “In our county, 1,400 families on the housing-assistance waitlist wait an average of 11 months, and no provider offers bilingual case management” is a problem need. Reviewers fund the second and quietly down-score the first.

The distinction matters because the grant is not a subsidy for your budget gaps; it is an investment in solving a documented problem. When your needs statement leads with your own shortfall, you have accidentally told the reviewer that the project exists to keep your organization running. Flip it. Lead with the people affected, the size of the problem, and the gap in current provision. Your capacity belongs later, in the approach and organizational sections, where it is actually scored. If you want a second set of eyes on that distinction before submission, OpenGrants’ managed grant writing services exist precisely to catch it.

A quick self-check: read your draft and highlight every sentence whose subject is your organization. If the first third of your needs statement is mostly “we,” you are writing an organizational need and the points are leaking out. The fix is rarely new research — it is reordering what you already have so the problem leads and your role follows.

What Reviewers Look For: Baseline, Gap, and Consequence

Strong needs statements share a structure, whether the writer knows it or not. They establish a baseline, name a specific gap, and spell out the consequence of leaving that gap unfilled. Each of the three should rest on a number a reviewer can verify.

Baseline

Start with the current state, quantified. How many people, in what geography, experiencing what condition? Use the most authoritative source you can find — Census data, a state agency dashboard, a peer-reviewed study, your own service records. The CDC’s own tips for preparing applications stress responding directly to the published requirements with clear, supported claims rather than assertions.

Gap

Name what is missing now. A gap is not “we have no program”; it is “existing programs reach only 30 percent of eligible residents, and none operate after 5 p.m. when shift workers need them.” Pair national context with local case detail so the reviewer sees both the scale and the human texture of the problem.

Consequence

Close with what happens if nothing changes — in measurable terms. Rising costs, worsening outcomes, missed federal targets. The U.S. Department of Transportation’s published evaluation criteria guidance is blunt that applications win when they tie the need to outcomes the program is designed to produce. The consequence paragraph is where you make that tie explicit, and it is the easiest place to separate yourself from applicants who stop at describing the problem.

How to Match Your Need to the Funder’s Review Criteria

The same problem can be framed several true ways. The winning frame is the one that maps to the funder’s scorecard. If a NOFO weights “evidence of need” at 20 points and lists three sub-questions, answer all three, in order, with a number for each. Reviewers often score with the criteria open beside the application; making your structure mirror theirs makes their job — and your score — easier.

Read the criteria before you draft, not after. Pull the notice, find the section that governs need or significance, and copy its exact language into your outline as subheadings. Then fill each one. This is also where a strong grant database earns its keep: comparing several notices in your area side by side shows you which evidence funders in your field reward, so you are not guessing. For nonprofits weighing multiple funders at once, the nonprofit grants hub is a faster way to see which programs phrase “need” in ways your data already supports.

One caution: do not pad. A needs statement that runs long to hit every adjacent point dilutes the few that are scored. Most reviewers reward a tight two-to-four paragraphs that answer the published criteria over a sprawling problem essay that buries them. When in doubt, cut the sentence that does not carry a number or move the reviewer toward a scored sub-question.

A Reviewer’s-Eye Rewrite Test

Before you submit, run your needs statement through the test a reviewer applies in the first 60 seconds. Ask four questions and answer honestly. First: can I point to the single sentence that states the problem? If the problem is implied rather than stated, rewrite. Second: is there at least one citable number in the first three sentences? If not, your baseline is missing. Third: whose problem is this — the community’s or my organization’s? If the grammar keeps returning to “we,” reframe around the people affected. Fourth: does the consequence of inaction appear, in measurable terms, before the section ends?

Applicants who pass all four read very differently from applicants who write to impress. The disciplined version is shorter, harder, and more specific. If you are early in your grant-writing practice, working alongside an experienced grant writer on a first draft is the fastest way to internalize the test — most people only need to be walked through it once before it sticks. More tactical breakdowns like this one live in the OpenGrants grant-writing resource library.

Frequently Asked Questions

How long should a statement of need be?

For most proposals, two to four tight paragraphs. The right length is set by the funder’s page limits and review criteria, not by a universal rule. A federal NOFO may give you a page or specify a word count; a foundation letter of inquiry may allow only a paragraph. Answer every scored sub-question with evidence and stop. Length earns nothing on its own — points come from documented need, not word count.

What is the difference between a statement of need and a needs assessment?

A needs assessment is the underlying research — surveys, data analysis, community input — that documents the problem. The statement of need is the concise, persuasive summary of that research inside the proposal. You conduct a needs assessment; you write the statement from it. Reviewers see the statement, but a strong one signals that a real assessment stands behind it.

Can I reuse the same statement of need across applications?

You can reuse your baseline data and core problem framing, but never the whole section verbatim. Each funder publishes different review criteria, and the winning frame maps to the specific scorecard in that notice. Reusing the evidence is efficient; reusing the framing without re-reading the criteria is how strong data ends up answering the wrong question.

Should the statement of need include emotion or just data?

Both, in that order of weight. Lead with verifiable numbers — the baseline, the gap, the consequence — and use one short human example to make the scale concrete. Reviewers score evidence, not sentiment, so emotion supports the data rather than replacing it. A single well-chosen case study after a strong statistic is far more effective than a paragraph of urgent adjectives.

Bottom Line

The statement of need is not where you make reviewers feel something; it is where you hand them the evidence to score the problem highly. The single change that moves the most points is reframing from organizational need to documented problem need, then structuring the section as baseline, gap, and consequence with a citable number behind each. After that, match your evidence to the exact criteria the funder publishes and run the four-question rewrite test.

Do that consistently and your needs statements stop reading like pleas and start reading like cases. If you want this done at the standard that wins competitive federal and foundation awards — with the scorecard read first and the need built to match it, then pressure-tested against real review criteria before the deadline — the team behind OpenGrants’ grant writing services can draft, score, and tighten the section with you.