Developer Changes Clause Samples

The "Developer Changes" clause defines the rights and procedures for making modifications to a project by the developer after the initial agreement. Typically, this clause outlines the circumstances under which the developer can propose or implement changes, such as design adjustments or technical updates, and may specify requirements for client approval or notification. Its core practical function is to provide a structured process for managing changes, ensuring both parties understand how alterations are handled and reducing the risk of disputes over unauthorized or unexpected modifications.
Developer Changes. 10.6.1 If Developer wishes to introduce a change in the Work (a “Developer Change”), it must deliver written notice (the “Developer Change Request”) to the Authority setting out the following: 10.6.1.1 the proposed change to the Works in sufficient detail to enable the Authority to evaluate it in full; 10.6.1.2 Developer’s reasons for proposing the change to the Works; 10.6.1.3 a request to the Authority to consult with Developer with a view to deciding whether to agree to the change to the Works and, if so, what consequential changes the Authority requires due to the Developer Change; 10.6.1.4 any implications of the change to the Works; 10.6.1.5 details regarding proposed variations to the Maintenance Payment, if any (and, if so, giving a detailed cost estimate of such proposed change); 10.6.1.6 any dates by which a decision by the Authority is critical; and 10.6.1.7 all of the information enumerated above in Section 10.3.1. 10.6.2 The Authority shall evaluate the Developer Change Request in good faith, taking into account all relevant issues, including whether: 10.6.2.1 a change in the Maintenance Payments will occur; 10.6.2.2 the change affects the quality of the Works or the likelihood of successful delivery of the Works; 10.6.2.3 the change will adversely interfere with the relationship of the Authority with third parties; 10.6.2.4 the financial strength of Developer is sufficient to perform the changed Work; 10.6.2.5 the residual value of the Project is reduced; or 10.6.2.6 the change materially affects the risk or costs to which the Authority is exposed. 10.6.3 As soon as practicable after receiving the Developer Change Request, the Parties shall meet and discuss the matters referred to in it. During their discussions the Authority may propose modifications or, subject to Section 10.6.7, approve or reject the Developer Change Request. Upon receipt of a Developer Change Request, the Authority shall issue a response to Developer as soon as practicable and in no event later than fifteen (15) days. 10.6.4 If the Authority approves the Developer Change Request (with or without modification), the implementation of the relevant change to the Works shall be commenced within five (5) Business Days of the Authority’s acceptance. Within this period, the Parties shall consult and agree on the remaining details as soon as practicable and shall enter into an appropriate change order to give effect to the relevant Developer Change Request. 10.6.5 If the Authority...
View SourceView Similar (4)
Developer Changes. The Parties acknowledge that there may be changes to the Developers from time to time in respect of the Development. Any proposal to accept an additional Developer shall be discussed and decided upon by the Developers for the time being. A Deed of Adherence shall be executed by any additional Developer agreed upon as a new Developer and Party to this Agreement and by the Council on behalf of itself and of all existing Parties to this Agreement. Each Party confirms the irrevocable authority of the Council to execute a Deed of Adherence on its behalf. Upon so entering into a Deed of Adherence that organisation or person (as the case may be) shall be deemed to be a party to this Agreement.
View SourceView Similar (2)
Developer Changes. If Developer desires to propose any material revisions to any Approved Plans, Developer shall submit such proposed changes to the City and shall also proceed in accordance with any State of Nevada and local laws and regulations regarding such revisions. The City shall review the proposed changes and notify Developer in writing within thirty (30) days after submission to the City as to whether the proposed changes are approved or disapproved and the specific reasons for any disapproval, provided, however, that such reasons shall be consistent with any items previously approved hereunder or pursuant to the Purchase Agreement and changes which generally and substantially conform to the basic uses of the Project as provided for in this Agreement shall be permitted. For purposes of this Section, a material revision is any change or changes which result in change orders which, in the aggregate, would increase or decrease the cost of the project by greater than $100,000.
View SourceView Similar (2)
Developer Changes. If Developer desires to make changes to the Final Plans, then Developer shall submit a Change Order Request to Owner for review and approval, together with an estimate of any increases to the BOT Purchase Price that would result from the change proposed in the Change Order Request. Within fourteen (14) days after Owner receives the Change Order Request, Owner shall deliver to Developer written notice that it approves or rejects the Change Order Request; provided that: (i) Owner shall not withhold its approval unreasonably. (ii) by way of example, and not limitation, it shall not be unreasonable for Owner to reject a Change Order Request from Developer if the change proposed in the Change Order Request would result in: (A) use of construction materials inferior to those contemplated in the Final Plans; (B) a change in the Construction Schedule that would make it unlikely, impracticable, or impossible for Developer to complete the Project by the then-current date set forth therein; ; (C) an increase operational costs, required man power or difficulty or (D) an increase in the BOT Purchase Price. (iii) if Owner approves a Change Order Request for a change that would result in an increase in the BOT Purchase Price (notwithstanding that, as provided above, Owner has the right to reject such Change Order Request), then, notwithstanding anything to the contrary set forth herein, the amount of such increase: (A) shall not be included in the BOT Purchase Price; and (B) instead, shall be paid by Owner as such costs are incurred. If Owner rejects all or any part of the Change Order Request, then such notice shall: (i) specify the part or parts that Owner is rejecting; and (ii) include the specific basis for such rejection. If Owner approves a Change Order Request, then Developer and Owner shall execute a Change Order.
View SourceView Similar (2)
Developer Changes. If Developer desires to make any changes to the Final Plans, then Developer shall submit a Change Order Request to Sewer Board for review and approval, together with an estimate of any increases to the approved Project Budget that would result from the change proposed in the Change Order Request. Within fifteen (15) days after Sewer Board receives the Change Order Request, Sewer Board shall deliver to Developer written notice that it approves or rejects the Change Order Request, provided that: if Sewer Board approves a Change Order Request for a change that would result in an increase in the Project Budget, then the amount of such increase shall be included in the Acquisition Price; Notwithstanding the following, if the Sewer Board fails to respond to the Change Order Request within fifteen (15) days of receipt, the Change Order Request is deemed denied.
View Source
Developer Changes 
View SourceView Similar (8)

Related to Developer Changes

  • Program Changes Contractor agrees to inform the County of any alteration in program or service delivery at least thirty (30) days prior to the implementation of the change, or as soon as reasonably feasible.

  • Room Changes No changes in room assignment will be based upon age, race, religion, national origin, disability, sexual orientation, and online profiles except as needed to provide a reasonable accommodation to residents with eligible disabilities registered with the University [Office of Disability Services]. Room change may only be made with the written approval of University Housing and is dependent upon space availability, timing of the request, and grounds for transfer. Residents who receive approval for a room change may be charged a room change fee as shown on the University Housing website, which will be posted to Resident’s account. Room changes that are not authorized by University Housing will result in a fine as shown on the University Housing website, which will be posted to Resident’s account.

  • Project Changes Project changes prior to bid opening shall be made by addendum to plans and specifications. Changes after bid opening shall be made by change order. The Local Government shall submit all addenda and all change orders to the Department for an eligibility determination. After execution of all construction, equipment and materials contracts, the Project contingency may be reduced.

  • Minor Changes Within Sale Area, minor adjustments may be made in boundaries of cutting units or in the timber individually Marked for cutting when ac- ceptable to Purchaser and Forest Service.

  • Interim Changes Since the date of its balance sheets, except as set forth in Exhibit C, there have been no (1) changes in financial condition, assets, liabilities or business of Amalgamated which, in the aggregate, have been materially adverse; (2) damages, destruction or losses of or to property of Amalgamated, payments of any dividend or other distribution in respect of any class of stock of Amalgamated, or any direct or indirect redemption, purchase or other acquisition of any class of any such stock; or (3) increases paid or agreed to in the compensation, retirement benefits or other commitments to its employees.