TLDR
A spend-down report is not an accounting report — it is a management tool. It answers the question that program staff, finance directors, and funders all need answered at any point in the grant period: are we on track to spend the grant correctly? The 'correctly' is important. Spending fast is not the goal. Spending on what the grant approved, in the right categories, within the right time period, with documentation — that is the goal.
The spend-down report is one of the most practical documents in grant management — and the one most frequently built too late. Finance teams often produce it at quarter-end as a review document. The value is in producing it monthly as a forward-looking management tool.
The question the report answers is not “what did we spend?” That is what the budget vs. actual report answers. The spend-down report answers “are we going to spend this grant correctly before it expires?” Those are different questions that require different data.
What a Spend-Down Report Shows
A well-built spend-down report has five columns per budget line: approved budget, cumulative actual to date, remaining balance, percentage spent, and projected balance at award end given the current burn rate.
The percentage spent column is the most immediately readable. At month three of a twelve-month grant, you expect roughly 25% spent on each line — not exactly, because grant spending is rarely linear, but in the neighborhood. A line at 8% spent at month three needs investigation. A line at 42% spent at month three needs investigation for different reasons.
The projected balance at award end is the most forward-looking and the most useful for early intervention. If the current burn rate projects a $15,000 remaining balance on a $100,000 grant, and the award end is six months away, you have six months to either increase spending on allowable activities or request a modification. If the award end is one month away, you have a problem.
The Common Mistakes
The most common mistake in spend-down monitoring is treating the report as a year-end document rather than a monthly one. Organizations that build the spend-down report in month eleven of a twelve-month grant find out too late that they have significant underspending. At that point, the options are limited: a last-minute no-cost extension request (which funders view skeptically if there is no substantive program reason), a rushed spending push that can create allowability problems, or returning unspent funds.
The second common mistake is looking at the total grant balance rather than the line-item breakdown. A grant can be 85% spent on time while simultaneously having one budget line at 140% of its approved amount and another line at 30%. The total looks fine. The compliance situation is not fine. The line-item analysis is what matters.
The third mistake is treating the spend-down report as a finance department document. Program staff are responsible for the activities that generate the expenditures. When spend-down is low on a personnel line, it is because a position has been vacant or a staff member has been working on activities outside the grant scope. Finance can see the number; program staff know the reason. The monthly spend-down review should involve both.
Building the Report in Practice
For organizations using an accounting system with proper fund coding, pulling actuals by budget line should be a standard report. The budget column is a manual entry based on the approved grant agreement. The formulas for remaining balance, percentage spent, and projected burn rate are straightforward.
For organizations using QuickBooks with Class tracking, building the spend-down report requires more effort: the Class report gives you spending by category, but translating that into a grant-budget-line format with forward projection requires manual assembly. This is one of the reasons dedicated grant compliance software reduces finance workload — the spend-down report is an automatic output of the grant record, not a manual construction.
The report is valuable at whatever level of automation you can achieve. A well-maintained spreadsheet updated monthly from exported accounting data is better than nothing. A system that produces it automatically from real-time data is better than a spreadsheet. The discipline matters more than the tool.
Free resource
Get the Grant Spend-Down Tracker
A budget burn monitoring template for active grants: grant name, budget by category, actuals by period, variance, projected end-of-award balance, burn rate calculation, and alert thresholds — with monthly use instructions. Delivered by email.
- Award period
- The period of performance specified in the grant agreement during which the organization is authorized to incur costs against the grant. Expenses incurred outside the award period — before the start date or after the end date — are generally unallowable, regardless of whether they serve the grant's purpose.
DEFINITION
- No-cost extension (NCE)
- A grant modification that extends the award period without adding additional funds. NCEs allow organizations to complete the approved scope of work when activities were delayed. Most federal funders allow one NCE of up to twelve months with timely request; subsequent extensions typically require more justification. Private foundations vary significantly in their NCE policies.
DEFINITION
- Budget modification
- A formal request to shift funds between approved budget line items. Funders typically allow modifications below a certain threshold (commonly 10–25% of the total budget line) without prior approval, while larger shifts require prior written consent. The grant agreement specifies what is allowed.
DEFINITION
- Indirect cost rate
- The percentage applied to direct costs to recover organizational overhead attributable to the grant. Federal grants use negotiated indirect cost rate agreements (NICRAs). Organizations without a negotiated rate may use the federal de minimis rate of 10% of modified total direct costs.
DEFINITION
Frequently asked