Write the campaign case before writing the appeal

A fundraising campaign case for support should explain the problem you plan to address, the work a gift will support, and the evidence behind that promise. Write those points before writing the appeal. If your team cannot explain what this campaign makes possible, a more emotional headline will not resolve the uncertainty.

For a lean nonprofit, the case can begin as a short working document. Its first reader is the colleague who must decide whether the proposed ask is accurate enough to publish.

Choose the work this ask will support

Start with one proposed campaign and a defined use of support. Explain the need without describing every problem your organization addresses. Then name the work your team plans to do and why you are equipped to do it.

BoardSource's fundraising guidance describes a case statement as an explanation of the need or problem and the proposed plan of action. That is a useful starting boundary: a case is the reasoning behind an ask, rather than a list of everything the nonprofit offers.

Decide whether the appeal supports a defined project or the organization's ongoing work. Both can be clear. Trouble starts when the page promises a tightly specified result while the actual use of gifts is broader. Have the program and fundraising owners resolve the scope before the copywriter starts.

Your fund, campaign, and appeal records can track different parts of the work. They do not replace the reader-facing explanation of what a donor is being invited to support.

Build a promise your evidence can carry

Use a compact set of questions to test the proposed case:

• What specific need is this campaign responding to?
• What work will the organization undertake?
• What resources does that work require?
• What evidence supports the plan and its feasibility?
• What will you tell supporters after the campaign?

Attach the source behind each important answer. A program plan can support the proposed activity. An approved budget can support the resources needed. A documented past result can show relevant experience, but should not become a guarantee that the next campaign will produce the same outcome.

Distinguish planned work from completed work in the wording. “We plan to add evening sessions” and “we added evening sessions” make different claims. If the case depends on staffing, a partner agreement, or a venue that is still pending, resolve that dependency or describe it accurately beside the promise.

Do not create an exact gift-to-outcome conversion merely because it makes an attractive giving level. Use your own gift history to set suggested amounts, and explain the work those gifts support without inventing a universal unit cost.

Give the budget a place in the explanation

Translate the budget into the resources the donor needs to understand. Name staffing, materials, transportation, space, or other actual requirements relevant to the proposed work. Avoid a string of internal account labels.

The aim is to make the scope understandable, not to publish every budget line. Keep an internal reference showing how the public explanation connects to the approved plan. If the goal changes, that reference helps the team update the case consistently.

State how the campaign fits the larger program. A reader may reasonably wonder whether the ask funds the whole service or one part of it. Say which it is. Where the campaign depends on other resources, explain the relationship without presenting unsecured support as already available.

Test the case before polishing the appeal

Give a colleague who did not help write it the draft. Ask them to explain what the gift supports and what the organization is promising. If their answer differs from the program owner's answer, revise the case first.

Then check the shortest versions. Does the donation-page introduction still carry the same promise? Does a social caption drop a limitation that matters? Does an appeal letter add a result the case never supported? Choose one approved statement of the need, action, and expected work, and use it as the reference for these variations.

The National Council of Nonprofits' storytelling framework separates need, action, and impact. When you use a story in the case, keep those pieces distinct: a real person's experience can illustrate the need without proving that every future gift produces their exact outcome.

Finish by naming the next update you owe supporters. Record what you expect to be able to report, who will gather the evidence, and when your team will review it. The case is ready when the ask, program plan, and future update all describe the same work.