7.2 CGL Occurrence vs. Claims-Made Triggers

7.2 CGL Occurrence vs. Claims-Made Triggers

Quick Reference: An Occurrence Form (CG 00 01) is triggered when the bodily injury or property damage occurs during the policy period, regardless of when the claim is filed—creating decades-long "long-tail" liability for carriers. In contrast, a Claims-Made Form (CG 00 02) requires that the injury occur on or after the Retroactive Date AND that the claim be first made against the insured during the policy period (or applicable ERP). Tail coverage includes the automatic, cost-free Basic Extended Reporting Period (BERP) (a 60-day "mini-tail" and a 5-year "midi-tail") and the optional Supplemental Extended Reporting Period (SERP) (an unlimited "maxi-tail" costing up to 200% of the annual premium that reinstates aggregate limits).

---

The Fundamental Trigger Dilemma: Occurrence vs. Claims-Made

Every commercial liability policy must define what specific temporal event "triggers" the insurer's contractual obligation to provide defense and indemnity. In casualty insurance, this temporal event is governed by two fundamentally different coverage architectures:

1. The Occurrence Trigger (ISO Form CG 00 01): Focuses strictly on when the injury or damage happened.
2. The Claims-Made Trigger (ISO Form CG 00 02): Focuses on when the claim is formally communicated to the insured and insurer, combined with a past boundary date (the Retroactive Date).

                             THE TWO COVERAGE TRIGGERS
                                        │
         ┌──────────────────────────────┴──────────────────────────────┐
         ▼                                                             ▼
  OCCURRENCE FORM (CG 00 01)                                    CLAIMS-MADE FORM (CG 00 02)
  • Trigger: BI or PD occurs during                             • Trigger: Dual Requirement:
    the active policy period.                                     1. Event occurs ON or AFTER Retro Date
  • When claim is reported: IRRELEVANT.                           2. Claim is FIRST MADE during policy
  • Creates "Long-Tail" exposures (suits                           period or active ERP
    filed 5, 10, or 25 years later).                            • Eliminates long-tail uncertainty

The Long-Tail Liability Problem

To understand why the insurance industry developed the claims-made form in the 1970s and 1980s, claims adjusters must understand the phenomenon of "long-tail" claims.

In standard personal injury or automobile collisions, the injury occurs instantaneously, and the claim is reported within days or weeks. However, in complex commercial casualties—such as asbestos exposure, environmental soil contamination, groundwater pollution, toxic chemical latency, pharmaceutical side effects, and latent construction defects—decades may elapse between the insured's physical act, the manifestation of bodily injury, and the filing of a formal lawsuit.

Under an Occurrence Form, an insurer that collected a modest $5,000 premium on a commercial manufacturing plant in 1985 remains contractually liable for an asbestos mesothelioma lawsuit filed in 2026, provided medical experts demonstrate that microscopic fiber inhalation occurred during the 1985 policy term. This created catastrophic actuarial unpredictability, insurer insolvencies, and the withdrawal of casualty capacity for high-risk industries.

The Claims-Made Form was designed to solve this actuarial crisis by establishing certainty: the carrier writing the policy today is responsible only for claims brought today, allowing precise rate-making based on current judicial climates, inflation, and known loss exposures.

---

ISO Occurrence Form (CG 00 01) Mechanics

The standard ISO Occurrence Form provides coverage under the following insuring agreement:

"This insurance applies to 'bodily injury' and 'property damage' only if the 'bodily injury' or 'property damage' occurs during the policy period... regardless of when the claim is made or 'suit' is brought."

Core Rules Governing Occurrence Policies

• Date of Injury Controls: The date the insured committed the negligent act is irrelevant; the date the claimant discovers the injury is secondary; the exact date the physical damage or bodily harm took place controls which policy is triggered.
• Open-Ended Tail: The insured enjoys perpetual, lifetime protection for that specific policy year. Even if the business dissolves, liquidates, or cancels its insurance, a valid occurrence policy from twenty years prior must defend and indemnify a timely filed lawsuit alleging injury during that term.
• Multiple Policy Triggers in Latent Injury Claims: In Texas, courts have grappled with which occurrence policy responds to long-tail losses involving continuous damage (e.g., ongoing foundation settlement or progressive water intrusion):
  • Manifestation Theory: Coverage is triggered when the damage first becomes reasonably apparent or discoverable.
  • Exposure / Injury-in-Fact Theory: Coverage is triggered by any policy in effect during the physical period when actual injury or cellular/structural damage was actively occurring (Don's Building Supply, Inc. v. OneBeacon Ins. Co.).

---

ISO Claims-Made Form (CG 00 02) Mechanics

The standard ISO Claims-Made Form replaces the open-ended occurrence mechanism with a strict dual-condition trigger.

The Dual-Condition Trigger Requirement

For coverage to exist under a Claims-Made policy, two mandatory criteria must be satisfied simultaneously:

$\text{Coverage Triggered} \iff (\text{Loss Date} \ge \text{Retroactive Date}) \;\mathbf{AND}\; (\text{Claim Date} \in \text{Policy Period / ERP})$

1. The Occurrence Requirement: The bodily injury or property damage must occur on or after the Retroactive Date stated in the Declarations and before the end of the policy period; AND
2. The Claim Requirement: The claim for damages must be first made against any insured during the active policy period or an applicable Extended Reporting Period (ERP).

What Constitutes a "Claim First Made"?

Under ISO CG 00 02, a claim is deemed to have been "first made" when:

• A notice or written demand for monetary damages or services is received by any insured or by the insurer; or
• A civil lawsuit or arbitration proceeding seeking damages is formally served upon the insured.
• All claims for damages because of bodily injury to the same person or property damage to the same property are deemed to have been made at the time the very first claim is made.

---

The Retroactive Date in Detail

The Retroactive Date is the fundamental anchor of the Claims-Made form. It is a specific calendar date recorded on the policy Declarations page marking the earliest date on which an event, accident, or occurrence can take place and still be eligible for coverage.

                                  THE CLAIMS-MADE TIMELINE
   ◄──────────────────────────────┬──────────────────────────────┬──────────────────────────────►
           PRIOR PERIOD           │         POLICY PERIOD        │          FUTURE PERIOD
                                  │                              │
   ===============================│==============================│==============================
   [   UNINSURED HISTORICAL GAP   │     COVERED OCCURRENCES      │   POLICY EXPIRES / CANCELLED
   [ Occurrences before this date │   Occurrences between these  │   Requires Extended Reporting
   [ are NEVER covered!           │   dates are covered IF claim │   Period (ERP) to cover future
   ===============================│   is filed during term!      │   reporting of past events!
                                  │                              │
                           RETROACTIVE DATE              EXPIRATION DATE
                           (e.g., Jan 1, 2023)           (e.g., Jan 1, 2024)

Three Retroactive Date Scenarios

1. Retroactive Date Same as Policy Inception Date: When an insured first purchases a claims-made policy, underwriters typically set the Retroactive Date equal to the policy's effective date. The policy covers only occurrences happening on or after that inception date and reported during the term. There is zero "prior acts" coverage.
2. Retroactive Date Earlier than Policy Inception Date (Prior Acts Coverage): When an insured renews a claims-made policy with the same or a new carrier, the underwriter agrees to maintain the original Retroactive Date (e.g., renewing on January 1, 2025, but maintaining a Retroactive Date of January 1, 2020). The policy covers claims made in 2025 for occurrences dating back to 2020. This continuity is vital to avoid coverage gaps.
3. No Retroactive Date (Full Prior Acts Coverage): The Declarations page states "None." The policy provides unlimited prior acts protection, covering any claim first made during the policy period regardless of how far in the past the occurrence happened. Because of the extreme underwriting exposure, full prior acts coverage commands substantial premiums.

The Danger of Advancing the Retroactive Date

If an insurer or insured "advances" the Retroactive Date (moves it forward in time, for example from January 1, 2020, to January 1, 2024 upon a renewal):

[!WARNING] The Uninsured Retroactive Gap: Advancing the Retroactive Date instantly eliminates coverage for all past occurrences that took place between the old date (2020) and the new date (2024) if those occurrences have not yet resulted in a formal claim. This creates an uninsurable liability chasm for the business.

Under ISO rules, an insurer may only advance or eliminate a retroactive date with the written consent of the first named insured, typically occurring only when there is a material change in operations, an extended lapse in coverage, or an acquisition.

---

Extended Reporting Periods (ERPs / Tail Coverage)

When a claims-made policy terminates, the insured loses all coverage for past occurrences unless the claim was formally asserted prior to expiration. To prevent catastrophic uninsured losses when a business closes, changes carriers, or switches to an occurrence policy, the contract provides Extended Reporting Periods (ERPs), commonly referred to as "tail coverage."

An ERP does NOT extend the policy period, nor does it cover occurrences that take place after policy expiration. An ERP simply extends the window of time during which claims for past covered occurrences (occurring on or after the Retroactive Date and before policy expiration) may be reported and covered.

                          EXTENDED REPORTING PERIODS (ERPs)
                                          │
        ┌─────────────────────────────────┴─────────────────────────────────┐
        ▼                                                                   ▼
 BASIC ERP (BERP / Automatic)                                SUPPLEMENTAL ERP (SERP / Optional)
 • Cost: FREE (Automatic, no premium)                       • Cost: UP TO 200% of annual premium
 • Mini-Tail: 60-day window for unknown claims               • Request: In writing within 60 days of expiry
 • Midi-Tail: 5-year window if potential occurrence          • Duration: UNLIMITED (Perpetual / Lifetime)
   reported to carrier within 60 days                        • Reinstates: 100% of Aggregate Limits!
 • Reinstates Limits: NO (Uses leftover limits)              • Excess coverage over surviving insurance

1. Basic Extended Reporting Period (BERP)

The Basic ERP (BERP) is provided automatically by contractual right without additional premium charge whenever a claims-made policy is cancelled, non-renewed, replaced with an occurrence policy, or renewed with an advanced retroactive date.

The BERP contains two distinct reporting timelines:

• The 60-Day "Mini-Tail": Automatically covers any unknown claim first made against the insured and reported to the insurer within 60 days immediately following policy expiration, provided the bodily injury or property damage occurred on or after the Retroactive Date and prior to expiration.
• The 5-Year "Midi-Tail": Extends the reporting window to 5 full years following expiration for claims arising from an occurrence, provided the insured or claimant gave written notice of the specific occurrence to the insurer no later than 60 days after policy termination. If the insured reports a potential jobsite incident during the 60-day window, and the injured worker waits three years before serving a formal lawsuit, the midi-tail covers the claim.

Critical Limitation of the BERP: The Basic ERP does NOT provide additional or reinstated aggregate limits of insurance. Claims paid under the BERP draw from whatever dollar balance remained in the policy's General Aggregate or Products-Completed Operations Aggregate at the time of expiration. If the limits were exhausted during the policy year, the BERP provides zero dollars of indemnity.

2. Supplemental Extended Reporting Period (SERP / "Maxi-Tail")

To secure permanent, comprehensive protection, the insured may purchase the optional Supplemental Extended Reporting Period (SERP) by policy endorsement (ISO form CG 27 15 or carrier equivalent).

Key statutory and contractual provisions governing the SERP include:

1. Written Request Window: The first named insured must request the SERP in writing within 60 days after policy expiration.
2. One-Time Premium Charge: The premium is calculated based on underwriting rules but cannot exceed 200% of the annual CGL premium for the expiring policy. The premium is fully earned upon policy issuance and is non-refundable.
3. Unlimited Duration ("Lifetime Tail"): The SERP provides an unlimited, perpetual reporting window. A claim reported 10, 15, or 30 years later will be covered, provided the injury occurred between the original Retroactive Date and the policy expiration date.
4. Reinstatement of Aggregate Limits: This is the single greatest advantage of the SERP. The endorsement completely reinstates 100% of the policy's original aggregate limits (both the General Aggregate and Products-Completed Operations Aggregate) for the entire duration of the supplemental period! Prior claims that depleted limits during the active policy year do not reduce the fresh aggregate limits available under the SERP.
5. Excess Coverage Status: The SERP operates as excess insurance over any other valid and collectible insurance that covers the same claim (such as a subsequent occurrence policy).

---

Occurrence vs. Claims-Made vs. ERPs Comparative Matrix

---

Adjuster Claims Timeline Analysis: Occurrence vs. Claims-Made

To master trigger application on licensing exams and in the field, examine how an adjuster resolves a multi-year latent environmental contamination claim under differing policy structures.

Timeline of Events:

• January 1, 2020: ChemTech Corp opens a chemical mixing plant in Houston, Texas.
• March 15, 2021: An underground solvent storage tank ruptures, leaking perchloroethylene into the soil and sub-surface water table. The leak is invisible and unknown to ChemTech.
• July 1, 2023: A neighboring residential subdivision discovers solvent contamination in drinking water wells. Chemical tracing confirms the leak originated from ChemTech's 2021 rupture.
• November 10, 2024: Neighboring homeowners file a multi-million-dollar toxic tort lawsuit against ChemTech.

                                 ADJUSTER TIMELINE ANALYSIS
  2020               2021              2022              2023              2024
   |──────────────────★─────────────────|─────────────────|─────────────────▲
Plant Opens     Tank Ruptures                     Contamination       Lawsuit Filed
                (Occurrence Date)                   Discovered        (Claim Date)

Adjuster Evaluation Under Differing Insurance Programs:

Program A: ChemTech Maintained Annual Occurrence Policies (CG 00 01)

• Policy in Force in 2021: Policy Period Jan 1, 2021 – Jan 1, 2022.
• Policy in Force in 2024: Policy Period Jan 1, 2024 – Jan 1, 2025.
• Adjuster Finding: The bodily injury and property damage occurred on March 15, 2021, when toxic chemicals penetrated the groundwater. Under the occurrence trigger, the 2021 policy is triggered, because the damage occurred during its policy period. The fact that the claim was made three years later in 2024 is irrelevant. The 2024 policy is not triggered because no new rupture occurred during its term.

Program B: ChemTech Maintained Claims-Made Policies (CG 00 02)

• Policy 1 (Jan 1, 2020 – Jan 1, 2023): Retro Date = Jan 1, 2020.
• Policy 2 (Jan 1, 2023 – Jan 1, 2024): Retro Date = Jan 1, 2020.
• Policy 3 (Jan 1, 2024 – Jan 1, 2025): Underwriter advanced Retro Date to Jan 1, 2024!
• Adjuster Finding: The lawsuit was served on November 10, 2024 (during Policy 3's policy term). However, Policy 3 carries an advanced Retroactive Date of January 1, 2024. Because the chemical rupture occurred on March 15, 2021 (prior to the new Retro Date), Policy 3 DENIES coverage.
• What about Policy 2? Policy 2 had a valid Retro Date (2020), but the claim was not made during Policy 2's term (which expired January 1, 2024). ChemTech has a catastrophic uninsured gap caused by advancing the Retroactive Date without purchasing tail coverage.