Donor Communication

How to Write a Grant Report That Sets Up Your Renewal

Your final grant report isn't the last step of this grant. It's the first page of your next request, so write it for the program officer who has to defend your renewal.

Most nonprofits treat the grant report as the last step of a grant. It's due, it's tedious, and once it's submitted, everyone is relieved to move on.

I think that's backward. The final report is the first document in your next grant request. It's the only thing the funder has from you that describes what actually happened with their money, and it lands on the desk of the person who will decide, or recommend, whether you get funded again.

If you write it as paperwork, it will be read as paperwork. If you write it for the person who has to defend your grant, it becomes one of the most useful fundraising documents you produce all year.

Who actually reads your grant report

At most foundations, your report isn't read by "the foundation." It's read by a program officer who championed your proposal, put your organization in front of a board or committee, and now has to explain whether that was a good decision.

That changes what a good report looks like. The program officer doesn't need a recap of your mission. They already know it. They need three things from you:

  1. A clear answer to "Did this work?"
  2. Enough detail to explain the result to someone who has never visited your program.
  3. Confidence that you understand your own work, including the parts that didn't go as planned.

Picture that person preparing for a docket meeting with 30 other grants on the agenda. Your report is either making their job easier or making it harder.

Many reports never get a conversation

The Center for Effective Philanthropy, which surveys grantees about their funders through its Grantee Perception Reports, has found that only about 60 percent of grantees say they've discussed the report they submitted with someone at their funder. The same CEP piece estimates that grantees spend about eight hours a year on reporting for a typical grant.

Put those together. Roughly four out of ten grantees do that work and never discuss the report with anyone at the funder.

You could read that as a reason to put less effort into reports. I'd read it the other way. If the report is the one place you're guaranteed to have the funder's attention, even briefly, it needs to do more work. And if no one at the foundation brings it up, you can. More on that below.

Foundations are not a small piece of the picture, either. Giving USA estimates that foundations gave about $117 billion in 2025, roughly 19 percent of all U.S. charitable giving. For many small and mid-size organizations, a handful of foundation relationships carry a large share of the budget. Losing one at renewal time hurts.

Lead with the answer, not the activities

Most weak reports open with a list of activities. "We held 42 tutoring sessions. We hired a part-time coordinator. We purchased new reading materials." That tells the program officer you were busy. It doesn't tell them whether anything changed.

Start with a short summary paragraph that answers the question they care about. Imagine a literacy program funded to help 120 third graders reach grade-level reading:

"With your $40,000 grant, we served 94 students this year, short of our goal of 120. Of the students who completed the program, 71 percent improved by at least one reading level. Enrollment fell short because one of our two partner schools changed its schedule in October. We've already moved those sessions to after school for next year."

That's four sentences. The program officer now knows the result, the shortfall, the reason, and the fix. Everything else in the report supports that paragraph.

Report the shortfall before they find it

In the example above, the program reached 94 of 120 students, about 78 percent of the goal. A lot of organizations would bury that number on page three or skip it entirely.

Don't. Funders know programs don't run exactly as proposed. What tends to damage trust isn't the missed target. It's discovering the missed target on their own, or getting a report that sounds like everything went perfectly when they suspect it didn't.

The Trust-Based Philanthropy Project, a peer-to-peer funder initiative, encourages foundations to "simplify and streamline paperwork" and to favor approaches "focused on dialogue and learning." Not every funder works this way, but the direction is clear. Many program officers want to know what you learned, not just what you completed.

When you report a shortfall, use a simple structure:

  • What we expected: 120 students across two schools.
  • What happened: 94 students, because one school's schedule change eliminated our in-school block.
  • What we learned: Relying on in-school time at a single site was a risk we didn't plan for.
  • What we're changing: After-school sessions at both sites starting in January.

This is the same principle that makes fundraising stories more believable, which is the subject of The Story You're Afraid to Tell: When Imperfect Outcomes Make Better Fundraising. Honest results tend to earn more trust than polished ones.

Give the numbers a face

A report full of outputs and percentages is accurate but forgettable. The program officer has to retell your results to their board, and people retell stories more easily than tables.

Include one short, specific story about a participant (with permission, and with identifying details changed where appropriate). Not a sweeping transformation story. A small, concrete one. A student who wouldn't read aloud in September and volunteered to read to the class in March. A quote from a teacher about what changed.

If you struggle to collect stories, the problem is usually process, not material. The 10-Minute Story Interview walks through a simple way to gather them from the people you serve without making it a burden on program staff.

Connect the report to what comes next

Your report should end by pointing forward, without turning into a proposal. One or two paragraphs is enough:

  • What you plan to do next year and why, based on what you learned.
  • What it would cost.
  • One specific question you're working through, if there is one.

That last point matters more than it sounds. Asking a program officer for their perspective ("We're deciding whether to expand to a third school or deepen work at the two we have. We'd value your view.") invites the conversation that 40 percent of grantees never get. It also signals that you see the funder as a partner in the work, not just a source of checks.

A simple grant report checklist

Before you submit your next report, run it through these questions:

  1. Could the program officer explain your results to their board from the first paragraph alone?
  2. Did you compare actual results against the specific goals in your proposal, using the same numbers?
  3. Is every shortfall named, explained, and paired with what you're changing?
  4. Does the budget section explain any variance larger than you'd be comfortable defending in person?
  5. Is there at least one concrete story or quote?
  6. Does the report point clearly to next year?
  7. Did you follow the funder's format and answer every question they asked, in the order they asked it?

That last one is easy to overlook. A brilliant report that ignores the funder's template creates extra work for the person you're trying to help.

Make the report a conversation, not a file

Here's where I'd start. Pull the final reports you submitted in the last 12 months. Read the first paragraph of each one as if you were the program officer seeing it for the first time. If you can't tell within 30 seconds whether the grant worked, rewrite the opening of your next report before you write anything else.

Then, two or three weeks after you submit, email the program officer. Keep it short: "I wanted to make sure our report gave you what you need. Would 20 minutes be useful to walk through what we learned and what we're planning next?" Some will say no. The ones who say yes are giving you time with the person most likely to shape your renewal.

If you want to tighten the program story that sits underneath every report and proposal, the Case for Support Audit is a good next read.

Grants work best as one part of a balanced plan. Here's how to write a fundraising plan.

Questions fundraisers ask

What should a grant report include?

Open with a short summary that says whether the grant worked, including where you fell short. Then give the numbers, a story that puts a face on them, and one or two paragraphs about what comes next.

How do you report results that missed the goal?

Name the shortfall before the funder finds it. Say what you expected, what happened, what you learned and what you changed.

Who reads a grant report?

At most foundations it's the program officer who championed your proposal and now has to explain whether funding you was a good decision. Write it for that person. Two or three weeks after you submit, offer a 20-minute call.

Ask a fundraiser

Still have a question about this?

Taggedfoundationgrantreportingstewardship

About the author

Jeremy Reis

Jeremy Reis is President of Serving Orphans Worldwide and has led nonprofit fundraising for two decades, including growing the World Concern monthly donor program from 800 donors to over 4,000 donors. He is the author of Magnetic Nonprofit and Why We Give, and hosts the Nonprofit Answers podcast.

Learn Fundraising in 10 Minutes

Ten minutes a week. Better fundraising for good.

One practical idea every Tuesday and Thursday from a fundraiser who is raising money right now.

Free. Unsubscribe anytime. See what's inside