I recently onboarded a new client in the food insecurity space. I've worked in this sector before, so I expected to know what their proposals would sound like. But as I read through their past applications, I noticed they wrote about hunger in a very intentional way.
There were no "needy families" or "at-risk kids" in their writing. There was no parade of statistics designed to make a reviewer wince. They still made a clear, urgent case for funding. They did it without shrinking the people they serve down to what they lack.
That's asset-based language, and this client did (and still does) it exceptionally well.
If you've sat through a "writing ethically" workshop, you've probably heard the term. But it's one of those phrases that gets nodded at more than it gets practiced.
So let's dig into what it actually means, and clear up three myths that keep good grant writers from using it.
What Is Asset-Based Language?
Asset-based language describes people and communities by their strengths, potential, and aspirations, not by their deficits.
Deficit-based language starts from what's missing or what's wrong. Asset-based language starts from what's present and what's possible.
The idea is often tied to Trabian Shorters, who popularized the term "asset framing." Grant writer Amaya Howard describes hearing him challenge a room full of nonprofit professionals: would you walk up to a young child and say, "Hello, little at-risk youth"? Of course not. So why do we write about them that way?
A few quick examples of the shift:
Instead of… At-risk youth. Try… Young people placed at risk by [specific systems or conditions].
Instead of… Underprivileged families. Try… Families who have been historically underserved.
Instead of… The Homeless. Try… People who have been excluded from safe, consistent housing.
Instead of… Giving back to those in need. Try… Working alongside our neighbors.
Notice what these swaps have in common. They put people first. And where there's a problem, they point to the systems that created it, rather than implying the people themselves are the problem.
Myth #1: Asset-Based Language Means Hiding the Need
You could think that if we stop leading with hardship, you could sound naive, or worse, like the problem isn't real.
But asset-based language isn't toxic positivity. As Eleanor Cotter of Green Pen Strategies puts it, needs and strengths are not opposites. A community can face real, serious challenges and show creativity, resilience, and leadership at the same time. Saying both is simply more accurate.
Here's what that looks like in a food insecurity proposal:
Deficit-based: Our county has one of the highest hunger rates in the state. Many low-income families struggle to put food on the table, and at-risk children go without nutritious meals.
Asset-based: One in [X] households in [County] can't count on steady access to groceries, a gap driven by rising rents, flat wages, and the loss of [two] full-service grocery stores since [year]. Families here are already stretching every dollar and sharing what they have; our neighbor-run pantry network grew directly out of that generosity. With your support, we'll expand it to [X] more households.
The second version still names the need, with a number. But it explains why the need exists, shows the community as active rather than passive, and makes a stronger case for why the program will work.
Myth #2: Funders Want the Hard-Luck Story
Most of us were trained to open a proposal with a problem statement: how many families live in poverty, how many students read below grade level. Many grant professionals feel real pressure from funders to tell trauma stories in order to get funded.
And yes, you need to speak your funder's language. Strong proposals align with a funder's priorities and show you understand how they define impact.
But alignment doesn't require adopting language that conflicts with your values. Echoing a funder's goals is not the same as echoing deficit framing.
In fact, plenty of funders (especially those with an equity lens) are moving away from deficit language themselves. And asset framing gives every funder something they want: evidence that you'll succeed. When you show the skills, networks, and leadership already present in a community, you're showing a reviewer why this investment will work, not just why it's needed.
A pity-driven proposal says, "Look how bad it is." An asset-based proposal says, "Look what's already happening, and what your support will make possible." Only one of those inspires confidence.
Myth #3: It's Just Swapping Out a Few Words
Word lists are a great place to start. Points of Light publishes a helpful "don't say this, say this instead" guide, and I keep it bookmarked. But if you only swap vocabulary, you can end up with a proposal that sounds asset-based and still thinks in deficits.
The real shift is in the frame. A few questions to ask of your draft:
Where does the responsibility sit? Asset-based writing places the burden on systems and conditions, not on individuals. "Impoverished" (made poor) tells a different story than "poor."
Are you working with or for? Watch for power-based phrases like "giving back to the less fortunate" or "helping us appreciate how lucky we are." They quietly cast your organization as the hero.
Is there pity in it? Lines like "they have nothing" put a person's worth up for debate, even when they're meant kindly.
Are you just trading clichés? "Resilient" and "untapped potential" can become their own kind of shorthand. Be specific about what people are actually doing.
And remember that no list is final. Even the guides sometimes disagree, and preferred terms keep changing.
The best source of language is the community itself. Ask people how they describe themselves, their neighborhood, and what they could do with the right resources. Then use their words.
Conclusion: There's Always More Work to Do
Even if you think you're already writing with asset-based language, there's probably room to grow.
I consider myself a very ethical writer, and my clients would say the same. And yet this new client showed me something I hadn't seen in my own work.
That's the thing about habits: they're hard to spot from the inside. The phrases we were trained to use slip into drafts without us noticing.
So here's my challenge to you. Partner up with a trusted grant friend who doesn't usually read your work, and swap proposals.
Review each other's writing with one specific goal: finding deficit-based language. Fresh eyes will catch what yours skim past. Then talk through the rewrites together.
The communities we serve deserve to be described the way they'd describe themselves. And honestly? Those proposals tend to be the more compelling ones anyway.
P.S. (Here is a freebie)
Are you drowning in grant work, unsure how and when to get it all written? Burned out from writing too much? I just released a free guide on how I run my business without hitting writer's burnout. Message me on LinkedIn at @MackenzieGreer to get your copy and learn how to keep your head above water and write things well.