This section displays general information about the subaward.
The following image shows an example of this section.
Field
Description
Project Title
Populated from the full title of the application associated with the initial subaward request.
Project Short Title
Populated from the short title of the application associated with the initial subaward request.
Subrecipient
The institution receiving the subaward.
Note: If the subrecipient’s certification status is expired and needs recertification, a prompt will display beneath the subrecipient name, as shown in the image above
If you would like to help facilitate that process:
Click the link to the Subrecipient Certification PDF form
Have the subrecipient complete the form
Upload the signed form as an attachment in your Subaward Request
The form is not required prior to submission of the subaward request. This status prompt and link will also display in the Subaward Overview Summary section.
Populated from the initial (New) subaward request. The Start Date for any modification requests will populate from that of the subaward. The End Date will adjust based on any modification requests that reach Active or Expired status.
Total Subaward Amount
Calculated field that includes any supplemental funding or de-obligation in modification requests that have reached Active or Expired status.
Automatic carry forward authorization by PI?
Yes, No, or Not Applicable, as indicated in the initial subaward request.
Subaward Contacts
Review the Subaward Contacts article for details on managing the contacts information.
Request in Process
When a subaward request has a status of Composing, In OSP, OSP Assigned, Issued, Withdrawn or Returned, it will display in this section.
Note: Only one request can be in process at a time.
The following image shows this section.
Summary information displays for the request.
Field
Description
Request Type
“Initial” for a new subaward; one or more types for a modification
Modification Number
OSP enters this value. It confirms the sequence of changes to the subaward agreement.
Current Status
Status of the request
Request End Date
End Date for the request
Request Amount
Amount for the request
BPO Number
PO Number for the request
OSP Assigned to
Upon submission, the system assigns a request to Subaward Intake. OSP will then assign it to the individual who will review it, generally when it moves to OSP Assigned status.
Latest Update
The latest status change event for this request. It shows who made the change and when, and includes a description and any related comments.
You can select the request number or the Open link to see the request details page.
From this section, you can also Withdraw a request in In OSP status, or cancel a request that is in Composing, Withdrawn or Returned status.
If there is no request in process, a Create Modification Request button will appear. Select it to create a new modification.
Processed Requests
This section lists all of the requests associated with this subaward, with the most recent listed first. The following image shows an example of this section.
Field
Description
Subaward Request Number
The subaward request’s system-generated unique number
Modification Number
OSP enters this value. It confirms the sequence of changes to the subaward agreement.
Request Type
Initial for a New request or one or more of the following types for Modifications:
Extension
Early Termination
Supplement
De-obligation
Scope Change
Other Modification
Note that a modification cannot be both an Extension and an Early Termination.
Subaward requests can now be submitted using SAGE. With the transition to Workday, subawards are now associated with Awards, rather than Funding Actions (FAs). To set up a new subaward, users will search and select their award, and the eGC1 data will default based on the award selected.
Funding Action (FA) Validation and Lookup Removed
Since subawards are now associated with awards, the subaward FA lookup is no longer active or needed, and the validation has been removed. For legacy subawards, the FA fields will continue to display for reference.
Holds on Award Setup (ASR) and Modification (MOD) Requests
OSP and GCA Can Apply Holds to ASRs and MODs
OSP and GCA can now set and remove holds on ASR and MOD Requests. A new Holds section is available in the left navigation. After saving holds, an entry will display in the Comments & History section of the ASR/MOD.
History of Holds Added to Comments & History Section
Campus, OSP, and GCA can view the history of holds activity on the Comments and History section of the ASR or MOD request.
Holds Banner Displays on ASR and MOD Requests
When holds are applied to an ASR or MOD request, users will now see a banner at the top of the request, alerting them to the hold. The campus banner will be informational only, and highlighted in blue. The OSP and GCA banner will be red, and indicate any action that may be needed before moving the item forward in the workflow.
Campus banner
OSP & GCA banner
Required Fields on Award and Budget Setup
Required Fields on SAGE Budget Worksheets
The SAGE Budget worksheet settings have been updated to show an asterisk next to fields that are required for ASR and MOD requests. These fields support the Workday award data needs.
In the SAGE Budget Salary and Benefit Costs section, additional help text has been added to remind campus that a person must be entered with the Principal Investigator role to provide the necessary grant PI data to Workday for award setup.
Required Fields on Award Setup Requests
Required fields on the Award Setup Request now display an asterisk next to the field label. When the user clicks in a required field and navigates away, additional red highlighting will draw their attention back to the fields required.
Miscellaneous Maintenance
eGC1 Status Updated to “Awarded” When Awards Are Processed
When awards are set up in Workday and the award setup request is marked as “Processed” in SAGE, the associated eGC1 status will now change from “Approved” to “Awarded.”
OSP Ability to Change the Linked eGC1 on Award Setup Requests
When OSP initiates an ASR and while it is in “OSP Setup” status, OSP can now change the linked eGC1 if an error has been made, prior to sending the ASR to campus. OSP will need to refresh the “Access & Roles” section after changing the eGC1 to see updated eGC1 data.
Modification Start and End Dates Display for Schedule Changes
On Modification Requests, when users select the Schedule Changes category, the “Current Authorized Spending Start Date” and “Current Authorized Spending End Date” fields will be visible and enabled for users to enter the dates. Existing MOD requests already processed with the Schedule Changes category will display the date fields without any dates populated.
Removal of Deny Reason for Requests
An issue was preventing the deny reason on requests from saving properly. Until a full fix can be completed, in the interim, the deny reason field has been removed and OSP or GCA will now enter the reason as a comment instead. The denial reason field will be added back into a future release.
Advance Extension Requests No Longer Show Former Budget Numbers
The former budget numbers no longer display for users on new Advance Extension Requests.
Award Request List Default Set to 25 Rows for OSP and GCA
In order to improve performance and reduce load on systems, the defulat setting of the Award Request List for OSP and GCA will initially show 25 rows instead of 50 rows. Users can still set it to up to 50 rows if needed, for now, but with dome deteriorated performance expected.
Fix: Truncated Comments on Requests with URLs
ASR and MOD request comments with URLs in them now show proper alignment without truncation.
Fix: SAGE Budget Personnel Side Panel Freezes
The SAGE Budget TBD personnel entry has been updated to prevent side panel freezing when users clicked out of fields quickly, prior to SAGE saving the data.
Update: Missing PI Validation Message on Award Setup Requests
The language used on the Award Setup Request Review and Submit page when the SAGE Budget worksheet PI is missing has been updated to direct users back to SAGE Budget to add a worksheet PI.
Fix: Cannot download previous version of attachments on Requests
Users can now select the current or prior version of attachments on ASRs, MOD, and Advance requests.
Fix: Animal Use Protocols Not Always Saving Country Data
An issue with the saving of “Country” data when a new institution was added to Animal Use protocols on the eGC1 has been fixed.
Due to performance issues, we have temporarily deactivated the “Processed” status filter on the SAGE Advance Tasklist. While we work on improvements, this temporary solution will protect system performance and mitigate risk. In the meantime, if campus users need to locate a processed advance, they should use Advanced Search and search by either the Advance number or the eGC1 number to find an item.
Please note that SAGE Central filters will not change, but we recommend avoiding filtering for all “Processed” advances until we patch the issue next week.
User Interface Design Component Updates
A required Angular Material version upgrade has been completed, which has slight impacts to the SAGE user interface. The design changes of note include the following:
SAGE Budget, Advances, and Awards Sections: Excess table spacing has been reduced, small font sizes have been increased, and all capital letters on buttons and table headers have been removed to improve readability and accessibility.
SAGE Budget Icons: Subaward and Fabrication worksheet icons have been updated in the left navigation and the Budget Summary section within the Other Costs table. The More Actions menu (three dots) has been replaced with a Delete Worksheet button for Internal, Subaward, and Fabrication worksheets in the left navigation.
Campus research teams and related central offices use the SAGE Suite electronic research administration system to manage application proposals and related items.
SAGE: System to Administer Grants Electronically – is used by campus researchers and administrators
SAGE Central is used by both the Office of Sponsored Programs (OSP) and Grants and Contract Accounting (GCA)
In addition, FIDS: Financial Interest Disclosure System is used by researchers designated as investigators; it integrates with SAGE.
The following set of tables gives a high-level overview of who uses each of the different components, and describes the possible actions and the why and/or when.
SAGE: System to Administer Grants Electronically
WHO: Campus research administrators, Principal Investigators, campus reviewers, compliance reviewers
ACTION
WHY / WHEN
Create SAGE Budgets
Centralizes data gathering for salaries, benefits, and F&A rates. It can be connected to an application, which automatically populates the eGC1 budget data on the Budget & Fiscal Compliance page. Any changes to the budget will update in real time when the eGC1 Budget & Fiscal Compliance page is viewed.
In addition, if your eGC1 is a Grant Runner application using the RR Detailed Budget form, your budget data will appear in the form.
When creating an Award Setup Request, you will need to connect a budget.
Create applications (standard or Grant Runner)
Required for all sponsored research. The standard eGC1 pages of the application are, in effect, an approvals routing cover letter for the proposal. Only the UW uses the eGC1; it does not go to the sponsor.
A Grant Runner application includes, in addition to the standard eGC1 pages, the sponsor forms for NIH. OSP submits the application “system-to-system.”
Approve routing applications
The Principal Investigator, Multiple-PI, Application PI, academic reviewers (division, department, dean) and compliance reviewers (human subjects, animal use, EH&S, etc.) view and approve the application. At each approval, SAGE captures a PDF snapshot of the application and attaches it to the eGC1’s Approvals History & Comments page. Copies of the attachments are also captured.
Administrators and reviewers have the option to return the application to the research team for changes. They can also add other reviewers (as individuals or a group) to the approval flow as needed. These are referred to as “ad hoc” reviewers (approvers or watchers).
Request an advance budget number for awards
Used when a research proposal is being awarded by the sponsor, but the actual award has not yet arrived. It requests GCA to set up a budget account in the financial system so the research team can start spending the anticipated award money. The preparer completes the request in SAGE, then GCA processes it in SAGE Central.
Create Award Setup Requests and Modification Requests for awarded eGC1 applications
Used when a research proposal has been awarded and the award has been received. A “new” Award Setup Request (ASR) is created. For an ongoing award, a Modification Request might be created.
SAGE Central
WHO: Office of Sponsored Programs (OSP), Grant & Contract Accounting (GCA)
ACTION
WHY / WHEN
Review and approve eGC1 applications
OSP reviews the information on the eGC1, such as the sponsor proposal information and compliance questions, after all campus reviewers have approved.
Process Award Setup Requests
Received from campus for reviews and approvals. Forwards to GCA for integration into Workday, with Award budget number. As part of completing the Award Setup Request, the system sends a notification to the requesters.
Manage Actions
Will manage existing items while transitioning to SAGE Central and Workday.
Process Advance Budget Number Requests
Received from the research team, an advance allows the team to spend award money before the actual award arrives. GCA adds a budget number to the Advance and sets up that budget in the financial system. As part of completing the Advance, the system sends a notification to the requesters.
FIDS: Financial Interest Disclosure System
WHO: Any research personnel designated as an “Investigator” on the PI, Personnel, & Organizations page of the eGC1.
ACTION
WHY / WHEN
Create a Financial Interest Disclosure for an eGC1
or
A disclosure for a CoMotion tech transfer agreement or IRB approval
or
Complete an Annual Update disclosure
Investigators are required to disclose any significant financial interests (SFI) such as salary, equity, sponsored travel, etc., that might, or might appear to, bias their research.
An investigator must complete a disclosure for each eGC1, whether or not there are SFI that apply, before the proposal can be marked as Ready-to-Submit = Yes.
The disclosures are reviewed by the SFI Reviewer, in the central Office of Research, who determines if there is a potential for a Financial Conflict of Interest (FCOI). The review occurs at the time of award (just-in-time).
Annual Updates: All investigators are required to review and update their SFI at least once a year. The “year” is calculated from the date of the last disclosure created in FIDS. Investigators are notified by email 45 days prior, and again at 15 days prior, to the end of that year’s time.
Full details on using FIDS can be found in its User Guide.
Thanks to valuable user feedback, the Office of Research Information Services (ORIS) launched a redesigned SAGE Budget tool in 2020 with a more streamlined, efficient, and intuitive look and feel. This new design also lays a foundation for upcoming integrations between SAGE and Workday.
Over the last year, we’ve collected your feedback and have added several features to ensure the current SAGE Budget format meets all of your core needs (e.g. APL and Fixed Fee). We are now ready to retire the legacy format, which allows us to focus our continued enhancements in the new format only. This is especially important as we prepare for the critical role that SAGE Budget will play in communicating award budget information to the financial system when the UW goes live with Workday Finance.
Upgrading of all Legacy Budgets
With the retirement of legacy SAGE Budget, all existing budgets in the legacy format will be upgraded to the new (current) budget format. Upgrading means:
When you open your budget, it will open in the new (current) version.
Those who had access to the legacy budget will have the same access on the upgraded version.
On the History page, snapshots of previous budget versions will now display in the new (current) format.
All costs and settings (like targets and salary caps) that were enabled on the legacy budget will be enabled on the upgraded budget.
Note: Auto Adjusting Entries (AAE) will not be available in the new (current) format. AAE will be converted to a standard costs line on the primary worksheet, with a note, “Converted Auto Adjusting Line.” The following budget details will remain the same:
object/sub-object code
cost amount
periods
Budget List Updates
The following changes have been made to the budget list:
The option to create a legacy budget has been removed
The Format column has been replaced with a Created Date column
An “Upgraded” indicator displays when a budget has been upgraded by the system
The default sort order on the budget list remains the same, descending by last edited date. You can still search for your budgets by Principal Investigator (PI) name, budget number, or budget title.
Other Budget Updates (released in advance)
The default Prorated Direct Cost (PDC) rate that displays when you enable APL on a budget worksheet has been updated from 35.2% to 35.0%.
SAGE eGC1
Ad Hoc Approver Improvements
Two changes were made to the list of roles that display when adding an ad hoc approver to an eGC1 approval flow:
Several out-of-date roles have been removed.
The list has been alphabetized.
SAGE Subawards (released in advance)
Subaward Expiration Fix
Subawards that reached Expired status were not updating to Active status when a modification was processed which pushed the End Date into the future. That issue has been fixed so that the overall Subaward reflects accurate status information.
Subaward History Now Includes All Subaward Status Changes
The Subaward History now includes events for each time the Subaward Status changes. Previously, the Subaward History only included status changes for Subaward Actions. This will provide more information about when the overall Subaward transitioned through process steps.
When you are logged in to SAGE, but have not been actively using the system for 40 minutes, a dialog message displays indicating that your session will expire in 5:00 minutes. The dialog will continue to count down the time. You have the option to click “Keep Working” to re-activate your session.
If you do not click “Keep Working”, then when the time count reaches zero (0) minutes, your session will expire. Your browser will be redirected to a “session expired” page from which you can log back in to the system you were using. Any unsaved data at the time your session expires will be cleared.
The SAGE system has always timed out after 45 minutes of inactivity. We have now made the timeout more visible so you know that your session has expired, instead of sending you to the tasklist with no explanation.
The following image shows the session timeout dialog, with the time remaining until expiration and the instruction to click “Keep Working” if you want to continue to stay logged in.
NIH will require the use of FORMS-E application packages for due dates on or after January 25, 2018. Grant Runner now includes the FORMS-E version for the following agency specific forms.
PHS 398 Cover Page Supplement
PHS 398 Research Plan
PHS 398 Career Development Award Supplemental
PHS 398 Modular Budget (expire date change only)
PHS Assignment Request
PHS Human Subjects and Clinical Trials Information (New!!)
Federal-wide form updates that will also be incorporated into FORMS-E packages, and which are supported by Grant Runner, include:
New Human Subjects and Clinical Trials Information Form
Grant Runner now includes the new PHS Human Subjects and Clinical Trials Information Form. You will have the option of completing the form in its entirety directly in Grant Runner, or importing a completed PDF version of the form into Grant Runner. Due to the length of this form, it is recommended that you preview the form in Grant Runner or in PDF format, early in the proposal development process to plan appropriately for the information collection involved.
SAGE Subawards
Subrecipient Re-Certification Status and Form
When completing the subaward request in SAGE, a prompt will display below the subrecipient’s name if their certification status is in an expired state and needs re-certification. This prompt will have a link to the Subrecipient Certification PDF form that can be uploaded in the Attachments section of the Subaward Request once completed. Attachment of the Subrecipient Certification form is not required prior to submission of the subaward request. This status prompt and link will also display in the Subaward Overview Summary section.
SAGE eGC1
Non-Award Agreement Application Types
SAGE now provides a dedicated, streamlined eGC1 format for submitting Non-Award Agreements to OSP by requiring only the set of fields necessary for these application types. You will now select Application Types “Non-Award Agreement (new)” or “Non-Award Agreement (continuation)” for the following types of agreement:
Confidentiality Agreement
Data Use Agreement
Memorandum of Understanding
Unfunded Collaborative Agreement
Unfunded Research Agreement
Affiliation Agreement
Material Transfer Agreement
Note that you should select “Non-Award Agreement (continuation)” to extend an existing agreement beyond the initial term.
Activity Locations Survey
We want your feedback on the new look and feel of the Activity Locations page. Click the “Give Feedback” link at the top of that page and let us know what you do/don’t like about the design as we evaluate updates to other parts of SAGE.
Use the View Attachments button on the upper right of the Subaward Overview page to display the Subaward Attachments page.
This page lists all of the attachments associated with the subaward, grouped into Department Request Documents and OSP Documents. You can use the Filter function to display attachments for just a single request.
In addition to the standard information about an attachment, the list includes the Subaward Request Number.
To return to the Subaward Overview page, select the Close button below the list or use the breadcrumb.
This final release for the SAGE Subawards Project includes priority items requested by preparers as well as some updates that will allow OSP to manage subrecipient profile data more effectively.
Managed Access
To make it easier for subaward preparers to cover absences and to allow for broader department review and access to subawards, you can now add additional users (beyond the three UW contacts) with either read/write or read-only access.
Expanded Subrecipient Profile
To improve OSP’s ability to report subaward information to sponsors and auditors, we have added the following attributes to the subrecipient profile in SAGE:
Employer Identification Number (Federal Tax ID)
DUNS and DUNS +4
Country
Subrecipient Types have also been revamped to better align with reporting requirements.
Attachments Display Changes
From a link on the Subaward Overview page, you can now view a consolidated list of attachments for the entire subaward.
On the subaward request details page, the Attachments section now visually separates attachments that departmental subaward preparers uploaded from those that OSP did.
Performance Improvements
Using the Subawards section of SAGE and SPAERC will now be faster and more responsive, allowing you to accomplish what you need to get done with less waiting.
Improved Validations
The Start and End Dates on subaward requests are now checked by the system to ensure they make sense within the context of the broader award and subaward. This will help alert you to any easy mistakes made when preparing a request.
Other Enhancements
SAGE Tasklist
The SAGE tasklist now displays the most recent BPO number, rather than the one listed on the first request. Searching the tasklist will also now only return subawards where the most recent BPO matches your search criteria.
Subaward Overview Page
A visual cue has been added to the Request in Process section on the Subaward Overview page to make it easier for users to identify how to open the details of request.
A new Modification Number field has been added, which will be populated by OSP in SPAERC but will be visible on the Subaward Overview page in SAGE as well. The Modification Number will confirm the sequence of changes to the subaward agreement.
You’ll now see the BPO number associated with each request, within both the Requests In Process and Processed Requests section of the Subaward Overview, for easy reference.
