City Revision of Supporting Documentation Sample Clauses

City Revision of Supporting Documentation. Any revision by the City of Supporting Documentation provided to the Company that causes the Company to substantially redesign and/or substantially change its plans regarding new or modified service to City facilities shall be deemed good cause for a reasonable extension of time to complete the Relocation under this Franchise.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
City Revision of Supporting Documentation. Any revision by the City of Supporting Documentation provided to the Company that causes the Company to substantially redesign and/or change its plans regarding an undergrounding project shall be deemed good cause for a reasonable extension of time to complete the undergrounding project under this Franchise.
Sample 1Sample 2Sample 3See All (6)

Related to City Revision of Supporting Documentation

  • Supporting Documentation Upon request, the HSP will provide the LHIN with proof of the matters referred to in this Article.

  • Paid Claims without Supporting Documentation Any Paid Claim for which Practitioner cannot produce documentation shall be considered an error and the total reimbursement received by Practitioner for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.

  • 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.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:

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