Negotiation Timelines Sample Clauses

Negotiation Timelines. The parties will begin negotiations for a new Agreement covering wages, hours, terms and conditions of employment of teachers no later than May 1 preceding the expiration of this Agreement.
AutoNDA by SimpleDocs

Related to Negotiation Timelines

  • Negotiation Teams Neither party in any negotiations shall have any control over the selection of the bargaining representatives of the other party. The parties mutually pledge that their representatives will be clothed with all necessary authority and power to make proposals, counterproposals and to reach tentative agreement on items being negotiated. The parties realize the Agreement shall only be effective subject to the ratification of the BTU-ESP and the School Board. The Negotiation/Labor Management team shall consist of no more than six

  • Negotiation Period The Parties shall negotiate in good faith and attempt to resolve any dispute, controversy or claim arising out of or relating to this Agreement (a “Dispute”) within 30 days after the date that a Party gives written notice of such Dispute to the other Party.

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

  • NEGOTIATIONS PROCEDURE A. Upon the request of Local 149 or the Board, not earlier than ninety (90) calendar days prior to the expiration of this Agreement, the parties may open negotiations for a successor contract. The first meeting will be held within fifteen (15) calendar days of receipt of the request unless the parties mutually agree to a later date. B. The Board and the Union shall be represented at negotiation meetings by a team of not more than six (6) members each. C. The Board and the Union negotiating teams shall exchange items for negotiations at the first negotiating session. All contract proposals shall be presented in writing by both parties. No issue shall be introduced by either party following the first session unless mutually agreed by both negotiating teams. D. Neither team shall release information to the public media without mutual agreement of the other team until such time as impasse is declared by either side. E. When tentative agreement is reached covering the matters of negotiation, it shall be reduced to writing, reproduced at Board expense for the Local 149 membership to ratify or reject. When approved by Local 149 membership, it shall be presented to the Board for its approval or rejection. F. In the event agreement is not reached within thirty (30) calendar days after the first actual negotiating session, either party may request that Federal Mediation and Conciliation Service be notified and requested to furnish the services of a mediator for the purpose of assisting the parties in reaching agreement. The request for a mediator shall be jointly filed. This procedure is intended to serve as an alternate dispute resolution procedure to those set forth in Chapter 4117 of the Ohio Revised Code. G. The procedures set forth above may be modified prior to the start of negotiations by joint agreement of the parties. Should that occur, the bargaining shall be governed by the ground rules agreed to modifying these procedures.

  • Negotiating Teams The Board, or designated representatives appointed to serve on its team, will meet with representatives designated by the Association for the purpose of establishing procedures for negotiating and reaching mutually satisfactory agreements. Each party's negotiating team shall consist of not more than five members.

  • Preparatory Contract Negotiations Meetings Where operational requirements permit, the Employer will grant leave without pay to an employee to attend preparatory contract negotiations meetings.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Order Coordination and Order Coordination-Time Specific 2.1.9.1 “Order Coordination” (OC) allows BellSouth and Lightyear to coordinate the installation of the SL2 Loops, Unbundled Digital Loops (UDL) and other Loops where OC may be purchased as an option, to Lightyear’s facilities to limit end user service outage. OC is available when the Loop is provisioned over an existing circuit that is currently providing service to the end user. OC for physical conversions will be scheduled at BellSouth’s discretion during normal working hours on the committed due date. OC shall be provided in accordance with the chart set forth below. 2.1.9.2 “Order Coordination – Time Specific” (OC-TS) allows Lightyear to order a specific time for OC to take place. BellSouth will make every effort to accommodate Lightyear’s specific conversion time request. However, BellSouth reserves the right to negotiate with Lightyear a conversion time based on load and appointment control when necessary. This OC-TS is a chargeable option for all Loops except Unbundled Copper Loops (UCL) and Universal Digital Channel (UDC), and is billed in addition to the OC charge. Lightyear may specify a time between 9:00 a.m. and 4:00 p.m. (location time) Monday through Friday (excluding holidays). If Lightyear specifies a time outside this window, or selects a time or quantity of Loops that requires BellSouth technicians to work outside normal work hours, overtime charges will apply in addition to the OC and OC-TS charges. Overtime charges will be applied based on the amount of overtime worked and in accordance with the rates established in the Access Services Tariff, Section E13.2, for each state. The OC-TS charges for an order due on the same day at the same location will be applied on a per Local Service Request (LSR) basis.

  • Commercialization Plan (a) Not later than three [***] after submission of Regulatory Filings for each Product in each country of the Territory, Licensee will provide to the JCC for review its initial Commercialization Plan for each Product for each country in the Territory. Such initial Commercialization Plan will describe Licensee’s plans for activities to be conducted for such Product for such country. Each Commercialization Plan shall include the details of obligations to be performed by Licensee to achieve the specific activities that are applicable to the stage of [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Commercialization (e.g., pre-launch, launch planning, launch, or post-launch) of the applicable Product during the time period covered by such Commercialization Plan and subsequent time periods. (b) Prior to the First Commercial Sale for such Product in such country, Licensee will provide to the JCC for review an updated Commercialization Plan for such Product for such country. Such updated Commercialization Plan will include, but not be limited to, Licensee’s updated plans for activities to be conducted for such Product for such country prior to launch as well as activities to be conducted in connection with such launch. (c) Promptly after each anniversary of the First Commercial Sale of such Product during the Term, Licensee will provide to the JCC for review updated Commercialization Plans for such Product for such country. Such further updated Commercialization Plan will include, but not be limited to, Licensee’s plans for Commercialization activities for such Product and such country for the twelve (12) month period following the date of delivery of such Commercialization Plan. No Commercialization Plan may be implemented by Licensee if [***]. Each Commercialization Plan shall be consistent with and shall not contradict the terms of this Agreement [***], and in the event of any inconsistency between the Commercialization Plan and this Agreement, the terms of this Agreement shall prevail. Notwithstanding the foregoing, if a [***], Licensee shall [***] and shall promptly [***].

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

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