How to Write a Grant Progress Report Your Funder Actually Reads

There's a particular kind of tired that shows up the week a grant report is due. I know it well. Three spreadsheets open, a survey export, a folder of sign-in sheets, the original proposal somewhere in an email from fourteen months ago, and a funder template asking, politely, what happened.

I've spent a lot of my career on the other side of that table, building the systems that hold the numbers. Here's what I've learned about writing a progress report funders actually read, and the bigger lesson about why the week-before scramble happens at all.

Funders all ask the same five questions

Read enough reporting guidelines and the pattern jumps out. The forms look different, but they're asking the same five things:

1. What did you promise? Your goals and objectives, as stated in the proposal.
2. What did you do? Activities and outputs for the period.
3. What changed? Progress toward outcomes.
4. What got in the way? Challenges, delays, changes to the plan.
5. What's next? Upcoming activities and, in a final report, sustainability.

You can see it across very different funders. The Gates Foundation's U.S. Program guidelines ask for a short summary, progress on outcomes and milestones, your greatest successes, unmet milestones and challenges, evaluation findings, a financial report with a narrative on any variance over 10%, and sustainability plans (Gates Foundation). The Sloan Foundation wants goals and metrics with whether each is on track, ahead or behind, plus key changes and lessons learned, in 2 to 4 pages (Sloan Foundation). The Appalachian Regional Commission requires actual outputs and progress toward outcomes in every interim report, plus problems encountered and what you'd do differently (ARC). The EPA says progress reports should explain why outputs or outcomes weren't met if they weren't (EPA).

Same five questions. Answer them in order and you've written most of any report.

Rule one: report against the proposal

Open your original proposal before you write a word. Find the goals, objectives and outcomes you promised, and copy them into your report in the same words and the same order.

Funders are reading your report next to your proposal. Sloan's guidelines put it directly: list the initial goals and metrics from your grant and describe progress towards each (Sloan Foundation). If you promised "70% of participants will have home internet at 60 days," your report should say, right there, "Target: 70%. Actual: 68%." Not a paragraph about connectivity in general.

If the goals changed during the grant, say when and why, and whether the funder approved it.

A template you can copy

This works for most foundation and many government interim reports. Adjust the headings to match your funder's form.

1. Grant information Funder, grant number, program name, reporting period, contact.

2. Summary (one paragraph) Where the project stands in plain English. Are you on track, behind or ahead? What's the one thing you most want the funder to know?

3. Progress on goals and outcomes

4. Activities and outputs What you did this period, with the counts. Keep it tight; the table above carries most of it.

5. A story that matches the numbers One participant's experience, with permission, that illustrates the most important outcome. Not your happiest story. The most representative one.

6. Challenges and what you're doing about them Each challenge in its own short paragraph: what happened, the effect on targets, and the fix.

7. Changes to the plan Staffing, timeline, approach or budget changes, and whether they were approved.

8. Next period What's coming, and anything you need from the funder.

9. Financial report Spending to date by budget line, with a short note on any big variance. Gates uses 10% as the line for explaining variance (Gates Foundation); it's a reasonable default if your funder doesn't set one.

For a final report, add: overall results against every goal for the whole grant, lessons learned, and how the work continues after the money ends. ARC asks directly whether the program will continue and what other funding you've found (ARC).

How to report a missed target

This is the section people write around, and they shouldn't. Funders expect some targets to slip. What they don't trust is a report where everything is fine.

The Gates guidelines literally ask you to discuss one to three unmet milestones and the steps you're taking (Gates Foundation). So do it well:

• Put the real number next to the target. "Target 70%, actual 52%."
• Explain the cause in one or two sentences. No hedging.
• Say what you're changing. A specific action with a date.
• Say what you learned. Funders are trying to learn too.

Something like: "We set a target of 70% with home internet at 60 days and reached 52%. The main reason was a six-week waitlist with our largest low-cost provider. We've added a second provider and moved check-ins to 90 days for anyone still waitlisted. We expect to report the updated figure next quarter."

That paragraph will do more for your next renewal than a page of adjectives. I feel strongly about this. Keeping the unflattering findings in, as lessons, is what makes the good findings believable.

Make every number traceable

Here's the question a careful program officer will eventually ask: "Where did 68% come from?"

You should be able to answer in one sentence. "68% is 82 of the 120 participants who reached their 60-day check-in, from our check-in call log, for the period July 1 to September 30." Who's in the denominator. Where the data came from. What period.

Write those definitions down the first time and reuse them every report. If "completed" meant four sessions in the spring report, it means four sessions in the fall report too. Changing definitions quietly is how two honest reports end up contradicting each other.

Why the week-before scramble happens

The writing is rarely the hard part. The hard part is that the data was never planned for the report. The intake form didn't ask the question the funder cares about. The follow-up happened for some people and not others. Nobody wrote down what "completed" means.

The fix is boring and it works: decide what you'll report on the day the grant starts. Take the outcomes from your proposal, turn each one into an indicator with a source and a date (my logic model guide walks through exactly this), and build the questions into intake and follow-up. Then the report becomes a readout.

That's why I built Storyhouse. It holds the plan, the questions and the records together, asks the same questions the same way every cycle, and links every number in the report to the de-identified rows behind it, so "where did 68% come from?" is a click, not a dig. If you're curious whether a chatbot can do this instead, I gave an honest answer in Can't We Just Write the Grant Report With ChatGPT?

A five-minute checklist before you hit send

• Every goal from the proposal appears, in the same words, with a target and an actual.
• Every percentage says what it's a percentage of.
• Missed targets are named, explained and paired with a fix.
• The participant story matches the numbers and has permission behind it.
• The financial section explains any big variance.
• No participant names or identifying details anywhere they don't belong.
• Someone who didn't write it has read it once, start to finish.

And if outputs and outcomes still blur together in your head, start with Outputs vs. Outcomes. It'll make section three of every report you write easier.