-
Step 1
Award Review
As an award end date approaches, the PI/DRA begins to proactively review their awards to determine if an at-risk extension should be requested. CCO sends notifications at 90, 60Â and 30 days prior to the award end date to serve as a reminder of awards that may be ending.
-
Step 2
At-Risk Extension Request
If it is determined the award will be ongoing, the PI/DRA submits the extension form. This is a mandatory form. Each department should determine who is responsible for submitting the extension form. The at-risk extension requires a departmental guarantee SpeedType and an authorized person to allow the use of that SpeedType in the event the extension is disallowed by the sponsor.
-
Step 3
Form Routing/Notification
The form will automatically route to CCO, with copies to the requestor and departmental guarantee approver.
-
Step 4
Award Provisionally Extended
CCO reviews and processes the at-risk extension request and adjusts the project end date in PeopleSoft. This is an internal extension and should not be interpreted as authorization by the sponsor.
-
Step 5
Monitoring
CCO monitors the award until sponsor-approved documentation is received. Monitoring is in conjunction with OCG and the department.
-
Step 6
Receipt of Sponsor-Approved Modification
OCG will receive and process the sponsor-approved modification in InfoEd, then route to CCO.
-
Step 7
Award is Officially Extended
CCO updates the award date and related dates in PeopleSoft. This triggers a system email notification to the PI and fiscal manager of the changes.
Step 1
Award Review
As an award end date approaches, the PI/DRA begins to proactively review their awards to determine if an at-risk extension should be requested. CCO sends notifications at 90, 60Â and 30 days prior to the award end date to serve as a reminder of awards that may be ending.
Step 2
At-Risk Extension Request
If it is determined the award will be ongoing, the PI/DRA submits the extension form. This is a mandatory form. Each department should determine who is responsible for submitting the extension form. The at-risk extension requires a departmental guarantee SpeedType and an authorized person to allow the use of that SpeedType in the event the extension is disallowed by the sponsor.
Step 3
Form Routing/Notification
The form will automatically route to CCO, with copies to the requestor and departmental guarantee approver.
Step 4
Award Provisionally Extended
CCO reviews and processes the at-risk extension request and adjusts the project end date in PeopleSoft. This is an internal extension and should not be interpreted as authorization by the sponsor.
Step 5
Monitoring
CCO monitors the award until sponsor-approved documentation is received. Monitoring is in conjunction with OCG and the department.
Step 6
Receipt of Sponsor-Approved Modification
OCG will receive and process the sponsor-approved modification in InfoEd, then route to CCO.
Step 7
Award is Officially Extended
CCO updates the award date and related dates in PeopleSoft. This triggers a system email notification to the PI and fiscal manager of the changes.