A budget variance is the difference between what a grant budget expected and what the project actually spends. Variances are normal. The compliance risk begins when organizations move money between lines, exceed thresholds or change activities without checking whether donor approval is required.
Monitor variance before it becomes a problem
Compare actual expenditure against budget regularly rather than waiting for the final report. A monthly variance review gives the team time to adjust implementation, forecast costs and seek approval where necessary.
Questions for every significant variance
- Why is this line over or under budget?
- Is the underlying activity still happening?
- Can funds legally be moved between categories?
- Does the donor set a percentage or amount threshold?
- Does the change affect outputs, staffing or timelines?
- Is written approval required before reallocation?
Document the reason, not just the number
A useful variance note explains the cause, impact and proposed response. For example: “Travel costs are 22% below budget because two monitoring visits were combined. The savings are proposed for additional community sessions, subject to donor approval.”
Keep forecasts current
Budget control is forward-looking. Update the forecast for the remainder of the award so management can see whether today’s underspend will become tomorrow’s rush to spend.
The Grant Budget Sanity Checker can help test whether the revised structure remains credible and internally consistent.
Approval rule
When the grant agreement sets a reallocation threshold, treat it as a control point. Seek approval before crossing it, not after the money has already been spent.
Want more practical grant-management guidance? Subscribe to Africads Grant News.
Frequently Asked Questions
What is a grant budget variance?
It is the difference between approved budget amounts and actual or forecast spending.
When does a variance require donor approval?
That depends on the award terms, including any line-item or percentage thresholds and prior-approval rules.
Should small variances be ignored?
No. Even when approval is not required, persistent variances can signal implementation delays, cost pressures or weak forecasting.
How should variances be explained?
Document the cause, financial impact, effect on delivery and any corrective action or donor communication needed.
Who should review budget variance?
Finance and program teams should review it together because the financial variance often reflects an operational change.
Conclusion
Budget variance should be monitored as an early-warning signal, not only as a reporting requirement. NGOs should know the donor’s approval thresholds, explain material differences and connect variance analysis to forecast and delivery decisions.
Put this guide into practice
Free resource: The Hidden Formula Funders Love. Use this free guide to apply the article’s advice to your next funding decision or application.
Optional paid resource: Nonprofit Grant Proposal Templates. Proposal, concept note, budget, logframe, M&E and donor-document starting points. Review the product details and current price before purchasing.