14.1 CGL Coverage Triggers (Occurrence vs Claims-Made & ERPs)

14.1 CGL Coverage Triggers (Occurrence vs Claims-Made & ERPs)

The Commercial General Liability (CGL) policy is the cornerstone of commercial casualty insurance in the United States. Designed by the Insurance Services Office (ISO), the CGL provides broad liability protection to businesses against third-party claims for bodily injury, property damage, and personal and advertising injury arising out of premises, ongoing operations, products, and completed operations.

For a North Carolina claims adjuster, analyzing commercial casualty claims begins with determining which policy responds to a loss. That determination depends entirely on the coverage trigger specified in the policy declarations: the Occurrence Form (CG 00 01) or the Claims-Made Form (CG 00 02).

1. Evolution and Purpose of CGL Coverage Triggers

Prior to 1986, commercial general liability was written almost exclusively on an occurrence basis. However, the emergence of long-tail liabilities—claims involving latent bodily injury or environmental contamination that manifest decades after initial exposure (e.g., asbestos exposure, chemical leaching, pharmaceutical side effects)—created severe underwriting instability. Insurers found themselves paying massive claims under policies written 20 or 30 years earlier, for which premiums had long been closed.

┌─────────────────────────────────────────────────────────────────────────┐
│                     THE CGL COVERAGE TRIGGER SPECTRUM                   │
├─────────────────────────────────────────────────────────────────────────┤
│  OCCURRENCE FORM (CG 00 01)                                             │
│  Injury/Damage MUST occur during policy period.                         │
│  Claim may be reported anytime (months, years, or decades later).        │
│  ──► Long-tail exposure rests on the insurer.                           │
├─────────────────────────────────────────────────────────────────────────┤
│  CLAIMS-MADE FORM (CG 00 02)                                            │
│  Injury/Damage MUST occur on or after the RETROACTIVE DATE.             │
│  Claim MUST be first made in writing during the policy period or ERP.   │
│  ──► Exposure is locked to the specific reporting window.               │
└─────────────────────────────────────────────────────────────────────────┘

To manage this unpredictability, ISO introduced the standardized Claims-Made Form in 1986. While both forms contain identical coverage parts (Coverage A, Coverage B, and Coverage C) and identical policy exclusions, their coverage activation mechanisms are completely distinct.

2. The Occurrence Coverage Trigger (CG 00 01)

Under the standard Occurrence Form (CG 00 01), coverage applies to bodily injury and property damage only if:

1. The bodily injury or property damage is caused by an occurrence (defined as an accident, including continuous or repeated exposure to substantially the same general harmful conditions); and
2. The bodily injury or property damage occurs during the policy period; and
3. Prior to the policy period, no insured knew that the bodily injury or property damage had occurred (the Montrose/known injury rule).

The Pure Occurrence Principle

The defining characteristic of the occurrence form is that the date the injury or damage physically occurs governs coverage, regardless of when the wrongful act took place or when the claimant files a formal claim or lawsuit.

Example: A contractor negligently installs a commercial HVAC system in 2021 while insured under an Occurrence CGL policy with Carrier A. In 2025, the system's electrical wiring overheats, causing a catastrophic fire that destroys the building. Even though the negligent work occurred in 2021 and Carrier A's policy expired in 2022, Carrier B (the insurer whose occurrence policy was in effect on the date of the 2025 fire) must defend and indemnify the claim, because the property damage occurred during its 2025 policy term.

Manifestation and Continuous Trigger Theories in Claims Adjusting

In complex North Carolina claims involving progressive or latent damage (e.g., hidden water intrusion behind synthetic stucco or gradual underground soil contamination), courts and adjusters evaluate four primary trigger theories to determine which occurrence policy responds:

• Exposure Theory: Coverage triggers during the period when the property or claimant was exposed to the harmful condition.
• Manifestation Theory: Coverage triggers exclusively under the policy in effect when the damage first becomes known, visible, or discoverable.
• Injury-in-Fact Theory: Coverage triggers during the period when actual physical harm or damage occurred, regardless of discovery.
• Continuous Trigger Theory: If injury or damage continuously progresses over multiple consecutive policy terms, every occurrence policy in effect from initial exposure through manifestation is triggered, allowing pro-rata or joint-and-several allocation among successive insurers.

3. The Claims-Made Coverage Trigger (CG 00 02)

Under the standard Claims-Made Form (CG 00 02), coverage is triggered only when two conditions are satisfied simultaneously:

1. The bodily injury or property damage occurs on or after the Retroactive Date shown in the Declarations (and prior to the end of the policy period); AND
2. The claim for damages is first made against any insured in writing during the policy period (or an applicable Extended Reporting Period).

┌─────────────────────────────────────────────────────────────────────────┐
│               THE CLAIMS-MADE TWO-PRONGED COVERAGE TEST                 │
├─────────────────────────────────────────────────────────────────────────┤
│  PRONG 1: THE EVENT PRONG                                               │
│  Did the injury or damage happen ON OR AFTER the Retroactive Date?      │
│  YES ──► Proceed to Prong 2.     NO ──► NO COVERAGE (Prior Acts Bar)    │
├─────────────────────────────────────────────────────────────────────────┤
│  PRONG 2: THE REPORTING PRONG                                           │
│  Was the claim first made against an insured in writing DURING the      │
│  policy period (or during an active Extended Reporting Period)?         │
│  YES ──► COVERAGE ATTACHES.      NO ──► NO COVERAGE (Late Reporting)    │
└─────────────────────────────────────────────────────────────────────────┘

When is a Claim "First Made"?

Under ISO CG 00 02 provisions, a claim is deemed to have been made at the earliest of:

• When notice of such claim is received and recorded by any insured or by the insurer, whichever comes first; or
• When the insurer issues a settlement offer or enters into a written settlement agreement.
• All claims for damages resulting from an injury to the same person or property are treated as a single claim first made when the first related claim was reported.

4. The Retroactive Date Mechanics and Underwriting Rules

The Retroactive Date is the fundamental gatekeeper of a claims-made policy. It represents the earliest date on which an occurrence, accident, or wrongful act can happen and still qualify for coverage under the current policy.

The Three Retroactive Date Options

When issuing a claims-made CGL policy, the underwriter must insert one of three entries in the Declarations:

1. Retroactive Date Matches Inception Date: Covers occurrences happening on or after the effective date of the first claims-made policy. Excludes all prior acts.
2. Retroactive Date Pre-Dates Inception Date (Prior Acts Coverage): Sets the retroactive date back to the inception of the insured's first continuous claims-made policy or a negotiated prior date. This preserves coverage for unknown past acts.
3. No Retroactive Date ("None"): Provides unrestricted prior acts coverage. The policy covers claims first made during the policy period regardless of how far in the past the occurrence happened (the broadest and most expensive option).

┌─────────────────────────────────────────────────────────────────────────┐
│               THE DANGER OF ADVANCING THE RETROACTIVE DATE              │
├─────────────────────────────────────────────────────────────────────────┤
│  Policy Year 1 (2024):  Retro Date = Jan 1, 2024 ──► Incident Occurs    │
│  Policy Year 2 (2025):  Retro Date ADVANCED to Jan 1, 2025              │
│  Claim Filed in 2025 for 2024 incident:                                 │
│  - 2024 Policy: Expired (no claim made during policy period)             │
│  - 2025 Policy: Incident occurred BEFORE the new Retro Date (Jan 1, 2025)│
│  ──► RESULT: COMPLETE COVERAGE GAP / NO INSURANCE APPLIES               │
└─────────────────────────────────────────────────────────────────────────┘

Strict Underwriting Restrictions on Advancing the Retroactive Date

Because advancing the retroactive date eliminates coverage for past acts and creates catastrophic coverage gaps, ISO rules and North Carolina insurance regulations strictly prohibit an insurer from advancing the retroactive date without the express written consent of the first named insured, except under specific circumstances:

• A substantial change in the insured's business operations that significantly increases exposure;
• The insured fails to provide required underwriting information or makes a material misrepresentation;
• A change in insurance carrier occurs, and the new insurer refuses to provide prior acts coverage; or
• The insured explicitly requests an advanced date to reduce premium.

5. Extended Reporting Periods (ERPs / Tail Coverage)

When a claims-made policy is cancelled, non-renewed, replaced by an occurrence policy, or renewed with an advanced retroactive date, a coverage gap is created for past occurrences that have not yet resulted in a formal third-party claim. To bridge this gap, the Claims-Made Form provides Extended Reporting Periods (ERPs), commonly known in the industry as "Tail Coverage".

ERPs do not extend the policy period or provide coverage for future occurrences; they merely extend the deadline for reporting claims arising out of occurrences that occurred after the retroactive date and before policy expiration.

┌─────────────────────────────────────────────────────────────────────────┐
│                     EXTENDED REPORTING PERIODS (ERPs)                   │
├───────────────────────────────────┬─────────────────────────────────────┤
│       BASIC ERP (AUTOMATIC)       │     SUPPLEMENTAL ERP (MAXI-TAIL)    │
├─────────────────┬─────────────────┼─────────────────────────────────────┤
│ "MINI-TAIL"     │ "MIDI-TAIL"     │ "MAXI-TAIL" / FULL TAIL             │
│ 60-Day Window   │ 5-Year Window   │ UNLIMITED DURATION                  │
├─────────────────┼─────────────────┼─────────────────────────────────────┤
│ - Built-in      │ - Built-in      │ - Optional endorsement              │
│ - Zero premium  │ - Zero premium  │ - Up to 200% annual base premium    │
│ - Reports claims│ - Formal suits  │ - Must request within 60 days of end│
│   or occurrences│   for incidents │ - Reinstates policy aggregate limits│
│   within 60 days│   reported in 60d│ - Non-cancellable once paid         │
└─────────────────┴─────────────────┴─────────────────────────────────────┘

1. Basic Extended Reporting Period (BERP)

The Basic ERP is automatically provided by the policy without additional charge and without requiring an endorsement. It activates automatically whenever the claims-made policy is cancelled, non-renewed, or renewed with an advanced retroactive date. It operates in two tiers:

• The 60-Day "Mini-Tail": Provides an automatic 60-day window following the policy expiration date for the insured to report any claims first made during those 60 days (arising from occurrences between the retroactive date and policy termination).
• The 5-Year "Midi-Tail": If an insured reports an occurrence (a known incident that might give rise to a future claim) to the insurer in writing within the initial 60-day mini-tail window, the policy provides a 5-year extended window from the expiration date for the third party to formally file the claim or lawsuit against the insured.
• Important Limitation: The Basic ERP does not increase or reinstate the policy aggregate limits of insurance. Any payments made under the Basic ERP continue to erode the remaining aggregate limits from the expired policy term.

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

The Supplemental ERP is an optional endorsement (CG 27 15) that provides unlimited, indefinite reporting duration ("Maxi-Tail") for claims arising out of occurrences that took place after the retroactive date and prior to policy expiration.

Key SERP Rules and Parameters:

1. Written Request Window: The named insured must request the SERP in writing within 60 days after the policy period ends.
2. Premium Charge: The insurer may charge a one-time additional premium of up to 200% of the annual base premium for the expiring policy.
3. Fully Earned & Non-Cancellable: Once the premium is paid, the SERP endorsement cannot be cancelled by either the insurer or the insured, and the premium is 100% fully earned.
4. Reinstated Aggregate Limits: Unlike the Basic ERP, the Supplemental ERP reinstates the policy's General Aggregate Limit and Products-Completed Operations Aggregate Limit for the entire ERP duration, ensuring fresh limits to pay future tail claims.
5. Excess Coverage Status: The SERP applies as excess insurance over any other valid and collectible insurance that covers the loss on an occurrence or claims-made basis.

6. Comprehensive Trigger Comparison Matrix

7. Practical Claims Adjuster Case Scenarios

Scenario A: The Long-Tail Chemical Exposure (Occurrence Form)

Case File: Apex Chemical maintained an Occurrence CGL policy with Insurer X from January 1, 2018, to January 1, 2019. In July 2018, Apex delivered industrial cleaning solvent to a commercial client. A worker inhaled toxic fumes during the delivery and developed chronic respiratory disease. In September 2026 (8 years later), the worker files a bodily injury lawsuit against Apex.

Adjuster Analysis: The policy in effect when the bodily injury occurred was Insurer X's 2018 occurrence policy. Under standard occurrence trigger rules, because the injury occurred during the 2018 policy period, Insurer X must defend and indemnify Apex, regardless of the fact that the claim was brought 8 years after policy expiration (assuming applicable tolling or statute of limitations compliance).

Scenario B: Advanced Retro Date and the Uninsured Gap (Claims-Made Form)

Case File: Vertex Engineering had a Claims-Made CGL policy with Carrier A from Jan 1, 2023, to Jan 1, 2024, with a Retro Date of Jan 1, 2023. On Jan 1, 2024, Vertex switched to Carrier B, which advanced the Retroactive Date to Jan 1, 2024. In June 2024, Vertex is sued for a property damage incident that occurred in November 2023.

Adjuster Analysis:

1. Carrier A Policy: Claim was not made during Carrier A's policy period, and no SERP was purchased. Carrier A denies coverage.
2. Carrier B Policy: While the claim was first made during Carrier B's policy period, the occurrence happened in November 2023—prior to Carrier B's January 1, 2024 Retroactive Date. Carrier B denies coverage.

• Result: Vertex has zero coverage due to the advanced retroactive date gap.

Scenario C: The 60-Day Notice and the 5-Year Midi-Tail

Case File: Precision Plumbing carried a Claims-Made CGL policy expiring on December 31, 2024, with a Retro Date of Jan 1, 2020. Precision did not purchase a Supplemental ERP. On January 20, 2025 (20 days after expiration), Precision received a customer letter warning that a pipe installed in August 2024 was leaking inside a wall. Precision immediately forwarded this notice to its insurer. In November 2028 (nearly 4 years later), the building owner files a $75,000 property damage lawsuit.

Adjuster Analysis: Precision reported the incident to the insurer within the 60-day mini-tail window (Jan 20, 2025). This timely incident report activated the 5-year midi-tail, extending coverage for any resulting lawsuit filed before December 31, 2029. Because the suit was filed in 2028, the insurer must provide defense and indemnity under the expired 2024 policy's remaining limits.