Federal Grant Budget Revision Rules (2026 Guide)

1. Federal Grant Budget Revision: Start With the Change, Not the 10% Calculation

According to 2 CFR 200.308(f), prior written approval is required for listed changes to program and budget plans. Some changes do not move any money. A scope change still needs the applicable approval screen when the budget stays the same.

Use the precise direction of a transfer. Paragraph (f)(5) names transfers out of participant support. It does not say every movement into that category is the same trigger. However, a new activity or another cost condition may still require approval. Do not label either direction automatically safe.

Subaward activity is also different from procurement of goods or services. Paragraph (f)(6) excludes procurement transactions from that particular subaward trigger. That does not waive procurement standards or cost rules. Classify the relationship correctly before choosing a request type.

The Uniform Guidance guide covers the surrounding framework. The allowable-costs guide addresses cost eligibility. Permission to revise a budget does not make an otherwise unallowable cost chargeable.

2. The 10% Rule Has Two Conditions and an Agency Restriction

According to paragraph (i), an agency may restrict transfers among direct cost categories, programs, functions, or activities when both conditions apply:

• The federal share exceeds the applicable simplified acquisition threshold.
• The cumulative transfer exceeds, or is expected to exceed, 10% of the total budget, including cost share, as last approved by the agency.

According to the HHS Grants Policy Statement (opens in a new tab), section 3.1.2.2 implements a significant-rebudgeting restriction for covered HHS awards. This demonstrates why the agency layer matters: the government-wide text permits a restriction, while an agency policy and the applicable award establish how it operates.

Do not hardcode a threshold dollar amount from an old FAQ into every award file. Public agency summaries can retain older figures. Check the applicable definition and award policy, and ask the authorized office when the documents do not establish the answer. The percentage test can still be explained without asserting an unverified dollar threshold.

For example, a hypothetical award with a last approved total budget of $500,000 has a 10% calculation line of $50,000. That arithmetic is not a permission decision. The federal-share condition, cumulative amount, agency restriction, scope, and other triggers still have to be checked.

A second hypothetical transfer of $8,000 out of participant support cannot be cleared solely because it falls below that $50,000 line. Its category-specific trigger is a separate question. This is why a spreadsheet with only a transfer percentage can produce the wrong next action.

The Approval-Route Record

Grantsights analysis of 2 CFR 200.308 (opens in a new tab) and the HHS Grants Policy Statement (opens in a new tab) identifies a source-delta in the old universal-threshold explanation: it omitted the order of checks. What the official pages do not show is a single recipient-owned record connecting a proposed revision to its authority and decision evidence.

Use this original record before changing the financial system:

This is an internal working template, not a replacement for the agency's required submission. Leave uncertain fields marked unresolved. Do not fill an empty approval cell with a conversation summary and call it authorized.

A subrecipient should identify its pass-through entity's approval route rather than assuming it can request a change directly from the federal agency. Your organization may also require internal finance or sponsored-programs review. Those steps do not replace the approval required by the award.

Use the budget-modification workflow for implementation tasks once the authority is established. The screen above covers the government-wide triggers and waivers; your institution's operational checklist still applies.

Preparing a Request the Agency Can Evaluate

According to paragraph (c), use the budget-information format from the application unless the agency has approved an alternative. An approved system, email format, or other mechanism may be permitted; do not assume an informal email is enough for every award.

Include the change, its reason, the impact on approved work, a before-and-after budget, the relevant time period, and any affected cost share or personnel. Identify whether the request also changes scope. A request labeled “rebudgeting” should not conceal a material program change.

The budget-categories guide helps keep the original and revised categories comparable. The grant-budget writing guide covers explanatory budget detail. Do not use a revised narrative to disguise an ineligible cost or unsupported estimate.

According to the HRSA grant FAQs (opens in a new tab), prior-approval requests use the applicable EHB or GrantSolutions route as HRSA transitions, and valid approvals require the Grants Management Officer's signature. Verify which system applies to your award instead of treating a transition announcement as universal access.

Keep the submitted request and the decision together. An agency contact's acknowledgement that your email arrived is not the same as approval. Record any conditions in the decision, such as limits on amount, activity, or timing, before updating the ledger.

Thirty Days Is a Review Expectation, Not Automatic Consent

According to 2 CFR 200.308(d), the agency or pass-through entity should notify the recipient within 30 days of receiving a request. If review requires more than 30 days, it must inform the recipient in writing when a decision can be expected.

The regulation does not make silence an approval. Do not start a restricted action because your request has been waiting a month. Follow up through the award's documented route and retain the response.

Plan backward from the date the revised work must begin. Include your internal submission time, any required supporting documents, and the possibility of clarification. An urgent internal deadline does not change the authority requirement.

If the request is denied, separate costs already committed from proposed costs. Ask finance and the authorized grants office how the denial affects each obligation. Do not silently shift a rejected charge to another category and assume that changes its allowability.

Carryover Is Not a Universal Expanded Authority

Paragraph (g)(3) addresses a waiver allowing unobligated balances to carry forward to subsequent budget periods. Paragraph (h) automatically waives the specified paragraph (g) approvals for research awards unless agency regulations or award terms say otherwise. Check both the award type and contrary conditions.

An unused balance does not itself prove that carryforward is permitted. Record which budget period it belongs to, whether it remains available, and whether a restriction or approval requirement applies. Distinguish a future budget period from the end of the overall period of performance.

For a hypothetical research award, an applicable waiver may establish a carryforward route. For a hypothetical non-research award, the recipient needs to locate the relevant agency authority rather than importing research flexibility. Both recipients must still account for costs correctly.

If documents conflict, hold only the unresolved carryforward action and ask the authorized office for clarification. Continue preparing the rest of a supported budget revision. Do not treat uncertainty about one balance as permission to ignore other approval triggers.

A One-Time Extension Has Conditions and a Notice Deadline

Paragraph (g)(2) permits an authorized one-time extension of up to 12 months under its conditions. The award terms must authorize the recipient to initiate it without prior approval. Written notice with justification and a revised period of performance must reach the agency at least 10 calendar days before the existing end.

The extension cannot be exercised solely to use unobligated balances. It also needs prior approval when award terms prohibit it, additional federal funds are required, or the approved scope changes. Paragraph (h)'s research-award waiver does not erase those exceptions.

A no-cost extension is a bad fit when the only justification is “we have money left.” Explain unfinished approved work and the time needed, if that is the actual situation. Do not invent delayed activities to produce a more acceptable rationale.

Other extension requests fall under paragraph (f)(10), which also says requests should be submitted at least 10 calendar days before the conclusion of the period. An agency can have an earlier practical submission requirement. Use the period-of-performance guide to separate performance dates, budget periods, and closeout tasks.

Build a calendar record containing the current end, internal review date, agency notice or request deadline, proposed new end, and authority cited. No-cost means no additional federal obligation for the extension; it does not mean every charge made during the extended period is allowable.

Pre-Award Costs and Other Costs Need Their Own Check

Paragraph (g)(1) describes a possible waiver for costs incurred up to 90 calendar days before the federal award date. Such costs are incurred at the recipient's risk. More than 90 days requires prior approval under that provision.

Do not confuse the expected award date with a promise of reimbursement. A delayed, reduced, or unfunded award can leave the organization responsible for costs it chose to incur. Record the organization's risk authorization separately from federal approval.

Check 2 CFR 200.407 (opens in a new tab) and the relevant cost provision for other prior-approval questions. Labels such as equipment, foreign travel, or contracting do not establish an identical approval rule across all agencies. Read the cost condition, waiver, and award term together.

Final Decision and Maintenance Checklist

The measurable next action is a documented authority decision and, where required, a submitted request through the correct route. A generic policy article cannot approve your specific change. No purchase is needed to use this screen.

Before implementing the revision:

• Confirm the applicable award and policy versions.
• Screen all changed activities and personnel, not just amounts.
• Locate any restriction or waiver relied upon.
• Calculate cumulative transfers on the correct budget base.
• Retain the written decision or permitted notice.
• Update accounting and program records consistently.
• Recheck the deadline if the change affects performance dates.

The grant database helps locate other funding routes when the current award cannot support a proposed activity. It is not a workaround for an agency denial. Search new opportunities on their own eligibility and application terms rather than charging new work to the old award.

This guide was reviewed September 27, 2026. Recheck the regulation, agency implementation, and award terms when making a revision. Maintain threshold references as applicable-rule checks rather than copying a fixed number forward. Update the precise affected trigger or waiver when the source changes; do not replace a substantive authority review with a date-only refresh.

What the Regulation Doesn't Tell You: Keep Authority Beside Arithmetic

Based on our analysis of the approval sequence in 2 CFR 200.308 (opens in a new tab) and 2 CFR 200.407 (opens in a new tab), the strongest internal record has the policy basis and written decision beside the transfer calculation. Don't store them in unrelated folders. You can't infer an agency waiver from an available balance, and a conversation isn't necessarily the required written approval.

Consider a hypothetical case study of one grantee at a university with a proposed category transfer. Finance has calculated the percentage, while the project team has changed the work plan. The request is not ready until both groups agree whether the changed activity affects scope. This is a planning example, not an actual audit finding or a ruling on a specific award.

Use a two-person check before implementation: the program owner confirms the activity and performance impact; the authorized finance or sponsored-programs official confirms the budget base, authority, and request route. Internal roles vary by organization, so record who actually owns each check rather than importing job titles from this example.

Label the proposed budget distinctly from the approved budget. Retain both versions and the approval conditions. If a request is revised during agency review, keep a version history so accounting does not implement an earlier amount.

For repeated transfers, update the cumulative record before approving the next internal action. Do not restart the calculation every time a category moves. The record should make the last approved total, prior revisions, and proposed action inspectable together. This reduces ambiguity without claiming that a spreadsheet can settle the legal authority.

Sources

Accessed September 27, 2026:

• 2 CFR 200.308: budget and program-plan revisions (opens in a new tab)
• 2 CFR 200.407: prior written approvals (opens in a new tab)
• HHS Grants Policy Statement, including section 3.1.2.2 (opens in a new tab)
• HRSA grant FAQs: significant rebudgeting and prior approvals (opens in a new tab)