Grant reporting is the mechanism by which funded organisations account to their funders for how money was used and what was achieved. Done well, it builds trust, generates learning, and strengthens the relationship. Done poorly — or approached as a compliance exercise — it produces documents that no one reads, wastes time on both sides, and leaves funders without the information they actually need.
Before writing a report, understand what the funder is actually trying to learn:
Financial accountability: How was the grant money spent? Did spending match the approved budget? Were there variations, and were these appropriate?
Programme progress: Did the funded activities happen as planned? What changed, and why?
Outcome evidence: What difference did the funded work make? Is there evidence that the intended outcomes are being achieved?
Learning and adaptation: What has the organisation learned from this work? How has this learning influenced the approach?
Relationship context: What is the current state of the programme and organisation? Are there issues the funder should know about?
Funders who receive reports that genuinely answer these questions can make better funding decisions, communicate more confidently with their boards and stakeholders, and be more useful to their grantees.
Actual vs. budget comparison
The core financial report is a comparison of actual expenditure against the approved budget. Present this clearly: budget line by line, actual spending, variance, explanation. Funders want to understand where money was spent differently from plan, and why.
Explanation of variances
Variance explanation is more important than the variance itself. Budget shifts happen for good reasons — delayed hiring, lower-than-expected costs for some activities, reallocation to meet unexpected needs. Clear explanation of what changed and why the reallocation served the programme purpose reassures funders that the variation was appropriate.
Receipts and documentation
Requirements for receipts and financial documentation vary widely between funders. Follow the funder's specific requirements. If unsure, keep records of all grant-related expenditure — you may be asked to provide them.
Unspent funds
If the grant period ended with unspent funds, address this directly. What happened? Why weren't funds fully spent? What will happen to the unspent balance? Many funders require unspent funds to be returned; some allow carryover; a few allow redirection to related purposes. Know the funder's policy and address it clearly in the report.
What happened
The programme narrative explains what funded activities actually occurred during the report period. Be specific and concrete: how many sessions ran, how many people attended, what outputs were produced. Avoid vague language ("we continued to deliver services") in favour of specific description.
What didn't happen, and why
The most common problem with grant reports is omission of things that didn't go to plan. Reporting only success — and silently omitting delays, challenges, changes to approach — produces a misleadingly positive picture and erodes trust when funders discover the full picture.
Reporting challenges honestly is a sign of strength, not weakness. Funders who work with grantees that are transparent about difficulties can offer support, extend timelines, or adjust expectations. Funders who only learn about problems at grant close — or after grant close — feel deceived.
Changes to the plan
If activities changed significantly from what was proposed — different target population, different delivery approach, different timeline — explain this clearly. What changed? Why did it change? How did the change affect the programme's ability to achieve the intended outcomes?
Outcome reporting is where grantees most commonly struggle — and where funders most commonly receive information that is less useful than it could be.
Distinguish outputs from outcomes
Outputs are activities and products: sessions delivered, people reached, publications produced. Outcomes are changes: people's knowledge, skills, behaviours, circumstances, or wellbeing improved as a result. Funders want both, but outcomes are what they ultimately care about.
Use the evidence you have
Many organisations don't have rigorous outcome data — surveys, assessments, administrative records — and feel unable to report on outcomes as a result. But evidence of outcomes doesn't require a randomised trial. Participant feedback, case studies, staff observations, administrative data, and stakeholder testimony are all forms of evidence. Use what you have, and be clear about its limitations.
Be honest about what you know and don't know
Overclaiming outcomes — attributing change to the programme without adequate evidence — is a common problem. Being honest about the limits of your evidence — "participants reported improved confidence, though we can't isolate the programme's contribution to this" — is more credible than unsupported attribution.
Tell stories alongside numbers
Quantitative outcome data is important, but case studies and stories illustrate what numbers can't capture. A brief case study of an individual whose situation changed as a result of the programme makes the impact real in a way that aggregate numbers don't.
The best grant reports include a genuine learning section — what the programme learned about what works and what doesn't, and how this is influencing future practice.
Learning doesn't require perfection. The most valuable learning often comes from things that didn't work: a programme approach that needed to change, a partnership that failed, a target population that was harder to reach than anticipated.
Funders who receive genuine learning — rather than retrospective justification of everything that happened — can support learning across their portfolio and contribute their own insights from comparable programmes.
Start early, not at deadline
Grant reports written at the last minute reflect it. Keeping running notes throughout the grant period — about what happened, what changed, what was learned — makes the final report much easier to write and more accurate.
Write for the reader
Programme officers are reading multiple reports. Clear structure, plain language, appropriate length (following the funder's guidance), and specific rather than vague description make reports easier to read and use.
Ask if you're unsure
If you're unsure what a funder wants, ask. Programme officers generally prefer a question early in the process to a report that misses the mark.
Tahua's grants management platform supports grantees with structured report submission — and gives funders the workflow, communication, and analysis tools to get genuine value from grant reports while minimising administrative burden on the organisations they fund.