A no-cost extension (NCE) lengthens the period during which a National Science Foundation (NSF) award recipient can spend already-obligated funds, without NSF adding any new money. NSF’s rules for who can approve an extension, how it is requested, and what deadlines apply are set out in the NSF Proposal & Award Policies & Procedures Guide (PAPPG), Chapter VI, and they differ in specific, load-bearing ways from how NIH’s no-cost extension process works — the two are easy to conflate if an administrator handles both agencies’ awards, but the mechanics, deadlines, and system of record are not interchangeable. This guide covers NSF’s process specifically: submitted electronically through Research.gov (NSF does not use eRA Commons), and structured as two distinct extension types rather than NIH’s first-year/second-year framing.
The two types of NSF no-cost extension
NSF’s PAPPG splits no-cost extensions into two categories with different approval authority, different deadlines, and different justification requirements.
1. Grantee-approved extension (the first, automatic extension)
A recipient institution may authorize, on its own authority, a one-time extension of the award’s end date of up to 12 months, without prior NSF approval, when additional time — not additional money — is needed to finish the originally approved scope of work. Key mechanics:
- Who submits it: the institution’s Authorized Organizational Representative (AOR) must sign and submit the notification electronically. A principal investigator cannot submit this directly; it goes through the sponsored programs office.
- Deadline: notification must be submitted at least 10 calendar days before the current award end date.
- System: submitted through Research.gov, using the award’s Notifications & Requests function.
- No amendment issued: because this is a grantee-authorized action, not an NSF approval action, NSF does not issue a formal grant amendment. The revised end date simply appears in NSF’s award system once the notification is processed; the Program Officer and sponsored programs office receive an electronic notice of the disposition.
- Restrictions: the extension exists to finish approved work, not to spend down a remaining balance — PAPPG is explicit that it may not be exercised merely to use unliquidated funds, and an award with a zero remaining balance is not eligible. It also does not apply to NSF cooperative agreements, which require NSF Grants and Agreements Officer approval for any extension from the outset.
2. NSF-approved additional extension (beyond the grantee-approved 12 months)
If the project genuinely cannot be completed within the grantee-approved extension — or a recipient has already used its one-time grantee-approved extension and still needs more time — a further extension requires an affirmative NSF approval, not just notification. PAPPG describes this as available when “exceptional circumstances warrant” additional time.
- Deadline: the request should be submitted at least 45 days before the current award end date. A late request needs a strong justification for why it wasn’t submitted on time, in addition to justifying the extension itself — NSF is not obligated to grant a late request.
- Who approves it: a first NSF-approved additional extension request is considered by the cognizant NSF Program Officer (this action also does not generate a formal amendment). A second or subsequent NSF-approved extension request requires approval from an NSF Grants and Agreements Officer and does result in a formal award amendment specifying the new end date.
- Submission mechanics: also submitted via Research.gov by the AOR, as a formal request rather than a notification — NSF’s system routes it for Program Officer or Grants and Agreements Officer review rather than auto-processing it.
Typical justification requirements
An unspent balance is, by itself, never sufficient justification for either extension type under PAPPG — NSF expects the request to demonstrate a genuine programmatic need for more time. A complete NSF-approved extension request generally needs to address:
- Why more time is needed — the specific circumstance (e.g., equipment delay, staffing gap, data-collection setback, a collaborator’s site becoming unavailable) that prevented completing the approved scope of work within the original or previously extended period.
- Current status of the project against the goals in the approved proposal, so the Program Officer can assess whether the remaining work is consistent with the original scope rather than a substantive change in direction.
- An estimate of unobligated funds remaining in the award.
- A plan for using those funds that ties directly back to completing the original project objectives, not a new or expanded activity.
A substantive change in the scope of work is a separate PAPPG action from a no-cost extension and may require its own prior approval; an extension request is not the mechanism for expanding what the award funds.
How to submit via Research.gov: step by step
- Confirm eligibility first. Check the award’s remaining balance and confirm it is not a cooperative agreement (cooperative agreements never qualify for the grantee-approved path).
- Determine which extension type applies. If this is the award’s first extension and 12 months or fewer is enough, use the grantee-approved path. If the award has already used its grantee-approved extension, or more than 12 months total is needed, an NSF-approved extension is required instead.
- Log in to Research.gov with NSF credentials under the appropriate role (AOR for submission; PIs typically initiate the internal request but cannot sign it themselves).
- Locate the award and open Notifications & Requests (grantee-approved extension) or the equivalent formal request workflow (NSF-approved extension).
- Enter the new requested end date and, for an NSF-approved extension, attach the written justification covering the elements above.
- Submit for AOR signature and electronic transmission to NSF. For the grantee-approved path this completes the action; for an NSF-approved extension, it routes to the Program Officer (or Grants and Agreements Officer, for a second/subsequent request) for review.
- Track the disposition in Research.gov and confirm the revised end date is reflected in the award record before assuming the extension is in effect.
NSF vs. NIH no-cost extensions: what’s actually different
Because both agencies use similar terminology (“no-cost extension,” “prior approval”), it’s easy to assume the mechanics transfer directly — they don’t. Administrators managing awards from both agencies should treat these as separate processes, not a shared template:
- System of record: NSF extensions are submitted through Research.gov. NIH extensions are submitted through eRA Commons — a completely separate federal system with its own login and role structure. See CASRAI’s companion guide, NIH No-Cost Extension: First-Year vs. Second-Year Rules and How to Request One, for the eRA Commons-specific process.
- Deadline structure: NSF’s grantee-approved extension requires only 10 calendar days’ notice before the end date, and its NSF-approved extension requires 45 days’ notice. NIH’s expanded-authority (first) extension has no fixed advance-notice window in the same way, but its process opens roughly 90 days before the project end date, and a second NIH extension request has its own separate eligibility window tied to days remaining before, and days elapsed after, the project period end date. The two agencies’ clocks do not run on the same schedule.
- Who can act on the first extension: both agencies delegate the first extension to the institution rather than requiring agency sign-off (NSF: “grantee-approved”; NIH: “expanded authority”), but NSF caps that delegated extension at 12 months in a single action, while NIH’s expanded-authority extension is also capped at 12 months but is described and processed under different regulatory language (NIH Standard Terms of Award) with a different notification screen (eRA Commons Status).
- Who signs: NSF requires the Authorized Organizational Representative (AOR) to sign and submit electronically. NIH’s equivalent role is the institution’s Signing Official (SO) — different title, same general function, but not interchangeable within either agency’s own system.
- Cooperative agreements: NSF explicitly excludes its own cooperative agreements from the grantee-approved (delegated) extension path, requiring Grants and Agreements Officer approval from the outset. Treat any NSF cooperative agreement as needing the NSF-approved process regardless of how much time is requested.
If your institution manages awards from both agencies, it is worth confirming with your sponsored programs office which system and which internal routing applies before assuming a process that works for one agency’s award will work the same way for the other’s.
Frequently asked questions
How many no-cost extensions can an NSF award receive?
Typically one grantee-approved extension of up to 12 months, plus, if still needed, one or more NSF-approved extensions beyond that — the first NSF-approved extension is decided by the Program Officer, and any further one requires a Grants and Agreements Officer’s approval. There is no fixed cap on the number of NSF-approved extensions in the PAPPG language itself, but each additional request faces a higher bar of justification and approval authority.
Does the grantee-approved NSF extension need Program Officer approval?
No. That is the defining feature of the grantee-approved extension — the institution’s AOR notifies NSF electronically and no NSF approval action or formal amendment is required, provided the award isn’t a cooperative agreement and hasn’t already used this one-time authority.
Can NSF deny a no-cost extension request?
NSF cannot deny a properly submitted grantee-approved extension because it is not an NSF approval action in the first place — it’s a notification. An NSF-approved extension, by contrast, is a genuine agency decision: the Program Officer or Grants and Agreements Officer can decline it, particularly if the justification is thin (e.g., an unspent balance alone) or if the request is late without a strong reason for the delay.
What is the deadline for an NSF no-cost extension request?
At least 10 calendar days before the award end date for the grantee-approved extension, and at least 45 days before the award end date for an NSF-approved additional extension.
Is the NSF no-cost extension process the same as NIH’s?
No. They share the same general concept and similar terminology, but run on separate electronic systems (Research.gov vs. eRA Commons), separate deadline structures, and separate approval titles. See the comparison section above and CASRAI’s NIH no-cost extension guide for the NIH-specific process.
