Role in School Policy Violations Sample Clauses

Role in School Policy Violations. SROs are not school disciplinarians and violations of the student code of conduct or school rules that are not criminal matters should always be handled by school faculty and staff, not SROs. SROs should not directly intervene unless the situation directly affects an imminent threat to the health, safety, and security of the student or another person in the school and will employ de-escalation techniques as appropriate. School discipline is the responsibility of the appropriate school administrator. The SRO will report school policy violations through the proper channels to be handled by school administration. Although the SRO should become familiar with the Student Handbook or Student Code of Conduct, it is not the responsibility of the SRO to enforce the rules in these documents.
Sample 1
AutoNDA by SimpleDocs
Role in School Policy Violations. SROs are not school disciplinarians and violations of the student code of conduct or the school’s rules that are not criminal matters should always be handled by school faculty and staff, not SROs. SROs should not directly intervene unless the situation directly affects an imminent threat to the health, safety, and security of the student or another person in the school and will employ de- escalation techniques as appropriate. School discipline is the responsibility of the appropriate school administrator and clear guidelines on SRO involvement should be developed and distributed to school staff. The SRO will report school policy violations through the proper channels to be handled by school administration. It is the responsibility of the SRO to become familiar with the Student Handbook or Student Code of Conduct, but it is not the responsibility of the SRO to enforce the rules in these documents. While the SRO works in conjunction with the school, because the school campus is the SRO’s patrol area and the population there has special needs which are being addressed through this MOU, the terms and conditions stated in this MOU does not cause the SRO to become an employee of the Board of Directors. The SRO is exclusively an employee of the Department at all times when acting in the course and scope of employment as an SRO under this MOU.
Sample 1
Role in School Policy Violations. SROs are not school disciplinarians and violations of the student code of conduct or schools rules that are not criminal matters should always be handled by school faculty and staff, not SROs. SROs should not directly intervene unless the situation directly affects an imminent threat to the health, safety, and security of the student or another person in the school and will employ de-escalation techniques as appropriate. School discipline is the responsibility of the appropriate school administrator and clear guidelines on SRO involvement should be developed and distributed to school staff. The SRO, as a staff member, will report school policy violations through the proper channels to be handled by school administration. It is the responsibility of the SRO to become familiar with the Student Handbook or Student Code of Conduct, but it is not the responsibility of the SRO to enforce the rules in these documents.
Sample 1

Related to Role in School Policy Violations

  • WAGE VIOLATIONS Contractor represents and warrants that, during the term of this Master Contract and the three (3) year period immediately preceding the award of the Master Contract, it is not 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 chapters 49.46, 49.48, or 49.52.

  • Reporting Violations a) When appropriate, faculty members will submit timely written communication to their immediate supervisor any condition that comes to their attention that may, in their judgment, pose a threat to the health or safety of any person associated with the District.

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

  • Sanctions for Violations 6.1 Any breach of the aforesaid provisions by the BIDDER or anyone employed by it or acting on its behalf (whether with or without the knowledge of the BIDDER) shall entitle the BUYER to take all or any one of the following actions, wherever required:-

  • ALLEGED VIOLATIONS ‌ At its discretion, NRMP will investigate alleged violations of this Agreement, including but not limited to:

  • 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. All notifications and written reports of data management incidents should be sent to the DAC(s) indicated in the Addendum to this Agreement. 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.

  • Disaster Relief Contract Violation Under Sections 2155.006 and 2261.053 of the Texas Government Code, PSP certifies that the individual or business entity named in the response or Agreement is not ineligible to receive the specified Agreement and acknowledges that this Agreement may be terminated and payment withheld if this certification is inaccurate.

  • No Conflict or Violation The execution, delivery and performance of this Disaffiliation Agreement or any document related hereto by Local Church and the consummation by Local Church of all of the transactions contemplated hereby or thereby, will not (with or without the giving of notice or the lapse of time or both): (a) violate or require any consent or approval under any applicable provision of any order, writ, injunction, decree, rule, regulation or law; (b) require any consent under, conflict with, result in termination of, accelerate the performance required by, result in a breach of, constitute a default under, or otherwise violate the terms of any leases, promissory notes, loans, agreements, instruments, obligations, contributions, gifts or endowments to which Local Church or a Subsidiary is a party or is beneficiary; (c) require any consent or approval by, notice to or registration with any governmental authority or any other person or entity; (d) violate any organizational documents or bylaws of Local Church; or (e) result in the creation or imposition of any lien or encumbrance upon any of the assets of the Local Church or accelerate any indebtedness of the Local Church, or result in the cancellation, modification, revocation or suspension of any of the licenses, permits, governmental authorizations or accreditations held by the Local Church.

  • Sanctions for Violation Any violation of the mandatory requirements of this WMBE Utilization provision shall be a material breach of contract for which the Contractor may be subject to damages and sanctions provided for by contract and by applicable law.

  • Entities that Boycott Energy Companies In accordance with Senate Bill 13, Acts 2021, 87th Leg., R.S., pursuant to Section 2274.002 (eff. Sept. 1, 2023, Section 2276.002, pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.) of the Texas Government Code (relating to prohibition on contracts with companies boycotting certain energy companies), Contractor represents and warrants that: (1) it does not, and will not for the duration of the Contract, boycott energy companies or (2) the verification required by Section 2274.002 (eff. Sept. 1, 2023, Section 2276.002, pursuant to House Bill 4595, Acts 2023, 88th Leg., R.S.) of the Texas Government Code does not apply to the Contract. If circumstances relevant to this provision change during the course of the Contract, Contractor shall promptly notify System Agency.

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