How to write donor reports that build trust
How to structure a donor report so it is read: what program officers look at first, how to explain a missed target, and a checklist before you send.
Short answer
A donor report that builds trust tells the reader what changed, what is off track and what you are doing about it. Open with a one-page summary, show results against targets in an indicator table, explain gaps with evidence, link spending to results, and ask for any decision you need. Honest, early reporting builds more trust than a perfect-looking report.
Key points
- Report what changed, not just what you did.
- Put a one-page summary first. It is the part every reader finishes.
- Show each result against its target, and explain every gap with evidence.
- Raise problems early. Hidden problems damage trust more than missed targets.
- End with clear asks and dates for any decision you need from the donor.
What do donors want from a report?
Donors want to know three things: did the money do what was promised, what is going wrong, and what happens next. A report is not a diary of activities. It is a decision tool for the person reading it.
A program officer may manage many grants and have limited time for each report. Weak reports are rarely weak because the data is bad. They are weak because nobody shaped the information for the reader.
What do donors read first?
Most readers look at the report in this order:
- Summary. Key achievements, key challenges, headline results and any change to the plan. If you write one section well, write this one.
- Results table. They look for indicators below target, falling trends or missing data.
- Challenges and response. They want to see that problems were found early and are being managed.
- Financial summary. They check spending against the timeline. Underspending can worry a donor as much as overspending.
They often skip activity descriptions that repeat the work plan and success stories with no data behind them. Write for the reader who has twenty minutes and several reports to read.
What structure works?
Check the donor's template first and follow it. If you have freedom, this structure works for most projects:
| Section | What to write |
|---|---|
| Summary | Reporting period, headline results, main challenges, changes, any request |
| Progress against results | One short narrative per outcome or output, tied to indicators |
| Results table | Baseline, target, actual and a short explanation for each gap |
| Challenges and adaptation | Problem, cause, action taken, support needed |
| Finance | Budget against spending, and reasons for large variances |
| Next period | Priorities, risks and dates |
| Annexes | Photos, stories, tools, tables |
Give the period the report covers and confirm that you are following the terms of the agreement. Make sure an authorised person signs or submits the report.
How do you write the narrative?
Write by result, not by activity. The reader wants to know whether an outcome is on track, not how many meetings you held. Compare these two:
- Weak: "The team held 48 training sessions in five townships."
- Stronger: "Forty-eight sessions took place. Completion of the training is behind the annual target because road access limited travel for three months. A revised schedule will reach the remaining participants by the end of the next quarter."
Lead with the finding, then give the cause and the response. Use plain words and short sentences. Spell out acronyms on first use. If a paragraph says only that you did what you planned, shorten it to one line. For help with structure, see our guide on writing a clear project report and on executive summaries.
How do you explain a gap or a change?
Use the same four steps each time:
- State the finding. Say what is behind target and by how much.
- Give the cause with evidence. Separate what you know from what you think. Cite the monitoring data, the date and who reported it.
- Describe your response. Say what you have done and what you will do.
- Say what you need. If you need an extension, a budget change or approval, ask clearly and give a date.
Do not wait for the report to share major changes. Talk to the donor first, then record the discussion in the report. Check your agreement for the rules on prior approval. Our guide on reporting rhythm helps you plan regular updates so that no report holds a surprise.
How do you build trust over time?
Trust comes from habits, not from one good report.
- Report on time. If you will be late, tell the donor before the due date.
- Be consistent. Use the same indicator names, definitions and formats from one report to the next.
- Be specific. Give dates, places and numbers where they are safe to share.
- Protect people. In insecure settings, leave out names, exact locations and details that could put communities or staff at risk.
- Say what you learned. One honest lesson is worth more than a page of praise.
- Thank the donor and share credit. A short, sincere note of thanks is part of good practice.
What should you check before you send?
Run through this list:
- Does the summary stand alone on one page?
- Does every result show a target, an actual and a reason for any gap?
- Do the numbers in the narrative match the table and the finance report?
- Are problems named, with cause and action?
- Is any decision you need stated, with a date?
- Did a colleague who did not write it read it?
How EMPO can help
EMPO is a reliable training and consultancy provider in Yangon and one of Myanmar's leading names in practical NGO training, with 1,200+ people trained and 15 partner organisations. We run report writing training for NGO teams, online or in person, in English and Burmese, and we can design a session around your donor's template. See our services or contact us.
Sources
- Narrative Report Guidance and Template — The Rockefeller Foundation, 2024
- How to Write Donor Reports That Actually Get Read — M&E Studio, 2026
Questions people ask
How long should a donor report be?
Follow the donor's template and page limit. Within that, keep the narrative short and put detail in tables and annexes. A program officer reading many reports will value a clear summary over length.
Should we report bad news?
Yes, early and plainly. Name the problem, the cause, the action you have taken and any support you need. Donors expect problems in difficult contexts. They do not expect surprises.
How do we report when staff cannot reach project sites?
State what you could not do, why, and how you checked results by other means, such as remote calls or community focal points. Say what is verified and what is not, and tell the donor before the report is due.