How do you write a donor report funders can use?
A useful donor report explains what you agreed to deliver, what happened during the reporting period, what the evidence supports, and what needs attention next. Include spending against the agreed budget, explain important differences from the plan, and show where readers can check your figures. Follow the funder’s required format first; use the structure below where you have flexibility.
Your next step in the reporting course
Goal: Turn reviewed findings into a useful report brief.
Start with: Bring the audience requirements, checked results and source trails. Do not start by polishing an unsupported success story.
Carry forward: Leave with an outline that covers findings, limits, spending where required, and the next decision. You can draft it yourself or use the next AI-assisted lesson.
This lesson is for program managers, grant leads and reporting teams preparing a progress or renewal report. In the related lesson on evidence traceability, you connected claims to their sources. Here you will turn that evidence into a report plan. The drafting reference covers working with an assistant once your brief is ready.
Your finished exercise: a one-page report brief, a claim-and-evidence table, and a list of questions that must be resolved before release. Bring the grant agreement, reporting instructions, approved results and financial records. Missing evidence belongs in the plan, too.
Start with the decision, without deciding the answer
Begin with what the reader needs to decide, then work backward to the evidence the report must contain. That might be whether delivery is on track, whether an underspend needs a revised plan, or whether another period of support is justified. It should not become an exercise in selecting only the evidence that makes renewal look attractive.
Write the decision as a question: “What should change before the next reporting period?” Then name the information needed to answer it fairly. Include results that challenge your expectations, negative experiences, and gaps in coverage. A credible report can say that a promising result is not yet conclusive.
Keep three documents distinct. A progress report accounts for an agreed period of work. A renewal proposal requests future support. An impact evaluation examines effects using a stated method. One document may draw on all three, but a progress report alone does not establish that the program caused an outcome.
Use a donor report format that answers the reader’s questions
The following is a planning format, not a universal funder requirement. If the funder provides a portal or template, map these questions to its fields rather than sending an alternative format without agreement.
| Section | Question to answer | Evidence to prepare |
|---|---|---|
| Overview | What does the reader need to know or decide? | The most material findings, limitations and requested discussion. |
| Delivery | What was delivered against the plan? | Agreed commitments, activity records and explanations of changes. |
| Outcomes | What changed, for whom and when? | Defined measures, denominators, follow-up coverage and relevant accounts. |
| Finances | How was the support used? | Reviewed budget-to-actual statement and explanations of material differences. |
| Learning and risks | What did not work or remains uncertain? | Shortfalls, negative feedback, missing evidence and response plans. |
| Next actions | What will the team do, and what needs agreement? | Named owners, timing and any separately justified request. |
Do not force every section onto one page. A short overview can point to a financial statement, methods note and source register. Keep essential caveats next to the result they qualify; a footnote many pages away cannot repair a misleading headline.
Build the report brief before writing paragraphs
- Confirm the audience and deadline. Identify who reviews delivery, finances and any renewal request. Record the submission date, word limits and required attachments.
- Fix the scope. Name the grant, sites, cohort and reporting period. Distinguish when an outcome happened from when its evidence arrived.
- Choose the approved evidence release. Record its date and version. If figures differ from the last report, explain the correction or changed definition.
- Assign reviewers. Give program claims, financial figures and privacy checks named owners. Leave time to resolve disagreements.
- Write the decision question. State what the reader needs to understand or authorize. Keep the requested action separate from claims about past results.
A brief might read: “Quarterly progress report for the training grant, covering the agreed cohort’s 90-day follow-up. Use release A and the approved budget statement. The program lead checks outcome definitions; finance checks expenditure; the grant lead signs off the explanation of missing follow-up. Ask the funder to discuss a revised follow-up plan.” This is a fictional exercise, not a report from a Sopact customer.
Worked example: report employment results without overstating them
Use this self-contained fictional cohort: 80 people started the program, 60 have a known employment status 90 days after exit, and 36 of those 60 were employed. Status is unknown for 20 people. This exercise uses release A; do not mix it with the later-evidence example in the consistency chapter.
A defensible sentence is: “At 90-day follow-up, 36 of the 60 participants with a known status were employed (60%). Status was known for 60 of 80 starters (75% coverage); the remaining 20 participants had an unknown status.” If useful, add that confirmed employment represents 45% of all 80 starters.
Do not shorten that to “60% of participants got jobs because of the program.” The denominator has changed, and the sentence adds a causal claim the data does not establish. Employment at one follow-up point also does not establish sustained employment or job retention.
| Proposed claim | Evidence and check | Permitted conclusion |
|---|---|---|
| 80 people started | Deduplicated start records for the agreed cohort. | Reach; not completion or an outcome. |
| 36 of 60 known-status participants were employed | Employment-status records at the agreed 90-day point; verify the denominator. | 60% among known statuses, with 75% coverage. |
| The program caused employment | No comparison or other adequate causal evidence in this exercise. | Do not make this claim. |
| Transport needs attention | 12 of 18 purposively selected interviews mention difficulties. | A theme to investigate; not a population estimate. |
For the exercise, suppose 12 of 18 purposively selected interviewees mentioned transport difficulties. You can report that theme with its sampling limit. You cannot call it the prevalence of transport problems among all 80 starters. Explain why those interviewees were selected and whether other voices are missing.
The report can now connect a finding to a reasonable action: review follow-up coverage and investigate transport barriers before changing delivery. It cannot promise that a transport intervention will improve employment without further evidence.
Bring financial and program evidence together carefully
Use the financial statement approved for the same reporting scope. Show the agreed budget, expenditure, material variances and an explanation of what they mean for delivery. If a funder requires restricted-fund balances, commitments or a particular accounting basis, follow those instructions and have the responsible finance reviewer check them.
An underspend is not automatically efficiency. It might reflect a delayed activity, a vacancy or an invoice not yet recorded. An overspend does not by itself establish poor performance. Explain the reason and whether the plan or permission needs to change.
Cost per participant can be useful only when the cost and participant definitions are clear. State which costs are included and whether the denominator counts starters, completers or people with a measured outcome. Do not compare programs using different periods or cost boundaries as if they were equivalent.
For a partner report, the survey narrative, uploaded financial statement and social audit may describe different periods. Check their dates before combining them. A Q3 update with a Q2 financial attachment should become a clarification request, not a silently completed Q3 report.
Use a human story to explain a finding, with permission
A participant account can make an outcome understandable. Ask whether the person has agreed to this audience and use, whether identifying details are necessary, and whether the story represents a wider pattern or one experience. Keep their words distinct from your interpretation. A compelling story does not substitute for the result’s denominator or demonstrate causality.
Operational examples can be useful, too. In Sopact’s published Open Play Foundation story, Marco Botha describes bringing ten programs into a single funder report, with breakdowns by facility, activity, coach and gender parity. His statement, “I’m digitizing our entire business through Sopact,” describes the wider operational approach.
The practical lesson is to collect the context needed for reporting while the work happens. This customer story illustrates that practice; it is not independent evidence that a particular report secured funding or proved causal impact.
Try it: turn your evidence into a balanced report outline
Use the prompt below with an approved, appropriately redacted evidence pack. Replace the brackets with your actual brief and sources. If the assistant cannot access a source, leave that part unresolved rather than asking it to estimate the missing result.
Help me plan a donor progress report. Audience and decision: [describe]. Reporting period and required format: [paste]. Approved evidence release and source register: [provide]. Create an outline covering delivery, outcomes, spending, limitations, lessons and next actions. For each proposed claim, identify its supporting source, denominator and period where relevant, and anything the evidence does not establish. Include findings that challenge the plan. Do not invent numbers, quotations, financial explanations or causal conclusions. Mark missing evidence and the reviewer needed. Keep any future funding request separate from measured results.
Review the outline before drafting. Can a colleague find every source? Are the stated questions answered, including awkward results? Are people with missing data visible? Does the proposed conclusion fit the evidence rather than the desired funding decision?
Keep the approved report separate from a changing dashboard
A live dashboard can support ongoing learning. A submitted report needs a recognizable version. Save the approved report, evidence release and review date together. If a correction is needed later, issue a clearly labeled revision with the reason; do not silently replace the figures a funder already reviewed.
In a configured Sopact workflow, collection, documents and follow-up can remain connected to the relevant records. Use that context to prepare the evidence pack and inspect findings. Before relying on a workflow for formal reporting, test that your team can retrieve a source, reproduce an important figure, respect access restrictions and preserve the approved release. Those checks matter regardless of which tool you use.
AI can help organize and phrase the report. It does not remove the need to check its calculations, citations or claims. NIST’s Generative AI Profile identifies confabulation as a risk; a fluent draft is not evidence that a statement is correct.
Finish the exercise: is the report ready to draft?
- The audience, period, instructions and decision question are written down.
- Each main result has an approved source, definition and coverage statement.
- Delivery, outcomes and spending are distinguished rather than blended into one success claim.
- Missing results, unexpected findings and changes from the previous report are explained.
- Financial and program reviewers have clear responsibilities.
- The next action follows from the findings, without a promise the evidence cannot support.
If one of these is missing, identify the owner and question to resolve. You can draft the parts that are ready while leaving the uncertain section visibly incomplete.
Watch: why clean data still needs reporting context
Watch the video · 6 minutes 7 seconds. This explanation connects data with framework, audience and presentation context. If you watched it in an earlier chapter, apply it now: check that your report brief names all four. Browse the full video library.
Frequently asked questions
What should a donor report include?
Include the reporting period and scope, progress against commitments, outcomes with their evidence and limitations, spending against the agreed budget, lessons, risks and next actions. Follow the funder’s own reporting instructions where they differ from a general format.
How long should a donor report be?
Use the funder’s required length. Where you have flexibility, provide a short decision-focused overview and enough supporting detail to check the claims. Put detailed calculations and source references in an appendix, but keep important limitations beside the relevant result.
What is the difference between a donor report and an impact report?
A donor report usually accounts to a particular funder for agreed support and a defined period. An impact report may address a wider audience and longer period. Neither label proves causal impact; explain the evidence and method behind any claim about change.
How do you report results when some follow-up data is missing?
State how many people have a known result and how many do not. Label the denominator for every percentage. Do not treat unknown status as success or failure, and do not assume respondents represent everyone without examining the missingness.
Should the report include results that missed the target?
Yes. Explain the target, the observed result, relevant evidence limitations and what the team will do next. Omitting a material shortfall prevents the reader from understanding delivery and making an informed decision.
Can AI write a donor report?
AI can draft an outline or narrative from an approved evidence pack. Review every number, quotation, citation and conclusion. Do not ask it to fill evidence gaps with estimates unless an explicit, appropriate estimation method has been agreed and disclosed.
Should a shared report link update automatically?
A current dashboard can update, but a formally submitted report should identify its approved version and evidence release. Publish corrections as labeled revisions so the reader can distinguish the original report from later information.
Does a strong report guarantee renewed funding?
No. A useful report helps a funder assess progress and uncertainty. Funding decisions also depend on priorities, available resources, eligibility and other considerations beyond the quality of a report.
Build your report from the reviewed brief
Get the ebook: How to Write an Impact Report for a broader writing guide. Explore report examples to compare ways of presenting evidence. Adapt their structure to your reader and required format; do not copy claims or measures that do not fit your work.
Drafting reference: Draft and check a funder report with an assistant. Bring the report brief and evidence table you completed here. For a broader starting point, use the impact report template guide.
Want to work through your reporting process? Bring a reporting requirement and sample evidence to a working session. Start with the collection and review problem your team needs to solve.
Lesson revised September 12, 2026. Numerical examples are fictional course exercises. Customer statements are attributed to the linked published story.