Planned PTO Requests Sample Clauses

Planned PTO Requests. All requests for planned time off must be received via the Employer’s electronic scheduling system at least two weeks in advance of the start of the requested time off. Approval is based on operational consideration and the employee having available PTO. Requests will be approved or denied timely but no later than 72 business hours once being received. If an employee submits a request less than two weeks in advance and the employer is unable to approve based on operational need, then the employee has the option to find their own coverage and be paid PTO. Employee must follow the correct process under Section 9.11 for shift substitution. If the employee does not have enough PTO at the time it is to be taken, the request will be denied.
AutoNDA by SimpleDocs
Planned PTO Requests. All requests for planned time off must be received via the Employer’s electronic scheduling system at least ten (10) calendar days in advance of the start of the requested time off. Approval is based on the employee having available PTO. Requests will be approved or denied within four (4) calendar days once received.

Related to Planned PTO Requests

  • Service Requests In support of services outlined in this Agreement, the Service Provider will respond to service related incidents and/or requests submitted by the Customer within the following time frames:

  • Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

  • Bona Fide Request/New Business Request Process for Further Unbundling 6.1 BellSouth shall, upon request of <<customer_name>>, provide to <<customer_name>> access to its network elements at any technically feasible point for the provision of <<customer_name>>'s telecommunications service where such access is necessary and failure to provide access would impair the ability of <<customer_name>> to provide services that it seeks to offer. Any request by <<customer_name>> for access to a network element, interconnection option, or for the provisioning of any service or product that is not already available shall be treated as a Bona Fide Request/New Business Request (BFR/NBR), and shall be submitted to BellSouth pursuant to the BFR/NBR process. 6.2 <<customer_name>> shall submit any BFR/NBR in writing to <<customer_name>>’s Account Manager. The BFR/NBR shall specifically identify the requested service date, technical requirements, space requirements and/or such specifications that clearly define the request such that BellSouth has sufficient information to analyze and prepare a response. The BFR/NBR also shall include <<customer_name>>’s designation of the request as being (i) pursuant to the Telecommunications Act of 1996 or (ii) pursuant to the needs of the business.

  • Special Requests Additional Services will be considered by request and billed separately: -Waxing -Shampooing of rugs and carpets -Additional Cleaning of areas or additional cleaning services not quoted in the Master Agreement’s Schedule, Building Areas and Janitorial Standards, and/or “Scope of Work” per agency.

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

  • Data Subject Requests To the extent legally permitted, Okta shall promptly notify Customer if Okta receives a request from a Data Subject to exercise the Data Subject's right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, object to the Processing, or its right not to be subject to an automated individual decision making (“Data Subject Request”). Factoring into account the nature of the Processing, Okta shall assist Customer by appropriate organizational and technical measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Service, does not have the ability to address a Data Subject Request, Okta shall, upon Customer’s request, provide commercially- reasonable efforts to assist Customer in responding to such Data Subject Request, to the extent that Okta is legally authorized to do so, and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Okta’s provision of such assistance.

  • Notification of Legal Requests Contractor shall immediately notify City upon receipt of any subpoenas, service of process, litigation holds, discovery requests and other legal requests (“Legal Requests”) related to all data given to Contractor by City in the performance of this Agreement (“City Data” or “Data”), or which in any way might reasonably require access to City’s Data, and in no event later than 24 hours after it receives the request. Contractor shall not respond to Legal Requests related to City without first notifying City other than to notify the requestor that the information sought is potentially covered under a non-disclosure agreement. Contractor shall retain and preserve City Data in accordance with the City’s instruction and requests, including, without limitation, any retention schedules and/or litigation hold orders provided by the City to Contractor, independent of where the City Data is stored.

  • Employee-Requested Schedule Changes Overtime-eligible employees’ workweeks and work schedules may be changed at the employee’s request and with the Employer’s approval, provided the Employer’s business and customer service needs are met and no overtime expense is incurred.

  • ERISA Notices and Requests Furnish Agent with immediate written notice in the event that (i) any Borrower or any member of the Controlled Group knows or has reason to know that a Termination Event has occurred, together with a written statement describing such Termination Event and the action, if any, which such Borrower or any member of the Controlled Group has taken, is taking, or proposes to take with respect thereto and, when known, any action taken or threatened by the Internal Revenue Service, Department of Labor or PBGC with respect thereto, (ii) any Borrower or any member of the Controlled Group knows or has reason to know that a prohibited transaction (as defined in Sections 406 of ERISA and 4975 of the Code) has occurred together with a written statement describing such transaction and the action which such Borrower or any member of the Controlled Group has taken, is taking or proposes to take with respect thereto, (iii) a funding waiver request has been filed with respect to any Plan together with all communications received by any Borrower or any member of the Controlled Group with respect to such request, (iv) any increase in the benefits of any existing Plan or the establishment of any new Plan or the commencement of contributions to any Plan to which any Borrower or any member of the Controlled Group was not previously contributing shall occur, (v) any Borrower or any member of the Controlled Group shall receive from the PBGC a notice of intention to terminate a Plan or to have a trustee appointed to administer a Plan, together with copies of each such notice, (vi) any Borrower or any member of the Controlled Group shall receive any favorable or unfavorable determination letter from the Internal Revenue Service regarding the qualification of a Plan under Section 401(a) of the Code, together with copies of each such letter; (vii) any Borrower or any member of the Controlled Group shall receive a notice regarding the imposition of withdrawal liability, together with copies of each such notice; (viii) any Borrower or any member of the Controlled Group shall fail to make a required installment or any other required payment under Section 412 of the Code on or before the due date for such installment or payment; (ix) any Borrower or any member of the Controlled Group knows that (a) a Multiemployer Plan has been terminated, (b) the administrator or plan sponsor of a Multiemployer Plan intends to terminate a Multiemployer Plan, or (c) the PBGC has instituted or will institute proceedings under Section 4042 of ERISA to terminate a Multiemployer Plan.

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