How to write a compelling statement of need
A statement of need proves that a specific, urgent problem exists, shows exactly who is affected and how, and establishes why the funder should act now. Keep it focused on the problem - not your solution - and back it with data you can actually verify.
What the section must prove
Reviewers read the statement of need to answer one question: is this problem real, and does it matter? Name the problem plainly, define the population affected, and describe the consequences of leaving it unaddressed. Resist the urge to jump to your program here; that belongs in the methods section.
Use data - but only data you can defend
Numbers make a need concrete: how many people, how often, at what cost. Prefer local or program-specific data over broad national figures, because it shows the problem in your community. Never invent statistics or citations. A single verifiable figure is worth more than a paragraph of impressive-sounding but unsourced claims.
Connect the need to the funder
The same problem can be framed many ways. Read the funder's mission and priorities, then emphasize the dimension of the need that maps to what they care about - literacy, health equity, workforce, environment - so the fit is obvious to the reviewer.
Common mistakes to avoid
Two errors sink otherwise strong sections: describing your organization's need for money rather than the community's need for change, and stacking vague adjectives instead of evidence. Center the beneficiary, quantify where you can, and stay specific.
A faster way to draft it
You can answer a few structured questions about the problem, who it affects, and your funder, and get a first-draft statement of need in minutes that you refine with your own local data.