Emergency Schedule Change Sample Clauses

Emergency Schedule Change. In the event of an emergency or other unusual circumstance 10 as determined by the principal or other immediate supervisor, an employee’s work schedule may 11 be temporarily changed. In situations affecting more than one worksite or department or more than 12 approximately fifty (50) employees, management will notify the Association of the change in 13 schedule. However, undue hardship on an employee will be dealt with on a case by case basis. The 14 Board agrees to meet with the Association to discuss make-up days when schools are closed due 15 to an emergency.
AutoNDA by SimpleDocs
Emergency Schedule Change. In the event of an emergency or other unusual circumstance 35 as determined by the principal or other immediate supervisor, an employee’s work schedule may 36 be temporarily changed. In situations affecting more than one worksite or department or more than 37 approximately fifty (50) employees, management will notify the Association of the change in 38 schedule. However, undue hardship on an employee will be dealt with on a case by case basis. The 39 Board agrees to meet with the Association to discuss make-up days when schools are closed due 40 to an emergency. 42 (4) Make-Up Due to Suspended Operations or Declared Emergency: If possible, employees 43 will be notified prior to the beginning of the work day when it is necessary to close schools as a 44 result of a hurricane or other declared emergency. Failure to make up missed time during the 45 scheduled work year or use appropriate leave on make-up days will result in a loss of 46 corresponding wages, with pay to be deducted from the employee’s paycheck for time missed. If 1 an employee terminates employment prior to the end of the work year, pay will be deducted from 2 his or her final paycheck. The SPALC Labor/Management Committee will prepare a schedule for 3 make-up of missed days to be provided to employees as soon as possible following a return to
Emergency Schedule Change. If the change is the result of a condition that could not have reasonably been anticipated seven (7) days in advance, such as the illness or termination of another employee, the Authority need not provide the seven (7) days’ notice.

Related to Emergency Schedule Change

  • Emergency/Declared Disaster Requirements In the event of an emergency or if Orange County is declared a disaster area by the County, state or federal government, this Contract may be subjected to unusual usage. The Contractor shall service the County during such an emergency or declared disaster under the same terms and conditions that apply during non-emergency/disaster conditions. The pricing quoted by the Contractor shall apply to serving the County’s needs regardless of the circumstances. If the Contractor is unable to supply the goods/services under the terms of the Contract, then the Contractor shall provide proof of such disruption and a copy of the invoice for the goods/services from the Contractor’s supplier(s). Additional profit margin as a result of supplying goods/services during an emergency or a declared disaster shall not be permitted. In the event of an emergency or declared disaster, emergency purchase order numbers will be assigned. All applicable invoices from the Contractor shall show both the emergency purchase order number and the Contract number.

  • Emergency Thresholds The following matrix presents the emergency thresholds that, if reached by any of the services mentioned above for a TLD, would cause the emergency transition of the Registry for the TLD as specified in Section 2.13 of this Agreement. DNS Service (all servers) 4-hour total downtime / week DNSSEC proper resolution 4-hour total downtime / week EPP 24-hour total downtime / week RDDS (WHOIS/Web-based WHOIS) 24-hour total downtime / week Data Escrow Breach of the Registry Agreement as described in Specification 2, Part B, Section 6.

  • Emergency Escalation Escalation is strictly for purposes of notifying and investigating possible or potential issues in relation to monitored services. The initiation of any escalation and the subsequent cooperative investigations do not in themselves imply that a monitored service has failed its performance requirements. Escalations shall be carried out between ICANN and Registry Operators, Registrars and Registry Operator, and Registrars and ICANN. Registry Operators and ICANN must provide said emergency operations departments. Current contacts must be maintained between ICANN and Registry Operators and published to Registrars, where relevant to their role in escalations, prior to any processing of an Emergency Escalation by all related parties, and kept current at all times.

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