Common use of Errors and Misdescriptions Clause in Contracts

Errors and Misdescriptions. 16 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 of such fact and of the changes to the provisions that Developer believed were the 20 minimum necessary to render the provisions correct and safe. Developer shall not take 21 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 of or, through the exercise of reasonable care, had reason to know of prior to the

Appears in 6 contracts

Samples: apps.azdot.gov, apps.azdot.gov, apps.azdot.gov

AutoNDA by SimpleDocs

Errors and Misdescriptions. 16 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 of such fact and of the changes to the provisions that Developer Xxxxxxxxx believed were the 20 minimum necessary to render the provisions correct and safe. Developer shall not take 21 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 of or, through the exercise of reasonable care, had reason to know of prior to the

Appears in 2 contracts

Samples: apps.azdot.gov, apps.azdot.gov

Errors and Misdescriptions. 16 18 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 19 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 20 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 21 of such fact and of the changes to the provisions that Developer believed were the 20 22 minimum necessary to render the provisions correct and safe. Developer shall not take 21 23 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 24 of or, through the exercise of reasonable care, had reason to know of prior to thethe 25 Effective Date.

Appears in 2 contracts

Samples: apps.azdot.gov, apps.azdot.gov

Errors and Misdescriptions. 16 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 of such fact and of the changes to the provisions that Developer Xxxxxxxxx believed were the 20 minimum necessary to render the provisions correct and safe. Developer shall not take 21 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 of or, through the exercise of reasonable care, had reason to know of prior to thethe Effective

Appears in 1 contract

Samples: azdot.gov

Errors and Misdescriptions. 16 19 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 20 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 21 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 22 of such fact and of the changes to the provisions that Developer believed were the 20 23 minimum necessary to render the provisions correct and safe. Developer shall not take 21 24 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 25 of or, through the exercise of reasonable care, had reason to know of prior to the

Appears in 1 contract

Samples: Public Private

AutoNDA by SimpleDocs

Errors and Misdescriptions. 16 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 of such fact and of the changes to the provisions that Developer believed were the 20 minimum necessary to render the provisions correct and safe. Developer shall not take 21 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 of or, through the exercise of reasonable care, had reason to know of prior to thethe Effective Date.

Appears in 1 contract

Samples: Design Build Maintain Agreement

Errors and Misdescriptions. 16 18 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 19 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 20 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 of 21 such fact and of the changes to the provisions that Developer believed were the 20 minimum 22 necessary to render the provisions correct and safe. Developer shall not take 21 advantage 23 of or benefit from any Error in the Contract Documents that Developer knew 22 of or, through 24 the exercise of reasonable care, had reason to know of prior to thethe Effective Date.

Appears in 1 contract

Samples: apps.azdot.gov

Errors and Misdescriptions. 16 18 1.5.1 Developer acknowledges that prior to the Effective Date Developer had 17 19 the opportunity to identify any Errors and potentially unsafe provisions in the Technical 18 20 Provisions and other Contract Documents, and the opportunity and duty to notify ADOT 19 21 of such fact and of the changes to the provisions that Developer Xxxxxxxxx believed were the 20 22 minimum necessary to render the provisions correct and safe. Developer shall not take 21 23 advantage of or benefit from any Error in the Contract Documents that Developer knew 22 24 of or, through the exercise of reasonable care, had reason to know of prior to thethe 25 Effective Date.

Appears in 1 contract

Samples: apps.azdot.gov

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!