Completion of conciliation process Sample Clauses

Completion of conciliation process. 1.2.1 A conciliation proceeding before the AIRC shall be regarded as completed when: a) the Parties have reached agreement for the settlement of the whole of the dispute; or b) whether or not the Parties have reached agreement for the settlement of part of the dispute: I. the AIRC is satisfied that there is no likelihood that, within a reasonable period, conciliation, or further conciliation, will result in agreement, or further agreement, by the Parties on terms for the settlement of the dispute or any matter in dispute; or II. the Parties to the dispute have informed the AIRC that there is no likelihood of agreement, or further agreement, on the dispute and the AIRC does not have a substantial reason to refuse to regard the conciliation proceeding as completed.
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Completion of conciliation process. 1.2.1 A conciliation proceeding before FWA shall be regarded as completed when: (a) the Parties have reached agreement for the settlement of the whole of the dispute; or (b) whether or not the Parties have reached agreement for the settlement of part of the dispute: (i) FWA is satisfied that there is no likelihood that, within a reasonable period, conciliation, or further conciliation, will result in agreement, or further agreement, by the Parties on terms for the settlement of the dispute or any matter in dispute; or (ii) the Parties to the dispute have informed FWA that there is no likelihood of agreement, or further agreement, on the dispute and FWA does not have a substantial reason to refuse to regard the conciliation proceeding as completed.
Sample 1Sample 2
Completion of conciliation process. 49.2.1 A conciliation proceeding before the FWC shall be regarded as completed when: (a) the Parties have reached agreement for the settlement of the whole of the dispute; or (b) whether or not the Parties have reached agreement for the settlement of part of the dispute: i) The FWC is satisfied that there is no likelihood that, within a reasonable period, conciliation, or further conciliation, will result in agreement, or further agreement, by the Parties on terms for the settlement of the dispute or any matter in dispute; or ii) The Parties to the dispute have informed the FWC that there is no likelihood of agreement, or further agreement, on matters in dispute and the FWC does not have a substantial reason to refuse to regard the conciliation proceeding as completed.
Sample 1
Completion of conciliation process. A conciliation proceeding before the AIRC shall be regarded as completed when:
Sample 1Sample 2
Completion of conciliation process. 45.4.1 A conciliation proceeding before the AIRC shall be regarded as completed when: 45.4.1.1 the Parties have reached agreement for the settlement of the whole of the dispute; or 45.4.1.2 whether or not the Parties have reached agreement for the settlement of part of the dispute:
Sample 1
Completion of conciliation process. 1.2.1 A conciliation proceeding before the Commission shall be regarded as completed when: (a) the Parties have reached agreement for the settlement of the whole of the dispute; or (b) whether or not the Parties have reached agreement for the settlement of part of the dispute: (i) the Commission is satisfied that there is no likelihood that, within a reasonable period, conciliation, or further conciliation, will result in agreement, or further agreement, by the Parties on terms for the settlement of the dispute or any matter in dispute; or (ii) the Parties to the dispute have informed the Commission that there is no likelihood of agreement, or further agreement, on the dispute and the Commission does not have a substantial reason to refuse to regard the conciliation proceeding as completed.
Sample 1

Related to Completion of conciliation process

  • Completion of Negotiations This Agreement represents complete collective bargaining and full agreement by the District and the Federation with respect to wages, hours of employment, and all other terms and conditions of employment which shall prevail during the term or terms hereof. This Agreement expresses the entire understanding between the parties and supersedes all previous agreements between them, written or oral. Any matter or subject not herein covered has been satisfactorily adjusted, compromised, or waived by the parties for the life of this Agreement.

  • Completion of Concrete Pours and Emergency Work (a) Except as provided in this sub-clause an Employee shall nor work or be required to work in the rain. (b) Employees shall not be required to start a concrete pour in Inclement Weather. (c) Where a concrete pour has been commenced prior to the commencement of a period of Inclement Weather Employees may be required to complete such concrete pour to a practical stage and for such work shall be paid at the rate of double time calculated to the next hour, and in the case of wet weather shall be provided with adequate wet weather gear. (d) If an Employee’s clothes become wet as a result of working in the rain during a concrete pour the Employee shall, unless the Employee has a change of dry working clothes available, be allowed to go home without loss of pay. (e) The provisions of clauses 32.7(c) and 32.7(d) hereof shall also apply in the case of emergency work where the Employees concerned and their delegates agree that the work is of an emergency nature and can start and/or proceed.

  • Escalation Process If Customer believes in good faith that Customer has not received quality or timely assistance in response to a support request or that Customer urgently need to communicate important support related business issues to Service Provider’s management, Customer may escalate the support request by contacting Service Provider and requesting that the support request be escalated to work with Customer to develop an action plan.

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

  • Commencement and Completion of Construction Subject to Unavoidable Delays, Developer shall cause construction of the Minimum Improvements to be undertaken and completed: (i) by no later than June 1, 2020; or (ii) by such other date as the parties shall mutually agree upon in writing. Time lost as a result of Unavoidable Delays shall be added to extend this date by a number of days equal to the number of days lost as a result of Unavoidable Delays. All work with respect to the Minimum Improvements shall be in conformity with the Construction Plans approved by the building official or any amendments thereto as may be approved by the building official. Developer agrees that it shall permit designated representatives of the City, upon reasonable notice (which does not have to be written), to enter upon the Development Property during the construction of the Minimum Improvements to inspect such construction and the progress thereof.

  • COMPLETION OF AGREEMENT This document comprises the entire agreement between the District and the Association in the matters lawfully within the scope of negotiation. Neither party shall have any obligation to meet and negotiate during the term of this agreement.

  • Completion of Construction Within 60 days of the completion of construction of the Project, Project Owner shall deliver to DoD copies of the FAA form 7460-2 for each ASN, including the final coordinates for each turbine erected.

  • Additional Wet Weather Procedure 14.15.1 Remaining On Site a) for more than an accumulated total of four hours of ordinary time in any one day; or b) after the meal break, as provided for in clause 17.1 of the Award, for more than an accumulated total of 50% of the normal afternoon work time; or c) during the final two hours of the normal work day for more than an accumulated total of one hour, the Enterprise will not be entitled to require the employees to remain on site beyond the expiration of any of the above circumstances.

  • Evaluation Process ‌ A. The immediate supervisor will meet with an employee at the start of their review period to discuss performance expectations. The employee will receive copies of their performance expectations as well as notification of any modifications made during the review period. Employee work performance will be evaluated during probationary, trial service and transition review periods and at least annually thereafter. Notification will be given to a probationary or trial service employee whose work performance is determined to be unsatisfactory. B. The supervisor will discuss the evaluation with the employee. The employee will have the opportunity to provide feedback on the evaluation. The discussion may include such topics as: 1. Reviewing the employee’s performance; 2. Identifying ways the employee may improve their performance; 3. Updating the employee’s position description, if necessary; 4. Identifying performance goals and expectations for the next appraisal period; and 5. Identifying employee training and development needs. C. The performance evaluation process will include, but not be limited to, a written performance evaluation on forms used by the Employer, the employee’s signature acknowledging receipt of the forms, and any comments by the employee. A copy of the performance evaluation will be provided to the employee at the time of the review. A copy of the final performance evaluation, including any employee or reviewer comments, will be provided to the employee. The original performance evaluation forms, including the employee’s comments, will be maintained in the employee’s personnel file. D. If an employee disagrees with their performance evaluation, the employee has the right to attach a rebuttal. E. The performance evaluation process is subject to the grievance procedure in Article 30. The specific content of a performance evaluation is not subject to the grievance procedure. F. Performance evaluations will not be used to initiate personnel actions such as transfer, promotion, or discipline.

  • Escalation Procedure Tentative Rates for those species and products listed in A4a are subject to quarterly escalation in accordance with the following pro- cedures: The calendar quarter index average for each price index described in A5 is the arithmetic average of the three such monthly price indices preceding January 1, April 1, July 1, and October 1. The difference between calendar quarter index average and Base Index listed in A4a shall be the basis for quarterly escalation. To arrive at Current Contract Rates for timber Scaled during the preceding calendar quarter, Tentative Rates for each species shall be reduced or increased by such difference, except when the calendar quarter index average is: (a) Less than the Base Index, the reduction shall not result in a rate below Base Rate or (b) Greater than the Base Index, the increase shall not exceed the difference between Tentative Rate and Base Rate. In the event of Contract Term Extension, the escala- tion procedure will be used during the extension period, except that adjusted payment rates for any calendar quar- ter cannot be less than Tentative Rates, for each species and product group, established under B8.23 for the ex- tension period.

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