Once an NIH grant moves from award to active management, most of the administrative work shifts from writing a competitive application to keeping the project compliant with the terms of the Notice of Award (NoA). A recurring set of post-award issues comes up on nearly every multi-year award: a budget needs to shift between categories, the project needs more time, a principal investigator (PI) moves institutions, or unspent funds need to roll into the next budget period. NIH treats each of these differently, and each has its own approval path, paperwork, and timing rules. This guide walks through the most common post-award issues, what NIH requires to resolve each one, and who at NIH actually has the authority to approve the request.
Discretionary changes vs. prior-approval changes
The NIH Grants Policy Statement (GPS) divides post-award changes into two broad categories: changes a recipient institution can make on its own authority under NIH’s expanded authorities, and changes that require written NIH prior approval before they take effect. Getting this distinction right matters, because acting on a change that actually needed prior approval — spending against it before NIH signs off — can turn into a disallowed cost during audit or closeout.
Common actions that require NIH’s written prior approval include:
- Change in scope — a shift in the specific aims, research design, or objectives that goes beyond what was reviewed and awarded. NIH looks at indicators such as a change in the direction of the research, a shift in clinical trial design, or reallocating work to a new performance site.
- Significant rebudgeting — moving a large share of direct costs between budget categories from what was awarded. This does not apply to modular grants, which are awarded and rebudgeted in $25,000 increments rather than itemized line items; non-modular, categorically budgeted awards are the ones where a significant shift between categories can trigger prior-approval review.
- Change in status of key personnel — replacing the PD/PI, reducing a PI’s effort below what was proposed, or a PI’s extended absence from the project.
- Adding a foreign component — any arrangement where a significant element of the project is performed outside the United States always requires NIH prior approval, regardless of dollar amount.
- Rebudgeting trainee costs — moving funds NIH awarded for stipends, tuition, and fees on a training grant into other categories of expense.
- No-cost extensions beyond the first year, or a late notification of even the automatic first extension.
- Carryover of unobligated funds for specific mechanisms where carryover is not automatic (see below).
- Change of grantee institution — transferring the grant to follow a PI who moves.
Everything on that list gets requested electronically, almost always through the Prior Approval module in eRA Commons, addressed to the awarding Institute or Center’s assigned Grants Management Specialist. See NIH Prior Approval and the general Prior Approval definition for how these requests are structured, and eRA Commons Roles for who at the institution has the system access to submit one.
Who to contact: Grants Management Specialist vs. Program Officer
NIH post-award questions get routed to two different roles that are easy to confuse but have distinct authority:
- Grants Management Specialist (GMS), part of the awarding Institute or Center’s Grants Management Branch. The GMS (or the more senior Grants Management Officer above them) is the only person with legal authority to obligate federal funds, issue or modify a Notice of Award, or approve the administrative and financial actions listed above — rebudgeting, no-cost extensions, carryover, change of grantee institution. Business and administrative questions about an award go to the GMS.
- Program Officer (also called Scientific/Program Official), who oversees the scientific and programmatic side of the project — progress, direction, and, for cooperative agreements, more active involvement in the work itself. A change in scope request typically needs the Program Officer’s programmatic sign-off before the GMS can act on it, but the Program Officer cannot unilaterally approve a budget or administrative change; that authority sits with the GMS alone.
In practice, a change-in-scope or key-personnel request often goes to both: the Program Officer evaluates whether the change is scientifically sound and still within the awarded aims, and the GMS evaluates and formally approves the administrative and budgetary consequences. The assigned GMS and Program Officer are both named on the Notice of Award (NoA) — see Sample Letter of Award (Notice of Award) for where to find them on the document.
No-cost extensions
A no-cost extension (NCE) lengthens the project period without adding funds, giving a project more time to use money it already has. NIH delegates the first extension, up to 12 months, to the recipient institution’s own authority in most cases — it does not require a Program Officer or GMS approval, only notification through eRA Commons before the current project period ends. A second or subsequent extension, or an extension longer than 12 months, always requires NIH’s written prior approval, and late notification of even the automatic first extension can jeopardize it. For the full step-by-step request process, required justification, and Commons screens involved, see NIH No-Cost Extension: How to Request One. The related dictionary entries — No-Cost Extension (NCE) and No-Cost Extension (lifecycle context) — cover where an NCE fits relative to closeout.
Carryover of unobligated funds
Carryover lets a recipient move unspent, unobligated funds from one budget period into the next rather than losing them. Most standard NIH research grants operate under automatic carryover authority: the institution does not need to ask NIH’s permission to carry the balance forward, as long as the award’s terms don’t say otherwise. There are documented exceptions where prior approval is always required regardless of the award’s other terms — commonly cited examples include Kirschstein-NRSA institutional training grants, non-Fast-Track Phase I SBIR/STTR awards, awards to individuals, and awards involving clinical trials. The Notice of Award’s terms and conditions section states explicitly whether a given award has automatic carryover authority or not — check it before assuming either way, since this is award-specific rather than a single blanket agency rule.
Change of grantee institution (PI transfers)
When a PI moves to a new institution mid-project and wants to bring an active NIH grant along, that is a change of grantee institution — a transfer of the legal and administrative responsibility for the award from the current recipient organization to the new one. This is never automatic; it always requires NIH’s written prior approval, and it involves both institutions:
- The current (relinquishing) institution submits a Relinquishing Statement (PHS Form 3734) documenting the PI’s departure date and the unspent balance from the current budget period, a Final Invention Statement (PHS Form 568), and, after the relinquishing budget period ends, a Final Federal Financial Report.
- The new (receiving) institution submits a Type 7 (change of institution) application: an updated budget for the remainder of the project, biographical sketches, a progress report, a facilities and resources statement, and documentation of any equipment moving with the project. The new institution’s own negotiated F&A rate applies going forward, not the departing institution’s rate.
NIH recommends notifying the awarding office at least three months before the intended transfer date, since Type 7 applications require review and can be delayed further around fiscal year-end. Transfers requested during an active no-cost extension are generally not approved except in unusual circumstances, and typically need to be discussed with the assigned Program Officer and GMS before a formal request is submitted.
How these post-award actions relate to closeout
Every one of the actions above needs to be resolved before a project reaches its final reporting deadline, because outstanding prior-approval items — an unresolved rebudgeting question, an unfiled relinquishing statement, an NCE requested too close to the project end date — can hold up closeout. See NIH Closeout for what NIH requires in the final 120 days after a budget or project period ends, and Closeout phase for how that fits the broader award lifecycle. For the standard federal financial report every award ultimately closes out with, see SF-425: The Federal Financial Report Explained.
Where these requests get submitted
Nearly all NIH post-award actions covered here — prior approval requests, no-cost extension notifications, relinquishing statements — are submitted electronically through eRA Commons, the system NIH recipients use to manage an award after it’s made. This is a different system, with a different purpose, from Grants.gov, which is used earlier in the lifecycle to submit the original application. Institutions and PIs sometimes ask which system a given post-award task belongs in; see eRA Commons vs. Grants.gov — What’s the Difference? for a full side-by-side, and eRA Commons ID for the account credential a PI or signing official needs before they can act on any of these requests. For the annual timeline these post-award milestones sit within, see The NIH Grant Cycle: A Full Annual Timeline.
Frequently asked questions
Do I need NIH prior approval to move money between budget categories?
It depends on the award type and the size of the shift. Modular grants are not subject to significant-rebudgeting prior approval since they’re awarded in $25,000 modules rather than itemized categories. Non-modular, categorically budgeted awards can trigger a prior-approval requirement when rebudgeting between categories is significant relative to the total costs awarded for the budget period — check the award’s Notice of Award and consult the assigned Grants Management Specialist before rebudgeting a large amount without asking.
Who approves an NIH no-cost extension — the Program Officer or the Grants Management Specialist?
The first, automatic 12-month extension doesn’t need either — it’s a recipient-institution notification, not an approval request. A second or longer extension needs the Grants Management Specialist’s written approval; the Program Officer may weigh in on the scientific justification, but the GMS holds the formal approval authority.
Can an NIH grant be transferred to a new institution if the PI moves?
Yes, through a change of grantee institution request, but it always requires NIH’s written prior approval and is not automatic. Both the departing and receiving institutions have to submit documentation, and NIH recommends starting the process at least three months before the intended move date.
What happens to unspent NIH grant funds at the end of a budget period?
For most standard research grants, unobligated funds carry forward automatically into the next budget period without a separate approval request. A specific set of mechanisms — including Kirschstein-NRSA training grants, some SBIR/STTR awards, individual fellowships, and clinical trial awards — always require prior approval to carry funds forward; check the award’s terms and conditions to see which category applies.
Who is the right point of contact for a post-award administrative question on an NIH grant?
The Grants Management Specialist named on the Notice of Award handles budget, rebudgeting, no-cost extension, carryover, and institutional-transfer questions. The Program Officer handles questions about the science, progress, and whether a proposed change stays within the project’s approved aims. Both are listed on the NoA, and for changes that touch both scope and budget, expect to coordinate with both.
