Third Occurrence Sample Clauses

Third Occurrence. The third incident will result in immediate expulsion from KC without refund. The Children, Family and Camp Director, Xxxx Xxxx, will make final determination for expulsion. Student’s Name (printed) Student’s Signature and Date Parent’s Signature and Date
AutoNDA by SimpleDocs
Third Occurrence. The employee shall be required to report to the Chief Human Resources Officer; the CSEA President and the employee shall be immediately notified that the employee shall be required to report to the Employee Assistance Program or any other appropriate program so that an alcohol or drug counselor can do an evaluation. The program may or may not include drug testing of the employee. If it is of the opinion of the alcohol or drug counselor that the employee has a dependency on alcohol or drugs, the Chief Human Resources Officer may request the employee to enroll in an Employee Assistance Program or other appropriate program.
Third Occurrence. For the third or subsequent occurrence within any one Calendar 776 Year of contamination for a particular container (i.e., Recyclable Materials or Organic Waste), Contractor 777 must collect the contaminated Container (as Solid Waste) and must charge the Service Recipient a 778 contamination fee as set forth in Exhibit 1. Contractor must continue providing the Recyclable Materials or 779 Organic Waste Collection Services. Contractor must provide (or have provided) digital/photographic 780 documentation to the Service Recipient that clearly documents the Service Recipient’s on-going 781 contamination problems and written Notices of contamination as described above. Contractor may increase 782 the Container size or collection frequency and impose a contamination surcharge on the account for a 783 period of six months or until the Service Recipient has demonstrated no contamination for a period of three 784 consecutive months. Contractor must document contamination issue and surcharge in Waste Reporting 785 System and notify City within five (5) Business Days if Contractor increases the Container size or collection 786 frequency for excessive contamination or imposes the contamination surcharge to the account. City will 787 consult with Contractor and consider, and pursue as applicable, appropriate legal remedies against 788 offending Service Recipients in order to secure discontinuance of the contamination. 789 5.08 Tracking Occurrences of Contamination. Regarding Section 5.07, each Contamination 790 occurrence is tracked annually per Calendar Year, and resets at the start of each Calendar Year if 791 contamination occurrences are not active and consecutive. Where contamination is occurring, and 792 occurrences are consecutive and unremedied their count shall continue across Calendar Years until remedy 793 occurs. In this case, once the Service Recipient has demonstrated no contamination for a period of three 794 consecutive months the tracking calendar will reset.

Related to Third Occurrence

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment.

  • Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).

  • Maximum Occupancy No more than two (2) guests per one (1) resident (who is present) are permitted in a student room/suite/apartment at any given time unless otherwise approved by the University (Residential Life).

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Authority Event of Default Any of the following events shall constitute an event of default by the Authority ("Authority Event of Default”), when not caused by a Developer Event of Default:

  • Commercial General Liability – Occurrence Form Policy shall include bodily injury, property damage, personal injury and broad form contractual liability. • General Aggregate $2,000,000 • Products – Completed Operations Aggregate $1,000,000 • Personal and Advertising Injury $1,000,000 • Blanket Contractual Liability – Written and Oral $1,000,000 • Fire Legal Liability $50,000 • Each Occurrence $1,000,000

  • Notice of Event of Default If the Mortgagee shall have Actual Knowledge of an Event of Default or of a Default arising from a failure to pay Rent, the Mortgagee shall give prompt written notice thereof to the Owner Trustee, the Owner Participant, Lessee, and each Note Holder. Subject to the terms of Sections 2.13, 4.03, 4.04, 4.08, 5.02 and 5.03 hereof, the Mortgagee shall take such action, or refrain from taking such action, with respect to such Event of Default or Default (including with respect to the exercise of any rights or remedies hereunder) as the Mortgagee shall be instructed in writing by a Majority in Interest of Note Holders. Subject to the provisions of Section 5.03, if the Mortgagee shall not have received instructions as above provided within 20 days after mailing notice of such Event of Default to the Note Holders, the Mortgagee may, subject to instructions thereafter received pursuant to the preceding provisions of this Section 5.01, take such action, or refrain from taking such action, but shall be under no duty to take or refrain from taking any action, with respect to such Event of Default or Default as it shall determine advisable in the best interests of the Note Holders; PROVIDED, HOWEVER, that the Mortgagee may not sell the Aircraft or any Engine without the consent of a Majority in Interest of Note Holders. For all purposes of this Trust Indenture, in the absence of Actual Knowledge on the part of the Mortgagee, the Owner Trustee or the Owner Participant, the Mortgagee, the Owner Trustee or the Owner Participant, as the case may be, shall not be deemed to have knowledge of a Default or an Event of Default (except, in the case of the Mortgagee, the failure of Lessee to pay any installment of Basic Rent within one Business Day after the same shall become due, if any portion of such installment was then required to be paid to the Mortgagee, which failure shall constitute knowledge of a Default) unless notified in writing by Lessee, the Owner Trustee, the Owner Participant or one or more Note Holders.

  • Developer Event of Default Any of the following events shall constitute an event of default by the Developer ("Developer Event of Default") unless such event has occurred as a result of a Force Majeure Event or the Authority Event of Default or any governmental action for reasons other than any breach, default or lapse on the part of the Developer:

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

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