Tag Archives: RRF

If your sponsor is the Royalty Research Fund, you will see this section. The fields are required.

Please also refer to the Instructions for Preparing an RRF Proposal for more details on completing an eGC1 for the RRF.

additional information for r r f applicants

Research Area
Select the one area that best classifies the research. If unsure, consider reviewing the RRF Committee Members list and their departmental affiliations.
The areas are:
  • Arts or humanities
  • Social or Behavioral Sciences
  • Physical Sciences
  • Engineering
  • Basic Biological or Biomedical Sciences
  • Clinical Biomedical Science
Application for RRF Scholar? (one quarter teaching release)
Answer Yes or No. If Yes, be sure to document your teaching load in section E of the Description of Research.

November 2013 SAGE Maintenance Release

New Features

Additional FG-3 compliance question validation for RRF eGC1s

  • eGC1s that have Royalty Research Fund (RRF) as the sponsor will display a validation error if question FG-3, the question about F&A cost reimbursement, on the Compliance Questions page is marked as ‘Yes’. RRF requires FG-3 to always be marked as ‘No’, so this validation error is intended to ensure that the eGC1 preparer selects the correct response prior to completing the eGC1.

Increase character limit in “Reason” field when adding Approvers and Watchers

  • The “Provide a reason” field when adding an Approver or Watcher on the Approval Flow Screen has been increased from 250 characters to 1000. Department and School reviewers who add additional Approvers and Watchers like to include detailed instructions in that comment box and needed a higher character limit.

We now will show all recipients on the TO line of SAGE auto-generated email notifications.

  • SAGE users will be able to see all persons who received the same Auto-generated SAGE email on the TO: line of the email. This was a frequent request from campus through our help desk and survey responses.


Inadvertent sending of disclosure notifications

  • Fixed the system to prevent investigators from receiving disclosure notifications when an old awarded eGC1 is opened. The system will now only trigger disclosure notifications when there is an investigator change made to the eGC1 (addition of an investigator or change of personnel to an investigator role).

HSD JIT email notifications are suppressed for RRF eGC1s

  • Human Subjects Just-In-Time emails will no longer be sent to the owners of eGC1s where the Royalty Research Fund (RRF) is the sponsor. RRF is an internal UW sponsor and operates differently than external sponsors. Unique characteristics of RRF opportunities include shorter application/review/award timelines and the lack of “fundable score” notifications. These unique characteristics therefore made the Human Subjects JIT email irrelevant and confusing for the owners of the eGC1.

New clarifying message displayed when clicking on Investigator Disclosure History and FIDS Profile is not yet established

  • If an Investigator has never completed a disclosure in FIDS, or does not have any disclosure history for the past 12 months, a new user-friendly message stating there is no history will display when the Investigator Disclosure History link is clicked.

New error message displayed when you have attachment upload errors due to hidden or invalid characters in file name

  • A new error message will display in SAGE if you attempt to upload eGC1 attachments with invalid characters in the file name. To correct this issue, rename the file on your computer by directly typing in the characters before attempting to upload it in SAGE.

For RRF grant applications, the “Dates Requested” should be given the following standard values:

Fall Round Spring Round
Begin Date January 15 of next year June 15 of the current year
End Date Start date plus one year Start date plus one year
Example Fall Round 2019 Spring Round 2020
Begin: 01/15/2018 Begin: 06/15/2020
End: 01/15/2019 End: 06/15/2021

Please refer to the Instructions for Preparing an RRF Proposal for more details.