Grant reporting templates shape what information funders receive from grantees — and by extension, what they can learn, what accountability they can demonstrate, and how much burden they impose on the organisations they fund. Well-designed templates collect what matters without requiring unnecessary effort; poorly designed ones generate compliance data while missing genuine insight.
Before designing a template, be clear about what you're trying to achieve:
Accountability. Confirming that the grant was used for the stated purpose. Financial accountability verifies the money was spent appropriately; programme accountability confirms the activities were delivered.
Learning. Understanding what worked, what didn't, and why — both for the funder's portfolio learning and to help grantees reflect on their practice.
Relationship. Progress reporting is a touchpoint in the funder-grantee relationship. A report that asks genuine questions signals that the funder cares about what the grantee is learning, not just whether boxes are ticked.
Stewardship. For funders accountable to stakeholders (boards, regulators, donors), reporting provides evidence that funds were used effectively.
What happened during the reporting period?
Design tip: Ask for narrative about what happened, not just a tick-box checklist against the original application. Narrative reveals more about what's actually happening.
What changed because of the funded work?
Design tip: Ask a direct question: "What is the evidence that your work is making a difference?" This invites honest reflection rather than promotional reporting.
What hasn't gone to plan?
Design tip: Make it psychologically safe to report challenges. Language like "challenges are a normal part of programme delivery — please share honestly what you've encountered" signals that honest reporting is welcome.
What is the organisation learning?
Design tip: This section often yields the most valuable content. Funders who read it with genuine curiosity — and act on what they learn — get enormous value.
What is the plan for the next reporting period?
Financial acquittal confirms that grant funds were spent for the approved purposes.
Standard acquittal components:
| Budget line | Approved budget | Actual expenditure | Variance | Notes |
|---|---|---|---|---|
| [Line item] | $X | $X | $X | Explanation if significant |
| Total | $X | $X | $X |
Required attestation: "I confirm that the above expenditure is accurate and that all funds were spent for the approved purposes of the grant."
Supporting documentation: For larger grants, requiring receipts or invoices for expenditure above a threshold (e.g., $500) provides additional assurance.
Proportionality. Templates should match grant size and risk. A $500 community grant doesn't need the same reporting as a $100,000 multi-year investment. Many funders use tiered reporting requirements: simple narrative for small grants, fuller reporting for larger ones.
One question per question. Avoid compound questions ("Please describe the outcomes achieved and any challenges encountered and what you learned") — these are harder to answer and harder to analyse.
Open questions for learning, closed for accountability. Open narrative questions generate learning; specific yes/no and numeric questions generate accountability data. Use both, in the right places.
Test with grantees. Before finalising a reporting template, ask a sample of grantees to complete it and give feedback. This reveals unclear questions, missing guidance, and unreasonable burdens.
Review and act. Reports that are filed and never read don't justify the burden they impose. If programme staff are too stretched to read reports, that's a signal to reduce reporting requirements — not to keep collecting data nobody uses.
Tahua supports configurable reporting templates — matching requirements to grant size, programme type, and outcome framework — with grantee-facing report submission portals that make reporting straightforward.