Grant budgets are plans, not prophecies. The conditions under which grants are delivered change — costs shift, timelines extend, activities need to be adjusted, unexpected opportunities emerge. Budget variance management — how funders and grantees handle changes to approved grant budgets — is one of the most practical aspects of grant administration.
Done well, budget variance management enables flexible, responsive delivery while maintaining appropriate accountability. Done poorly, it creates bureaucratic friction that frustrates grantees and wastes programme officer time reviewing trivial variations.
Changed circumstances. Community needs shift, prices change, staff turn over, and external factors affect what's possible. A community health programme planned in one context may need to adapt significantly as conditions change.
Realistic planning uncertainty. Detailed activity budgets are prepared before delivery begins, often months before. Some variance from plan is an inevitable feature of operating in real-world conditions.
Learning and adaptation. Effective programmes adapt as they learn what works. A grantee who discovers mid-delivery that one activity isn't working and needs to redirect resources is demonstrating good programme management, not poor financial control.
Scope changes. Sometimes a funded programme needs to expand its scope (more demand than expected), contract (activity proves more difficult than anticipated), or shift (partnership arrangements change).
Line item reallocation. Moving budget between approved expenditure categories (e.g., from equipment to personnel, or from travel to contracted services) without changing the total grant amount. The most common type of variation.
Underspend carry-forward. Returning to the funder with unspent funds from one period, requesting permission to spend them in a subsequent period. Relevant for multi-year grants.
Budget increases. Requesting additional funds beyond the original grant amount to cover unforeseen costs or expanded scope. Less common and generally requires stronger justification.
Budget reductions and return of funds. When a programme delivers at lower cost than planned, or when planned activities can't proceed, returning unspent funds to the funder.
Define threshold-based approval levels. Not all budget variations should require funder approval. A common approach:
Distinguish between budget categories differently. Some cost categories warrant different treatment. Personnel costs (particularly changes to who is employed or their time commitment) often warrant explicit approval even when the dollar amounts are modest, because they affect delivery capability. Overhead/indirect cost changes may be treated differently from direct programme costs.
Define what "prior approval" means. Some funders require written approval before incurring a varied expense; others are satisfied with notification before year-end reporting. Pre-approval requirements create more friction but provide better oversight for high-risk variations.
Address underspend policy explicitly. How does the funder treat unspent funds? Common approaches:
- All unspent funds are returned at grant end
- Unspent funds up to a threshold can be carried forward to the next grant period with notification
- Grantees can redirect modest underspends to related activities without approval
Over-specified original budgets. Funders who require extremely detailed budget breakdowns (dozens of line items) create their own variance management problems — small, inevitable variations trigger approval requirements that consume everyone's time. Higher-level budgets (5-8 line items) reduce variance frequency without sacrificing accountability.
Approving variations late or slowly. If a grantee submits a variation request and waits weeks for approval, it may create compliance problems (they need to incur the expense now) or programme problems (they can't adapt until approval arrives). Programme officers should handle variation requests promptly.
Treating all variations as problems. Programme officers who respond to every variation request with concern or resistance create incentives for grantees to avoid disclosing variations. Normalising budget variance as a routine operational matter — and distinguishing it clearly from performance concerns — produces better transparency.
No record of approved variations. If budget variations aren't documented in the grants management system, end-of-grant acquittal becomes confusing (what was the approved budget?) and audit trails break.
Track variances proactively. Don't wait until year-end reporting to discover that you've significantly over or underspent a line item. Monthly or quarterly comparison of actual to budget allows early identification and proactive communication.
Communicate early. Funders respond much better to early notification ("we've identified that our travel costs will be lower than planned and would like to redirect to staffing") than to surprises in final reports. Proactive communication demonstrates good financial management.
Document the reason. Budget variation requests should briefly explain why the variation is needed. Funders assessing reasonableness need to understand the context, not just the numbers.
Keep records of approved variations. Grantees should maintain records of all approved budget variations. This matters for internal financial management and for demonstrating compliance in acquittal and audit situations.
Effective grants management software should support budget variance management:
Tahua's grant management tools include configurable budget tracking, variation request workflows, and acquittal reconciliation designed for ANZ grant programme practice.