Common use of Project Change Procedures Clause in Contracts

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 a change in scope, Key Milestone Dates, or Availability Termination Date, Recipient shall submit a written request to XXXXXxxxxxxXxxxxxx@xxxx.xxxxxx.xxxXXXXXxxxxxxXxxxxxx@xxxx.xxxxx.xx.xx. 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 a change in scope, Key Milestone Dates, or Availability Termination Date, Recipient shall submit a written request to XXXXXxxxxxxXxxxxxx@xxxx.xxxxxx.xxxXxxxxxxxxXxxxx@xxxx.xxxxxx.xxx. The request for change must be submitted before the change occurs. ii. i. 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.