Grant reporting is how grantees demonstrate accountability to funders and communicate the impact of funded work. A well-written grant report builds the funder relationship, improves the chance of future funding, and contributes to the sector's collective knowledge. This guide covers how to write effective grant reports — from progress reports to final acquittals.
For grantees: Reports are the primary communication channel with funders between grants. They are an opportunity to demonstrate competence, build trust, and set the scene for future funding requests.
For funders: Reports are the evidence that funded activities were delivered and that outcomes were achieved. They inform future funding strategy and portfolio decisions.
For the sector: Published findings from well-reported grants contribute to shared learning about what works.
A poor report — late, superficial, or evasive — damages the funder relationship. A strong report — timely, honest, specific, and outcomes-focused — strengthens it.
Progress report (interim report)
For multi-year or longer grants, progress reports are typically required at 6-12 month intervals. They cover:
- Progress against the work plan (activities completed vs planned)
- Early outcomes and evidence (what's changing as a result of the work?)
- Financial update (expenditure to date vs budget)
- Risks or changes to the programme
- Any variations needed
Final report
Submitted at grant close. It covers:
- Summary of all activities completed
- Outcomes achieved (with evidence)
- Financial acquittal (full expenditure against budget)
- Learnings and reflections
- Next steps or sustainability plans
Financial acquittal
Often part of the final report or a standalone document. Detailed financial statement showing expenditure against the approved grant budget. See the grant acquittal guide for detail.
Outcomes, not just outputs
The biggest weakness in most grant reports is describing what was done (activities, outputs) without explaining what changed (outcomes).
Funders want to know what changed as a result of the funded work — not just what happened.
Honesty about challenges
Many organisations write reports as if everything went perfectly. Funders know this is rarely true — and they find sanitised reports less credible than honest ones.
Strong reports acknowledge:
- What didn't go as planned
- What was harder than expected
- What the organisation learned from challenges
- What would be done differently
This honesty builds trust and positions the organisation as a reflective, credible partner.
Evidence
Claims about outcomes should be supported by evidence:
- Survey or evaluation data
- Case studies and participant stories
- Statistical data (service users, geographic reach)
- Testimonials and quotes
- Third-party validation (evaluation reports, media)
Financial accuracy
Financial sections should be accurate, clearly presented, and explain any significant variances from the approved budget.
A typical progress report structure:
1. Executive summary (1 paragraph)
What happened in the reporting period? Key achievements, any significant issues.
2. Activity update
Progress against the work plan — what was delivered, what wasn't and why.
3. Outcomes to date
Early evidence of change — what are participants, communities, or systems experiencing differently?
4. Financial update
Expenditure to date against budget. Note any significant variances.
5. Risks and changes
Any changes to scope, staff, timeline, or context. Any risks to programme delivery.
6. Upcoming activities
What will happen in the next reporting period?
A typical final report structure:
1. Executive summary (1-2 paragraphs)
What was funded, what was achieved, key outcomes.
2. Programme summary
Overview of all activities and outputs delivered over the grant period.
3. Outcomes achieved
Detailed outcomes — what changed, for whom, with evidence.
4. Learnings and reflections
What worked well, what was difficult, what the organisation would do differently.
5. Financial acquittal
Full statement of expenditure against budget, with supporting documentation.
6. Sustainability and next steps
How the work will continue beyond the grant period (if applicable).
Reporting on activities instead of outcomes: Describes what was done, not what changed.
Vague language: "Many participants benefited" instead of "47 of 60 participants reported X outcome."
Avoiding difficult topics: Not acknowledging delays, challenges, or variances.
Not matching the funder's questions: Answer the specific questions in the reporting template, not a generic format.
Late submission without warning: Contact the funder in advance if you need an extension — don't just go quiet.
Inaccurate financial reporting: Budget categories don't match the approved budget, variances unexplained.
The best grant reports are readable as well as accurate. Concrete stories and participant quotes bring outcomes to life in ways that statistics alone cannot:
"Before joining the programme, Maria had never spoken at a public meeting. After six months, she presented to the local council on behalf of her community — and the council changed its decision as a result."
One story like this, grounded in the outcomes you're reporting, is more persuasive than five pages of output tables.
For organisations managing multiple grants, a reporting calendar is essential:
- Record all reporting deadlines at grant commencement
- Build data collection into programme delivery (not just at report time)
- Assign responsibility for each report
- Build in review time before submission
Tahua's grants management platform helps funders manage grantee reporting — automated reminders, configurable reporting forms, and a consolidated view of all reporting activity across the portfolio.