Occurrence Policy Clause Samples

An occurrence policy is an insurance provision that covers claims arising from incidents that happen during the policy period, regardless of when the claim is actually filed. For example, if an event causing damage or injury occurs while the policy is active, the insurer will provide coverage even if the claim is reported years later, after the policy has expired. This type of clause ensures that policyholders are protected for incidents that occur within the coverage window, addressing the risk of late-emerging claims and providing long-term security for covered events.
POPULAR SAMPLE Copied 1 times
Occurrence Policy. All insurance required hereunder shall provide insurance for occurrences from the date hereof throughout the later of the expiration or termination hereof.
View Source
Occurrence Policy. If the Participant or a Contractor takes out an ‘occurrence’ policy, which requires the circumstances to which a claim relates to occur during the period of insurance whilst the notification of event can occur at any time subsequently, the Participant must, and, where relevant, must ensure that the Contractor, maintain the policy: in the case of insurance taken out pursuant to clause 22.2(a) during the Agreement Period; in the case of insurance taken out pursuant to clause 22.2(c), during the construction of the Works until the date of achievement of Practical Completion; and in the case of insurance taken out pursuant to clause 22.2(d), during the Designated Use Period.
View SourceView Similar (2)
Occurrence Policy. An occurrence shall be defined as any correctable failure that has not been appropriately addressed by PCS including:  Failure to meet required response times.  Failure to correct mission critical problems.  Negligence on the part of PCS or its employees. PCS expressly warrants against the event of such occurrences as caused by PCS. Occurrences shall be described only as those issues which are under the aegis and control of PCS, and may not be indicated as items that are beyond the control of PCS. Third party vendor-related failures will be dealt with completely by PCS, though no fault will attach to PCS for third party vendor-related failures.
View Source

Related to Occurrence Policy

  • Event of Loss Grantor shall at its expense promptly repair all repairable damage to any tangible Collateral. In the event that any tangible Collateral is damaged beyond repair, lost, totally destroyed or confiscated (an "Event of Loss") and such Collateral had a value prior to such Event of Loss of $25,000.00 or more, then, on or before the first to occur of (i) 90 days after the occurrence of such Event of Loss, or (ii) 10 Business Days after the date on which either Grantor or MLBFS shall receive any proceeds of insurance on account of such Event of Loss, or any underwriter of insurance on such tangible Collateral shall advise either Grantor or MLBFS that it disclaims liability in respect of such Event of Loss, Grantor shall, at Grantor's option, either replace the Collateral subject to such Event of Loss with comparable Collateral free of all liens other than Permitted Liens (in which event Grantor shall be entitled to utilize the proceeds of insurance on account of such Event of Loss for such purpose, and may retain any excess proceeds of such insurance), or pay to MLBFS on account of the Obligations an amount equal to the actual cash value of such Collateral as determined by either the applicable insurance company's payment (plus any applicable deductible) or, in absence of insurance company payment, as reasonably determined by MLBFS. Notwithstanding the foregoing, if at the time of occurrence of such Event of Loss or any time thereafter prior to replacement or payment, as aforesaid, an Event of Default shall have occurred and be continuing hereunder, then MLBFS may at its sole option, exercisable at any time while such Event of Default shall be continuing, require Grantor to either replace such Collateral or make a payment on account of the Obligations, as aforesaid.

  • 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 <▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇▇▇.▇▇▇/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) <▇▇▇▇▇://▇▇▇.▇▇▇-­‐▇▇▇▇.▇▇▇/▇▇▇▇/▇▇▇▇/▇▇▇▇>. 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 <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇▇/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • No Default or Event of Default No Default or Event of Default shall have occurred and be continuing on such date or after giving effect to the Extension of Credit to be made on such date unless such Default or Event of Default shall have been waived in accordance with this Agreement.

  • No Default or Event of Default has occurred and is continuing as of the date hereof or after giving effect to the Loans to be made on the date hereof. [Borrower only]

  • Default or Event of Default Seller shall notify Buyer of the occurrence of any Default or Event of Default with respect to Seller as soon as possible but in no event later than two (2) Business Days after obtaining Knowledge of such event.