Planning agreement register Sample Clauses

Planning agreement register. Council is required to keep a register of planning agreements applying to land within the local government area, whether or not the Council is a party to the agreement. The register must record the date an agreement was entered into and a short description of the agreement, including any subsequent amendments. Ku-ring-gai Council will make available for public inspection during ordinary office hours:  the planning agreement register;  copies of all planning agreements (and any amendments) that apply within the Ku-ring-gai local government area; and  copies of explanatory notes relating to those agreements (including any amendments) A planning agreement register on council web pages is also ordinarily available outside normal business hours.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Planning agreement register. Council is required to keep a register of planning agreements applying to land within the local government area, whether or not the Council is a party to the agreement. The register must record the date an agreement was entered into and a short description of the agreement, including any subsequent amendments. Ku-ring-gai Council will make available for public inspection during ordinary office hours: • the planning agreement register; • copies of all planning agreements (and any amendments) that apply within the Ku-ring-gai local government area; and • copies of explanatory notes relating to those agreements (including any amendments)
Sample 1Sample 2
Planning agreement register. ‌ The Council will establish and maintain a planning agreement register. The register will:
Sample 1
Planning agreement register. (1) Council is required to keep a register of planning agreements (including the related explanatory notes) applying to land within its local government area. The planning agreement register will indicate:
Sample 1
Planning agreement register. Section 25F (1) and (2) of the EP&A Regulation states that a Council must keep a Planning Agreement register. Council must keep a record of the following in its register:
Sample 1

Related to Planning agreement register

  • Warrant Register The Company shall register this Warrant, upon records to be maintained by the Company for that purpose (the “Warrant Register”), in the name of the record Holder hereof from time to time. The Company may deem and treat the registered Holder of this Warrant as the absolute owner hereof for the purpose of any exercise hereof or any distribution to the Holder, and for all other purposes, absent actual notice to the contrary.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its Reliability Planning Process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Short-Term Reliability Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the STAR or Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Short-Term Reliability Process Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

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