First Incident Sample Clauses

First Incident. 1. If two trained administrators, using the “Observed Behavior-Reasonable Cause Record” (which is attached to this agreement) have made a determination that there is reasonable suspicion that an employee may be at work with detectable levels of alcohol (.04 or above), illegal, or unauthorized drugs in their body, the employee shall receive a Notice of Rights (attached). The Notice of Rights shall be signed by the employee to indicate that it has been received, and a copy shall be placed in an investigative file. The issuance of the Notice of Rights may not be grieved or arbitrated. The Notice of Rights is not considered discipline nor is it evidence of substantiated unprofessional conduct. No further action will take place unless there is another reasonable suspicion incident (within 36 months of the issuance of the notice) in which two trained administrators make a determination that there is reasonable suspicion that an employee is at work with detectable levels of alcohol (.04 or above), illegal, or unauthorized drugs in their body.
Sample 1Sample 2Sample 3See All (22)
AutoNDA by SimpleDocs
First Incident. Following the first incident resulting in damage to the device, the device will be repaired at no cost, and the student and family will be warned about the consequences of further damage to the device.
Sample 1Sample 2Sample 3See All (4)
First Incident. There is no charge for the first incident resulting in accidental damage to the Chromebook as it is covered under the CCPS policy. Parents will receive a bill with no charge for these repairs as notification.
Sample 1
First Incident. The employee will be counselled as to reasons and a first warning will be issued. Second Incident The employee will be counselled as to reasons and a second warning will be issued. Third Incident The employee will be counselled as to reasons and will be dismissed. Counselling and warnings issued in connection with this clause will be considered in conjunction with counselling and warnings issued for any other reason.
Sample 1
First Incident. No charge for accidental damage to mobile device; letter to parents. Full price of repair or replacement for an intentionally damaged mobile device and a parent/guardian meeting with administrator required. For lost devices, student must report loss to student help desk within 10 days. If device is unable to be located, a parent/guardian meeting with administrator is required to determine eligibility for a replacement device. For stolen devices, a police report must be completed within 10 business days and a copy provided to the school administration.
Sample 1
First Incident. After you review the device care and security sections of the MV Acceptable Use Agreement with your building administrator, you may be issued a replacement device, if one is available. Your building administrator will take into account the situation that led to the damage or loss. This may result in limiting your device use to in-school only, for a period to be determined by your administrator. You still will be required to complete all school assignments, and your teachers will make reasonable accommodations as needed. You and your family may be held responsible for the full cost of repair or replacement. SECOND INCIDENT: You may be restricted to use a device only at school, and the device must be checked in and out with the assigned building staff at the beginning and end of the school day. You may not be allowed to take the device home until you and a parent or guardian meet with a building administrator and agree to a plan for preventing the loss or damage in the future. You may face school disciplinary actions. You and your family may be held responsible for the full cost of repair or replacement.
Sample 1
First Incident. 13th September 2013
Sample 1
AutoNDA by SimpleDocs

Related to First Incident

  • Error Incident An Error Incident is a single or series of NAV Errors that results from the same act, omission, or use of incorrect data. Correction NAV Errors will be corrected as follows: · If an NAV Error is less than ½ of 1% of NAV and results in a Net Benefit, the fund will retain the benefit. · If an NAV Error is less than ½ of 1% of NAV and results in a Net Loss, the Net Loss will be paid to the fund by the party responsible for causing the NAV Error. · In the case of a Material NAV Error, shareholder transactions/accounts will be corrected/ reprocessed at the corrected (restated) NAV, subject to a $10 per-account correction minimum threshold; any residual Net Benefit after correction of shareholder accounts will be retained by the fund and any residual Net Loss (resulting from uncorrected accounts below the $10 minimum threshold) will be paid to the fund by the party responsible for causing the error. If an NAV error is not caused by either the fund accounting agent or TRP, both TRP and the fund accounting agent will provide all reasonable assistance to the fund in its attempt to recover all costs from the responsible third party. · Notwithstanding any contractual provisions to the contrary, to the extent a NAV Error was caused by the actions or omissions of the fund’s accounting agent, any Net Loss or residual Net Loss equal to $5,000 or less that results from the same Error Incident will be paid by the accounting agent. TRP will be responsible for summarizing and reporting to the funds’ Audit Committee or Trust Company’s Board (or designated committee), as applicable, all NAV Errors related to the funds/trusts in conjunction with other relevant error statistics on a quarterly basis. The report will include corrected NAV Errors as well as the aggregate effect of any uncorrected NAV Errors. The report will also include information about shareholder accounts that were corrected in the discretion of TRP in the case of an NAV Error that is not a Material NAV Error. The funds’ Audit Committee and the Trust Company’s Board shall have the authority to adjust these procedures with respect to the funds and trusts, respectively, to the extent necessary or desirable to address NAV Errors by providing notice thereof to TRP and the fund’s accounting agent.

  • Reporting Incidents The Interconnection Parties shall report to each other in writing as soon as practical all accidents or occurrences resulting in injuries to any person, including death, and any property damage arising out of the Interconnection Service Agreement.

  • Security Incident “Security Incident” means the attempted or successful unauthorized access, use, disclosure, modification, or destruction of information or interference with system operations in an information system.

  • Significant Incidents In addition to notifying the appropriate authorities, Grantee will submit notice to the SUD email box, XxxxxxxxxXxxxx.Xxxxxxxxx@xxxx.xxxxx.xx.xx and Substance Use Xxxxxxxx@xxxx.xxxxx.xx.xx significant incidents involving substantial disruption of Grantee’s program operation or affecting or potentially affecting the health, safety or welfare of the System Agency funded clients or participants within three (3) calendar days of discovery.

  • Security Incidents 11.1 Includes identification, managing and agreed reporting procedures for actual or suspected security breaches.

  • Security Incident Reporting A security incident occurs when CDA information assets are or reasonably believed to have been accessed, modified, destroyed, or disclosed without proper authorization, or are lost, or stolen. Subrecipient must comply with CDA’s security incident reporting procedures located at xxxxx://xxx.xxxxx.xx.xxx/ProgramsProviders/#Resources.

  • Security Incident Notification The Transfer Agent shall promptly notify the Trust but in no event later than 72 hours following discovery of any Security Incident(s). Such notification shall include the extent and nature of such intrusion, disclosure, or unauthorized access, the identity of the compromised Customer Confidential Information (to the extent it can be ascertained), how the Transfer Agent was affected by the Security Incident, and its response to such Security Incident. The Transfer Agent shall use continuous and diligent efforts to remedy the cause and the effects of such Security Incident in an expeditious manner and deliver to the Trust a root cause analysis and future incident Mitigation plan with regard to any such incident. The Transfer Agent shall reasonably cooperate with the Trust’s investigation and response to each Security Incident. If the Trust determines in its sole discretion that it may need or be required to notify any individual(s) as a result of a Security Incident, the Trust shall have the right to control all such notifications and the Transfer Agent shall bear all direct costs associated with the notification, to the extent the notification and corresponding actions are required by U.S. law, and subject to the limitation of liability set forth in the Agreement. Without limiting the foregoing, unless otherwise required by U.S. law, no such notifications shall be made by the Transfer Agent without the Trust’s prior written consent and the Trust shall, together with the Transfer Agent, determine the content and delivery of all such notifications. For the avoidance of doubt, the Transfer Agent shall be solely responsible for all costs and expenses, subject to the limitations of liability under the Agreement that the Trust and/or the Transfer Agent may incur to the extent that they are attributable to or arise from the Transfer Agent’s breach of its confidentiality obligations under the Agreement.

  • Security Incident Response Upon becoming aware of a Security Incident, MailChimp shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.

  • Breaches and Security Incidents During the term of the Agreement, CONTRACTOR 27 agrees to implement reasonable systems for the discovery of any Breach of unsecured DHCS PI and PII 28 or security incident. CONTRACTOR agrees to give notification of any beach of unsecured DHCS PI 29 and PII or security incident in accordance with subparagraph F, of the Business Associate Contract, 30 Exhibit B to the Agreement.

  • Notification of Incidents If Contractor becomes aware of or has reasonable suspicion of a privacy incident or security incident regarding any State data, Contractor must report such incident to the State and the State Chief Information Security Officer as soon as possible, but no later than twenty-four (24) hours after such incident. The decision to notify the affected data subjects and the form of such notice following report of a privacy incident or security incident are the responsibility of the State. Notwithstanding anything to the contrary in this Contract, Contractor will indemnify, hold harmless and defend the State and its officers, and employees for and against any claims, damages, costs and expenses related to any privacy incident or security incident involving any State data. For purposes of clarification, the foregoing sentence shall in no way limit or diminish Contractor’s obligation(s) to indemnify, save, hold harmless, or defend the State under any other term of this Contract. Contractor will reasonably mitigate any harmful effects resulting from any privacy incident or security incident involving any State data.

Time is Money Join Law Insider Premium to draft better contracts faster.