Agreement Renegotiation Sample Clauses

Agreement Renegotiation. The parties agree that the Agreement shall be subject to renegotiation on the three-month anniversary of the Agreement's Effective Date, based upon the good faith intention of the parties, subject to the financial condition of the Company at the time, to replace the Agreement with an Executive Employment Agreement, which would provide the Executive with: (a) a monthly base salary, reflecting an increase in the monthly Fee then in effect, (b) employee-related executive benefits, including health and medical insurance, life and travel insurance, and an automobile lease allowance and reimbursement of related maintenance and operating expenses, and (c) a grant of stock options, as of the effective date of the Executive Employment Agreement. Should the Agreement not be replaced with an Executive Employment Agreement on the above noted three-month anniversary date, due to financial constraints of the Company, the parties agree to continue, in good faith, to attempt to renegotiate the Agreement on a monthly basis thereafter.
Sample 1Sample 2
AutoNDA by SimpleDocs
Agreement Renegotiation. In the event of an M&A Transaction (as defined in Section 4.(b).(iii).(5) of this Agreement) or initial public offering (“IPO”) on a major US, or International stock exchange with the Employer having a Market Capitalization of over $250 million, the Employee shall be entitled to renegotiate terms of this Agreement.
Sample 1
Agreement Renegotiation. The parties agree to commence renegotiation of this Agreement for a successor to this Agreement three months prior to its expiry.
Sample 1
Agreement Renegotiation. Three months before the expiry date of this agreement the parties will commence discussions aimed at renegotiating a new agreement. Until such time as a new Agreement commences which has been approved by FWC, the terms and conditions of this Agreement will continue to apply.
Sample 1
Agreement Renegotiation. This Section of the Agreement shall be replaced in its entirety with the following revised Section 12:
Sample 1
Agreement Renegotiation. If within 120 days after the Effective Date it is determined on the basis of information that was neither provided by a Vendor to the Purchaser nor otherwise known to the Purchaser before the Effective Date that, by agreement between an Operator and a Vendor, the rates shown under the heading “Royalty” in the Royalties Summary for any of the Royalties except those identified as Avebury & Xxxxx Flats, Las Cruces, Xxxx Creek and High Lake were amended or any of the Royalties except those identified as Avebury & Xxxxx Flats, Las Cruces, Xxxx Creek and High Lake were extinguished, then the Vendors will at the request of the Purchaser meet in good faith to discuss transactions which might provide the Purchaser with at least partial off-setting benefits, the Parties acknowledging however there shall be no obligation to refund any portion of the Purchase Price.
Sample 1

Related to Agreement Renegotiation

  • AGREEMENT RENEWAL This Agreement shall not bind nor purport to bind the AZDOHS for any contractual commitment in excess of the original Agreement period.

  • Renegotiation The contract may be renegotiated at any time by the parties, based upon appropriate and reasonable changes in circumstances upon which the original terms of the contract were based.

  • Modification or Renegotiation This agreement may be modified only by written agreement signed by the parties hereto. The parties agree to renegotiate the agreement if federal and/or state revisions of any applicable laws or regulations make changes in this agreement necessary.

  • No Negotiation Until such time, if any, as this Agreement is terminated pursuant to Section 9, Sellers will not, and will cause the Company and each of their Representatives not to, directly or indirectly solicit, initiate, or encourage any inquiries or proposals from, discuss or negotiate with, provide any non-public information to, or consider the merits of any unsolicited inquiries or proposals from, any Person (other than Buyer) relating to any transaction involving the sale of the business or assets (other than in the Ordinary Course of Business) of the Company, or any of the capital stock of the Company, or any merger, consolidation, business combination, or similar transaction involving the Company.

  • Agreement Review If, pursuant to section 25.10 (Review of Agreement) of the Bilateral Agreement, the Bilateral Agreement is reviewed after three or five years, or both, of the effective date of the Bilateral Agreement, and any changes to the Bilateral Agreement are required as a result, the Parties agree to amend the Agreement as necessary and in a manner that is consistent with such changes.

  • Contract Negotiations Where operational requirements permit, and on reasonable notice, the Employer shall grant special leave with pay for not more than two (2) representatives of each bargaining unit for the purpose of attending contract negotiation meetings with the Employer on behalf of the Union. Such permission shall not be unreasonably withheld.

  • NEGOTIATION PROCEDURE 3.1 On or before September 1 of the prior year in which this agreement is to expire either party may initiate negotiations in accordance with RSA 273:A. The parties shall meet not later than September 15th, at which time the Association shall submit its proposals, unless another date is mutually agreed to by the parties. 3.2 The Negotiating Committee of the Board and the Negotiating Committee of the Association shall have authority to reach a complete agreement, subject to ratification by the Board and the qualified voting members of the Association covered by this Agreement. 3.3 Any agreement reached shall be reduced to writing and signed by the Board and the Association. Any agreement reached which requires the expenditure of additional public funds for its implementation shall not be binding on the Board, unless and until the necessary appropriations have been made by the Annual School District Meeting. The Board shall make a good faith effort to secure the funds necessary to implement said agreements. 3.4 If, after discussion of all negotiable matters, the parties fail to reach agreement, either party may declare impasse. In the event of impasse, the rules and procedures for “Resolution of Disputes” as outlined under RSA 273: A-12 shall be followed. 3.5 The cost for the services of the mediator and/or fact finder including per diem expenses, if any, will be shared equally by the Board and the Association. 3.6 Determinations and/or recommendations under the provision of Section 3.4 of this Article III will not be binding on the parties in accordance with RSA 273: A 3.7 If the monies to fund the economic provisions are not appropriated as provided in this Article III, Section 3.3 and/or if either party rejects the recommendations set forth in this Article III, Section 3.6, then the parties shall do the following: A. The appropriate party shall notify the other party of its intent to renegotiate the provisions of this Agreement, and: B. If either negotiating team rejects the neutral party’s recommendations, his/her findings and recommendations shall be submitted to the full membership of the employee organization and to the Board of the public employer, which shall vote to accept or reject so much of his/her recommendations as is otherwise permitted by law. C. If either the full membership of the employee organization or the public employer rejects the neutral party’s recommendations, his/her findings and recommendations shall be submitted to the legislative body of the public employer, which shall vote to accept or reject so much of his/her recommendations as otherwise is permitted by law. D. If the impasse is not resolved following the action of the legislative body, negotiations shall be reopened. Mediation may be requested by either party and may involve the Board of the public employer if the mediator so chooses. 3.8 The parties may, by mutual agreement, pass over mediation and go directly to fact finding. 3.9 Neither party in any negotiations shall interfere with the selection of the negotiating or bargaining representatives of the other party.

  • Negotiated Agreement (1) This Settlement Agreement has been the subject of negotiations and discussions among the undersigned, each of which has been represented and advised by competent counsel, so that any statute, case law, or rule of interpretation or construction that would or might cause any provision to be construed against the drafter of this Settlement Agreement shall have no force and effect. The Parties further agree that the language contained in or not contained in previous drafts of this Settlement Agreement, or any agreement in principle, shall have no bearing upon the proper interpretation of this Settlement Agreement.

  • Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-­‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-­‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).

  • Negotiation of Agreement Owner and Manager are both business entities having substantial experience with the subject matter of this Agreement, and each has fully participated in the negotiation and drafting of this Agreement. Accordingly, this Agreement shall be construed without regard to the rule that ambiguities in a document are to be construed against the draftsman. No inferences shall be drawn from the fact that the final, duly executed Agreement differs in any respect from any previous draft hereof.

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