Grant reporting is the accountability mechanism that closes the loop between funder investment and community impact. Done well, reporting serves both parties: funders get evidence that grants are working, grantees get structured opportunity to reflect on their programmes. Done poorly — with onerous, irrelevant requirements — reporting creates burden without generating useful information.
This piece covers how funders design effective reporting requirements, what good templates look like, and the principles that make grant reporting genuinely useful.
Reporting serves several distinct purposes, and clarity about which purposes matter most shapes how requirements should be designed:
Accountability: verifying that funds were spent as intended and that the programme was delivered as promised. This is the minimum requirement for charitable stewardship.
Learning: understanding what worked, what didn't, and why — for the grantee's own programme improvement and for the funder's portfolio learning.
Relationship: reporting as a touchpoint in the funder-grantee relationship — an opportunity to surface challenges, share progress, and deepen mutual understanding.
Portfolio management: enabling the funder to manage its overall grants portfolio — tracking progress across multiple grants, identifying patterns, making reallocation decisions.
Good reporting design is explicit about which purposes the requirements are meant to serve.
Progress reports (also called interim reports or milestone reports)
Submitted during a multi-year grant, typically at 6-12 month intervals:
- Programme update: what activities have occurred, what milestones have been reached
- Financial update: expenditure to date against budget
- Emerging issues: any significant changes to plan, unforeseen challenges, or programme adjustments
- Looking ahead: plans for the next period
Final reports (acquittals)
Submitted at the close of a grant period:
- Programme outcomes: what was achieved against stated objectives
- Beneficiary data: numbers served, demographics, outcomes achieved
- Financial acquittal: full account of expenditure, explanation of any variances
- Learnings: what worked, what didn't, what would be done differently
- Future sustainability: how the work continues beyond the grant period
Narrative reports
Qualitative reporting — stories, case studies, community voice — that complements quantitative outcome data:
- One or two stories that illustrate impact
- Quotes from beneficiaries (with permission)
- Community context that data alone doesn't capture
Match complexity to grant size
A $2,000 grant should not require the same reporting as a $200,000 grant. A rough guide:
- Under $10,000: one-page acquittal — activities summary, outcome statement, financial account
- $10,000–$100,000: structured 3-5 page report — activities, outcomes, financials, learnings
- Over $100,000: full report — detailed outcomes, evaluation data, financial statements, external evaluation where appropriate
Ask about outcomes, not just outputs
Outputs are what you do (ran 12 workshops, served 150 people). Outcomes are what changed (60% of participants reported improved financial skills). Ask for both, but prioritise outcomes — they're what funders are investing in.
Make financial reporting proportionate
Financial reporting should be sufficient for accountability without being burdensome:
- Small grants: simple expenditure summary (budget vs actual, brief explanation of variances)
- Medium grants: detailed budget vs actual by line item, certification that funds were used for grant purpose
- Large grants: audited financial statements or independent accountant review
Build in narrative
Numbers alone don't tell the story. Space for narrative — a brief qualitative account of what happened and what it meant — makes reports richer and more useful.
Avoid duplication
Don't ask grantees to report information you already have (organisation details, grant amount) or that they've already provided in a previous report. Each reporting requirement should generate new information.
A well-designed progress report for a mid-size grant might look like:
Section 1: Programme update (1-2 pages)
- Activities delivered during the period (brief description of what happened)
- Milestones achieved against the grant plan
- Significant changes or adaptations to the programme (with explanation)
Section 2: Outcomes (1 page)
- Outcomes achieved against stated measures
- Data table: metric → target → actual
- Brief narrative on what the data shows
Section 3: Stories from the community (half page)
- One story or case study illustrating impact
- Direct quote from a participant or community member (with permission)
Section 4: Financial report (1 page)
- Budget vs actual expenditure
- Remaining balance
- Brief explanation of any significant variances
Section 5: Looking ahead (half page)
- Plans for next period
- Any emerging challenges or opportunities
- Anticipated changes to programme
Section 6: Declaration
- Certification by authorised person that report is accurate
Asking for the same information twice: if an outcome is measured in the progress report, don't ask for it again in the final report without a clear reason.
Requiring proprietary data beyond what's needed: grantees sometimes guard data about beneficiaries for good reasons (privacy, sensitivity). Requiring unnecessary data creates friction.
Opaque assessment criteria: grantees should know how their report will be assessed. What constitutes a satisfactory report? What happens if outcomes aren't achieved?
No feedback loop: if funders don't use reporting information — don't respond to reports, don't follow up on challenges raised — grantees quickly learn that reports are filed and forgotten.
Annual reporting for quarterly activities: mismatch between reporting frequency and programme rhythm means reports are either too fresh or too stale.
Some funders are simplifying reporting in line with trust-based philanthropy principles:
Streamlined reporting: shorter templates focused on a few key questions rather than exhaustive structured data.
Conversational reporting: replacing formal written reports with structured conversations — a phone call or meeting that covers the same ground more efficiently.
Grantee-led formats: allowing grantees to report in formats that suit them (video, narrative, presentation) rather than a prescribed template.
Reduced frequency: for trusted, established grantees, reducing reporting frequency — annual rather than 6-monthly for multi-year grants.
Eliminating duplicate reporting: for grantees reporting to multiple funders, accepting reports prepared for another funder rather than requiring separate documentation.
These approaches maintain accountability while reducing grantee burden — recognising that reporting time is programme time diverted.
Tahua's grants management platform includes configurable grant reporting workflows — with customisable report templates, automated reminders, financial acquittal tracking, and the portfolio tools that help funders manage reporting requirements across a complex grants programme.