Award Management (Post-Award)

Effort Reporting

Subawards

Incoming Contract Contact by Assigned Academic Unit

Email and Phone: preaward@uconn.edu / 860.486.3622

• Do you have a proposal-specific issue? Please contact your SPS assigned proposal reviewer (see below for portfolio assignments) for assistance via email or Teams call, since they will be most familiar with your proposal.
• Not sure who your assigned proposal reviewer is? For this or non-urgent matters, please email preaward@uconn.edu.
• For more urgent assistance, such as when you are unsure who is reviewing or you have been unable to reach your reviewer,
  please email spshelp@uconn.edu, or call 860.486.1023. Both are actively monitored during regular business hours.

Pre-Award Contact by Assigned Academic Unit

Post-Award Contact by Assigned Academic Unit

InfoEd offers investigators and administrators easy access to a host of information regarding their sponsored projects. Key features include the ability to track project funding status, research compliance approval status and requested/awarded revenue. For more information about use of InfoEd at UConn and access to How To guides, visit the InfoEd page. To login to the system, visit https://www.infoed.uconn.edu using your UConn NetID username and password.

The eRA Commons system is an online interface where grant applicants, grantees, and grantor agencies can access and share administrative information relating to research grants as they are received by NIH via ASSIST or Grants.gov. The eRA system allows Principal Investigators to track their applications; view summary statements and score letters; view notice of awards; submit just in time information; access eSNAP Progress Reports, Financial Status Reports and final closeout reports; and no-cost extensions.

eRA Commons registration is required prior to initiating an NIH proposal. To register for an eCommons account, complete the NIH eCommons Account Registration Form below. If you already have an ID and password, click on the second link below to login to eRA Commons.

NIH & Grants.gov

The University of Connecticut is already registered with Grants.gov. Investigators and departmental personnel need not register. NIH provides guidance on submitting applications through Grants.gov at the following sites:

Instructions for Routing NIH Proposals via Grants.gov. Internal paperwork must be routed through SPS before it is submitted electronically through Grants.gov.

1. The routing process should be initiated 5 business days before the deadline date. This allows SPS to review and approve the proposal prior to submission.
2. The proposal will not be submitted electronically to NIH until SPS receives the complete proposal package, and it has been reviewed and approved. The “complete proposal package” consists of:
   • Internal Proposal Review Form with signatures
   • Budget and Budget Justification
   • Grants.gov application

The PI does not submit the proposal to NIH. Only SPS has the authority to submit the proposal to NIH after receiving full access permission from the PI.

1. The PI will complete the electronic application and email to preaward@uconn.edu.
2. SPS will print the application, review for compliance with application instructions and request additional information and/or corrections as necessary.
3. The PI will be notified when the application has been reviewed and approved.
4. The final version must be reviewed prior to submission.

The Principal Investigator may submit a draft application to SPS for review and approval. The PI may submit draft attachments in the application for review and continue to update their science during the review process.The final application should be submitted to SPS 2 business days before the deadline date.

Do not wait until the last minute to deliver the final proposal package.

The grants.gov server has been known to “bog down,” particularly on deadline dates. This may result in missing the deadline.

Remember: Submission to Grants.gov and the NIH is a multi-step process. Grants.gov processes a series of validations prior to sending the application to the NIH. NIH, in turn, processes a series of business process validations prior to accepting the application.

A series of email messages will be sent to the PI and SPS when the proposal is submitted via Grants.gov.

The PI must have an eRA Commons account in order for the application to be validated by NIH. Once an application completes validation by Grants.gov, it is sent to the NIH. In order for the application to be validated by the NIH, each PI must have an eCommons account (Credential Log-In) in the NIH eRA Commons system.

If the application meets NIH validation requirements, the application is posted in the PI’s eRA eCommons account. The PI and SPS need to check the assembled application in eCommons to ensure the application is complete and has no system conversion issues. If the application did not meet NIH validation requirements and errors were generated, a corrected application must be submitted prior to the submission deadline. If warnings were generated upon validation and the PI would like to address, the previous application must be rejected and a corrected application must be submitted prior to the submission deadline.

Additional information for NIH submission:

• NIH Website
• Program Deadlines
• Unsolicited Program Applications – Parent Announcements
• NIH Policies and Guidance
• News from NIH
• NIH Quick Guide

NSF FastLane

FastLane, NSF’s interactive real-time grant management system, is used to conduct NSF business over the internet. Research.gov registration is required prior to initiating an NSF proposal.   To register for an account, complete the  Account Registration Form below. Once completed, SPS will receive an email notification for Research.gov and approve the registration.  Step-by-step instructions can be found in the Account Registration Guide.   If you already have an ID and password, click on the second link below to login to Fastlane.

• Account Registration Form
• Login to FastLane
• Fastlane Proposal Preparation
• FAQs on Proposal Preparation
• FastLane Help

Instructions for Routing NSF Proposals via FastLane

Internal paperwork must be routed through SPS before the proposal is submitted electronically through NSF Fastlane.

1. The routing process should be initiated 5 business days before the deadline date. This allows SPS to review and approve the proposal prior to electronic submission through NSF FastLane.
2. The proposal will not be submitted electronically to NSF until SPS receives, reviews, and approves the “complete proposal package.”  The “complete proposal package” consists of:
   • Internal Proposal Review Form with signatures
   • Budget and Budget Justification
   • Access to Fastlane application

The PI does not submit the proposal to NSF. Only SPS has the authority to submit the proposal to NSF after receiving full access permission from the PI. The PI may only “Allow SRO [Sponsored Research Office, i.e. SPS] Access.”

• The PI will complete the electronic proposal in Fastlane and “Allow SRO Access”. SPS will print the proposal, review for compliance with proposal guidelines, and request additional information and/or corrections as necessary.
• The PI will be notified when the application has been reviewed and approved.
• The PI will notify SPS when the proposal is finalized and is ready for submission.
• The final version must be reviewed by SPS prior to submission.

Understand the different levels of allowing SRO Access.

Pressing the “Allow SRO Access” button within FastLane directs the PI to a screen entitled “SRO Access Control,” where the PI should choose one of three options:

1. Allow SRO to only view proposal but not submit.
2. Allow SRO to view and edit but not submit proposal.
3. Allow SRO to view, edit and submit proposal.

The third option can be activated by the PI at any stage of the proposal. Selecting the third option will not be interpreted by SPS as a signal to submit the proposal to NSF unless the PI previously indicated otherwise. The PI should contact SPS when the proposal has been finalized and is ready for submission.

The Principal Investigator may continue to edit a proposal after granting SRO Access. Remember: two events need to occur before SPS will submit a proposal to NSF:

1. SPS must receive and approve the complete proposal package, as described above.
2. From within the “SRO Access Control” interface, the PI must select the third option, “Allow SRO to view, edit and submit proposal.”

Do not wait until the last minute to deliver the proposal package or “Allow SRO Access.”

The FastLane server has been known to “bog down,” particularly on deadline dates.  This may result in missing the deadline, in which case the PI would need to seek an extension from the Program Officer. An email message will be sent to the PI when the proposal has been submitted via FastLane.

Instructions for Submitting Subawards to NSF

All UConn personnel who plan to submit subaward budgets via FastLane must first be registered FastLane users. If you are not a registered user, please complete SPS’ online registration form (see link above). Participation as a subawardee entails two distinct administrative responsibilities.

1. FastLane Portion

• The PI from the Lead Institution assigns a Personal Identification Number (PIN) to the proposal and then shares that PIN and Proposal ID with the UConn subaward applicant.
• The UConn subaward applicant then logs in with last name, NSF ID, FastLane password, and the PIN and Proposal ID#. This provides access to the Llead Institution’s proposal and enables full functionality including the uploading of budgets, letters of support, biographical sketches, and etcetera.

2. UConn Portion. In addition to FastLane requirements, there are several documents that the UConn subaward applicant is required to submit to SPS for review and approval:

• Internal Proposal Review Form with signatures
• Signed Significant Financial Interest Disclosure Forms for all key personnel
• Completed Cooperating Institution Consortium Statement
• Budget and Budget Justification
• Scope of Work – a narrative description of the subawardee’s role in the lead institution’s project.

NSF Data Management Plan Requirements

National Science Foundation (NSF) Cost Sharing Policy Guidance

NSF policy states that the inclusion of voluntary committed cost sharing is prohibited in all proposals except when required in the NSF solicitation.  SPS has guidance available to assist you during proposal preparation and to help to ensure that applications are compliant with NSF and University policy including situations where senior personnel do not request salary for their effort on the project.

Additional information regarding NSF submissions

• Guide to NSF Programs/Browse Funding Opportunities
• Program Deadlines by Date
• NSF Proposal & Award Policies & Procedures Guide
• News from NSF
• NSF Revised Cost Sharing Policy
• FAQs on Revised Cost Sharing Policy