Refusals and Violations Sample Clauses

Refusals and Violations. A. A refusal will be given on days when an employee is required to be available for work, work is offered and employee does not return a phone call. Bypass pay shall not apply when an employee has a refusal for any days of which an attempt to offer work as defined in Appendix A 5.08 A had been made. This process shall apply to free days however no refusal will be recorded on a Free Day.
View SourceView Similar (4)
Refusals and Violations. Four (4) refusals in a work period shall constitute a violation. If an employee accepts any job on a day in which they were previously marked as having a refusal, the refusal shall not be counted. A relief deck employee can only accrue one refusal on any given day. a. First (1st) Violation An employee that has one (1) violation must choose from all available jobs when called in order to fill their obligation of seventy-six (76) to eighty (80) hours or they shall be assigned for the work period following the violation. b. Second (2nd)
View SourceView Similar (3)
Refusals and Violations. A. A refusal will be given on days when an employee is required to be available for work, work is offered and employee does not return a phone call. Bypass pay shall not apply when an employee has a refusal for any days of which an attempt to offer work as defined in Appendix A 5.08 A had been made. This process shall apply to free days; however, no refusal will be recorded on a free day. 1. First call – If the employee does not respond within fifteen (15) to thirty (30) minutes of the first call, the Employer shall move on down the list. If the employee does not return the call it shall be refusal number one (1). 2. Second and third calls – If the employee does not respond within fifteen (15) to thirty (30) minutes of the first call, for any additional calls, dispatch will place a call to the relief employee for work available during daily dispatch. Should the relief deck employees not pick up the call placed by the dispatcher, a message will be left for the employee. Dispatch need not observe the fifteen (15) to thirty
View Source
Refusals and Violations. A. A refusal will be given on days when an employee is required to be available for work, work is offered and employee does not return a phone call. Bypass pay shall not apply when an employee has a refusal for any days of which an attempt to offer work as defined in Appendix A 5.08 A had been made. This process shall apply to free days however no refusal will be recorded on a Free Day. 1. First (1st) Call – If the employee does not respond within fifteen (15) to thirty (30) minutes of the first (1st) call, the employer shall move on down the list. If the employee does not return the call it shall be refusal number one (1).
View Source

Related to Refusals and Violations

  • WAGE VIOLATIONS Contractor represents and warrants as previously certified in Contractor’s Bidder’s Certification, that during the term of this Contract and the three (3) year period immediately preceding the award of the Contract, Contractor has not been determined, by a final and binding citation and notice of assessment issued by the Washington Department of Labor and Industries or through a civil judgment entered by a court of limited or general jurisdiction, to be in willful violation of any provision of Washington state wage laws set forth in RCW 49.46, 49.48, or 49.52.

  • Repeat Violations ▇▇▇▇▇▇ agrees to comply with all regulatory requirements and acknowledges that repeat violations could result in increased penalties in the future.

  • Reporting Violations A. When the District receives a written report of unsafe condition which poses a serious and immediate threat to the health or safety of any unit member, the District shall investigate the allegations and take appropriate actions in a timely manner. B. The individual bargaining unit member forwarding a written report of an unsafe condition may request information relating to action(s) taken as a result of his or her report pursuant to the California Public Records Act.

  • Consents and Requisite Governmental Approvals; No Violations (a) No consent, approval or authorization of, or designation, declaration or filing with, any Governmental Entity is required on the part of a Parent Party with respect to such Parent Party’s execution, delivery or performance of its obligations under this Agreement or the Ancillary Documents to which it is or will be party or the consummation of the transactions contemplated by this Agreement or by the Ancillary Documents, except for (i) the filing with the SEC of (A) the Registration Statement / Proxy Statement and the declaration of the effectiveness thereof by the SEC and (B) such reports under Section 13(a), 15(d) or 16 of the Exchange Act as may be required in connection with this Agreement, the Ancillary Documents or the transactions contemplated hereby or thereby, (ii) such filings with and approvals of Nasdaq to permit the Parent Common Stock to be issued in connection with the transactions contemplated by this Agreement and the other Ancillary Documents to be listed on Nasdaq, (iii) filing of the Certificates of Merger, (iv) the approvals and consents to be obtained by each Merger Sub pursuant to Section 5.9, or (v) the Parent Stockholder Approval. (b) Subject to the receipt of the Consents, approvals, authorizations and other requirements set forth in Section 4.3(a), neither the execution, delivery or performance by a Parent Party of this Agreement nor the Ancillary Documents to which a Parent Party is or will be a party nor the consummation by a Parent Party of the transactions contemplated hereby or thereby will, directly or indirectly (with or without due notice or lapse of time or both) (i) result in any breach of any provision of the Governing Documents of a Parent Party, (ii) result in a violation or breach of, or constitute a default or give rise to any right of termination, cancellation, amendment, modification, suspension, revocation or acceleration under, any of the terms, conditions or provisions of any Contract to which a Parent Party is a party, (iii) violate, or constitute a breach under, any Order or applicable Law to which any such Parent Party or any of its properties or assets are bound or (iv) result in the creation of any Lien upon any of the assets or properties (other than any Permitted Liens) of a Parent Party, except, in the case of any of clauses (ii) through (iv) above, as would not, individually or in the aggregate, reasonably be expected to be material or prevent, materially delay or materially impair the ability of a Parent Party to consummate the Transactions.

  • Policy Compliance Violations The Requester and Approved Users acknowledge that the NIH may terminate the DAR, including this Agreement and immediately revoke or suspend access to all controlled-access datasets subject to the NIH GDS Policy at any time if the Requester is found to be no longer in agreement with the principles outlined in the NIH GDS Policy, the terms described in this Agreement, or the Genomic Data User Code of Conduct. The Requester and PI agree to notify the NIH of any violations of the NIH GDS Policy, this Agreement, or the Genomic Data User Code of Conduct data within 24 hours of when the incident is identified. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification(s), the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.