TLDR
Grant rebudgeting requires prior approval when the modification would affect project scope, change a key person, exceed the award's specific rebudgeting threshold, or involve restricted categories under 2 CFR 200.308. The threshold applies to cumulative transfers during the award period, not individual transactions. The most common error: spending from an unapproved budget category and then seeking retroactive approval - which is itself a compliance violation.
Rebudgeting is one of the more nuanced compliance decisions in grant management. It happens routinely - programs change, staffing shifts, supply costs move - and most organizations handle it without incident. It becomes a compliance problem when organizations move money between budget categories without understanding whether approval was required.
Why the Prior Approval Question Is Not Simple
The federal framework under 2 CFR 200.308 provides a set of conditions under which prior approval is required for budget modifications. The problem is that applying the framework to a specific situation requires more context than the regulation’s language alone provides.
The regulation requires prior approval when a modification would “significantly change the scope or objectives of the project.” What counts as significant? A program officer at one agency may view a staffing change as operational. A program officer at another may view the same change as affecting program delivery. The regulation does not resolve this ambiguity - it requires judgment.
The regulation also establishes thresholds for certain types of modifications, but agencies can and do impose different standards. An organization that manages one federal grant under HHS and another under HUD may be operating under different rebudgeting thresholds for each award without realizing it.
The only reliable approach is to read the specific award terms, contact the program officer when the application of the threshold is genuinely unclear, and document the decision logic when you determine that a modification falls below the prior approval threshold.
The Cumulative Threshold Problem
The single most common rebudgeting compliance error is failing to track modifications cumulatively.
An organization makes a $6,000 transfer from personnel to supplies in month four. The award is $200,000, so the transfer is 3% - well below the threshold. At month seven, another $9,000 transfers from personnel to equipment. Also below threshold individually. At month nine, $5,000 more moves from personnel to consultants. Each individual transfer passed the threshold check. The cumulative transfer from personnel is now $20,000 - 10% of the total award - and one more transfer without prior approval crosses into territory requiring pre-approval.
The organization that does not track this cumulatively discovers the problem at the audit, not during the grant period. At that point, every transfer above the cumulative threshold is an unauthorized expenditure in a budget category that was not approved for those funds.
A rebudgeting log in the grant file - updated after every transfer, showing the running cumulative total - is not bureaucratic overhead. It is the evidence you need to demonstrate that every transfer was within the approved parameters.
When to Contact the Program Officer Before Submitting
If there is genuine uncertainty about whether a modification requires prior approval - if you are not sure whether a proposed change affects “scope” within the meaning of the award - contact the program officer informally before submitting a formal request.
A brief email: “We’re considering shifting $12,000 from the personnel budget to the consultant line to cover a temporary subject-matter expert we need for [specific deliverable]. We believe this falls within the rebudgeting threshold and does not affect project scope - but wanted to check with you before proceeding. Is this the kind of modification that requires a formal prior approval request?”
This approach has two benefits. It gets you a clear answer that you can document. And it demonstrates to the program officer that your organization takes the prior approval requirements seriously enough to ask when uncertain - which is exactly the kind of compliance culture that makes future modifications easier to obtain approval for.
Download the Grant Budget Amendment Request Template for a complete fill-in template with the description, justification, cumulative transfer tracking table, and budget comparison sections needed for a formal rebudget request.
Free resource
Get the Grant Budget Amendment Request Template
A template for requesting a grant budget modification: description of the change, justification, cumulative transfer tracking table, budget before/after comparison, and submission checklist. Delivered by email.
Q&A
What is the difference between a rebudget request and a scope change?
A rebudget request moves funds between approved budget categories without changing what the project does or who it serves. A scope change modifies the project's objectives, activities, target population, or geographic area. Scope changes almost always require prior approval regardless of dollar amount. Some budget modifications that look like rebudgeting are actually scope changes - for example, cutting the mentoring program hours in half and using those funds for a different activity changes the scope, even if it does not change the budget total.
Q&A
How do I track cumulative budget transfers across the award period?
Maintain a rebudgeting log in the grant file: a table showing every budget modification, the date it was approved, the categories affected, the dollar amounts transferred, and the cumulative total of modifications to date. Update it after every approved transfer. This log is what an auditor asks for when reviewing budget compliance - the question is not just whether you had approval for the last transfer, but whether the cumulative modifications exceeded the threshold at any point during the award.
Frequently asked