Search traffic around the NIH Grants Policy Statement no-cost extension provisions spikes every year around the same time: the final months of a project period, when a principal investigator realises the data collection is behind schedule and someone in the sponsored programs office has to explain, again, what counts as an allowable extension and what does not. The terminology in the NIH Grants Policy Statement (GPS) is precise, but it is scattered across dozens of pages, cross-referenced against 45 CFR Part 75 and the Uniform Guidance, and rarely explained in one place for the administrators who have to apply it daily.
This glossary collects the recurring terms — no-cost extension, carryover, consortium agreements, and program income — that generate the highest volume of long-tail searches from research administrators, and sets out what each one actually means in practice. It follows the same reference format CASRAI uses across its dictionary of research-administration terms: definition first, then the operational detail that determines whether an institution stays compliant.
The audience is deliberately broad. US-based sponsored programs offices are the primary users of NIH terminology, but institutions that hold both NIH awards and funding from UK bodies increasingly need to translate between systems — a researcher who has learned to apply for grants under UKRI’s rules and then moves onto an NIH-funded consortium project discovers quickly that “extension” and “carryover” do not mean the same thing, or follow the same approval path, on both sides of the Atlantic.
What the NIH Grants Policy Statement Says About No-Cost Extensions
A no-cost extension (NCE) lengthens the period of performance on an NIH award without adding funds. The NIH Grants Policy Statement recognises two routes:
- First, unilateral NCE: the recipient institution may extend the final budget period of a grant once, for up to 12 months, without prior NIH approval, provided the award is not in its final year of a competitive segment for reasons that require agency sign-off (for example, if additional time is needed beyond the single automatic extension, or if the award carries specific terms restricting this authority). This authority sits with the institution’s authorised organisational representative, not the principal investigator alone.
- Second, NIH prior-approval NCE: a second extension, or any extension where the unilateral authority does not apply, requires a formal request to the assigned NIH awarding component, submitted well before the current project period ends, with a justification tied to the scientific rationale — not simply “more time is needed.”
The distinction matters because a unilateral NCE that should have gone through prior approval is a compliance finding waiting to happen. Institutions that log every NCE — automatic and approved — in a central tracking system tend to catch these errors before an NIH grants management specialist does.
Carryover: The Companion Concept to No-Cost Extensions
Carryover is the mechanism that lets unobligated funds from one budget period move into the next. It is distinct from a no-cost extension, though the two are frequently requested together: a project that needs more time to spend down its budget usually also needs the unspent funds to travel with it.
Under the NIH Grants Policy Statement, carryover authority depends on the type of award:
- Awards issued under the Streamlined Non-Competing Award Process (SNAP) generally carry automatic carryover authority, meaning unobligated balances may move forward without a separate request.
- Non-SNAP awards, and awards with specific restrictive terms, require prior NIH approval before carryover funds can be obligated in the next budget period.
Administrators should treat carryover and NCE requests as related but separate compliance events. A common error is assuming that approval of one automatically covers the other — it does not. Each has its own authority basis in the GPS, and each needs its own documentation trail in the institution’s grants management system.
Consortium Agreements and Subrecipient Monitoring
Multi-institutional NIH awards are structured through consortium agreements — legally binding documents between the prime recipient and each participating (subrecipient) institution. The NIH Grants Policy Statement requires that these agreements flow down all applicable federal terms, including the prime award’s specific conditions, and that the prime recipient carry out subrecipient monitoring consistent with the Uniform Guidance (2 CFR 200.332).
Where searches for “nih grants policy statement” cluster most heavily around consortium terms is usually at renewal or no-cost extension time, because an NCE on the prime award does not automatically extend the subaward — each consortium agreement needs its own amendment, on its own timeline, coordinated by the prime institution’s sponsored programs office. Institutions that manage large multi-site NIH awards (common in clinical trials networks and multi-PI R01s) typically maintain a master tracking sheet cross-referencing prime award dates against every subaward’s period of performance, precisely to avoid a subrecipient continuing work after its own agreement has technically lapsed.
Program Income: An Often-Overlooked GPS Category
Program income is gross income earned by the recipient that is directly generated by a supported activity, or earned as a result of the award — for example, fees from clinical services delivered through a research protocol, registration fees at a conference funded by the grant, or proceeds from the sale of research-generated data or materials. The NIH Grants Policy Statement sets out three methods for handling it: deduction (reducing NIH’s contribution), addition (adding it to the project’s committed funds), or cost-sharing/matching. Which method applies is usually specified in the notice of award, and applying the wrong method is a recurring finding in post-award reviews.
Because program income rules interact with the same budget period concept that governs carryover and no-cost extensions, administrators processing an NCE should verify whether unspent program income also needs to be reported and carried forward under the applicable method.
What This Means for Research Administrators
The terms in this glossary are not abstract definitions — each one triggers a distinct approval workflow, a distinct system-of-record entry, and in some cases a distinct federal reporting obligation. The practical implications for institutional research offices are:
- Track authority levels separately. Unilateral NCE authority, prior-approval NCE, automatic carryover, and prior-approval carryover each rest on different sections of the GPS. Conflating them in institutional policy documents is a common source of audit findings.
- Coordinate consortium timelines actively. A no-cost extension on the prime award is not self-executing across subawards; each consortium agreement needs its own amendment.
- Build cross-training between NIH and non-NIH portfolios. Institutions managing both NIH grants and awards from bodies such as UKRI, Horizon Europe, or other funders that researchers may apply for grants through, benefit from a single internal glossary that maps equivalent-but-different terms (for example, NIH’s “no-cost extension” against a UK funder’s “extension request”) so that PIs moving between funding streams are not caught out by assuming identical rules.
- Document the scientific justification, not just the administrative request. NIH awarding components scrutinise the rationale behind prior-approval NCE and carryover requests; a request that reads as purely administrative is more likely to be questioned or delayed.
These distinctions also matter for research integrity and reproducibility more broadly. Standards bodies such as NISO and initiatives supported by SPARC and cOAlition S increasingly expect that data management, sharing, and reporting obligations tied to federal awards are tracked with the same rigour as the funding mechanics themselves — an NCE that extends a project’s timeline, for instance, typically extends the data-sharing and reporting deadlines tied to NIH’s data management and sharing policy as well.
A Reference Point, Not a Substitute for the Statement Itself
No glossary replaces a careful reading of the current NIH Grants Policy Statement, which is updated periodically and should always be consulted in its original form for the specific fiscal year and award terms in question. What a reference like this can do is give research administrators — particularly those new to federal awards, or those managing a mixed portfolio spanning NIH grants and non-US funders — a shared vocabulary for the conversations that recur every budget cycle: whether an extension is unilateral or requires approval, whether carryover is automatic or restricted, whether a consortium agreement needs its own amendment, and how program income should be handled once it appears on the books.
As federal reporting requirements continue to tighten and data-sharing obligations extend further into the post-award period, the administrative precision this glossary describes is likely to matter more, not less. Institutions that build internal reference materials mapping these terms — and keep them current against each GPS revision — will spend less time reconciling compliance findings after the fact.
