Making a grant is the beginning, not the end, of a funder's responsibility. Once funds are deployed, funders have an obligation to their mission, their donors, and the communities they serve to ensure that grants are used as intended. Grant compliance monitoring — the systems and processes through which funders track grant use and outcomes — is an essential part of responsible grantmaking.
Done well, compliance monitoring creates accountability without creating burden. Done poorly, it either fails to identify genuine problems or imposes such heavy reporting requirements that grantees spend more time on compliance than on the work the grant is meant to fund.
Compliance monitoring is about ensuring grants are used in accordance with the grant agreement — for the purposes for which they were made, by eligible organisations, within the time and budget parameters agreed. It includes:
Compliance monitoring is NOT:
- Micromanaging how grantees run their programmes
- Second-guessing grantee decisions about programme design
- Creating excessive reporting burdens that drain grantee capacity
- Substituting funder preferences for grantee expertise
The goal is ensuring public trust and grant purpose — not control for its own sake.
Compliance starts with clear grant conditions. Grant conditions specify what the grantee has agreed to do, by when, and subject to what constraints. Well-designed conditions:
Are specific and verifiable: "Deliver 50 family mentoring sessions by December 31" is better than "continue to provide mentoring services." Specific conditions create clear accountability.
Are proportionate to grant size and risk: A $5,000 grant to a trusted long-term partner needs minimal conditions; a $500,000 grant to a new organisation in a high-risk area needs detailed conditions.
Include key milestones: For multi-year grants or complex programmes, milestone conditions — specific deliverables or phases that trigger payment or reporting — create structured accountability without requiring constant oversight.
Are agreed, not imposed: Conditions that grantees have had input into are more likely to be understood, accepted, and met than conditions presented as a take-it-or-leave-it requirement.
Include reporting requirements: The conditions should specify when reports are due, what they should cover, and what happens if they're late.
Progress reports: Qualitative narrative of what's been done, what's working, what challenges have arisen, and what's planned next. Usually mid-grant.
Outcome reports: Assessment of what has changed for the communities or people served as a result of the funded programme. Usually end-of-grant.
Financial reports: Accounting of how grant funds have been spent — what was spent on what, whether the budget is on track, whether unspent funds will be used by the grant end date.
Milestone reports: Reports triggered by specific programme milestones rather than calendar dates — "when X is completed, report on Y."
Acquittal: Final financial report confirming all grant funds have been spent in accordance with the grant conditions. Required for most grants upon completion.
Not all grants need the same level of monitoring. Risk-based monitoring concentrates attention where it's most needed:
High monitoring intensity: Large grants; grants to new or unknown organisations; organisations with previous compliance concerns; grants in high-risk areas; grants to organisations in financial difficulty.
Medium monitoring intensity: Established grantees with good track records receiving medium-sized grants; first-time but vetted organisations.
Low monitoring intensity: Small grants; long-term trusted partners; renewal grants to consistently performing organisations.
A risk register — maintained for active grants — allows monitoring intensity to be calibrated appropriately and reviews triggered when risk factors change.
Late reporting is one of the most common compliance issues. A systematic follow-up process:
The key insight is that persistent late reporting often signals a grantee in difficulty — and early identification of difficulty allows the funder to support the organisation rather than discover a problem when it's too late to address it.
For significant grants or high-risk situations, site visits provide evidence that grants management systems can't. A site visit allows the funder to:
Site visits require investment of funder time and should be proportionate. A $10,000 community grant doesn't justify a formal site visit; a $500,000 multi-year programme might warrant an annual visit.
Grantees who are struggling — financially, operationally, or programmatically — need support, not just compliance pressure. Early warning signs include:
When warning signs appear:
1. Make contact: A conversation (not just a compliance letter) to understand what's happening
2. Assess the situation: Is this a temporary challenge or a systemic problem?
3. Consider support: Can the funder help? Through peer connections, capacity building funding, extended timelines?
4. Document carefully: Whatever happens, document the situation, conversations, and decisions
5. Decide on path forward: Continue with modified conditions, suspend pending resolution, or exit the grant relationship
The relationship-based approach — treating grantees as partners in achieving shared goals — produces better outcomes than a purely transactional compliance approach.
Grant acquittal is the final financial accounting for a completed grant. A standard acquittal requires:
Acquittal requirements should be proportionate. A one-page acquittal is sufficient for a $5,000 grant; a more detailed financial acquittal is appropriate for $100,000+.
Tahua's grants management platform provides end-to-end compliance management — automated reporting reminders, structured report collection, financial acquittal workflows, risk flags, and the audit trail that funders and their auditors need to demonstrate responsible stewardship of grant funds.