Project Change Procedures Sample Clauses

Project Change Procedures. Any proposed changes in the scope of the Project, the Project objectives, key Project personnel, time period, or Budget must be requested in writing and approved by Agency. Grantee shall not perform any Project changes without a Grant Adjustment Form, submitted in the form provided by ODOT, and signed by Agency and Grantee. Any extension of the time period for completion or performance of the Project must be requested at least six weeks prior to the end of the stated time period and may need approval of the funding agency (identified in Section 8 of this Agreement) if the end of the grant award year is involved.
AutoNDA by SimpleDocs
Project Change Procedures i. If Recipient anticipates a change in scope, Key Milestone Dates, or Availability Termination Date, Recipient shall submit a written request to XXXXXxxxxxxXxxxxxx@xxxx.xxxxxx.xxx. The request for change must be submitted before the change occurs. ii. Recipient shall not proceed with any changes to scope, Key Milestone Dates, or Availability Termination Date before the execution of an amendment to this Agreement executed in response to ODOT’s approval of a Recipient’s request for change. A request for change may be rejected at the sole discretion of ODOT.
Project Change Procedures i. If Recipient anticipates Project key milestones will be delayed by more than ninety (90) days from the key milestones shown in Exhibit A, Recipient shall submit a Request for Change Order (Form 734-2648), the form of which is hereby incorporated by reference, to ODOT’s Project Liaison as soon as Recipient becomes aware of any possible delay. The Request for Change Order must be submitted prior to the milestone completion date shown in Exhibit A. The fillable form can be downloaded on-line at the following address: xxxxx://xxx.xxxxxx.xxx/ODOT/LocalGov/Pages/Forms-Apps.aspx ii. Recipient shall not proceed with any changes to Project scope or delivery schedule prior to the execution of an amendment to this Agreement executed in response to ODOT’s approval of a Request for Change. A Request for Change Order may be rejected at the discretion of ODOT. ODOT may choose to request review by the Oregon Transportation Commission.
Project Change Procedures i. If Recipient anticipates a change in the Project’s scope or the Project’s completion date identified in Exhibit A (the “Project Completion Date”), Recipient shall submit a request for change to XXXXXxxxxxxXxxxxxx@xxxx.xxxxx.xx.xx. The request for change must be submitted before the change occurs. ii. Recipient shall not proceed with any changes to the Project’s scope or the Project Completion Date without first executing an amendment to this Agreement that documents ODOT’s approval of Recipient’s request for such a change. A request for a change in the Project’s scope or the Project Completion Date may be rejected at ODOT’s sole discretion.
Project Change Procedures i. If Recipient anticipates a change in scope or Availability Termination Date, Recipient shall submit a written request to their ODOT project liaison. The request for change must be submitted before the change occurs. ii. Recipient shall not proceed with any changes to scope or Availability Termination Date before the execution of an amendment to this Agreement executed in response to ODOT’s approval of a Recipient’s request for change. A request for change may be rejected at the sole discretion of ODOT.
Project Change Procedures a. If Recipient either seeks a change in Project scope or anticipates that a Project milestone will be delayed by more than ninety (90) days from the milestones shown in Exhibit A, Recipient shall submit a Request for Change Order (Form 109-009) to ODA’s Project Coordinators as soon as Recipient becomes aware of any possible change in Project scope or delay. The Request for Change Order must be submitted prior to the milestone completion date shown in Table 1 of Exhibit A. b. Recipient shall not proceed with any changes to Project scope or delivery schedule prior to the execution of an amendment to this Agreement executed in response to ODA’s approval of a Request for Change Order. A Request for Change Order may be rejected at the discretion of ODA. ODA may choose to request review by the State Aviation Board.
Project Change Procedures i. If Recipient anticipates that a Milestone (as that capitalized term is defined in subsection B(i) of Exhibit A) will be delayed, Recipient shall submit a Request for Change Order (Form 734- 2648), the form of which is hereby incorporated by reference, to ODOT’s Connect Oregon Program Manager as soon as Recipient becomes aware of any possible delay. The Request for Change Order must be submitted before the Milestone’s completion date shown in Table 1 of Exhibit A. The fillable form can be downloaded on-line at the following address: ii. Recipient shall not proceed with any changes to Project scope or delivery schedule before the execution of an amendment to this Agreement executed in response to ODOT’s approval of a Request for Change. A Request for Change Order may be rejected at the sole discretion of ODOT. ODOT may choose to request review by the Oregon Transportation Commission.
AutoNDA by SimpleDocs
Project Change Procedures. Project change orders are only for changes to the schedule. Recipient shall submit a Request for Change Order (Form 109-009), the form of which is hereby incorporated by reference to ODA’s Program Coordinators: a. If Recipient anticipates Project milestones will be delayed by more than ninety (90) days from the milestones shown in Exhibit A, Recipient shall submit a Request for Change Order (Form 109-009), the form which is hereby incorporated by reference, to ODA’s Project Coordinators as soon as Recipient becomes aware of any possible delay. The Request for Change Order must be submitted prior to the milestone completion date shown in Exhibit A. b. Recipient shall not proceed with any changes to Project scope or delivery schedule prior to the execution of an amendment to this Agreement executed in response to ODA’s approval of a Request for Change. A Request for Change Order may be rejected at the discretion of ODA. ODA may choose to request review by the State Aviation Board. Changes will not include additional costs or reimbursement requests in excess of the original Agreement.
Project Change Procedures i. If Recipient anticipates that a Milestone (as that capitalized term is defined in subsection B(i) of Exhibit A) will be delayed, Recipient shall submit a Request for Change Order (Form 734- 2648), the form of which is hereby incorporated by reference, to ODOT’s Connect Oregon Program Manager as soon as Recipient becomes aware of any possible delay. The Request for Change Order must be submitted before the Milestone’s completion date shown in Table 1 of Exhibit A. The fillable form can be downloaded on-line at the following address: ii. Recipient shall not proceed with any changes to Project scope or delivery schedule before the execution of an amendment to this Agreement executed in response to ODOT’s approval
Project Change Procedures. Project changes are permitted only to the Scope of Work and only with the prior written permission of ODOT. If Recipient anticipates a need for project change, Recipient shall submit a request via email to the ODOT Project Manager. ODOT Project Manager may authorize changes to Scope of Work via email.
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!