How to write a Statement of Need that moves foundation trustees

Trustees are not federal reviewers

A federal objective reviewer reads your need section with a scoring form and a checklist. A foundation trustee usually reads a docket summary prepared by program staff, sometimes a page or two drawn from your proposal, often the night before the board meeting. They are looking for a reason to care and a reason to trust. They rarely have time to interpret a dense table of county indicators.

That changes how a need statement should work. The program officer is your first reader and your advocate. Your job is to give them language they can lift directly into the docket memo: a clear description of the problem, a credible sense of its scale, and a specific gap that your organization is positioned to close. If the program officer has to rewrite your need section to make it presentable, you have made their job harder.

Lead with the gap, not the misery

Many need statements open with a long catalogue of hardship: poverty rates, overdose deaths, eviction filings. The data is real and it matters, but trustees have read hundreds of these. A list of bad numbers tells them a community is struggling. It does not tell them why your program is the right response.

A stronger structure names the gap first. For example: 'Families in the eastern half of the county wait an average of 11 weeks for a developmental evaluation because the only two pediatric providers who perform them are 40 minutes away by car.' That sentence holds a problem, a population, a measurable condition and an implied solution. The supporting data then explains why the gap exists and why it is getting worse, instead of trying to carry the whole argument on its own.

Test your opening sentence on someone outside the sector, such as a board member or a friend who works in another field. Ask them to tell you, in their own words, what the problem is and who it affects. If they cannot, the sentence is doing too much or too little, and a trustee skimming a docket will have the same trouble.

• Who is affected, described specifically
• What condition they face, with a measurable indicator
• Why existing services do not reach them
• What changes if the gap closes

Use local, current, sourced data

Foundations, especially community and regional funders, know their geography. A statewide statistic about food insecurity will not impress a trustee who sits on the board of the local food bank. Use the smallest geography your sources support. The American Community Survey 5-year estimates reach down to census tracts. CDC PLACES publishes model-based estimates for counties, places and tracts. The County Health Rankings and Roadmaps program, run by the University of Wisconsin Population Health Institute, compiles county measures with sources and years listed for each.

Your own data is often more persuasive than any public dataset. Waitlist length, intake referrals you could not serve, the share of clients who travel from outside your service area: these numbers prove demand for your specific program. Cite the source and the date for every figure, including internal ones. 'Agency intake records, July 2025 to June 2026' is a citation. 'Our data shows' is not.

Pair one number with one person

Trustees respond to stories, but a story without context reads as an exception. A number without a human face reads as abstraction. The combination works: one carefully chosen statistic, followed by a short, consented, de-identified account of someone who lives inside that statistic. Keep the story to four or five sentences. Make it specific enough to be believable and plain enough to avoid sentimentality.

Get written consent for any client story, change identifying details, and say that you did. Foundations increasingly ask about client dignity in their materials, and a story that reads as exploitative can damage a proposal faster than weak data. If your program staff collect stories informally, set up a short consent form and a shared folder now, before the next proposal deadline forces a rushed request.

Connect the need to the funder's own strategy

Most foundations publish their priorities, and many publish a strategy document or theory of change. Read it and use its vocabulary. If a funder talks about 'economic mobility for young adults', frame your workforce program's need statement around barriers to mobility rather than generic unemployment. Do not stretch your program to fit a priority it does not serve. Program officers can tell, and a mismatched application wastes their time and yours.

Look at the foundation's recent grants too. Many publish a grants list on their website, and Form 990-PF filings, which are publicly available through sources such as the IRS Tax Exempt Organization Search and ProPublica Nonprofit Explorer, list grants paid. If the funder already supports two organizations in your area, explain how your program differs or complements theirs. Trustees do not want to fund duplication, and acknowledging the landscape shows you understand it.

Keep it short and make it reusable

A foundation need statement rarely needs more than 500 to 800 words. Many online portals cap the field at a character count, and an overrun forces cuts at the worst moment. Write a full version, then a 250-word version, then a two-sentence version for the docket summary. Store all three together with their source citations and a review date.

This is where a shared library pays off. In ELIXIR CONSUMERS, need statements live in the vault with their data sources attached, so when the ACS releases new estimates you can see every paragraph that cites the old ones. The underlying discipline does not depend on software: name the gap, prove it locally, put a person beside the number, and make the program officer's next memo easy to write.