Use and Approval of FMLA Leave Sample Clauses

Use and Approval of FMLA Leave. (1) The University shall approve FMLA leave for an eligible employee as long as the reasons for absence qualify under the FMLA and the employee has not exhausted the employee's four hundred and eighty (480) hours within the appropriate 12-month period for such leave. The employee may request FMLA leave as accrued leave, leave without pay, or a combination of both. (2) The University may require that the employee use accrued leave with pay prior to requesting leave without pay for four hundred and eighty (480) hours (12 workweeks) of FMLA leave. Requiring the use of paid leave shall be applied consistently and may not be used merely to exhaust the employee's leave balance in order to prohibit the use of paid leave while on leave without pay as provided for in this Policy. (3) After the President or designee has acquired knowledge that the leave is being taken for an FMLA required reason, the President or designee shall within two business days, absent extenuating circumstances, notify the employee of the period of FMLA leave to be granted, including the date of return to employment. If the notice is oral, it shall be confirmed in writing no later than the following payday (unless the payday is less than one week after the oral notice, in which case the notice must be no later than the subsequent payday).
AutoNDA by SimpleDocs
Use and Approval of FMLA Leave. (1). The University shall approve FMLA leave for an eligible employee as long as the reasons for absence qualify under the FMLA and the employee has not exhausted the employee's four hundred and eighty (480) hours within the appropriate 12-month period for such leave. The employee may request FMLA leave as accrued leave, leave without pay, or a combination of both.
Use and Approval of FMLA Leave. (1) The University will approve FMLA leave for an eligible faculty member as long as the reasons for absence qualify under the FMLA and the faculty member has not exhausted his or her four hundred and eighty (480) hours within the appropriate twelve (12) month period. (2) The faculty member may request FMLA leave as accrued sick and/or annual leave, leave without pay, or a combination thereof. (3) The University may require that the faculty member use accrued leave with pay prior to requesting leave without pay for four hundred and eighty (480) hours (12 work weeks) of FMLA leave. Requiring the use of paid leave will be applied consistently and may not be used merely to exhaust the faculty member's leave balance in order to prohibit the use of paid leave while on leave without pay as provided for in section 19.12(e). (4) Faculty members on approved FMLA leave may not be employed elsewhere without the prior written approval of the University.
Use and Approval of FMLA Leave. (1) The President or his/her representative shall approve FMLA leave for an eligible employee as long as the reasons for absence qualify under the FMLA and the employee has not exhausted the employee's four hundred and eighty (480) hours within the appropriate 12-month period for such leave. The employee may request FMLA leave as accrued leave, leave without pay, or a combination of both. (2) The University may require that the employee use accrued leave with pay prior to requesting leave without pay for four hundred and eighty (480) hours (12 workweeks) of FMLA leave. Requiring the use of paid leave shall be applied consistently and may not be used merely to exhaust the employee's leave balance in order to prohibit the use of paid leave while on leave without pay as provided for in Section 17.2(c). (3) Employees on approved FMLA may not be employed elsewhere without the written approval of the University.

Related to Use and Approval of FMLA Leave

  • Certification Regarding Prohibition of Boycotting Israel (Tex Gov. Code 2271)

  • Convicted, Discriminatory, Antitrust Violator, and Suspended Vendor Lists In accordance with sections 287.133, 287.134, and 287.137, F.S., the Contractor is hereby informed of the provisions of sections 287.133(2)(a), 287.134(2)(a), and 287.137(2)(a), F.S. For purposes of this Contract, a person or affiliate who is on the Convicted Vendor List, the Discriminatory Vendor List, or the Antitrust Violator Vendor List may not perform work as a contractor, supplier, subcontractor, or consultant under the Contract. The Contractor must notify the Department if it or any of its suppliers, subcontractors, or consultants have been placed on the Convicted Vendor List, the Discriminatory Vendor List, or the Antitrust Violator Vendor List during the term of the Contract. In accordance with section 287.1351, F.S., a vendor placed on the Suspended Vendor List may not enter into or renew a contract to provide any goods or services to an agency after its placement on the Suspended Vendor List. A firm or individual placed on the Suspended Vendor List pursuant to section 287.1351, F.S., the Convicted Vendor List pursuant to section 287.133, F.S., the Antitrust Violator Vendor List pursuant to section 287.137, F.S., or the Discriminatory Vendor List pursuant to section 287.134, F.S., is immediately disqualified from Contract eligibility.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Authorization to Release and Transfer Necessary Personal Information The Grantee hereby explicitly and unambiguously consents to the collection, use and transfer, in electronic or other form, of the Grantee’s personal data by and among, as applicable, the Company and its Subsidiaries for the exclusive purpose of implementing, administering and managing the Grantee’s participation in the Plan. The Grantee understands that the Company may hold certain personal information about the Grantee, including, but not limited to, the Grantee’s name, home address and telephone number, date of birth, social security number (or any other social or national identification number), salary, nationality, job title, number of Award Units and/or shares of Common Stock held and the details of all Award Units or any other entitlement to shares of Common Stock awarded, cancelled, vested, unvested or outstanding for the purpose of implementing, administering and managing the Grantee’s participation in the Plan (the “Data”). The Grantee understands that the Data may be transferred to the Company or to any third parties assisting in the implementation, administration and management of the Plan, that these recipients may be located in the Grantee’s country or elsewhere, and that any recipient’s country (e.g., the United States) may have different data privacy laws and protections than the Grantee’s country. The Grantee understands that he or she may request a list with the names and addresses of any potential recipients of the Data by contacting his or her local human resources representative or the Company’s stock plan administrator. The Grantee authorizes the recipients to receive, possess, use, retain and transfer the Data, in electronic or other form, for the sole purpose of implementing, administering and managing the Grantee’s participation in the Plan, including any requisite transfer of such Data to a broker or other third party assisting with the administration of Award Units under the Plan or with whom shares of Common Stock acquired pursuant to the vesting of the Award Units or cash from the sale of such shares may be deposited. Furthermore, the Grantee acknowledges and understands that the transfer of the Data to the Company or to any third parties is necessary for the Grantee’s participation in the Plan. The Grantee understands that the Grantee may, at any time, view the Data, request additional information about the storage and processing of the Data, require any necessary amendments to the Data or refuse or withdraw the consents herein by contacting the Grantee’s local human resources representative or the Company’s stock plan administrator in writing. The Grantee further acknowledges that withdrawal of consent may affect his or her ability to vest in or realize benefits from the Award Units, and the Grantee’s ability to participate in the Plan. For more information on the consequences of refusal to consent or withdrawal of consent, the Grantee understands that he or she may contact his or her local human resources representative or the Company’s stock plan administrator.

  • Human Trafficking Prohibition Under Section 2155.0061 of the Texas Government Code, Contractor certifies that the individual or business entity named in this Contract is not ineligible to receive this Contract and acknowledges that this Contract may be terminated and payment withheld if this certification is inaccurate.

  • Certification Regarding Prohibition of Certain Terrorist Organizations (Tex Gov. Code 2270) Certification Regarding Prohibition of Boycotting Israel (Tex. Gov. Code 2271) 5 Certification Regarding Prohibition of Contracts with Certain Foreign-Owned Companies (Tex. Gov. 5 Code 2274) 5 Certification Regarding Prohibition of Discrimination Against Firearm and Ammunition Industries (Tex.

  • Compliance with Federal and State Work Authorization and Immigration Laws The Contractor and all subcontractors, suppliers and consultants must comply with all federal and state work authorization and immigration laws, and must certify compliance using the form set forth in Section 7 (“Georgia Security and Immigration Compliance Act Affidavits”). The required certificates must be filed with the Owner and copied maintained by the Contractor as of the beginning date of this contract and each subcontract, supplier contract, or consultant contract, and upon final payment to the subcontractor or consultant. State officials, including officials of the Georgia Department of Audits and Accounts, officials of the Owner, retain the right to inspect and audit the Project Site and employment records of the Contractor, subcontractors and consultants without notice during normal working hours until Final Completion, and as otherwise specified by law and by Rules and Regulations of the Georgia Department of Audits and Accounts.

  • Anti-Money Laundering and Red Flag Identity Theft Prevention Programs The Trust acknowledges that it has had an opportunity to review, consider and comment upon the written procedures provided by USBFS describing various tools used by USBFS which are designed to promote the detection and reporting of potential money laundering activity and identity theft by monitoring certain aspects of shareholder activity as well as written procedures for verifying a customer’s identity (collectively, the “Procedures”). Further, the Trust and USBFS have each determined that the Procedures, as part of the Trust’s overall Anti-Money Laundering Program and Red Flag Identity Theft Prevention Program, are reasonably designed to: (i) prevent each Fund from being used for money laundering or the financing of terrorist activities; (ii) prevent identity theft; and (iii) achieve compliance with the applicable provisions of the Bank Secrecy Act, Fair and Accurate Credit Transactions Act of 2003 and the USA Patriot Act of 2001 and the implementing regulations thereunder. Based on this determination, the Trust hereby instructs and directs USBFS to implement the Procedures on the Trust’s behalf, as such may be amended or revised from time to time. It is contemplated that these Procedures will be amended from time to time by the parties as additional regulations are adopted and/or regulatory guidance is provided relating to the Trust’s anti-money laundering and identity theft responsibilities. USBFS agrees to provide to the Trust: (a) Prompt written notification of any transaction or combination of transactions that USBFS believes, based on the Procedures, evidence money laundering or identity theft activities in connection with the Trust or any Fund shareholder; (b) Prompt written notification of any customer(s) that USBFS reasonably believes, based upon the Procedures, to be engaged in money laundering or identity theft activities, provided that the Trust agrees not to communicate this information to the customer; (c) Any reports received by USBFS from any government agency or applicable industry self-regulatory organization pertaining to USBFS’ Anti-Money Laundering Program or the Red Flag Identity Theft Prevention Program on behalf of the Trust; (d) Prompt written notification of any action taken in response to anti-money laundering violations or identity theft activity as described in (a), (b) or (c) immediately above; and (e) Certified annual and quarterly reports of its monitoring and customer identification activities pursuant to the Procedures on behalf of the Trust. The Trust hereby directs, and USBFS acknowledges, that USBFS shall (i) permit federal regulators access to such information and records maintained by USBFS and relating to USBFS’ implementation of the Procedures, on behalf of the Trust, as they may request, and (ii) permit such federal regulators to inspect USBFS’ implementation of the Procedures on behalf of the Trust.

  • Compliance with Federal Law, Regulations, and Executive Orders This is an acknowledgement that FEMA financial assistance will be used to fund all or a portion of the contract. The contractor will comply with all applicable Federal law, regulations, executive orders, FEMA policies, procedures, and directives.

  • Interlocal Cooperation Act RCW 39.34 allows cooperative purchasing between public agencies, and other political subdivisions. SMC 20.60.100 also allows non profits to use these agreements. If a public agency files or has filed an Intergovernmental Cooperative Purchasing Agreement with the City of Seattle, those agencies are eligible to purchase from Contracts established by the City. Such agencies may ask City of Seattle Contractors to accept orders from the agency, citing the City of Seattle contract as the basis for the order. The Vendor may accept or decline such orders. If the Vendor accepts an order from another public agency using the City of Seattle contract as the basis, the Vendor agrees to sell additional items at the contract prices, terms and conditions. The City of Seattle accepts no responsibility for the payment of the purchase price by other governmental agencies. Should the Vendor require additional pricing for such purchases, the Vendor is to name such additional pricing upon Offer to the City.

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