The Proposal Lifecycle
The proposal lifecycle is managed in the UW electronic research administration system. The system is comprised of three modules: SAGE, SPAERC, and SERA.
Researchers and administrators enter their proposal information into the SAGE Suite Database. This information can be accessed and parts of it may be edited by OSP in SPAERC. Grants and Contract Accounting (GCA) views the application information in SERA.
All research proposals submitted to sponsors external to the university go through the following process:
- Application creation in SAGE
- Campus review and approval
- OSP review and approval
- Submission to the sponsor
- Funding or rejection by the sponsor
When a principal investigator (PI) at the UW decides to solicit funding for a research project from a sponsor, he or she identifies an appropriate funding opportunity and then, often with the assistance of a research administrator, puts together a research proposal according to the sponsor’s instructions. From the proposal information, the PI and/or research administrator create an online application—called an “eGC1”—in SAGE (System to Administer Grants Electronically). The application provides the means to route the proposal information around campus and to OSP for approval before the proposal is eventually submitted to the sponsor.
The application includes the proposal components for submission to the sponsor and provides the university answers and explanations to a series of compliance questions. The application includes:
- Information about the PI
- Information for any other research personnel
- The funding agency (sponsor) and its submission deadline
- The timeframe and details of the research
- A brief description of the project (abstract)
- The budget and any cost sharing information
- The attached proposal documents that will be submitted to the sponsor
- Attachments of any other relevant documents needed by reviewers.
While the application is created, it has a status of Composing. Once the application has been fully prepared with all but the final version of the scope of work for the sponsor, the preparer "completes" it. The status of the application changes to Routing and it moves into the campus approval phase.
Preparers have the option to "withdraw" the application from routing to make adjustments, which changes its status to Withdrawn, and then re-complete it so that it resumes routing, resetting its status to Routing.
Tip: An eGC1 originates from the original paper form which was called the GC-1 (Grant and Contracts form 1). The "e" indicates the electronic version of this form.
Campus Review and Approval
Each school or college at the UW defines its own approval "routing rules" which are built into SAGE. They indicate which unit level (division, department, dean) will need to review an application based on:
- The PI's department
- The organization receiving the funding
- Any additional research personnel
- Any cost sharing
- The answers to certain compliance questions
When the application is initially "completed" an automatic email notification is sent to the first reviewer(s), usually just the PI. If the PI is the person who completes the eGC1, upon completion, it is also automatically approved by the PI, in which case the next set of reviewers would be notified. After each group has indicated approval, the next group is notified.
Note: There are usually several reviewers defined for a unit, but only one reviewer needs to approve the application.
When a specific unit approves the application, information is added to the eGC1's approval history, which can be viewed by OSP on the History & Comments page.
Approvers have the option to "return" the application to the preparers for any needed changes. This changes the application's status to Returned, and automatically sends an email to the PI, eGC1 Preparer, Administrative Contract, and Pre-Award Budget Contract, notifying them of the change in status.
Once all the required campus units have indicated their approval of an application, the application changes to a status of In OSP, indicating it is now ready for review by OSP.
OSP Review and Approval
OSP staff review the application and proposal documents to verify compliance with research regulations, and the sponsor's requirements. If changes are required, the application is returned to the preparer. The preparer, PI and Contacts receive an email notifying them of the return, which contains the comments you make when you return it. The comments can also be viewed from the History & Comments page of the eGC1 in SAGE.
When OSP determines that the application is ready, it is submitted to the sponsor, and then "approved" in the system. When you approve an application, its status changes to Approved, and the application's data at that point in time becomes a permanent record of the submission.
Submission to Sponsor
There are multiple ways in which an application can be submitted to a sponsor. OSP staff usually submits all federal and electronic applications.
When a proposal is funded by the sponsor, OSP uses SPAERC to manage that information by creating a Funding Action (FA). The FA is sent to Grant and Contract Accounting (GCA) from within SPAERC. When the FA is sent to GCA, the application's status is automatically changed from Approved to Awarded. GCA will process the FA and also create a budget number for the research project in the financial system.
If the sponsor does not fund the proposal, OSP staff manually change the status of the application to Denied by Sponsor.
Have feedback on this guide? Email firstname.lastname@example.org.