How to write a compelling statement of need.

A statement of need is not an introduction to your organization and not a description of how badly you need funding. It establishes a specific condition affecting a defined group in a defined place, explains why that condition persists, and identifies the gap the proposed work can credibly address. Its job is to make the project necessary and logically appropriate before the reviewer reaches the solution.

Start with a one-sentence claim that includes population, place, condition, and consequence. Then support it with current, relevant evidence. National statistics can establish scale, but local data establishes relevance. Use public datasets, administrative records, waitlists, referral patterns, program data, community assessments, and credible qualitative evidence. Give every statistic a source and date, and do not use precision your data cannot support.

Move from condition to consequence. Explain what happens to people, families, institutions, or communities when the condition continues. Be concrete about educational, health, economic, or operational effects, but avoid reducing people to deficits. A strong needs statement describes barriers and systems while preserving the agency and strengths of the community.

Then identify the service gap. What currently exists? Who provides it? Why is it insufficient, inaccessible, fragmented, or mismatched? Funders need to see that you understand the landscape and are not duplicating effective services. ‘No one is addressing this’ is rarely true. A narrower claim—such as no provider offering evening services in two target counties—is more credible and more useful.

Explain the underlying causes your intervention can influence. If transportation, language access, staffing, policy, trust, or affordability drives the gap, say so and connect the project to that mechanism. Do not use the statement of need to solve every cause. The proposed response should be proportionate to the problem and honest about what remains outside its reach.

Lived experience adds meaning that aggregate data cannot, but it must be gathered and used responsibly. Use consented quotations, listening-session themes, participant advisory input, or documented community feedback. Do not ask AI to invent a participant voice or turn a composite into a real person. Distinguish direct testimony from organizational interpretation and protect identifying details.

End with urgency and readiness, not with your full program description. Explain why action matters now—an emerging trend, policy change, service interruption, or documented growth in demand—and why the proposed scale is reasonable. The transition should make the solution feel like a response to the evidence, not a program looking for a problem.

Revise with four tests. Could another nonprofit paste its name into this statement unchanged? Does every major claim have support? Does the evidence point to the proposed activity? Would a person described in the section recognize their community fairly? If any answer is no, the section needs more specificity or restraint.

Mavenly helps teams build statements of need from their own organization library, program profiles, outcome data, and cited source documents. Its Proposal Builders can draft each structured section, flag missing evidence, and preserve bracketed items that require human confirmation. Use Mavenly to accelerate assembly and review—not to replace the community knowledge and consent that make the argument true.