Some sponsors allow a Department chair to sign an eGC1 and proposal on behalf of a PI in his or her department. This requires an Escalation of PI Certification which is indicated on the Certify & Route page of the eGC1.
Be sure to notify the appropriate reviewer to approve the application for him or herself, as well as for the PI.
For information on the approval of applications in the PI’s absence, contact your department administrator/chair.
This component of SAGE (System to Administer Grants Electronically) is an electronic workflow to route eGC1s 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 to:
The core SAGE system allows you to carry out several tasks, including budget development, creating an eGC1, using Grant Runner to complete SF424 R&R forms for NIH opportunities, reviewing and approving applications, and submitting a request for a budget advance.
You can stay up-to-date on changes in SAGE (and FIDS) by subscribing to our Office of Research Information Services (ORIS) News.
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.
eGC1s are the electronic Grants and Contracts forms you use to route your grant proposal through the University’s internal compliance process.
A Grant Runner application combines 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.
This electronic routing engine stages eGC1s for approval by associated departments, colleges, compliance offices, and the Office of Sponsored Programs.
Use this part of SAGE to complete an online form to request an advance budget number.
Submit 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:
You can modify the Approval Flow at various times in the life-cycle of an application. You can either add additional nodes directly or the system may change the flow due to changes to a withdrawn or returned eGC1.
If you make changes to a withdrawn or returned eCG1, and none of the changes affect the approval flow, then when you re-completed the eGC1, it will continue routing to the next reviewers. Any campus approvals that already occurred will remain, and any that are “waiting approval” will receive another email notification.
However, if you update the list of research personnel or the organization receiving funding, this may add or remove nodes from the previous approval flow. When you re-complete the eGC1, the system compares the previous flow and the new flow. Any previously approved nodes will keep their approved status and information on the new flow. All reviewers on any new nodes will be notified at the appropriate time. The system will remove any nodes no longer needed.
If the changes to an eGC1 are substantial, it is up to the preparer and/or PI to notify any reviewers who have already approved it. If you decide that additional approval is necessary, you can add an ad hoc. Otherwise you might add a comment, or do nothing.
Regardless of what fields you change on a withdrawn or returned eGC1, the system does not change the assigned OSP person. This ensures that the OSP person who was reviewing the eGC1 will see it on their tasklist once you re-completed it. They can then reassign it as needed.
This is the visual graph of approvers and watchers. The graph begins on the left with the PI and ends on the right with the Office of Sponsored Programs (OSP). Directly under the PI node, is a node for the Preparer/Owners.
If there is an Application PI, that node is immediately to the right of the PI. If there are one or more Multiple PIs, they will follow the PI or the Application PI, if there is one. The Multiple PIs are displayed one below the other. Note that if the Multiple PI is a non-UW person, they will not appear on the approval flow.
The top line of nodes on the graphical version generally are the reviewers associated with the organization receiving funding. The order of other nodes is not fixed.
There is a Legend that defines what the colors of the nodes mean. The heavily outlined node on the graph indicates your location in terms of the overall Approval process.
Each node lists the person or unit reviewing, the role (for example: Div Reviewer), and the status.
In the example below, the nodes in green have been approved, and they list who the approver was. The outlined node is the one for this approver and shows a status of “Waiting Approval”. The node for OSP has a status of “En Route”.
This initial section explains your relationship to this application.
|Current Status||This approval status is based on you or your role and the current routing status of the eGC1.|
|Your action options||Based on your status with this eGC1, this field displays what actions you may take.|
|Reason for your review||This is the reason(s) you or your organization needs to approve this eGC1.|
Approvers (other than the PI) can only approve an eGC1 which is in Routing status. If you do not see the Approve or Return buttons, check the eGC1s status on the My Approvals page. The PI can approve an eGC1 in Composing status by completing it, or in Routing status by using the Approve button.
Use the Add Comment link to include a note which will display on the History & Comments page.
Use the Add Approver or Add Watcher link to include an additional approver or watcher in the approval flow. See the appropriate section for the steps to do this: Add Approver or Add Watcher.
The View eGC1 link opens the application in a new window, in a read-only mode. This allows you to review the details of the application.
The View Attachments link opens a new window and displays a list of all the attachments for this eGC1.
The PDF link opens a new window that displays a printer-friendly copy of the entire application.
This section lists selected fields from the eGC1 to help you confirm that you are viewing the correct item (eGC1 Application Details). The data fields include:
Only the person who has added an ad hoc reviewer node can remove it from the approval flow.
To start the process, click the Delete link in the graph node, or next to the approver on the text flow page. This opens the Remove Reviewer page in a pop-up window. The pop-up contains two sections: Application Details and Reviewer Details.
The Application Details section lists selected fields from the eGC1 to help you confirm you are viewing the correct item. The data fields include:
The Reviewer Details section lists the Role, Reason, and Status for this reviewer and includes a comments field.
Use the Comments required when deleting an ad hoc reviewer field to enter the reason for removal. Select the Remove button to complete the process or the Cancel link to return to the flow page.
Details about the removal of an ad hoc reviewer will display on the History & Comments page.
Definition of ad hoc: Formed, arranged, or done for a particular purpose only; from Latin, meaning “for this.”
An owner (PI, preparer, contacts), a person with assigned read/write access, or an approver, can add an ad hoc reviewer to the approval flow. These manually added reviewers can be for a particular role, such as a department reviewer, or can be a specific person.
Note: there is a known issue when the person with read/write access also has a Global Edit role for the corresponding organization code. The links to add an ad hoc reviewer will not appear. Contact the ORIS Help Desk for assistance.
The process to add an ad hoc approver or watcher is the same. The only difference is that the approver needs to take action and approve the eGC1, while the watcher is not required to act. For this section we’ll use the term “reviewer” to refer to either an approver or watcher.
The Add Approver or Add Watcher link allows you to add a person or role (for example: Dept Reviewer) to the Approval Flow. This function may be used when
Note: If a division, department or dean’s reviewer needs to re-approve an application, add the appropriate ROLE (not person) to the graph. The approval history will show the unit name and the name of the person who approved, providing a more complete audit trail.
The eGC1 must be in either Routing or In OSP status for you to add an ad hoc reviewer.
To begin the process, click on either the Add Approver or Add Watcher link to open the corresponding window. The following steps are the same for both.
The next step is select a location on the graph for the added reviewer based on an existing reviewer
Enter a comment to describe why this role or person needs to review this eGC1. This comment will display on the History & Comments page.
As an example, we chose Human Center Design Engineeing as the ad hoc role to add to the flow. The new reviewer was located in parallel with the existing Dept Reviewer for Bioengineering node. The image shows the new node directly above that of Bioengineering on the same thread of the graph.
On the node, the role description is Ad Hoc Reviewer. When the person who added the node views it, she will see a Delete link. Only the person who added the ad hoc reviewer node can remove it. For more details, see Delete an Ad Hoc Reviewer.
When other reviewers see the ad hoc node, they will see the name of the person who added it instead of the Delete link.