Data Shows the Scope. Stories Show the Stakes.

Reviewers read your statement of need first, and they read it with one question in mind: is this problem real, and is it as significant as the applicant claims. Everything else in the application answers a need the reader has to believe in first.

Data and story each fail alone. Data without story is sterile, and a reviewer who feels nothing is not persuaded the problem is urgent. Story without data is anecdotal, a single moving example that reads as the exception rather than the pattern. Together they work, because data shows the scope and story shows the stakes.

Three layers, and most applicants invert them

Local data is the foundation. Your own service data, your school district's figures, county health numbers, state agency data filtered to your geography, census data cut to your service area. It proves the problem is here rather than merely somewhere.

Regional and state data is the second layer. It shows whether your local problem is part of a larger pattern, which tells a funder the investment addresses something structural rather than isolated.

National data is the framing layer. It signals the problem is documented at scale and is a legitimate target for federal resources.

The strongest statements of need lead with local data and layer the wider context on top. The common mistake runs the other way, opening with a national statistic and hoping it stands in for local proof. National numbers frame. They cannot carry the case alone.

Two habits strengthen every statistic. Pair percentages with raw numbers, because a percentage without a count hides the scale and a count without a percentage hides the proportion, and a skeptical reader notices both omissions. And watch the age of the data. A figure more than five years old, with no acknowledgment that it is the most recent available, invites the question of whether the problem has changed since.

For a nonprofit, your own data is the underused asset

The people you already serve, the waitlists you already keep, the outcomes you already track are local evidence no national dataset can match, because they describe the exact population and geography the project will address. Treat internal data as the first and strongest layer, then reach outward.

The story layer is where closeness to the community becomes an asset, and it carries an obligation. The strongest statements of need pair the numbers with one specific account of a person or family, told with permission and anonymized where needed, that shows what the statistics mean in a life. Consent, dignity, and accuracy are not optional. A story told carelessly costs more credibility than it earns. Done right, one honest account turns a page of data into a problem the reader can feel.

For a local government, the problem is marshaling, not finding

Public agencies generate and hold administrative data as a matter of operation: crash records, code enforcement logs, utility usage, 911 call volumes, inspection results, ridership counts, permit records. This is local data of the most credible kind, because it is the government's own official record, and it is frequently stronger than anything a nonprofit can assemble.

Governments also have easy access to authoritative regional and state data that reinforces their own record. State agency dashboards, metropolitan planning organization datasets, transportation safety data, public health surveillance systems, university research partnerships. The strongest public sector need statements stack the agency's administrative data as the local layer, state and regional datasets as context, and national framing on top, with every figure sourced to its system of record.

Two cautions are specific to the public sector, and both are worth building into your process.

Administrative data is messier than it looks. Records kept for operations are not always clean enough for a statement of need without verification, so confirm the numbers against the system of record before they go in an application rather than trusting a figure remembered from a dashboard.

And the human story is genuinely harder for a government to tell well. A public agency rarely holds the consented individual narratives a direct service nonprofit does, and inventing or over claiming one is both an ethical and a credibility risk.

The honest substitute for a person is a place. A named intersection, a particular census tract, a specific facility, described concretely enough that the data acquires a human face without putting words in anyone's mouth.

A public library system shows the pattern. Applying to fund digital access, it opens with its own administrative data, the share of cardholders relying on library devices for internet access and public computer wait times across branches. It layers in county broadband adoption figures and state digital equity data, then national framing on the digital divide. In place of a patron's story it describes a specific high need branch, with its device counts and turn away numbers, concretely enough that the need reads as real without claiming to speak for any one patron.

Signals worth a second look

Evidence gaps weaken every section built on the statement of need, so catch them before you draft.

All five point back to the same work: build the local layer first, source every figure, keep the data current, and pair the numbers with something a reader can feel.

Evidence is the most perishable thing you maintain. A fit statement can hold for years; a statistic ages by the quarter. So the organizations that stay ready track when their sources update rather than when applications are due. Census releases, agency dashboards, and internal service data each have their own rhythm, and knowing that rhythm is what keeps a statement of need from opening on a four year old number the day after the source published a newer one.

Knowing what you do not have is part of this too. A documented gap with a plan to fill it is a sign of an organization in command of its evidence, not a weakness in it.

The Data and Evidence Builder pulls together your three strongest statistics and pairs them with a story, and it is the fourth worksheet in the series.

Get free access to the Grant Readiness Resource Hub. One signup opens the whole library of free tools, templates, and checklists, built from real federal grant work and updated as the rules change.