How to Write a Case for Support

What a case for support is, and what it is not

Every organization that asks for money is making an argument: our work matters, we do it well, and your gift will make a real difference. A case for support is simply that argument written down properly, in one place, with the evidence behind it. Fundraisers sometimes call it a case statement, and the two terms are used interchangeably in practice.

The most useful way to think about it is as a master document. It is usually not the thing you hand to a donor. It is the source you draw from when you write a grant proposal, draft a year-end appeal, prepare a board member for a donor meeting, update your website or design a campaign brochure. Because every piece comes from the same source, every piece tells the same story, with the same facts and the same numbers.

That is what makes a case different from a brochure or an annual report. A brochure is short and visual, written for one audience at one moment. An annual report looks back at what happened last year. A case for support looks forward: it explains what you want to do next, why it matters and what support it needs.

“A case for support is the argument your whole organization makes, written down once and told the same way every time.”

For a small nonprofit with one stretched fundraiser, or with board members doing much of the asking, this consistency is the whole point. Nobody has to reinvent the pitch from memory before every meeting, and nobody accidentally promises something the organization cannot deliver.

Why small nonprofits need one most

Large charities have development teams, campaign consultants and communications staff who can produce polished materials on demand. Small and mid-sized organizations usually have an executive director who fundraises between everything else, a few committed board members and maybe a part-time development coordinator. That is exactly why a written case pays off.

• Speed. When a grant deadline appears with two weeks’ notice, most of the narrative is already written.
• Consistency. Board members, staff and volunteers describe the work the same way, with the same facts.
• Confidence. People who are nervous about asking for money ask better when they have a clear, true story to tell.
• Onboarding. New staff and board members learn the organization’s argument in an afternoon instead of absorbing it over a year.
• Strategy. Writing the case forces conversations about priorities, costs and outcomes that many organizations put off.

That last point is easy to underestimate. Plenty of organizations discover, while drafting their case, that they cannot clearly say what a gift will do or how they measure success. Better to find that out at the writing stage than in front of a foundation program officer.

If your fundraising feels scattered, start with our guide to building a nonprofit fund development strategy. The case for support is one of the first tools that strategy will need.

The three kinds of case you might need

Not every case is the same size or serves the same purpose. Most organizations need one of three, and some eventually need all of them.

Start with the organizational case. The others borrow heavily from it: the same mission, the same evidence of need and the same track record, with a narrower focus and more detail on one budget and one set of outcomes.

There is also a difference between your internal case and the external pieces you make from it. The internal case can be long, detailed and plain. External versions are shorter and designed for their audience: a two-page leave-behind for a donor meeting, a section in a grant proposal, a page on your website. Keep the internal document as the single source of truth, and update it first whenever something changes.

The questions every case must answer

Strip away the formatting and every strong case answers the same handful of questions a thoughtful donor asks, even if they never say them out loud:

If your current materials skip any of these, that is where donors lose interest or funders start asking awkward questions. Use the list as an outline for your first draft, then come back to it as a final check before anything goes out.

State the need in your community’s terms

The need section is where many cases go wrong in one of two ways. Some describe a global problem so broadly that no single organization could make a dent in it. Others describe their programs in detail and forget to explain the problem at all. A strong need statement sits in between: specific to your community, backed by evidence and honest about scale.

Use the best evidence you have and say where it comes from. That might be data from your municipality or the Statistics Canada Census Profile for your area, a needs assessment you ran, waitlists for your programs, referrals from partner agencies or what participants tell you directly. Local, recent and specific evidence usually beats impressive national numbers that have little to do with your neighbourhood.

• Name who is affected, in respectful, people-first language.
• Show the scale locally, with a source for every number.
• Explain what happens to people when the need is not met.
• Describe the gap: why existing services do not already cover it.

Show your response and why it works

Once the need is clear, explain what your organization does about it. Describe your programs and services in plain words: who takes part, what happens, how often, and what changes as a result. Avoid sector jargon. A donor should be able to picture a Tuesday afternoon in your program.

Then explain why your approach makes sense. This is where a theory of change helps: a clear description of how your activities lead to the outcomes you want, and the assumptions that link them. If you have not built one yet, our guide to the theory of change for nonprofits walks through it step by step.

Finally, show your track record. How long have you been doing this work? Who trusts you: partner agencies, funders, participants, the community? What have you learned and changed over the years? Credibility comes from specific facts, not from calling yourself trusted or innovative. Describe what you have done and let the reader draw the conclusion.

Prove impact without exaggerating

Impact is the heart of the case and the place where organizations are most tempted to overstate. Resist it. Distinguish between outputs, the things you did, such as meals served or workshops delivered, and outcomes, the changes that followed, such as families reporting fewer skipped meals or participants finding work.

Use the outcome data you actually collect, and be clear about what it shows. If your evidence is a participant survey, say so. If you track results for six months after a program, say that too. Precise, modest claims are more persuasive than sweeping ones, because they sound like an organization that knows its work.

Stories bring the numbers to life, but they come with responsibilities. Get informed consent, protect privacy, change identifying details when needed and make sure the story is typical rather than your single best result presented as normal. Our guide to nonprofit impact reporting covers how to collect and present outcomes in a way funders trust.

Make the ask concrete

Donors give to things they can picture. Whenever you can, connect support to specific, real costs from your own budget: what it costs to run a session, train a volunteer, keep a drop-in open for a month or support one family through a program. Use your actual numbers, worked out with your finance lead, and update them every year.

Be careful with gift equivalencies. Saying a gift will fund a specific item is only honest if that is how the money will actually be used, or if you clearly describe it as an illustration of what support makes possible. If gifts go into general operations, say that, and explain why unrestricted support is what lets the organization respond to need.

It also helps to describe a few levels of support in plain terms, as long as each one is built from your real costs. Someone considering a modest monthly gift and a foundation weighing a multi-year grant are asking the same question at different scales: what will this make possible? Answer it at each scale, and be clear about which parts of the work depend on unrestricted money that keeps the lights on, the staff paid and the programs running between grants.

• Show the total you need and what it covers.
• Break it into real program costs, not invented round numbers.
• Explain what unrestricted support does, in plain words.
• Tell donors how you will report back on what their support achieved.

If monthly giving is part of your plan, connect it to the case too. Our guide to building a monthly giving program shows how steady, predictable gifts fit into the larger fundraising picture.

Answer why now, honestly

Urgency moves people to act, but false urgency erodes trust fast. Good reasons for why now are real: a growing waitlist, a funding gap opening when a grant ends, a matching gift with a genuine deadline, a building lease up for renewal or a season when demand peaks.

Explain what happens if support does not come. Will a program shrink, a waitlist grow or an opportunity close? Be truthful and proportionate. Exaggerated warnings of collapse might raise money once, but they make the next appeal harder to believe, and donors talk to each other.

Timing also matters inside your own calendar. A case for support for an annual campaign should line up with your budget year and your board’s plan. If your strategic plan is out of date, refresh it before you finalise the case, because donors increasingly ask to see where the organization is heading over the next few years.

Keep it honest: the rules that apply

Honesty in fundraising is not just good manners in Canada. For registered charities, it is part of the rules. The CRA’s guidance on fundraising by registered charities states that registered charities cannot engage in fundraising practices that deceive the public.

The guidance lists specific misrepresentations to avoid, including which charity will receive the donation, the geographic area where the charity operates, whether third-party fundraisers are involved and how they are paid, and the percentage of funds raised that will go to charitable work. It also cautions that claims that all money goes to charitable work must be made with care, because fundraising usually has costs.

Professional standards say the same thing. The Association of Fundraising Professionals’ Code of Ethical Standards asks members to ensure that development marketing and communications are accurate and that contributions are used in accordance with donor intent and restrictions.

A structure you can copy

There is no single correct format, but this order works for most organizational cases. It follows the donor’s questions and moves from the problem to the ask:

1. Opening. Two or three sentences on who you are, who you serve and why it matters, written so they could stand alone.
2. The need. The problem in your community, backed by sourced evidence and described respectfully.
3. Your response. Your programs and approach, explained in plain language, with your theory of change in a sentence or two.
4. Your results. Outputs and outcomes, with one or two consented stories that are typical, not exceptional.
5. Your plan. What you want to do next and why, connected to your strategic plan.
6. The ask. What it costs, what support makes possible and why it matters now.
7. Trust. Leadership, governance, financial stewardship and how you will report back.
8. The invitation. A warm, direct close that tells people how to give and who to contact.

Aim for something your board chair could read in fifteen minutes. Long enough to be complete, short enough to be used. You can always add appendices for budgets, evaluation data and program details.

Writing it so people actually read it

Most cases fail not because the argument is weak but because the writing is. They read like a grant report: dense, abstract and full of acronyms. A few habits make a big difference.

• Write for one real reader. Picture a specific donor or funder and write to them.
• Use plain language. Short sentences, everyday words, active voice. Explain any term a newcomer would not know.
• Lead with people, not the organization. Start with the community and the change, then explain your role in it.
• Be specific. Replace words like many, significant and innovative with what actually happened.
• Show the donor’s part. Make clear what their support makes possible, without pretending they did the work themselves.

Read the draft aloud. Anywhere you stumble, a reader will too. And ask someone outside the organization to read it and tell you, in their own words, what you do and why it matters. If their summary does not match yours, keep editing.

Who should write it, and who should review it

One person should hold the pen, usually the executive director or the lead fundraiser, because a case written by committee reads like one. But the content should come from across the organization, and several people should review it before it is used.

• Program staff check that descriptions of the work and outcomes are accurate.
• Finance confirms every cost and budget figure.
• The board confirms the plan and priorities match what it approved.
• A few trusted donors or volunteers read it as outsiders and say what is unclear.
• Participants or community members, where appropriate, check that they are described respectfully.

Build the review in from the start, with dates, so it does not stall at the end. A case that sits in draft for six months because one person never sent comments is a common and avoidable problem.

How your board uses the case

A case for support is one of the best tools you can give board members, many of whom joined to help but feel awkward asking for money. With a clear, true story in hand, most directors become far more comfortable opening doors and making introductions, even if they never make a formal ask themselves.

Walk the board through the case at a regular meeting, section by section, and invite questions. Then ask each director to practise a two-minute version in their own words, focusing on the need, one result and what support makes possible. You will hear quickly which parts of the case are clear and which need work.

• Give every director a short version they can carry or keep on their phone.
• Agree on the one or two facts everyone should know by heart.
• Encourage directors to share the story with their own networks and report back on reactions.
• Update the board whenever the case changes, so nobody repeats an old number.

Board engagement in fundraising is a governance question as much as a fundraising one. If roles are unclear, our guide to nonprofit board governance best practices covers how to set expectations that directors can actually meet.

Turning the case into fundraising materials

Once the case is approved, put it to work. Each fundraising piece borrows the parts it needs and adapts the tone for its audience:

Keep a simple record of which version went where. When a funder asks a follow-up question, you want to know exactly what you told them. Our guide on how to write a grant proposal in Canada shows how to adapt case material to a funder’s specific questions without copying and pasting.

Test it, then keep it current

Before printing anything, test the case in real conversations. Use it to prepare for two or three donor meetings and a grant application, and notice which parts land and which questions keep coming up. Those questions point to gaps in the document.

Then schedule an annual update, ideally when your budget and plan for the next year are approved. Refresh the numbers, swap in new stories with consent, update outcomes and retire anything that is no longer true. A case that matches the current plan keeps everyone asking with confidence.

Mistakes that weaken a case

Most weak cases share a handful of problems. They are easy to spot once you know what to look for, and most can be fixed in an afternoon of editing.

Run your draft against this list before every annual update. It takes ten minutes and catches the problems that funders and donors notice first.

Frequently asked questions

What is a case for support in fundraising?

It is the core written argument for giving to your organization: the need, your response, your results, your plan, what a gift will do and why it matters now. It is used as a master document for proposals, appeals, donor meetings and your website.

How long should a case for support be?

Long enough to answer the donor’s key questions and short enough to be used. Many organizational cases can be read in about fifteen minutes, with budgets, evaluation data and program details in appendices.

Is a case statement the same as a case for support?

In practice the terms are used interchangeably. Both describe the core argument for supporting an organization or campaign, and both serve as the source for other fundraising materials.

Does a small nonprofit really need a case for support?

Yes, arguably more than a large one. It saves time on proposals, keeps staff and board members telling the same story, and forces clear answers about priorities, costs and outcomes.

Who should write the case for support?

One person should write it, usually the executive director or lead fundraiser, with input from program staff, finance and the board, and review by a few trusted outsiders before it is used.

How often should we update our case for support?

At least once a year, ideally when the budget and plan for the coming year are approved, and whenever a major change happens, such as a new program, a campaign or a shift in strategy.

Can we use our case for support in grant applications?

Yes. Grant proposals borrow the need, approach, outcomes and budget sections, adapted to each funder’s questions. Keep a record of what you sent to each funder so follow-up answers stay consistent.

What should a charity avoid claiming in its case?

Anything deceptive. The CRA says registered charities cannot fundraise in ways that deceive the public, including about where donations go, where the charity operates and how much goes to charitable work, and it cautions that all-to-programs claims must be made with care.