Development Contingency Sample Clauses

Development Contingency. (strike one) Buyer / Seller obtaining all requisite approvals from any governing body having jurisdiction for the construction/development of the Property as . (strike one) Buyer / Seller is to have until , 20 to obtain approval in final, non-appealable form, upon conditions reasonably acceptable to the Buyer. □ (b) Subdivision Contingency. (strike one) Buyer / Seller obtaining all requisite approvals from any governing body having jurisdiction for subdivision approval of the Property. (strike one) Buyer / Seller must make an application for subdivision approval by , 20 _ and the Parties agree to use commercially reasonable efforts to diligently pursue the application. The final approval, upon conditions reasonable acceptable to the Buyer, shall be obtained on or before , 20 .
AutoNDA by SimpleDocs
Development Contingency. This Contract is contingent upon (strike one) Buyer / Seller obtaining all requisite approvals from any 58 governing body having jurisdiction for the construction/development of the Property as . 59 (strike one) Buyer / Seller is to have until , 20 to obtain approval in final, non-appealable form, upon conditions 60 reasonably acceptable to the Parties.
Development Contingency. Lessor understands that Lessee’s construction of the Charging Stations is contingent upon award of funding pursuant to application to New Mexico Environment Department in respect of the Volkswagen Mitigation Trust Funding. Lessor understands that the results of any such application may not be resolved until January 1, 2021.
Development Contingency. Notwithstanding any other provision of this Agreement to the contrary, no Development Contingency that arises directly or indirectly out of (a) the execution, delivery, and performance of this Agreement by the Company or its Affiliates or the consummation by the Company or its Affiliates of the Merger or any other Transactions, (b) any action taken by Parent, Merger Sub or their respective Affiliates, (c) any action taken by the Company at the written request of Parent or Merger Sub, or (d) any action required to be taken by the Company or its Affiliates or necessary in order to satisfy their obligations, or cause other parties to perform their obligations, under the Headquarters Lease or the Development Documents, shall constitute a Company Material Adverse Effect, a breach of any of the representations, warranties, or covenants of the Company under this Agreement, or the failure of any condition to the obligations of each of Parent and Merger Sub to effect the Merger under this Agreement, except, in each case, to the extent such breach, failure, or Company Material Adverse Effect arises out of a (i) failure by the Company to provide true and correct copies of the Development Documents to Parent, (ii) a breach by the Company of any of the representations, warranties or covenants set forth in this Agreement, or (iii) a breach by the Company or its Affiliates of the terms of the Headquarters Lease or Development Documents.
Development Contingency. This Contract is contingent upon (strike one) Buyer / Seller obtaining all requisite approvals from any 59 governing body having jurisdiction for the construction/development of the Property as . 60 (strike one) Buyer / Seller is to have until , 20 to obtain approval in final, non-appealable form, upon conditions 61 reasonably acceptable to the Parties. Buyer Initials: 3 of 4 Buyer Initials: Seller Initials: Seller Initials: 62 □ (B) Subdivision Contingency. This Contract is contingent upon (strike one) Buyer / Seller obtaining all requisite approvals from any 63 governing body having jurisdiction for subdivision approval of the Property. (strike one) Buyer/Seller must make an application for 64 subdivision approval by , 20 and the Parties agree to use commercially reasonable efforts to diligently pursue the 65 application. The final approval, upon conditions reasonable1 aofcc4eptable to the Parties, shall be obtained on or before , 20 .

Related to Development Contingency

  • Development of the Project 4.1 TSP's obligations in development of the Project: Subject to the terms and conditions of this Agreement, the TSP at its own cost and expense shall observe, comply with, perform, undertake and be responsible:

  • Development Activities The Development activities referred to in item “b” of paragraph 3.1 include: studies and projects of implementation of the Production facilities; drilling and completion of the Producing and injection xxxxx; and installation of equipment and vessels for extraction, collection, Treatment, storage, and transfer of Oil and Gas. The installation referred to in item “c” includes, but is not limited to, offshore platforms, pipelines, Oil and Gas Treatment plants, equipment and facilities for measurement of the inspected Production, wellhead equipment, production pipes, flow lines, tanks, and other facilities exclusively intended for extraction, as well as oil and gas pipelines for Production Outflow and their respective compressor and pumping stations.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Development 3.3 Within twenty (20) Working Days after the Commencement Date and in accordance with paragraphs 3.10 to 3.12 (Amendment and Revision), the Contractor will prepare and deliver to the Authority for approval the full and final Security Plan which will be based on the draft Security Plan set out in Appendix B.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

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