Variance notes often describe the number without explaining the cause, impact or action. A good financial management process turns the approved budget into a living decision tool rather than a spreadsheet reviewed only when a donor report is due.
Start with the financial decision
Begin by write variance explanations that connect cause, impact and response. Define what management needs to know and what threshold should trigger action. The purpose is to understand future financial exposure, not merely to explain past expenditure.
Review the important drivers
Focus on budget line, amount, percentage, root cause, delivery impact, forecast and corrective action. Use current information and distinguish actual expenditure from commitments and estimates. Where a cost assumption changes, record both the cause and the effect on delivery.
Connect finance and program information
Financial variances often reflect implementation changes. Review delayed activities, recruitment, procurement and partner progress alongside the numbers so the forecast tells one coherent story.
Use a controlled record
Keep approved budgets, current forecasts, commitments, donor approvals and material explanations traceable. The current version should be clearly identified so staff do not make decisions from an outdated spreadsheet.
Useful fields
- Budget or cash-flow item.
- Approved amount.
- Actual amount.
- Committed amount.
- Forecast amount.
- Variance.
- Cause.
- Owner and action.
Example
Travel is 30% below plan because field activities started late. The note explains the delay, confirms no target change yet and shows the revised forecast for the next quarter. The value comes from seeing the issue while management still has options rather than explaining it after the reporting period has closed.
Common mistakes
Avoid treating unspent cash as available budget, moving costs simply to improve a variance, ignoring signed commitments or waiting until donor reporting to reconcile the forecast. Review material changes with both finance and program staff.
Executive decision table
| Area | Leadership question | Evidence to review | Action if weak |
|---|---|---|---|
| Cost assumption | Can your finance team trace the figure to a current source? | Quotation, payroll, prior actual or approved rate | Revalidate the amount before approval |
| Cash flow | Can your organization carry the timing gap if donor funds are late? | Cash-flow forecast and payment terms | Change timing, reserve or payment structure |
| Approval | Does the donor require prior approval for this change? | Grant agreement and donor guidance | Escalate before committing the cost |
| Forecast | What would make leadership intervene? | Actuals, commitments and forecast | Set a materiality threshold and response |
Detailed example
Illustrative example: Consider a mid-sized NGO managing a 12-month institutional grant worth about US$250,000. Halfway through implementation, its finance team notices that the original assumptions behind grant variance explanation template: how ngos can write clear budget notes no longer match current delivery: one major procurement is delayed, two staff positions started late, and a partner tranche is still unliquidated. Rather than treating each item separately, the executive director asks finance and program leads to quantify the combined effect on cash flow, deliverables and donor approvals. The team then records the decision, updates the forecast and only makes changes that remain consistent with the grant agreement.
Leadership checklist
- Reconcile actuals, commitments and forecast before leadership review.
- Check donor approval thresholds before moving or committing funds.
- Confirm the cash-flow effect, not only the accounting effect.
- Keep the current approved budget and supporting evidence clearly identified.
- Record the management decision and what would trigger a further review.
Free nonprofit budget template
Download the Africads Nonprofit Budget Template (DOCX) to document assumptions, cost lines, funding sources, budget notes, and numerical checks. Adapt it to the grant agreement and your organization’s controls.
What to do next
Use the Grant Budget Sanity Checker to structure the next financial review and keep the resulting record with the grant file.
For practical grant opportunities and funding intelligence, subscribe to Africads Grant News.
Frequently asked questions
What should a good variance explanation include?
Explain the amount or percentage variance, the underlying cause, the effect on delivery, whether it is temporary or permanent, and what action is being taken.
What makes a variance note weak?
Phrases such as ‘timing difference’ or ‘activity delayed’ without explaining the cause, scale, or response are usually too vague.
Should favorable variances be explained too?
Yes, especially when they are material. Large underspend can indicate delay, overbudgeting, or a change in scope.
Who should write the explanation?
Finance should verify the numbers while program staff explain the operational cause and implications.
When should donor approval be mentioned?
Where the variance leads to a budget change or reallocation requiring donor consent, the note should state the approval status clearly.
Conclusion
A good variance explanation turns a number into a management story. Your organization should explain the cause, consequence, and response clearly enough that leadership and donors can understand what changed and what happens next.