CHANGES IN SHIFT ASSIGNMENT Sample Clauses

The "Changes in Shift Assignment" clause defines the employer's right to modify employees' scheduled work shifts. Typically, this clause outlines the procedures for notifying employees of shift changes, such as required advance notice or methods of communication, and may specify circumstances under which changes can be made, like operational needs or emergencies. Its core practical function is to provide flexibility for the employer to adjust staffing as needed while establishing clear expectations for employees regarding how and when their work schedules may be altered.
CHANGES IN SHIFT ASSIGNMENT. In recognition that team members make plans and commitments around their shift schedule, every reasonable attempt will be made to provide Operating and Shift Engineers with 30 calendar days notice of a permanent change in shift assignment and 48 hours notice of temporary change in shift assignment.
View SourceView Similar (10)
CHANGES IN SHIFT ASSIGNMENT. An employee must be notified of a change in normally scheduled shift twenty four (24) hours before the change is to take place except in cases of emer- gencies. If an employee is required to work non-scheduled hours, the employee will be compen- sated at the rate of one and one-half (1 ½) employee's basic hourly rate of pay.
View SourceView Similar (3)
CHANGES IN SHIFT ASSIGNMENT. Hebe shall not change working hours or shift assignments of employees or positions except for lawful purposes in the exercise of its management rights.
View Source
CHANGES IN SHIFT ASSIGNMENT. The City shall not substantially change working hours or shift assignments of employees or positions except for lawful purposes and then only after the employee has been given a minimum of 21 calendar days written notice prior to the change in the exercise of its management rights. This provision does not prohibit insubstantial changes or changes within a menu of shifts pre-approved for the position. For all unit members that conduct the majority of their duties outdoors summer schedules will begin the first day of Summer to first day of Fall with a beginning shift of 5 AM. A two-week extension can be added to those dates with a mutual agreement between the Association and the Department Head.
View Source
CHANGES IN SHIFT ASSIGNMENT. The shift to which a sergeant desires to be assigned shall be bid upon by seniority in September of the preceding year, except in the event such a bid shall result in a shift which possesses an unbalanced mixture of experience or necessary skills, the Chief shall have the right to balance the shift as considered appropriate. In the event a sergeant rotates out of a specialty unity during mid-year, the sergeant will be assigned by seniority in accordance with the bid pick selected the preceding September. All rotations shall be scheduled to rotate on January 1 and sergeants rotating from such assignments on January 1 shall participate in the regular shift bid held the preceding September. When manpower must be changed from one shift to another within the Patrol Division during a calendar year, the shift of the most junior sergeant in the Patrol Division will be changed to meet manpower requirements. If the change results in a second manpower shortage, the shift of the second most junior sergeant will be changed to accommodate the secondary shortage. The process for changing shifts shall continue in the same manner with the succeeding junior sergeant until no further manpower changes are required.
View Source
CHANGES IN SHIFT ASSIGNMENT. The Chief of Police shall have the discretion to change shift assignments if at any time he establishes that such changes are necessary for the effective operations of the Department. Changes shall not be made in any manner which are arbitrary or capricious. All shift assignments shall be reviewed in not less than an annual basis in an effort to accommodate the scheduling preference of senior officers. In addition, once annually, beginning twelve (12) months after the implementation of this shift schedule, any officer who desires to be transferred to another shift and is aware of a vacancy in that shift or another officer willing to be reciprocally transferred, shall have the right to make an application through the chain of command to the Chief of Police and such a transfer request shall not be unreasonably denied.
View Source

Related to CHANGES IN SHIFT ASSIGNMENT

  • Shift Assignments When an opening occurs in a shift assignment in an appropriate work group at a location, preference shall be given to employees within the classification who possess the training, ability and any required special qualifications to perform the work required, on the basis of seniority. In the event that no employee desires a shift assignment, employees shall be selected in order of inverse seniority. This provision shall not apply to necessary training assignments. This provision shall not in itself alter the practice of rotating shifts where such practice presently exists. No employee who has a regular shift assignment on the effective date of the Agreement shall be involuntarily displaced from such shift assignment as a result of this Article.

  • Change of Control; Assignment and Subcontracting Except as set forth in this Section 7.5, neither party may assign any of its rights and obligations under this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any subcontracting arrangement that relates to any Critical Function (as identified in Section 6 of Specification 10) for the TLD (a “Material Subcontracting Arrangement”) shall be deemed an assignment. (a) Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any assignment or Material Subcontracting Arrangement, and any agreement to assign or subcontract any portion of the operations of the TLD (whether or not a Material Subcontracting Arrangement) must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator. (b) Within thirty (30) calendar days of either such notification pursuant to Section 7.5(a), ICANN may request additional information from Registry Operator establishing (i) compliance with this Agreement and (ii) that the party acquiring such control or entering into such assignment or Material Subcontracting Arrangement (in any case, the “Contracting Party”) and the ultimate parent entity of the Contracting Party meets the ICANN-­‐adopted specification or policy on registry operator criteria then in effect (including with respect to financial resources and operational and technical capabilities), in which case Registry Operator must supply the requested information within fifteen (15) calendar days. (c) Registry Operator agrees that ICANN’s consent to any assignment, change of control or Material Subcontracting Arrangement will also be subject to background checks on any proposed Contracting Party (and such Contracting Party’s Affiliates). (d) If ICANN fails to expressly provide or withhold its consent to any assignment, direct or indirect change of control of Registry Operator or any Material Subcontracting Arrangement within thirty (30) calendar days of ICANN’s receipt of notice of such transaction (or, if ICANN has requested additional information from Registry Operator as set forth above, thirty (30) calendar days of the receipt of all requested written information regarding such transaction) from Registry Operator, ICANN shall be deemed to have consented to such transaction. (e) In connection with any such assignment, change of control or Material Subcontracting Arrangement, Registry Operator shall comply with the Registry Transition Process. (f) Notwithstanding the foregoing, (i) any consummated change of control shall not be voidable by ICANN; provided, however, that, if ICANN reasonably determines to withhold its consent to such transaction, ICANN may terminate this Agreement pursuant to Section 4.3(g), (ii) ICANN may assign this Agreement without the consent of Registry Operator upon approval of the ICANN Board of Directors in conjunction with a reorganization, reconstitution or re-­‐incorporation of ICANN upon such assignee’s express assumption of the terms and conditions of this Agreement, (iii) Registry Operator may assign this Agreement without the consent of ICANN directly to a wholly-­‐owned subsidiary of Registry Operator, or, if Registry Operator is a wholly-­‐owned subsidiary, to its direct parent or to another wholly-­‐owned subsidiary of its direct parent, upon such subsidiary’s or parent’s, as applicable, express assumption of the terms and conditions of this Agreement, and (iv) ICANN shall be deemed to have consented to any assignment, Material Subcontracting Arrangement or change of control transaction in which the Contracting Party is an existing operator of a generic top-­‐level domain pursuant to a registry agreement between such Contracting Party and ICANN (provided that such Contracting Party is then in compliance with the terms and conditions of such registry agreement in all material respects), unless ICANN provides to Registry Operator a written objection to such transaction within ten (10) calendar days of ICANN’s receipt of notice of such transaction pursuant to this Section 7.5. Notwithstanding Section 7.5(a), in the event an assignment is made pursuant to clauses (ii) or (iii) of this Section 7.5(f), the assigning party will provide the other party with prompt notice following any such assignment.

  • Changes in Agreement Any changes deemed necessary in this Agreement may be made by mutual agreement at any time during the existence of this Agreement.