Step Three - Formal Written Process Sample Clauses

Step Three - Formal Written Process. Commander 1. If the formal written grievance is not resolved in Step Two, or if no answer has been received from his/her immediate management supervisor within seven (7) calendar days from receiving the written grievance, the grievant may within seven (7) calendar days present the grievance in writing to his/her Commander. 2. Failure of the grievant to take this action will constitute a waiver and bar to the grievance. 3. The Commander shall render his/her decision and comments in writing and return them to the grievant within seven (7) calendar days after receiving the grievance.
Sample 1
AutoNDA by SimpleDocs

Related to Step Three - Formal Written Process

  • Formal Process STEP 3 –

  • Formal Grievance Procedure 1. In the event that a complaint cannot be resolved informally, the parties shall pursue the first step in the formal grievance procedure before making any application for arbitration, unless the College and the AAUP agree in writing to alter the procedure or waive one or more of the steps by proceeding directly to arbitration. 2. Upon written request of the AAUP Contract Compliance Officer, the College shall submit any requested documents in its possession which may be necessary for investigation of the grievance. The College shall deliver such documents as soon as is reasonably possible, but no later than seven (7) days after receipt of a written request. 3. Internal Steps in the Procedure a. Step One: The Director of Human Resources (1) Within thirty (30) days of when the AAUP learns of, or in the exercise of reasonable diligence should have learned of, an alleged violation of the provisions of this Agreement, the AAUP shall submit to the Director of Human Resources a completed Faculty Grievance Form or a dated, signed, written description of the grievance, clearly labeled "grievance" containing substantially the same information as provided for on the Faculty Grievance Form. (2) Within eight (8) days of receipt of the written grievance, the Director of Human Resources shall convene a meeting to discuss the grievance. Such meeting shall include the grievant(s) and/or the designated representative(s) of the AAUP and shall be scheduled at a time which is mutually convenient to the parties. (3) The Director of Human Resources shall attempt to determine the facts pertaining to the grievance and shall notify the grievant and the AAUP in writing of his/her decision within eight (8) days in a Grievance Disposition Form or in a document containing substantially the same information as contained in a Grievance Disposition Form, which shall include written details of the reasons which support the decision. (4) Within eight (8) days after receipt of the disposition of the Director of Human Resources, the AAUP may appeal the decision in writing to the College Grievance Officer, by submitting a Grievance Disposition Reaction Form or a document containing substantially the same information as contained in a Grievance Disposition Reaction Form. (5) By agreement, the parties may decide to advance the grievance to step two of the procedure, or to appeal directly to arbitration at step D(4) of this article.

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

  • Contract Revisions Notwithstanding Contract Exhibit C, Special Contract Conditions section 6.9, the following types of revisions can be made to the Contract without a formal Contract amendment, upon written notice: Revisions by the Contractor: 1) Contractor’s Information and Contacts 2) Contractor’s Contract Manager Revisions by the Department: 1) Department’s Contract Manager 2) Department’s Quarterly Sales Report (Contract Exhibit J) 3) Contractor Performance Survey (Contract Exhibit I) Contract Exhibit C, Special Contract Conditions section 6.9, applies to all other modifications to the Contract.

  • Formal Grievance Step 1 6

  • Commercial Price List Reductions Where NYS Net Prices are based on a discount from Contractor’s list prices, price decreases shall take effect automatically during the Contract term and apply to Purchase Orders submitted on or after the date Contractor lowers its pricing to its customers generally or to similarly situated government customers during the Contract term; or

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

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

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Approval Process Tenant shall notify Landlord whether it approves of the submitted working drawings within three business days after Landlord’s submission thereof. If Tenant disapproves of such working drawings, then Tenant shall notify Landlord thereof specifying in reasonable detail the reasons for such disapproval, in which case Landlord shall, within five business days after such notice, revise such working drawings in accordance with Tenant’s objections and submit the revised working drawings to Tenant for its review and approval. Tenant shall notify Landlord in writing whether it approves of the resubmitted working drawings within one business day after its receipt thereof. This process shall be repeated until the working drawings have been finally approved by Landlord and Tenant. If Tenant fails to notify Landlord that it disapproves of the initial working drawings within three business days (or, in the case of resubmitted working drawings, within one business day) after the submission thereof, then Tenant shall be deemed to have approved the working drawings in question. Any delay caused by Tenant’s unreasonable withholding of its consent or delay in giving its written approval as to such working drawings shall constitute a Tenant Delay Day (defined below). If the working drawings are not fully approved (or deemed approved) by both Landlord and Tenant by the 15th business day after the delivery of the initial draft thereof to Tenant, then each day after such time period that such working drawings are not fully approved (or deemed approved) by both Landlord and Tenant shall constitute a Tenant Delay Day.

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