Builds a needs statement that argues from data at three levels (community, population, and your specific service gap) without a single unverifiable statistic slipping through.
Who it's for: grant writers who keep getting the same reviewer comment — "the need is asserted rather than demonstrated" — and cannot tell which sentence is the problem.
What it produces: a needs statement structured as a descending argument. Community-level context from public data, then the specific population, then the service gap only your organization can document, then the consequence of inaction stated in concrete terms. Plus a source table listing every figure, where to find it, and its vintage.
What makes it non-obvious: it separates the three kinds of data a reviewer weighs differently and most drafts mash together — public secondary data that establishes context, population-level data that narrows to your people, and your own service data that proves the gap is real and that you are the one standing in it. It also names the specific public sources you should be pulling from by name — American Community Survey tables, state education and health department dashboards, county community health assessments, the Point-in-Time count — so the research step becomes a checklist. And it refuses to write a statistic it cannot attribute.
You are a grant writer building the needs section of a proposal. Reviewers do not doubt that need exists; they doubt that you have measured it. Argue in three descending layers — community, population, service gap — and attach a source to every number. If you cannot source a number, do not write the number; write
**Statement of Need — Cedar County Adult Literacy Project** **Community context.** Cedar County's adult population without a high school credential is estimated at 12.4% `[VERIFY — ACS 5-Year Estimates, Table S1501]`, against a state figure of 6.8% `[VERIFY — same table, state level]`. **The population.** Of 1,180 adults enrolled in county workforce services last program year, 31% screened below ninth-grade reading level `[VERIFY — county workforce board annual report]`. This is who our program serves. **The service gap.** Cedar County has one adult basic education site, open two evenings per week. Last year our waitlist averaged 47 adults, median wait 14 weeks. Twenty-two people withdrew before a seat opened. This is our own enrollment data. **Consequence of inaction.** Without added capacity, roughly 90 adults per year will be referred and not served. `[GAP: no data on transportation barriers, which staff cite constantly — consider a short participant survey.]`
The section that carries the most weight is your own service data — waitlist length, referrals turned away, time-to-service — because it is the only data no other applicant has. If you leave that field blank, the statement will be structurally sound and unpersuasive, and the output will tell you so.
Adapt it by setting the word ceiling to match the funder's section limit; the argument compresses from the community layer inward, which is the correct order to cut.
Limitations, stated plainly: the model does not have live access to ACS, state dashboards, or any current dataset, and its training data is stale. It names the table and the source so you can pull the real figure; every number it produces is a placeholder marked `[VERIFY]` and must be replaced with a figure you retrieved yourself. Publishing an unverified statistic in a proposal is a credibility problem with a funder and, in a federal application, a compliance problem. This is drafting support, not research, and it is not legal or compliance advice.