Advice Stage Sample Clauses

Advice Stage. If you agree to proceed to the advice stage, for Safeguarded / Defined Benefits you will start to incur fees once you have confirmed that you accept our charges. These will be sent to you beforehand in our document ‘Your Personalised Charges’. If we provide you with an ‘Abridged Advice’ Report there will be no charge for the report. For ‘full’ advice in respect of Safeguarded / Defined Benefit Pensions there will usually be a non-contingent fee (ie a fee that is chargeable irrespective of the advice provided or whether or not you follow the advice). The fee chargeable varies upon the size of the pension plans under review. There is a minimum charge of £3,000 for ‘full’ advice. If you qualify for a ‘contingent fee’ on the basis of your health or financial circumstances, we will advise you of this. If you qualify for this there is a minimum fee of £3,000 but any fee due above this amount is only payable if a transfer is recommended and transacted. For defined contribution plans, our fees would only become payable if you transact our advice, although the minimum fee of £3,000 would remain.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs

Related to Advice Stage

  • Joint Preparation The preparation of this Agreement has been a joint effort of the parties and the resulting documents shall not, solely as a matter of judicial construction, be construed more severely against one of the parties than the other.

  • LEAD HANDS 28.01 Lead hands may be appointed by the Gallery from time to time as the Gallery in its discretion deems necessary. Lead hand responsibilities generally include assigning and monitoring work performance, scheduling, administration and resolving work-related problems. Such persons shall receive an additional one dollar ($ 1.00) per hour for each hour worked for the duration of the appointment. This lead hand premium will not form part of the employee's regular straight time hourly rate.

  • Negotiation In the event of a controversy, dispute or claim arising out of, in connection with, or in relation to the interpretation, performance, nonperformance, validity or breach of this Agreement or otherwise arising out of, or in any way related to this Agreement or the transactions contemplated hereby, including any claim based on contract, tort, statute or constitution (collectively, “Agreement Disputes”), the Party claiming such Agreement Dispute shall give written notice to the other Party setting forth the Agreement Dispute and a brief description thereof (a “Dispute Notice”) pursuant to the terms of the notice provisions of Section 7.1 hereof. Following delivery of a Dispute Notice, the general counsels of the relevant Parties and/or such other executive officer designated by the relevant Party shall negotiate for a reasonable period of time to settle such Agreement Dispute; provided that such reasonable period shall not, unless otherwise agreed by the Parties in writing, exceed forty-five (45) calendar days from the time of receipt by a Party of a Dispute Notice; provided further, that in the event of any arbitration in accordance with Section 6.3 hereof, the relevant Parties shall not assert the defenses of statute of limitations and laches arising during the period beginning after the date of receipt of the Dispute Notice, and any contractual time period or deadline under this Agreement to which such Agreement Dispute relates occurring after the Dispute Notice is received shall not be deemed to have passed until such Agreement Dispute has been resolved.

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

  • Settlement Discussions This Agreement is part of a proposed settlement of matters that could otherwise be the subject of litigation among the Parties hereto. Nothing herein shall be deemed an admission of any kind. Pursuant to Federal Rule of Evidence 408 and any applicable state rules of evidence, this Agreement and all negotiations relating thereto shall not be admissible into evidence in any proceeding other than to prove the existence of this Agreement or in a proceeding to enforce the terms of this Agreement.

  • Lead Hand Employee who performs hands-on work in a group or small section of a department (usually four or fewer employees) and directs work assignments and is responsible for its completion. Employees providing work direction or supervision must be layered over (i.e. placed at a higher classification than) all employees to whom direction or supervision is provided. The resulting classification will be determined by the classification levels of the applicable job family.

  • Preparation Periods 31-1 The School District agrees to maintain daily preparation periods during the student day in all junior and senior high schools. At schools where block scheduling is in effect, the total preparation time provided shall be equal to the preparation time provided at schools not operating on a block schedule. 31-2 The School District shall maintain at each elementary school a minimum of two hundred and fifty (250) minutes preparation time per week per teacher, during the students’ instructional day, in not less than forty- (40) minute blocks. Each elementary school shall be allocated and assigned library aide hours per school day in accordance with the following schedule: This aide time is provided in addition to the assigned media clerk time. Library aide time is guaranteed for the school year once set on a school year basis. There will be no changes in library aide time allocated due to fluctuation in enrollment. This provision for allocating library aide time will only remain as part of this Agreement if librarians are used to provide preparation time to elementary teachers. 31-3 Preparation time provided for in this Article shall be utilized by teachers in a manner which enables further development and refinement of professional skills and for instructional effectiveness. 31-4 Although it does not relate to any mandatory subject of bargaining, the School District states that it is its aim and objective to establish a maximum class load of thirty (30) students in grades 4, 5, and 6. 00-0 Xxx Xxxxxxxx may direct use of teacher preparation periods if such directed use is infrequent, advance notice is given and the District’s use of the teacher’s preparation period must not consume an entire period.

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

  • Preparation Period During the preparation period, a teacher will have no other assignment except in an emergency situation. It is recognized that the preparation period is a scheduled part of the teacher's work day and the teacher is expected to be in his/her respective Building. If the teacher must leave the Building during his/her preparation and/or lunch period, he/she must notify the Building switchboard operator.

  • 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

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