Notice of Occurrence, Accident, Injury or Damage Sample Clauses

Notice of Occurrence, Accident, Injury or Damage. The Contractor shall promptly notify the County Contact Person, in writing, of any accident or occurrence involving injury to persons or damage of property during the course of construction. The report shall be made notwithstanding the fact that no injury or damage may be apparent at the time of the accident or occurrence. A copy of a doctor’s report of examination will also be furnished.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Notice of Occurrence, Accident, Injury or Damage. The CONTRACTOR shall promptly notify the Owner’s Representative, in writing, of any accident or occurrence involving injury to persons or damage of property during the course of construction. The report shall be made notwithstanding the fact that no injury or damage may be apparent at the time of the accident or occurrence. A copy of a doctor’s report of examination will also be furnished.
Sample 1Sample 2

Related to Notice of Occurrence, Accident, Injury or Damage

  • 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).

  • 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. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <xxxxx://xxx.xxx-­‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Tenant’s Default 14.1 Any other provisions in this Lease notwithstanding, it shall be an event of default (“Event of Default”) under this Lease if: (i) Tenant fails to pay any installment of rent or any other sum payable by Tenant hereunder when due and such failure continues for a period of ten (10) days after written notice from Landlord to Tenant that such payment has not been received, or (ii) Tenant fails to observe or perform any other material covenant or agreement of Tenant herein contained and such failure continues after written notice given by or on behalf of Landlord to Tenant for more than thirty (30) days, provided, however, that if such non-monetary Event of Default by Tenant cannot reasonably be cured within such thirty (30) day period, and provided further that Tenant is proceeding with due diligence to effect a cure of said Event of Default, no Event of Default hereunder shall be declared by Landlord if Tenant continues to proceed with diligence to cure said Event of Default, but in no event shall such cure period extend beyond ninety (90) days following notice from Landlord of such violation, default or breach, or (iii) Tenant files a petition commencing a voluntary case, or has filed against it a petition commencing an involuntary case, under the Federal Bankruptcy Code (Title 11 of the United States Code), as now or hereafter in effect, or under any similar law, or files or has filed against it a petition or answer in bankruptcy or for reorganization or for an arrangement pursuant to any state bankruptcy law or any similar state law, and, in the case of any such involuntary action, such action shall not be dismissed, discharged or denied within sixty (60) days after the filing thereof, or Tenant consents or acquiesces in the filing thereof, or (iv) a custodian, receiver, trustee or liquidator of Tenant or of all or substantially all of Tenant’s property or of the Premises shall be appointed in any proceedings brought by or against Tenant and, in the latter case, such entity shall not be discharged within sixty (60) days after such appointment or Tenant consents to or acquiesces in such appointment, or (v) Tenant shall generally not pay Tenant’s debts as such debts become due, or shall make an assignment for the benefit of creditors, or shall admit in writing its inability to pay its debts generally as they become due. The notice and grace period provisions in clauses (i) and (ii) above shall have no application to the Events of Default referred to in clauses (iii) through (v) above. 14.2 If Tenant shall fail to make any payment of rent when due or if Tenant shall fail to keep and perform any express written covenant of this Lease and shall continue in default for a period of ten (10) days after Tenant has received written notice of such default and demand of performance from Landlord, Landlord may commence judicial proceedings, provided, however, if any default shall occur (other than in the payment of rent) which cannot be cured within a period of thirty (30) days and Tenant, prior to the expiration of thirty (30) days from and after the giving of notice as aforesaid, commences to eliminate such default and proceeds diligently to take steps to cure the same, Landlord shall not have the right to declare the term ended by reason thereof for an additional period of sixty (60) days. 14.3 In the event of any such Event of Default, Landlord at any time thereafter may at its option exercise any remedies available to Landlord at law or in equity, including, without limitation, one or more of the following remedies:

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