Prime Time PTO request Sample Clauses

Prime Time PTO request. 15 1. From and after the nurses’ most recent date of employment until the nurse’s 16 fourth (4th) anniversary of continuous employment, the nurse may take 1 week of Prime 17 Time in a calendar year. 19 2. From and after the nurse’s fourth (4th) anniversary of continuous employment 20 until the nurse’s ninth (9th) anniversary of continuous employment, the nurse may take 2 21 weeks of Prime Time in a calendar year. 23 3. From and after the nurse’s ninth (9th) anniversary of continuous employment until 24 the nurse’s twentieth (20th ) anniversary of continuous of employment, the nurse may 25 take 3 weeks of Prime Time in a calendar year. 27 4. Nurses with twenty years or more of employment can take up to 4 weeks of 28 Prime Time in a calendar year.
Sample 1
AutoNDA by SimpleDocs
Prime Time PTO request. 1. 1. From and after the nurses’ most recent date of employment until the nurse’s fourth (4th) anniversary of continuous employment, the nurse may take 1 week of Prime Time in a calendar year. 2. 2. From and after the nurse’s fourth (4th) anniversary of continuous employment until the nurse’s ninth (9th) anniversary of continuous employment, the nurse may take 2 weeks of Prime Time in a calendar year. 3. 3. From and after the nurse’s ninth (9th) anniversary of continuous employment until the nurse’s twentieth (20th ) anniversary of continuous of employment, the nurse may take 3 weeks of Prime Time in a calendar year. 4. 4. Nurses with twenty years or more of employment can take up to 4 weeks of Prime Time in a calendar year.
Sample 1
Prime Time PTO request. 9 1. All nurses taking or making PTO requests during prime time will be 11 2. A nurse must request the actual days that he/she wishes to be gone.
Sample 1

Related to Prime Time PTO request

  • HOW TO REQUEST SERVICE To request service for the Covered Product, contact the Administrator toll-free at 833.749.8726, or go online to xxx.xxxxxxxxx.xxx/xxxxxxxxxxx. All repairs must be authorized by the Administrator prior to service being completed. Claims for unauthorized repairs will be denied. Many oversights, which are not covered under this Agreement, can be due to simple circumstances such as the Covered Product not being switched on, being unplugged, or a fuse blown at the junction box. To avoid a non-covered claim, perform a hard reset as illustrated by the manufacturer in the owner’s manual of Your Covered Product. If You refuse service on a Covered Product after We have dispatched the authorized technician to Your location, You will be billed for that servicer’s applicable trip charge. If You refuse service on a Covered Product, We are no longer responsible for any costs associated with the repair or replacement of Your Covered Product and may choose to refund You the prorated cost of this Agreement. If the cost of this Agreement is refunded at full cost or at a prorated cost, this Agreement will be considered fulfilled and no further action to repair or replace Your Covered Product will be considered.

  • Response Times Qubit bases its response times and the actions it takes to resolve problems on an assessment of the impact of the reported technical issue. The more serious the impact, the higher the assigned priority. For all support issues relating to Customer, Qubit will respond in accordance with Table 1: P1 1 hour 4 hours P2 1 hour 8 hours P3 4 hours 72 hours P4 1 business day Next or a later major release **The Priority Levels are defined in Section II(2) below.

  • Response to Demand Letter Within 10 days after the receipt of the Demand Letter, RMC shall either: (a) cure the breach to OIG’s satisfaction and pay the applicable Stipulated Penalties or (b) request a hearing before an HHS administrative law judge (ALJ) to dispute OIG’s determination of noncompliance, pursuant to the agreed upon provisions set forth below in Section X.E. In the event RMC elects to request an ALJ hearing, the Stipulated Penalties shall continue to accrue until RMC cures, to OIG’s satisfaction, the alleged breach in dispute. Failure to respond to the Demand Letter in one of these two manners within the allowed time period shall be considered a material breach of this CIA and shall be grounds for exclusion under Section X.D.

  • Response Time PROVIDING PARTY shall respond to and resolve any problems in connection with the Corporate Services for RECEIVING PARTY within a commercially reasonable period of time, using response and proposed resolution times consistent with its response and resolution of such problems for itself.

  • Optional Xactimate Response Attachment (Part 2)

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

  • Information Request The Owner Trustee shall provide any information regarding the Issuer in its possession reasonably requested by the Servicer, the Administrator, the Seller or any of their Affiliates, in order to comply with or obtain more favorable treatment under any current or future law, rule, regulation, accounting rule or principle.

  • Interconnection Request This Section 3 shall not apply to any proposed modifications by Interconnection Customer to its facilities for which Interconnection Customer must make an Interconnection Request under the Tariff. In such circumstances, the Interconnection Customer and Transmission Provider shall follow the requirements of Subpart A of Part IV of the Tariff.

  • Right to request 7.4.4(a) An employee entitled to parental leave pursuant to the provisions of 7.4.2 may request the employer to allow the employee:

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

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