A one-year grant is a relatively bounded administrative event. An application is received, assessed, decided, offered, accepted, and acquitted within twelve months. The record is mostly self-contained.
A multi-year grant is a different kind of commitment. A three-year programme grant runs through multiple budget cycles, often outlasts the staff who approved it, may encounter changes in the funded organisation's leadership or direction, and generates ongoing accountability obligations that need to be actively managed rather than filed and retrieved when needed.
Most grants management challenges at the post-award stage originate in multi-year programmes — not because the grants are inherently difficult but because the systems used to manage them are designed for single-year programmes.
The fundamental problem with tracking multi-year grants in spreadsheets is that spreadsheets are static documents. They represent the state of information at the time they were last updated. A grant file created in 2023 with a five-year milestone schedule does not generate reminders, does not surface overdue items, and does not integrate with the payment process.
The operational consequence: programme staff rely on personal knowledge and manual diarising to remember when things are due. This works when the same person manages the same grants for years. It fails — sometimes catastrophically — at the moment of staff turnover. An organisation receiving a second tranche payment in year three of a grant, despite not having submitted their year-two progress report, is a failure mode that is common in programmes where condition tracking lives in an individual's memory rather than a system.
The secondary problem is version control. A grant offered in year one may be varied in year two — different milestones, extended timeline, adjusted budget. If the original offer letter is filed and the variation is managed through email correspondence, the live terms of the grant are assembled from multiple documents in a way that creates real risk of the programme manager operating on outdated information.
A well-designed milestone schedule is the core management tool for a multi-year grant. It converts the programme objectives into a sequence of specific, testable deliverables, assigns timing to each, and links payment releases to milestone achievement.
What makes a milestone schedule work:
- Specificity. "Progress on programme goals" is not a milestone. "Delivery of first cohort training module to minimum 25 participants, with attendance records submitted to funder" is a milestone. The test is whether you can determine from the submitted evidence whether the milestone has been met or not.
- Proportional payment linkage. Not all milestones are equal. A milestone that represents completion of a major programme phase should release a larger payment than a milestone that represents submission of a progress report. The payment schedule should reflect the actual distribution of programme effort.
- Realistic timing. Milestones set to accommodate the funder's budget cycle rather than the programme's actual workflow create predictable problems — either the grantee rushes to hit an artificial deadline, or they miss it and create an administrative issue.
- Clarity about what counts as evidence. For each milestone, the offer letter should specify exactly what evidence the grantee needs to provide. Ambiguity about what counts as satisfactory evidence leads to disputes at the milestone review stage that could have been avoided by clear specification at the outset.
Grants do not always proceed as planned. Over three or five years, changes are almost inevitable: staff turnover at the funded organisation, changes in programme scope, delays caused by external factors (a global pandemic being the obvious recent example), budget adjustments, or changes in the funder's strategic direction.
Managing these variations is one of the most operationally intensive aspects of multi-year grant management:
Formal variation processes. For material changes to a grant's terms — extended timeline, changed budget, modified deliverables — a formal variation process is required. The variation needs to be requested, assessed, approved (often at the same delegation level as the original grant), and documented. Both parties need a copy of the varied terms.
Maintaining the live terms. After a variation, the operative document is the original offer letter as amended by the variation. But if the variation is filed separately and the offer letter is not updated to reflect it, the "live" terms of the grant exist only in two documents that need to be read together. In a portfolio of 50 active grants, some of which have been varied multiple times, maintaining a clear view of current terms across all grants is a significant administrative challenge.
Decision trails for variations. When an audit or OIA request later asks why a grant was extended by twelve months, the decision trail needs to be recoverable. Who requested the variation, who approved it, and on what basis. This documentation standard applies to variations as much as it applies to original decisions.
For funders managing 20, 50, or 100 active multi-year grants, the individual grant level is not the only management level that matters. Programme managers and governance need to see the portfolio in aggregate.
Questions the portfolio view needs to answer:
- How much uncommitted funding is available for new grants in the current period?
- Which grants have outstanding milestone reports that are overdue?
- Which payment tranches are due in the next 90 days, and against which conditions?
- How is the portfolio distributed across the fund's strategic priorities?
- Which funded organisations have not submitted any reports this year?
These questions cannot be answered from individual grant files. They require aggregation across the portfolio — and that aggregation only works if the underlying grant records are structured consistently enough to be queried.
A funder that cannot answer the first question — available funding for new grants — is at risk of over-committing in new rounds or under-investing because the committed balance is unknown. This is a risk that materialises frequently in programmes where multi-year grant commitments are tracked in spreadsheets that the finance team does not have access to.
A board or committee overseeing a grants programme needs regular reporting on the health of the portfolio. This typically means:
- Status of active grants: on track, at risk, overdue
- Exception reporting: grants where conditions have not been met or milestones have been missed
- Financial summary: total committed, total disbursed, total outstanding
- Programme completion forecast: grants expected to close in the current and next reporting period
Producing this reporting from a spreadsheet-based system requires someone to manually compile and verify the data before each board meeting. The accuracy of the report depends on the spreadsheet having been updated consistently, which is not always the case.
A purpose-built system should be able to generate this governance report from live data — with the status of each grant reflecting the current record rather than a snapshot from the last manual update.
For funders managing multi-year grant portfolios, the how it works page covers how Tahua handles milestone tracking, payment conditions, and portfolio reporting. For charitable trusts and foundations managing endowment-funded multi-year programmes, the community foundations page is more relevant. To discuss your specific situation, book a conversation.