Time to Submit Proposed Change Order Sample Clauses

Time to Submit Proposed Change Order. Developer shall submit its PCO within five (5) working days of the date Xxxxxxxxx discovers, or reasonably should have discovered, the circumstances giving rise to the PCO, unless additional time to submit a PCO is granted in writing by the District. Time is of the essence in Developer’s submission of PCOs so that the District can promptly investigate the basis for the PCO. Accordingly, if Developer fails to submit its PCO within this timeframe, Developer waives, releases, and discharges any right to assert or claim any entitlement to an adjustment of the Guaranteed Maximum Price and/or Contract Time based on circumstances giving rise to the PCO.
Sample 1Sample 2Sample 3See All (19)
AutoNDA by SimpleDocs

Related to Time to Submit Proposed Change Order

  • Change Order (5) The Change Order is then submitted to the Project Manager who immediately processes the CO with OPC as required by Bulletin 3.5 and BGS’ Contracting Plan.

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

Time is Money Join Law Insider Premium to draft better contracts faster.