How to Write a Case for Support Nonprofit

Every nonprofit has a version of the case for support. Many of them live in a grant proposal from three years ago, or in the executive director’s head, or in a brochure that doesn’t reflect what the organization actually does anymore. Very few are written down in a form that’s current, consistent, and usable across channels.

A strong case for support is one of the highest-leverage documents your organization can have. When it’s well-constructed and kept current, it makes every ask easier—because the foundational work of explaining why your organization matters, why the problem you’re solving is real, and why you’re the right organization to address it is already done.

What a Case for Support Actually Is

The case for support is not a grant proposal. It’s not your mission statement. It’s not your annual report narrative. It’s the underlying argument for why your organization deserves philanthropic investment—the structured reasoning that funders and donors need before they’ll commit significant dollars.

Think of it as the source document. Grant proposals, major gift talking points, board presentations, and campaign materials all draw from it. When the case is strong and current, writing those other documents is faster and more consistent.

A complete case for support makes an argument with six components:

The problem statement — What is the specific, documented problem your organization exists to address? Not the broad social issue, but the particular manifestation of it in your community or field.
Your solution — What specifically does your organization do, and why is your approach effective?
Evidence of effectiveness — What outcomes have you achieved? What do participants, clients, or beneficiaries experience as a result of your work?
Organizational credibility — Why are you positioned to do this work? Leadership experience, track record, community relationships, and operational capacity.
Urgency — Why does this matter now? What happens if this work stops or is underfunded?
The ask — What specific investment are you seeking, and what will it make possible?

The sequence matters. You cannot make a credible ask until the funder understands the problem, believes your solution works, and trusts your organization to execute. Rushing to the ask before building that foundation is one of the most common case-for-support failures.

The “Why You, Why Now” Structure

The most useful framing for a case for support is the “why you, why now” structure. It forces you to answer the two questions funders are actually asking, even when they don’t say them out loud.

“Why you” is about organizational fit and credibility. Not every nonprofit that addresses a problem is the right one to receive this particular investment. Your case needs to explain what makes your approach distinctive, what relationships or expertise you have that others don’t, and what your track record demonstrates about your capacity to deliver.

“Why now” is about urgency and timing. Funders have many options and limited dollars. The case needs to explain what is happening in your community, your field, or the policy environment that makes this the right moment to invest. Is demand for your services increasing? Is there a policy window closing? Is there an opportunity to scale something that works?

These two questions should be embedded throughout the case, not treated as separate sections.

The Anatomy of a Strong Problem Statement

The problem statement is where most cases for support are weakest. Common failures include being too broad (“poverty affects millions of Americans”), using dated statistics, or making claims without sources.

A strong problem statement is:

Local and specific. If you serve a particular county, the statistics should be about that county. National poverty rates don’t make the case for funding a food pantry in Trumbull County, Ohio. Local rates do.

Documented. Every factual claim should be sourced. Census data, state agency reports, peer-reviewed research, local needs assessments—these establish credibility with sophisticated funders who will check your work.

Connected to your program. The problem statement should create a direct line to what you do. The problem you describe should be the problem your program addresses—not a larger social issue of which your work is a small part.

Written for someone who doesn’t know your community. A foundation program officer in a different city should be able to read your problem statement and understand both the situation and why it matters.

Using Data Without Being Data-Heavy

There’s a common mistake in nonprofit case-writing: loading the document with statistics to demonstrate rigor, but actually making it harder to read.

Data is most effective when it illustrates a point that a human story then makes real. The statistic tells the reader the scale; the story tells them the weight.

A useful structure: one anchoring statistic → one specific example or story → the implication for your work.

“Trumbull County’s child food insecurity rate is 24%, nearly double the national average. Last November, Maria, a mother of three working two jobs, came to our food pantry for the first time. She’d been stretching meals for weeks before she could bring herself to ask for help. This is not unusual—60% of first-time visitors to our pantry report waiting more than three months after realizing they needed assistance before seeking it.”

Three data points, one story, a clear implication about unmet need. That’s more effective than a paragraph of statistics.

Using the Case Across Channels

Once you have a strong case for support, it becomes the source document for multiple uses. The adaptation required for each channel is real but manageable.

Foundation grant applications. The case maps directly to the needs statement, program description, and organizational capacity sections of most grant proposals. Your problem statement becomes the needs statement; your solution and evidence become the program description; your credibility section becomes the organizational history and capacity section. The main work is adapting length and responding to funder-specific criteria.

Major gift conversations. The written case should be the preparation tool, not the presentation. A major donor conversation is not a reading exercise—it’s a dialogue. The development officer or ED who has internalized the case can adapt it in real time: leading with the problem if the donor needs context, or with outcomes if they already understand the issue. The written case ensures everyone at your organization is telling the same story.

Board presentations. Board members need to understand the case in order to be effective ambassadors and to make their own philanthropic decisions. A regular case review at a board meeting—especially before a campaign or major ask season—aligns the board around a shared narrative. It also surfaces misalignments: board members who don’t actually believe the problem is significant, or who have a different story about what makes the organization distinctive.

Capital campaigns. Capital campaigns require an expanded case that includes the case for the specific project (the building, the endowment, the equipment) in addition to the organizational case. But the organizational case is the foundation. Major donors don’t fund buildings; they fund organizations they trust, for purposes they believe in.

What to Avoid

Certain patterns undermine an otherwise strong case:

Jargon. “Wraparound services for justice-involved youth” means something specific to professionals in your field and almost nothing to a program officer or donor who doesn’t have that background. Plain language is not dumbing down—it’s respecting your reader’s time.

Passive voice. “Services are provided to over 200 families” is weaker than “we serve 200 families.” Passive constructions make organizations sound less confident and less accountable.

Vague outcomes. “Families are better equipped to manage their finances” is not an outcome statement. “78% of program participants maintained a positive bank balance for 12 consecutive months” is. If you don’t have outcome data this specific, that’s a program measurement problem worth addressing—but don’t paper over it with vague language in the case.

Too much organizational history. Funders care far more about what you’re achieving now than about when you were founded or the difficulties you’ve overcome. A brief organizational history is appropriate; three paragraphs about your founding story is not.

The “we’re the only organization” claim. Unless it’s documentably true, avoid it. Funders know their field. Claiming to be unique when you’re not damages credibility. Instead, be specific about what makes your approach distinctive.

Keeping the Case Current

A case for support has a shelf life. Outcome data ages. Community conditions change. Programs evolve. Leadership changes.

Plan a formal case review at least once per year—typically before the start of your major gift season or before a significant grant proposal cycle. The review should include:

Updated outcome data from the most recent program year
Any changes to the problem statement (new local data, changed policy context)
Verification that the organizational credibility section reflects current leadership and current track record
Review of the “why now” framing—is it still accurate?

Assign ownership of the case to a specific person (usually the development director) and schedule the annual review on the calendar. A case that’s 18 months out of date will have statistics that contradict what you’re saying in proposals, and sophisticated funders will notice.

The internal process for developing and approving the case should include the ED, the development director, and at least one program staff member who can validate the outcome data and the program description. The case should also be reviewed by a board member who represents the perspective of an intelligent outsider—someone who will tell you when the language isn’t clear or the argument isn’t connecting.

For grant-funded programs, keeping your case current is closely tied to the quality of your grant reporting. If your funder reporting templates are capturing the right outcome data throughout the year, updating the case at year-end is straightforward. If you’re scrambling to find program data because reporting has been inconsistent, the case review will expose that gap.

Related resources:

Free resource

Get the Nonprofit Grant Compliance Checklist

A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.

How to Write a Case for Support That Works for Major Gifts and Grant Applications