The Advanced Search link on the My Approvals page displays the search criteria which you can use to find specific eGC1s or Advance Budget Requests.
You can search on any single field or a combination of the criteria to locate items. More specific searches will return fewer results.
||Enter the entire eGC1 or Advance number with the prefix. For example, “A12345” or “ADV12345”.
||Enter any of the words or string of letters contained in the title. You must enter at least three characters.
|Full Application Title
||Enter any of the words or string of letters contained in the title. You must enter at least three characters.
|PI name (last, first)
||Enter the last name, or the last name plus first initial, or the last name plus first name. For example: Smith; Smith, J; or Smith, John. You may also enter just the beginning of the last name as long as you enter at least two characters.
|Org Code Receiving Funding
||Enter three or more starting digits of the organizational code. See the Organization Code description for information about the codes.
||Enter any of the words, string of letters contained in the sponsor name, or the sponsor’s acronym. You must enter at least two characters.
|Date Approved After
||Enter a valid date (mm/dd/yyyy). For example, enter 6/1/19 to display eGC1s that you approved after that date.
|Date Approved Before
||Enter a valid date (mm/dd/yyyy). For example, enter 6/1/19 to display eGC1s that you approved before that date.
|My Approval Status
||Choose an approval status from the drop-down menu. eGC1s in the selected status will appear on the display list. Choices are:
- En Route
- Waiting Approval
||Choose an item status from the drop-down menu. Only Items in the selected status will appear on the display list. Some of the statuses only apply to eGC1s or Advances, as noted. Choices are:
- In OSP (only applies to eGC1s)
- Approved (only applies to eGC1s)
- In GCA (only applies to Advances)
- Processed (only applies to Advances)
- Awarded (only applies to eGC1s)
- Denied by Sponsor (only applies to eGC1s)
- Permanently Withdrawn (only applies to eGC1s)
Select Search to display the results list, which displays the following information:
- Item # – select this to view the approval flow
- PI Name
- Org Recvg Funding
- Short Title
- Sponsor Name
- My Approval Status
- My Approval Date
- Item Status
- Ready to Submit
The “approval flow” includes all UW individuals, divisions, departments, deans, and/or compliance offices (including OSP), that must review and sign off on a proposal before its submission to the sponsor. Review: How the Flow is Generated.
SAGE automatically routes the proposal to the individuals and units included in the approval flow. The system also sends email notifications of pending approvals to Approvers on campus. OSP uses their SPAERC (Sponsored Projects Administration & Electronic Research Compliance) tasklist to manage proposals waiting for approval. Review: Reviewer Email Notifications.
As a reviewer, you can access the approval flow for an application from the Approvals tab in SAGE. You have the option of viewing a graphical or a textual representation of the approval flow. If you are a preparer or owner of the eGC1, you can also access the approval flow from the Certify & Route page of the application.
Generally, anyone who appears on the SAGE approval flow is referred to as a reviewer. More specifically, reviewers are either Approvers or Watchers.
- Monitor the status of an eGC1; they are not required to approve the eGC1
- May choose to “mark” the application as Watched
- May add a comment that then becomes part of the permanent record of the proposal
The item status indicates where an eGC1 or Advance Budget Request is in the overall creation and routing process. Use the check boxes to filter your approvals list. Some check boxes only apply to one item type which is included in the label. For example, In GCA (Adv) indicates that the In GCA status only applies to Advances.
The following image shows the My Approvals page with the My Item status choices displayed.
The item statuses are:
||Items which have been completed and are currently routing to campus approvers.
|In OSP (eGC1)
||eGC1s which the PI and all required campus units have approved, and OSP has received for review.
||eGC1s which OSP has approved.
|In GCA (Adv)
||Advances which the PI and all required campus units have approved, and GCA has received for review.
||Items which someone with owner or edit access has withdrawn from routing to edit.
||Items which a reviewer has returned for modifications.
||Advances which GCA has reviewed and completed.
||eGC1s which the sponsor has awarded.
|Denied by Sponsor (eGC1)
||Applications which the sponsor has denied. SAGE users can change an application to Denied by Sponsor status if the sponsor is not the UW Royalty Research Fund (RRF), or if there is no child FA. OSP can also change an application to this status.
|Permanently Withdrawn (eGC1)
||Applications which will not be submitted to the sponsor. SAGE users can change an application to Permanently Withdrawn if there is no child FA. OSP can also change an application to this status.
When you are logged in to SAGE, but have not been actively using the system for 40 minutes, you will see a dialog message 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.
Campus research teams and related central offices use the SAGE Suite electronic research administration system to manage application proposals and related items. The suite is comprised of three components that access the shared SAGE Suite database.
- SAGE: System to Administer Grants Electronically – used by campus researchers and administrators
- SPAERC: Sponsored Projects Administration & Electronic Research Compliance – used by the Office of Sponsored Programs (OSP)
- SERA: System for Electronic Research Accounting – used by Grants and Contract Accounting (GCA)
- FIDS: Financial Interest Disclosure System – used by researchers designated as investigators and 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
||WHY / WHEN
|Create SAGE Budgets
||Centralizes data gathering for salaries, benefits, 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 be mapped into the form.
|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. It is used only by the UW and does not go to the sponsor.
A Grant Runner application includes, in addition to the standard eGC1 pages, the sponsor forms for NIH. It is submitted system-to-system by OSP.
|Approve routing applications
||Used by the Principal Investigator, Multiple-PI, Application PI, academic reviewers (division, department, dean) and compliance reviewers (human subjects, animal use, EH&S, etc.) to view and approve the application. At each approval, a PDF snapshot of the application is captured and attached to the eGC1 on the 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. These are referred to as “ad hoc” reviewers (approvers or watchers).
|Request an advance budget number for awards
||Used when the 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 SERA.
|Create subaward requests for awarded applications
||Used when a research proposal has been awarded and part of the award needs to go to the subrecipients (subcontractors) that are the UW research team’s collaborators. For a new award, a “new” subaward request (SA) is created along with its parent subaward (SC). For an ongoing award, a “modification” request would be created within the existing subaward (SC).
SPAERC: Sponsored Projects Administration & Electronic Research Compliance
WHO: Office of Sponsored Programs (OSP)
||WHY / WHEN
|Review and approve applications
||OSP reviews the information on the eGC1, such as the sponsor proposal information and compliance questions, after all campus reviewers have approved. When OSP approves the application, they place it into a new or existing Cycle.
|Add Approved applications to a Cycle
||A Cycle holds a “competing segment” for a research team/project/sponsor combination. It’s a container to keep applications, their related advances, funding actions, admin actions, and subawards together. One cycle can be “related” to another, so that more than one segment is associated.
A Cycle is automatically deleted when the last item in it is removed.
|Create various types of Administrative Actions as needed
||Administrative Actions document various related agreements, adjustments and/or changes, and the finalization of a research project. These actions all appear in the project’s cycle, associated to their appropriate parent item.
Note that all actions (including Funding Actions) start as “unidentified” ones, with a prefix of AA. They are then converted to the specific type needed.
- Non-Award Agreement (NAA) records a generic agreement not pertaining to funding.
- Pre-Award Notification (PAN) records a change to the proposed project before the sponsor awards funding.
- Post-Award Change (PAC) records changes to the project after the sponsor awards the funding.
- Close Out (CO) records the tracked activities to terminate a project upon completion of the research.
|Create Funding Actions (FA) for awards
||When an application is awarded by the sponsor, OSP creates a Funding Action as a child of the application. Depending on answers to certain compliance questions, there may be automatic “holds” applied.
Once the FA is completed (and all holds are cleared), it is trasmitted to SERA for GCA to establish a budget in the financial system (if not already done via Advance Request).
||OSP reviews the subaward requests, and negotiates the contract with the subrecipient. The request moves through several statuses until, when the agreement is “fully executed” the request becomes Active. It is automatically “Expired” once the End Date is passed.
SCs and FAs can have a many-to-many relationship. The system enforces that all related FAs and SCs must be within the same cycle.
SERA: System for Electronic Research Accounting
WHO: Grant & Contract Accounting (GCA)
||WHY / WHEN
|Process Advance Budget Number Requests
||Received from the research team, this allows the team to spend award money before the actual award arrives. GCA adds a budget number to the ADV and sets up that budget in the financial system. As part of completing the ADV, the system sends a notification to the requesters.
|Process Funding Actions
||Received from OSP. GCA adds a budget number, if needed, and sets up the budget in UW financial system. As part of completing the FA, the system sends a notification to the requesters, and the first-level reviewers for the organization code receiving funding.
|Process Post-Award Changes
||Received from OSP. Not all types of PACs are sent on to GCA. As part of completing the PAC, the system sends a notification to the requesters.
|Create “Other” items
||Created as needed for various budgetary processes. These items only appear in SERA.
FIDS: Financial Interest Disclosure System
WHO: Any research personnel designated as an “Investigator” on the PI, Personnel, & Organizations page of the eGC1.
||WHY / WHEN
|Create a Financial Interest Disclosure for an eGC1
A disclosure for a CoMotion tech transfer agreement or IRB approval
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. 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.
Note: only a UW NetID is needed to access FIDS.
This component of SAGE (System to Administer Grants Electronically) is an electronic workflow to route eGC1s and Advance Budget Requests for approval by associated departments, colleges, compliance offices, and the Office of Sponsored Programs.
SAGE – the System to Administer Grants Electronically – is the web-based system used by faculty, researchers, administrators and staff.
You can stay up-to-date on changes in SAGE (and FIDS) by subscribing to our Office of Research Information Services (ORIS) News.
The core SAGE system allows you to carry out several tasks.
- SAGE Budget helps you create an accurate budget for your grant proposal. It auto-populates data from the payroll and financial systems, helps you select proper rates, and calculate totals automatically. You can connected a budget to a standard or Grant Runner eGC1 to populate budget data.
- eGC1 Forms are the electronic Grants and Contracts forms you use to route your grant proposal through the University’s internal compliance process.
- Grant Runner applications combine the eGC1 and sponsor forms for some NIH funding opportunities requiring SF424 R&R forms, including Modular, Detailed and Subaward Budgets. With the click of a button, OSP can electronically submit your application via Grants.gov to the sponsor.
- Approvals is the electronic routing engine that stages eGC1s for approval by associated departments, colleges, compliance offices, and the Office of Sponsored Programs.
- Advances creates an online request form for an advance budget number.
- Subawards submits a request for a new subaward or a modification of an existing one.
The text version of the page has an Approval Flow Details section instead of the graph. It consists of a table listing the units and individuals who need to approve or watch this application.
The table columns are:
- Rule Type: The reviewer, and when applicable, their affiliated unit.
- Approval Status: Waiting Approval, En Route, etc. See the Approval Statuses article for more details.
- Acted On By: The name of the person who approved or watched the application.
- Date: The date and time the approval or watched status changed.
- View Reviewers: Click to display the Reviewer Details for this role, which includes the reasons for this reviewer.
The following image shows an example of this section.