Grant Writing. It’s Political. And Your Needs Statement Proves It.
The Power and Politics of Language in Grant Narratives
Grant writing is not just about writing. And it never has been.
It’s about framing. Positioning. Translating. Deciding which words make a problem feel urgent, solvable, fundable, and worthy of attention. Language in grant narratives is never neutral.
The words we choose in a needs statement shape how a community is seen. The logic we use in a project justification shapes which solutions feel legitimate. The tone of a narrative can either reinforce harmful assumptions or reshape the way a community or problem is perceived.
This is where grant writing becomes more than technical skill. Whether we like it or not, grant writing is often a political act.
If you’ve ever stared at a blank page trying to describe a community’s challenges without flattening its dignity, this conversation is for you. If you’ve ever wondered why certain phrases seem to “work” with funders even when they don’t fully reflect the truth, this conversation is for you too.
Because strong grant narratives do two things at once: they make the case, and they protect the people at the center.
The Problem: Too Many Grant Narratives Confuse Need With Deficiency
Let’s start here. It’s really quite basic. A needs statement should explain the problem your project addresses. A project justification is supposed to explain why your proposed approach makes sense. Straightforward enough.
But in practice, these sections often become a performance of scarcity. In fact, early in my career, I heard an advanced career grant professional say that we should all approach a needs statement as if we were convincing a funder: “all needs are important, just not as great as mine.” The sentiment being, take the funder on a tour of everything that is not working and convince them your organization is serving the “neediest” cases.
Organizations start reaching for language that sounds dramatic, distressed, or devastating because they assume that is what funders want to hear. They begin to describe communities exclusively through what is missing: no access, high rates of personal failings, and poor outcomes.
Some of that language may be factually true.
And some of us will pat ourselves on the back, thinking, “I don’t do that. I focus on disparities and the history of how we got here.” We do need to name inequity plainly. We do need to describe harm honestly. We do need data.
But there is a difference between documenting injustice and narrating people as broken.
When a grant narrative leans too hard into damage, it can unintentionally do at least three harmful things:
It can reduce a community to its hardest statistics.
It can imply that outside institutions are the primary source of rescue.
It can reward language that feels more extractive than accountable.
And once that becomes the norm (which I’d argue it already is), grant writers may come to believe they must choose between being compelling and being truthful.
You may feel this tension. I know I do.
Needs Statements Are Not Neutral Summaries of Data —They Are Arguments
A needs statement is not just a section of a proposal. It is an argument about what matters.
It answers questions like:
What problem deserves attention?
What problem can be solved?
Who is affected?
Why now?
Why here?
Why should this funder care?
That means every choice inside the statement carries weight. Which data points you include. Which historical context you name. Whether you focus on individual behavior or structural conditions. Whether you describe residents as passive recipients or active stakeholders. Whether you mention racism, disinvestment, exclusion, and policy failure, or avoid them in favor of softer, more “comfortable” language.
That is the politics of grant language.
Not politics in the partisan sense. Politics in the real-world sense: who gets named, who gets blamed, who gets believed, and who gets funded.
For example, compare these three framings:
Version one:
This neighborhood suffers from chronic unemployment, low educational attainment, and generational poverty.
Version two:
This neighborhood has faced decades of disinvestment, limited access to quality employment pathways, and inequitable education and economic systems that have constrained opportunity.
Version Three:
This neighborhood is home to residents who have long navigated and challenged the effects of disinvestment, limited access to quality employment pathways, and inequitable education and economic systems—while continuing to build local solutions, support networks, and pathways to opportunity.
All three describe serious issues. But they do not do the same work. The first subtly locates the problem in the people, allowing a reviewer to assume that the neighborhood’s residents are lazy and do little to help themselves. The second locates the problem in systems and conditions. The third acknowledges the system's challenges and the active work of residents to build despite them.
These could all be written about the same neighborhood, but they are not the same story.
The Best Needs Statements Tell the Truth Without Stripping Away Dignity
A strong needs statement does not minimize hardship. It does not avoid hard numbers. It does not pretend that inequity is less severe than it is. But it also refuses lazy deficit framing.
We can say, “families are actively navigating severe housing instability, making difficult and strategic choices to maintain stability in an increasingly constrained housing market,” without implying, “families are irresponsible or incapable.”
We can say, “Black women and families are navigating maternal health systems shaped by persistent racial disparities in care, access, and treatment, while continuing to advocate for safer, more equitable care,” without saying “Black communities are simply ‘high risk’ as though the risk appeared out of nowhere.”
We can say, “youth and families in this region are actively seeking mental health support but face limited access to services that are culturally responsive, affordable, and consistently available,” without implying “youth and families are failing to seek help.”
See the shift? Quickly jot down an improvement you can make in the needs framing for your organizations’ programs.
Needs Statements Reveal What We Believe About Change
If the needs statement explains the problem, the project justification should explain why your approach makes sense.
Once the problem is defined, there is a tendency to move straight into describing activities. Workshops, case management, training, outreach, services, staffing. The narrative becomes a list of what will happen, rather than an explanation of why those choices are the right ones.
A strong project justification does more than outline activities or refer to evidence based interventions. It connects the approach to something credible that has already happened. That might be prior results, community input, evidence, or lived experience. It shows that the design is not just well-intentioned, but grounded in the local context.
This is also where the language starts to reveal deeper assumptions. How an organization talks about its work often signals how it understands change.
Are we describing an effort to fix people, or to remove barriers that limit opportunity?
Are community members positioned as active participants, or as targets of intervention?
Is the case for the program built on what sounds “fundable,” or on what is actually needed and supported by evidence and community demand?
Under pressure to stand out, many proposals drift toward inflated language. Terms like “transformative,” “holistic,” and “cutting-edge” start to replace clear explanations. At the same time, local knowledge and existing community efforts get pushed to the background.
In many cases, the strongest justification is also the simplest. The approach works. The community has asked for it. The organization has the experience and relationships to carry it out well.
So if it is simpler, why wouldn’t this be the approach that most grant writers take?
Frankly, it is harder to write.
Funders Don’t Just Fund Problems—They Fund Narratives About Problems
This is the part we do not talk about enough. Funders are not reading needs statements as detached observers. They are reading from within their own frameworks, priorities, biases, institutional habits, and political realities.
They have a preferred language. Preferred evidence. Preferred signals of credibility. And these frequently do not align with community work and are more closely aligned with academic approaches, evidence-based interventions, and models designed to work, but often fall short of their promised impact because they lack the flexibility or space for community context.
So, yes, grant writers often make strategic choices. We may use certain terms because they map onto a Notice of Funding Opportunity. We may mirror funder language because alignment matters. We may foreground data because evidence matters. That is part of the game we play.
But we need to be clear about what we are doing here. If we contort a community’s reality to fit a funder’s vocabulary, we risk writing narratives that are technically polished but fundamentally misaligned. We have to ask:
Are we using language that clarifies? Or language that performs a familiar story?
Are we making the case? Or selling a version of the case that funders find more palatable?
Are we preserving complexity? Or flattening it for convenience and comfort?
This is especially important for organizations serving communities that are already over-studied, underfunded, and misrepresented.
In our next blog, we will look at three common language traps in needs statements and how to start to shift toward language that places community members at the center of their own stories as main characters.