A user with the Principal Investigator (PI), Sponsored Project Officer (SPO), or Authorized Organizational Representative (AOR) role can initiate and submit an LOI in Research.gov. For a funding opportunity that requires AOR submission, the PI or SPO must share the LOI with the AOR.

For solicitations that require or request submission of an LOI, there is a field on the full proposal Cover Sheet titled "Letter of Intent ID Number." Enter your LOI number in this field and then save the Cover Sheet. A green confirmation message will display and will include your LOI title below the LOI ID number field. Additionally, there will be a blue information message at the top of the full proposal Cover Sheet confirming the successful association of your LOI and your full proposal. If the LOI ID number you entered is invalid or is for an LOI for which you do not have access, you will receive an error message and the LOI will not be associated to your full proposal.

Yes. Follow the solicitation requirements and enter the LOI Number on the full proposal Cover Sheet. Although the system allows this entry to be optional, the cognizant Program Office will verify compliance of the submitted full proposal with the solicitation.

To remove an LOI number that is associated with a full proposal, go to the full proposal Cover Sheet, clear the Letter of Intent Number field, and then save the Cover Sheet.

A valid LOI must meet the following criteria:

• Exists in the user's Submitted LOI list
• Is not associated with another submitted full proposal
• Belongs to the same organization as the full proposal
• Was created using the same solicitation as the full proposal

Research.gov will require that each LOI has an LOI Title, a Project Synopsis, and an associated PI.

The following LOI attributes are solicitation-dependent:

• Number of Senior Personnel
• Number of Participating Organizations
• Organization and Project Information
• Additional information permitted in the Other Comments section

No, an LOI prepared in Research.gov can only be associated with a Research.gov full proposal. Likewise, an LOI prepared in FastLane can only be associated with a FastLane full proposal.

Yes, an LOI can be associated to a single submission collaborative proposal with subaward or to a lead organization proposal that is part of a separately submitted collaborative proposal from multiple organizations. An LOI cannot be associated with a non-lead organization separately submitted collaborative proposal.

The Research.gov Supplemental Funding Request Submission System provides the ability to create, submit, track, and update supplemental funding requests, including Career-Life Balance requests, associated with active NSF awards. Supplemental funding requests can be submitted in Research.gov regardless of which system (Research.gov, FastLane or Grants.gov) was used to submit the proposal. This furthers an NSF goal of providing quick access to supplemental funding request information and grants management services in one location in Research.gov. NSF goals for the system are to provide a modernized, intuitive environment for supplemental funding request preparation and submission; reduce administrative burden via real-time compliance checking; provide online help tips and guidance; and incorporate a wizard that walks users through the supplemental funding request setup process.

Yes. Research.gov accepts supplemental funding request updates/budget revisions for supplemental funding requests submitted in Research.gov.

A supplemental funding request Temporary ID Number is a unique identifier that is generated by the system to keep track of and manage supplemental funding requests before they are submitted. Once submitted to NSF, the supplemental funding request is assigned a permanent supplemental funding request ID. The permanent supplemental funding request ID will be different from the ID of the award to be supplemented.

Automated compliance checks triggering an error message will stop supplemental funding request submission to NSF, whereas checks triggering a warning message will still allow supplemental funding request submission. Expanded compliance checking in Research.gov helps to reduce administrative burden for the research community and NSF staff, as well as minimizes the return without review of supplemental funding requests. Refer to the Automated Compliance Checking of NSF Proposals   page for the current Research.gov automated supplemental funding request checks. Awardees who receive a compliance error or warning message should check the Automated Compliance Checking of NSF Proposals   page, program page, and solicitation for specific supplemental funding request requirements. Awardees should also review the topic-specific supplemental funding request FAQs. For example, the Uploading Documents FAQ topic includes document formatting FAQs, and the Supplemental Funding Request Sections FAQ topic includes Cover Sheet and Budget FAQs.

The Actions section on the supplemental funding request main page has a new Check Error(s) and Warning(s) button. After clicking this button, the Check Error(s) and Warning(s) page will display to show the identified automated compliance error and warning messages for the proposal. Individuals with a PI, co-PI, SPO, AOR, or Other Authorized User (OAU) role on the proposal can view the error and warning messages. If there are no errors or warnings, this page will display a green success message. Please refer to the Automated Compliance Checking of NSF Proposals   page for a listing of the current compliance checks.

Although a Program Officer concurrence email is not required to be uploaded in Research.gov when submitting a supplemental funding request, NSF strongly recommends that the PI or co-PI contacts the NSF cognizant Program Officer before preparing and submitting a supplemental funding request for an award.

No. There is no system limit on the number of supplemental funding requests that can be prepared and submitted in Research.gov for an active award. In-progress supplemental funding requests for the specified award will be displayed on the In Progress Supplemental Funding Requests page. Submitted supplemental funding requests for the specified award will be displayed on the Submitted Supplemental Funding Requests page.

No. Supplemental funding requests and supplemental funding request updates/budget revisions cannot be submitted for an award that is closed or cancelled.

Submitted supplemental funding requests cannot be deleted but they can be withdrawn from NSF. To initiate a supplemental funding request withdrawal, the PI, SPO or AOR can navigate to their Submitted Supplemental Requests list, select the appropriate supplemental funding request for withdrawal, and click on the Withdraw Supplemental Request button in the Actions section of the supplemental funding request main page. For more information, see the Supplemental Funding Request Withdrawal FAQ topic .

Individuals who are using Chrome will encounter a networking error when attempting to use the download file functionality. We recommend clicking on the Print icon and Save as PDF or using a different browser.

To access the Research.gov Supplemental Funding Request Submission System:

• Open Research.gov and, select Sign In at the top of the page.
• After entering credentials to sign in to Research.gov, you will be navigated to the Research.gov homepage.
• Under Awards & Reporting, click the Supplemental Funding Requests (including Career-Life Balance) link to go to the supplemental funding request preparation landing page.

Yes, InCommon access login credentials can be used. From the Research.gov Sign In page, select your organization from the organization drop-down menu to be taken to the InCommon Log In page for your organization. (Note: Only InCommon Federation participants can use their organization-issued credentials to sign in to Research.gov. If you are signing in with your organization-issued credentials, you will be prompted to link your credentials to your NSF ID if they are not already linked.)

Yes, Login.gov credentials can be used. After entering your Login.gov credentials on the Research.gov Sign In page, you will be prompted to link your Login.gov credentials to your NSF ID if they are not already linked.

An SPO is able to review and edit supplemental funding requests, supplemental funding request updates, and revised budgets after the PI or co-PI shares supplemental funding request access. The SPO can also initiate supplemental funding request withdrawal requests for approval and submission by the AOR.

An AOR is authorized to sign on behalf of the organization. The AOR is able to view, edit, and submit supplemental funding requests after they are shared by the PI or co-PI. The AOR can also initiate and submit supplemental funding request withdrawals. In addition, the AOR reviews supplemental funding request withdrawal requests initiated by PIs and SPOs and submits the approved withdrawals to NSF.

Only a PI or co-PI with an active award can initiate a supplemental funding request for that award in Research.gov; however, individuals with other roles (i.e., SPO, AOR, and OAU) who are granted access to the supplemental funding request by the PI will be able to prepare and edit the supplemental funding request.

No, users with the OAU role can assist with supplemental funding request preparation in Research.gov without being required to also have another organization-approved role (e.g., View Only role)OAUs can assist with preparing supplemental funding requests by selecting the Work with In Progress Supplemental Requests link under In Progress Supplements on the supplemental funding request preparation landing page.

Users without the OAU role can request this role from their organization by following the instructions in the Add a New Organizational Role section of the Account Management Guide.

No, individuals added to a Research.gov supplemental funding request as Other Senior Personnel cannot view, access, or edit the supplemental funding request.

A PI or co-PI can share a supplemental funding request with the SPO/AOR even before required supplemental funding request data is entered or uploaded and sections are completed. On the supplemental funding request main page, select the Share Supplemental Request with SPO/AOR button in the Actions section and then choose the type of access to provide the SPO/AOR: No access, View-only access, Edit access, or Edit access with Allow supplemental request submission (AOR only). The Allow supplemental request submission (AOR only) checkbox is automatically checked as the default when the Edit access radio button is selected. However, the PI or co-PI can remove the check from the Allow supplemental funding request submission (AOR) checkbox and then add it again for supplemental funding request submission.

No. The only personnel automatically added to the supplemental funding request from the award are the PI, postdoctoral fellow (fellowship awards only), and co-PI(s). Users do have the ability to add OAUs and Other Senior Personnel to the supplemental funding request. However, new co-PI(s) not included on the award cannot be added on the supplemental funding request.

No. If a PI transfer for an award is completed, the award will be closed and a new award and award number will be issued. The new award number can be used by the PI to prepare and submit a supplemental funding request for the new award. The new award must be active in order for a supplemental funding request to be submitted.

Yes. Supplemental funding requests can be prepared for active postdoctoral fellowship awards. Either the postdoctoral fellow or a co-PI on the award can initiate a supplemental funding request but the postdoctoral fellow must submit the supplemental funding request. Career-Life Balance (CLB) supplemental support can be requested in Research.gov provided that the postdoctoral fellowship award, funded through one of NSF’s postdoctoral fellowship programs, is made to an organization and not directly to the fellow. NSF postdoctoral fellows who receive funding directly from NSF rather than through an organization are ineligible to receive CLB supplements.

You must have the Proposed Postdoctoral Fellow role to initiate a supplemental funding request for an active postdoctoral fellowship award. A Proposed Postdoctoral Fellow role is different than a PI role. The fellowship award(s) will only display and be available to select if it is active and you have the Proposed Postdoctoral Fellow role.

When a user is affiliated with an organization and has multiple organization-approved roles such as PI, co-PI, SPO, OAU, or AOR as well as the role of a Proposed Postdoctoral Fellow, all active awards that you are listed as a PI, co-PI, or postdoctoral fellow will be displayed and available for selection on the Prepare New Supplemental Funding Request – Select Award page.

Research.gov will not enforce that personnel documents (i.e., Biographical Sketch, Current and Pending (Other) Support, and Collaborators and Other Affiliations) are uploaded for a postdoctoral fellow or co-PI in a supplemental funding request. However, updated personnel documents should be uploaded in the supplemental funding request for the postdoctoral fellow and co-PI if there were any personnel document updates since the awarded postdoctoral fellowship proposal was submitted.

Yes. Supplemental funding requests, including Career-Life Balance requests, can be submitted for active SBIR or STTR Phase I or Phase II awards by the PI or co-PI. Please contact the NSF cognizant Program Officer before preparing and submitting a supplemental funding request for the SBIR or STTR award.

To prepare a supplemental funding request for a lead organization award in a separately submitted collaboration from multiple organizations, the PI or co-PI of the lead organization navigates to the Prepare New Supplemental Funding Request page and selects the lead award in the Research.gov Supplemental Funding Request Preparation Wizard. The PI/co-PI(s) of the non-lead organization award(s) cannot prepare a supplemental funding request for the lead organization award.

To prepare a supplemental funding request for a non-lead organization award in a separately submitted collaboration from multiple organizations, the PI or co-PI of the non-lead organization navigates to the Prepare New Supplemental Funding Request page and selects the non-lead award in the Research.gov Supplemental Funding Request Preparation Wizard. The PI/co-PI(s) of the lead organization award and of other non-lead organization awards in the collaboration cannot prepare a supplemental funding request for a non-lead organization.

No. A submitted supplemental funding request will only apply specifically to the award for which the supplemental funding request was submitted and not to each award in the separately submitted collaboration from multiple organizations. If the supplemental funding request is awarded, the additional funding will only be applied to the award for which the supplemental funding request was submitted.

Research.gov runs selected automated checks for PAPPG formatting compliance when a PDF document is uploaded. If non-compliance is detected, a warning or error message will display that identifies the issue(s). Some issues stop document upload (i.e., compliance errors), such as a violation of page length, while others allow document upload to complete (i.e., compliance warnings), such as violations of line spacing. For complete information, see the PAPPG, Chapter II.C. proposal preparation instructions   and the Automated Compliance Checking of NSF Proposals   page. If unexpected errors occur when uploading a PDF document, please contact the NSF IT Service Desk at 1-800-381-1532 for assistance. The PDF can be analyzed, and a solution can be identified. The NSF IT Service Desk is available by phone from 7:00 AM to 9:00 PM ET Monday - Friday except federal holidays or via email to  rgov@nsf.gov.

The supplemental funding request must conform to the formatting requirements specified in PAPPG Chapter II.C.2.   including the font and margin requirements detailed in PAPPG Chapter II.C.2.a.  Refer to the Automated Compliance Checking of NSF Proposals   page for the complete list of current compliance checks for supplemental funding requests.

Line and Margin Requirements per PAPPG Chapter II.C.2   :

• No more than six lines of text within a vertical space of one inch.
• Margins, in all directions, must be at least an inch. No PI-supplied information may appear in the margins.
• Paper size must be no larger than standard letter paper size (8½ by 11").

Some potential margin issue root causes may be:

• Text in headers/footers and page numbers: Be sure that the document has no text in the header or footer including page numbers. Research.gov will automatically paginate and add page numbers for you when the supplemental funding request PDF is generated, so page numbers should be removed.
• Document elements not visible or not obvious on inspection: Items such as a space character in the header/footer or code inserted when using LaTeX to create the source file can trigger a margin error.
• Inserted images, figures, shapes, and hyperlinks: Margins can be set to one inch, but an image, figure, shape, or hyperlink can violate the margin rule. Setting the margin rule to one inch would not automatically correct the images, figures, shapes or hyperlinks within margins. Be sure to review all inserted images, figures, shapes, or hyperlinks that may be causing a margin issue.
• Known issues with PDF conversion software:
  • Fully justified text (i.e., both the left and right sides of the text have clean edges) may result in right margin issues for some PDF conversions. Some characters, such as commas, can bleed into the margins. If you want to maintain justified text and encounter margin issues, experiment by increasing the right margin settings (e.g., 1.02 - 1.05). Settings will vary and are dependent on the user's software. As an alternative, consider using left justification.
  • Some PDF conversion software can overwrite metadata and alter the formatting of files, and the NSF IT Service Desk has seen issues with Quartz PDF Context that is prevalent in Macs. Please use alternative methods to perform the PDF conversion.
  • The PDF conversion process from older versions of Microsoft Word may alter the margins set in the original document. Please use alternative methods to perform PDF conversions. Other options may include increasing margins or using a more recent Microsoft Word version.
  • Be wary of the use of heading styles in Microsoft Word: Using the heading style in Word will automatically add features to the document that collapse and expand text, and users may inadvertently collapse and hide non-compliant content. Starting a page with heading style text can cause top margin issues. It is helpful to check if any content is hidden by pressing Control-A to select the entire document and changing the style to "Normal" to identify hidden content.
  • Special characters, equations, or use of bolded font in the first line of text on a page: Documents with special characters, equations, or bolded font in the first line of a page can cause a top margin issue in some versions of Microsoft Word. Inserting an entire blank line or two before the text may resolve this issue. For equations, consider using an image of an equation instead of an equation inserted by Equation Editor.
• Margins less than 72 points: Ensure your document margins are compliant before exporting the document to PDF. The system recognizes one inch as 72 points. If you notice margin issues for your PDF document, try exporting the PDF to Microsoft Word format to correct the margins to one inch. Then save the file as a PDF and upload it again.

For line spacing, there should be no more than six lines of text within a vertical space of one inch. Some potential line spacing root causes may be:

• Documents originating in LaTeX sometimes will trigger the line spacing warning even though the font type and font size are compliant.
• Some PDF generators change the size of document content slightly.
• In some versions of Microsoft Word, Arial 10 and Courier New 10 will produce line spacing errors. In this instance, try changing the line spacing to 1.05 as a workaround. Also consider experimenting with a different font or increasing the font to 11 or more. Please note that caption fonts smaller than 10 will trigger line spacing warnings.

In Microsoft Word, the number of lines per inch is dynamic based on font size. An option in Word to try is to format the paragraphs to specify an exact point size to use between lines. Here's how to do this:

• Open the document Layout tab
• Open paragraph settings by clicking the arrow icon below the Spacing Before and After options
• Select the Indents and Spacing tab
• In the Spacing section, go to Line Spacing and select Exactly in the dropdown menu and then 12 pt in the At field.

Search on key domain suffixes such as .gov, .edu, .com, .io, .biz, etc.

Search for "www" or "http" text.

Hidden or embedded URLs can be prevalent when using citations. Citations created by Zotero or Paperpile, for example, can create hidden clickable links. Avoid using third party citation software and type out the citation.

The following are some examples of known issues:

• Outdated software used for exporting the file to PDF (recommend using PDF version 1.5 or higher).
• OpenOffice inserts an unallowable font for superscript and subscript.
• Google Docs may not properly export bulleted text.
• Google Docs Print→Save as PDF is not supported. Use File→Download→PDF Document.
• Microsoft Office for Macs Save as PDF functionality and Best for Printing may not be supported. Instead, select the Best for electronic distribution and accessibility (uses Microsoft online service) option.
• For Microsoft Office, do not use Print as PDF to create a PDF. Instead, use Export and Create PDF.

Yes, a repository of compliant LaTeX/TeX sample input files has been created at https://github.com/nsf-open/nsf-proposal-latex-samples   as a resource for LaTeX/TeX users to reference for their own documents. The NSF IT Service Desk cannot troubleshoot LaTeX files or converting LaTeX files to PDF.

The following are some examples of possible COA missing data causes:

• Cell contents exceed the cell limit of 255 characters including spaces.
• Data is missing, especially in column A for tables 2-5.
• Last Active column is entered using a date format other than MM/DD/YYYY.
• Cutting and pasting from other programs or files with formatting has produced errors or brought in invalid fonts and borders that trigger warning(s) on upload.

NSF continues to invest in expanding automated compliance checking capabilities to reduce administrative burden on both the research community and NSF staff. Additional information is available on the Automated Compliance Checking of NSF Proposals   page.

There is not currently a way to modify the order of senior personnel documents in the PDF. However, NSF will discuss a possible future enhancement to allow reordering of senior personnel documents in the PDF.

A PDF file that is a certified signed document or is password protected will produce this error. Open the PDF file with a browser and print it with the destination set as Adobe PDF (not Save PDF or Save As). If this does not resolve the issue, please contact the Help Desk at 1-800-381-1532 (7:00 AM - 9:00 PM ET; Monday - Friday except federal holidays) or via email to  rgov@nsf.gov for assistance.

No, the system does not have a validation requiring you to submit your supplemental funding request by a specified time. Refer to the funding opportunity or contact the cognizant Program Officer for any programmatic guidance on supplemental funding request submission that must be followed.

If Pending is displayed, this means that a Supplemental Funding Request Number has not yet been generated for your supplemental funding request. Try refreshing the page and if that does not work, please contact the NSF IT Service Desk at 1-800-381-1532 (7:00 AM - 9:00 PM ET; Monday - Friday except federal holidays) or via  rgov@nsf.gov for assistance.

Only the AOR can submit a supplemental funding request to NSF. A PI or co-PI must first use the Share Supplemental Request with SPO/AOR button to provide the AOR with submit supplemental request access. Then the AOR will see the Initiate Supplemental Request Submission button enabled in the Actions section on the main supplemental funding request page. The AOR will click the Initiate Supplemental Request Submission button to start supplemental funding request submission.

The Allow supplemental request submission (AOR only) checkbox is automatically checked as the default when the Edit access radio button is selected by the PI/co-PI. However, the PI/co-PI can remove the check from the Allow proposal submission (AOR) checkbox. The PI/co-PI should ensure that the Allow proposal submission checkbox is selected when the supplemental funding request is ready for submission by the AOR.

Revisions to submitted supplemental funding requests (e.g., uploaded documents and budget amounts) can be made using a supplemental funding request update initiated by the PI. Edits must be done via the Update Supplemental Request/Revise Budget Information button on the Submitted Supplemental Funding Request page. How you edit your supplemental funding request depends on its status (see the submitted status table at the end of these FAQs). Supplemental funding request updates follow the same process in Research.gov as proposal file updates use for proposals.

To withdraw a submitted supplemental funding request in Research.gov, the PI, SPO, or AOR navigates to the Supplemental Funding Requests list, selects the supplemental funding request they want to withdraw, and clicks on the Withdraw Supplemental Request button in the Actions section of the supplemental funding request main page to initiate the withdrawal process.

A submitted supplemental funding request may be withdrawn at any time before a funding recommendation is made by the cognizant NSF Program Officer.

The supplemental funding request's PI, SPO or AOR may initiate a withdrawal request but only the AOR can approve the request and submit the withdrawal to NSF.

Submitted supplemental funding request are withdrawn from NSF as soon as the AOR approves the withdrawal in Research.gov.

A pending supplemental funding request withdrawal request initiated by the PI or SPO can be deleted at any time before the AOR approves the withdrawal in Research.gov.

No, supplemental funding requests with a pending withdrawal request cannot be updated using the supplemental request update/budget revision process. The pending withdrawal request must first be deleted (PI or SPO action) or rejected (AOR action) before a supplemental request update/budget revision can be prepared to edit the submitted supplemental funding request.

No, you cannot withdraw a supplemental funding request if the award is closed or cancelled. The supplemental funding request can only be withdrawn if the award is active and the cognizant NSF Program Officer has not made a funding recommendation for the supplemental funding request.

Withdrawn supplemental funding requests are indicated by a supplemental request status of Withdrawn on the Submitted Supplemental Funding Requests list. In addition, the PI, SPO, and AOR will receive an email and system notification to confirm the supplemental funding request withdrawal.

If there is an in-progress supplemental request update/budget revision that was started prior to initiation of a withdrawal request, the in-progress supplemental request update/budget revision becomes read-only and cannot be submitted unless the supplemental funding request withdrawal request is deleted or rejected. A new supplemental request update/budget revision cannot be prepared when there is a pending withdrawal request or after a supplemental funding request has been withdrawn.

No. Once a supplemental funding request is withdrawn, it cannot be re-submitted to NSF by the organization. However, the PI,SPO and AOR may still view and print the withdrawn supplemental funding request in Research.gov.

Yes. To request an extension of the current award end date, you must enter a value in the Requested Additional Duration section in terms of months. The NSF Grants and Agreements Officer will issue an amendment to the award if the supplemental funding request is approved, including the award end date extension. If no extension to the current award end date is needed, the Requested Additional Duration section should be blank.

The Award Amount is the current amount of the award and includes the original award amount plus the total amount for any awarded supplemental funding requests. The Supplemental Funding Request Amount is the total requested amount for the supplemental funding request only and does not include the original award amount.

The number of years in a subaward budget must be equal to or less than the number of years in the prime organization budget. If the number of years in a subaward budget exceeds the number of years in the prime organization budget, an automated compliance error will be generated and the supplemental funding request will be stopped from being submitted to NSF.

Certain categories of information that are submitted in conjunction with a supplemental funding request are for "NSF Use Only" and not provided to reviewers for use in the review of the supplemental funding request. The Single Copy Document in supplemental funding requests include Collaborators and Other Affiliations Information. Please see PAPPG, Chapter II.D.1.   for additional information about Single Copy Documents.

The postdoctoral mentoring plan must be uploaded in a supplemental funding request when both of the following conditions are true:

• Funds are included in the Postdoctoral Fellow budget line in the supplemental funding request
• A postdoctoral mentoring plan was not uploaded in the original awarded proposal

Although Research.gov does not enforce submission of a postdoctoral mentoring plan through an automated compliance check, Program staff will check that a postdoctoral mentoring plan is included if it is required.

The supplemental funding request demo site provides the research community an opportunity to initiate and edit supplemental funding requests as well as check compliance of uploaded documents (e.g., Collaborators and Other Affiliations and Biographical Sketch) before preparing supplemental funding requests in the actual Research.gov Supplemental Funding Request Submission System. The supplemental funding request demo site also is accessible by NSF staff.

All demo site users are able to perform the supplemental funding request preparation functions that a PI is able to perform in the actual Research.gov Supplemental Funding Request Submission System, such as initiating and editing supplemental funding requests, uploading supplemental funding request documents, and adding budgets. The demo site does not support supplemental funding request submission and will not trigger any system-generated email notifications (e.g., sharing supplemental request access with SPO/AOR emails).

Note that demo site supplemental funding requests are not available in the actual Research.gov Supplemental Funding Request Submission System, and information cannot be transferred between the demo site and the actual Research.gov Supplemental Funding Request Submission System.

Yes. The demo site will generate "dummy" awards that can be used to prepare a supplemental funding request in the demo site. These demo site "dummy" awards can only be used in the demo site and not in the actual Research.gov Supplemental Funding Request Submission System.

Yes. The user's actual awards as well as "dummy" awards generated by the demo site will display for selection to try out preparing a supplemental funding request.

The Give Feedback button is displayed on all demo site supplemental funding request pages for supplemental funding requests created in the demo site. When this button is clicked, a new browser tab will open and displays the Research.gov Feedback page. Select the Supplemental Funding Request Demo Site option under Site Area to submit feedback about the demo site. Demo site feedback from users will help NSF improve the site, as well as identify potential enhancements to improve the user experience when preparing supplemental funding requests in the Research.gov Supplemental Funding Request Submission System.

External users can access the demo site by following these steps:

• Navigate to Research.gov.
• Click "Sign In" located at the top right of the Research.gov page.
• Sign in to Research.gov using your primary email address, NSF ID, your organization-issued credentials, or Login.gov credentials. 
  
  Note: Only InCommon Federation participants can use their organization-issued credentials to sign in to Research.gov. If you are signing in with your organization-issued credentials, you will be prompted to link your credentials to your NSF ID if they are not already linked. If you are signing in with Login.gov credentials, you will be prompted to link your credentials to your NSF ID if they are not already linked. 
  
   
• After signing into Research.gov, you will land on the Research.gov homepage, where there are two ways to access the demo site:
  • From the top menu bar, select Awards & Reporting, then select Demo: Supplemental Funding Requests.
  • From the the Research.gov homepage, select Demo Site: Supplemental Funding Requests (Training) under Awards & Reporting.

To access the demo site, you will first need to create an NSF account and obtain an NSF ID by clicking Register on Research.gov. View the Register for a New NSF Account video tutorial for a walk-through of steps. Additional information is available on the Research.gov About Account Management page. Users with an existing NSF account (i.e., nine-digit NSF ID) will use that account to access the demo site. After signing in to Research.gov, you will land on the Research.gov homepage, where there are two ways to access the demo site.

• From the top menu bar, select Awards & Reporting, then select Demo: Supplemental Funding Requests.
• From the the Research.gov homepage, select Demo Site: Supplemental Funding Requests (Training) under Awards & Reporting.

No, you are able to access the demo site if you have an NSF ID and can sign in to Research.gov. All demo site users are given the PI role for demo site use only and are not required to obtain a special user role to access the demo site. All demo users have the National Science Foundation as their organization for purposes of the demo site. The demo site PI role will not be available in the user's NSF account profile for use on the actual Research.gov Supplemental Funding Request Submission System.

The organization(s) that you are affiliated with in your NSF account profile for your organization-approved roles will be incorporated when you are in the supplemental funding request demo site but the user role(s) that you have will not be available in the demo site. All users who access the demo site are given the role of PI, and unaffiliated users including NSF staff will be assigned National Science Foundation as their organization. Users with an affiliated organization in their NSF account profile will have that organization and the NSF organization incorporated in the demo site. All affiliated organizations will be included if the user is affiliated with multiple organizations

All demo site users have the PI role and can perform the same PI functions as in the actual Research.gov Supplemental Funding Request Submission System. The Proposed Postdoctoral Fellow role must be specifically added to prepare a supplemental funding request for a fellowship award in the demo site. The demo site does not include the OAU, SPO or AOR roles.

Yes. Any individual added to a demo supplemental funding request as an OAU by entering the individual's NSF ID will be able to access that supplemental funding request in the demo site from the In Progress Supplemental Funding Request section on the Supplemental Funding Request Demo Site homepage. The permissions and available functions for the OAU in the demo site are identical to the permissions and available functions for the OAU in the actual Research.gov Supplemental Funding Request Submission System.

No. All demo site users have the PI role and can perform the same PI functions as in the actual Research.gov Supplemental Funding Request Submission System. You will be able to go through the process of sharing supplemental funding request access (view, edit and/or submit) with the SPO/AOR, but the SPO/AOR will not be able to view, edit, and/or submit the supplemental funding request since SPO and AOR roles and supplemental funding request submission are not supported in the demo site. In addition, no system-generated email notifications will be created or sent to the SPO/AOR in the demo site.

You must first have the Proposed Postdoctoral Fellow role to initiate a supplemental funding request for a fellowship award in the demo site. A Proposed Postdoctoral Fellow role is different than a PI role. Demo site postdoctoral fellowship awards will only display and be available for selection for users preparing a supplemental funding request in the demo site as a Proposed Postdoctoral Fellow.

After signing in to the Research.gov supplemental funding request demo site, a message box will display with demo site information. From within the message box, click the Add a New Role hyperlink. Proceed to complete the required information as appropriate. Once the role has been added, allow up to 60 minutes for the system to process the request. Then you will need to sign out of Research.gov and sign back in again before initiating and preparing a supplemental funding request for a postdoctoral fellowship award.

Yes. You can add real subaward organization(s) to any supplemental funding request that’s created in the demo site. However, no system-generated email notifications will be created or sent to personnel affiliated to the subaward organization(s) when their organizations are added to your demo supplemental funding request.

No. All system-generated email notifications are disabled in the demo site.

The supplemental funding request demo site currently only supports the initiation, preparation, and editing of supplemental funding requests.

Supplemental funding requests created in the demo site will be available for six months and then will be deleted by NSF. Neither NSF nor users will be able to access deleted demo supplemental funding request data. If your demo supplemental funding request was created within the previous six months and your supplemental funding request data is not visible, please contact the NSF IT Service Desk at 1-800-381-1532 (7:00 AM - 9:00 PM ET; Monday - Friday except federal holidays) or via  rgov@nsf.gov for assistance.

Yes. All compliance checks that are enabled in the actual Research.gov Supplemental Funding Request Submission System also apply to supplemental funding requests in the demo site. The demo site can be used to check compliance of uploaded supplemental funding request documents (e.g., Collaborators and Other Affiliations and Biographical Sketch). Refer to the Automated Compliance Checking of NSF Proposals   page for the current automated supplemental funding request checks.

No. Supplemental funding request data created in the demo site will not be displayed in and cannot be transferred to the actual Research.gov Supplemental Funding Request Submission System. Supplemental funding request data created in the demo site is only available in the demo site.

If any of your active awards lists you as a PI, co-PI, or Postdoctoral Fellow and the selected award also has co-PI(s), those co-PI(s) would be included in the demo supplemental funding request. In this scenario, these co-PIs will be able to access, view, or edit the supplemental funding request in the demo site for the selected award.

Other individuals can also view or edit a supplemental funding request that you create in the demo site if you add the individual to the supplemental funding request as an OAU by entering their NSF ID.