8.1 CGL Form Structure: Occurrence vs. Claims-Made, Retroactive Dates & ERPs
Key Takeaways
- The fundamental difference between CGL forms is the coverage trigger: the Occurrence Form (CG 00 01) responds when bodily injury or property damage occurs during the policy period, while the Claims-Made Form (CG 00 02) requires the claim to be first made against the insured during the policy period or an extended reporting period.
- Under a Claims-Made policy, an injury or damage event must occur on or after the policy's Retroactive Date; events occurring even one day prior to this date are strictly barred from coverage.
- Advancing a Retroactive Date to a later date creates an uninsured gap for unknown past occurrences, exposing the policyholder to severe uncovered liabilities.
- The Basic Extended Reporting Period (BERP) is automatic and provided at no additional premium, offering a 60-day mini-tail for unknown occurrences and a 5-year midi-tail for incidents reported to the insurer within 60 days of expiration.
- The Supplemental Extended Reporting Period (SERP, or 'Maxi-Tail') must be requested in writing within 60 days of policy expiration, provides an unlimited reporting window, may cost up to 200% of the annual premium, and reinstates the policy's aggregate limits.
CGL Form Structure: Occurrence vs. Claims-Made, Retroactive Dates & ERPs
Exam Focus: The New York Series 17-70 exam tests your ability to distinguish between the two primary commercial liability coverage triggers—Occurrence versus Claims-Made—and understand the strict rules governing Retroactive Dates, potential coverage gaps, and the deadlines and terms of Extended Reporting Periods (ERPs).
The Commercial General Liability Architecture
Commercial enterprises face continuous exposure to civil liability arising from their day-to-day operations, premises, products, and completed operations. The standard industry form developed by the Insurance Services Office (ISO) to insure these risks is the Commercial General Liability (CGL) policy. ISO provides two primary coverage forms that share identical insuring agreements, exclusions, definitions, and limits, but differ fundamentally in their coverage trigger—the specific legal event that activates the policy to respond to a claim:
- Occurrence Form (CG 00 01): The traditional and most widely utilized commercial liability form.
- Claims-Made Form (CG 00 02): A specialized form designed primarily for risks with latent or long-tail liability potential.
┌─────────────────────────────────────────────────────────────────────────────┐
│ CGL COVERAGE TRIGGER MECHANISM │
├─────────────────────────────────────────────────────────────────────────────┤
│ OCCURRENCE FORM (CG 00 01): │
│ [Injury / Damage Occurs during Policy Term] ───► Claim Filed Anytime │
│ │
│ CLAIMS-MADE FORM (CG 00 02): │
│ [Injury / Damage on or after Retro Date] + [Claim First Made during Term] │
└─────────────────────────────────────────────────────────────────────────────┘
The Occurrence Coverage Trigger (CG 00 01)
Under the Occurrence Form (CG 00 01), coverage is triggered solely by the timing of the injury or damage:
- The bodily injury (BI) or property damage (PD) must occur during the policy period.
- The injury must be caused by an occurrence, which the policy defines as "an accident, including continuous or repeated exposure to substantially the same general harmful conditions."
- It is entirely irrelevant when the claim is formally communicated, when the injured party consults legal counsel, or when the lawsuit is served on the insured. Even if a lawsuit is initiated ten, twenty, or thirty years after the policy has expired, the insurer that had the policy in force on the exact date the injury occurred must defend the insured and pay any covered settlement or judgment up to policy limits.
Long-Tail Liability and Underwriting Challenges
The occurrence form's indefinite reporting horizon creates what underwriters refer to as long-tail liability. In cases involving environmental contamination, chemical exposure, asbestos, or hidden building structural defects, decades often elapse between the initial physical exposure and the manifestation of injury or filing of a lawsuit.
Because claims under occurrence policies can emerge years after policy expiration, insurers historically struggled to establish accurate loss reserves or set actuarially sound premiums. In response to unpredictable toxic tort and environmental liabilities during the liability insurance crises of the 1970s and 1980s, ISO introduced the claims-made form.
The Claims-Made Coverage Trigger (CG 00 02)
The Claims-Made Form (CG 00 02) resolves the long-tail uncertainty by linking coverage to the date the claim is formally asserted against the insured rather than when the injury occurred. To trigger coverage under an unendorsed claims-made policy, a loss must satisfy a two-prong test:
- Prong 1 (Timing of the Claim): The claim for damages must be first made against any insured during the policy period (or during an applicable Extended Reporting Period).
- Prong 2 (Timing of the Occurrence): The bodily injury or property damage must have taken place on or after the Retroactive Date stated in the policy Declarations and before the end of the policy period.
When Is a Claim "First Made"?
Under standard ISO policy provisions, a claim is deemed to have been "first made" when written notice of such claim or suit is received by any insured or by the insurer, whichever occurs first. If an insured receives a formal lawyer's demand letter on the last day of the policy term and notifies the insurer, the claim is validly triggered under that term.
| Feature | Occurrence Form (CG 00 01) | Claims-Made Form (CG 00 02) |
|---|---|---|
| Trigger Event | Bodily injury or property damage occurs | Claim is first made against the insured in writing |
| Timing of Injury | Must occur during policy period | Must occur on or after the Retroactive Date |
| Reporting Horizon | Indefinite; claims can be reported years later | Limited to policy period plus applicable ERPs |
| Primary Risk Scope | Standard commercial risks (retail, office, contractors) | High-hazard, long-tail risks (environmental, professional) |
| Underwriting Certainty | Low (carrier exposed to unknown future claims) | High (carrier closes policy year with definite claim tally) |
The Retroactive Date
The Retroactive Date is the single most critical structural element of a claims-made policy. Entered on the Declarations page, it establishes the historical boundary line for covered events.
- Pre-Retroactive Date Exclusion: Any bodily injury, property damage, or personal/advertising injury that occurred prior to the Retroactive Date is completely excluded, even if the claim is asserted against the insured during the current active policy term.
- Maintaining the Retroactive Date: When an insured renews a claims-made policy year after year, the retroactive date should remain the inception date of the very first claims-made policy ever issued to that insured. Preserving this original date ensures uninterrupted coverage for all past acts and occurrences that have not yet resulted in a claim.
- Advancing the Retroactive Date: If an underwriter advances the retroactive date to a later date (such as the renewal date), or if the insured switches carriers and the new carrier refuses to honor the prior retroactive date, an uninsured gap is created. Any occurrence that took place between the original retroactive date and the new advanced date will never be covered by the new policy, and cannot be submitted to the expired policy if no claim was asserted during its term.
Adjuster Warning: Whenever you encounter a claims-made policy during a coverage analysis, immediately verify the Declarations page for the Retroactive Date. If the date of the underlying accident precedes the Retroactive Date by even a single day, there is no coverage under that policy.
Extended Reporting Periods (ERPs / Tail Coverage)
When a claims-made policy is cancelled, non-renewed, replaced with an occurrence form, or renewed with an advanced retroactive date, the insured loses coverage for past occurrences that have not yet matured into formal claims. To prevent catastrophic uninsured losses, claims-made policies provide mechanisms known as Extended Reporting Periods (ERPs), commonly called tail coverage.
An ERP does not extend the policy period, nor does it provide coverage for new injuries occurring after the policy has terminated. Instead, an ERP simply extends the deadline for reporting claims that arise out of occurrences that took place between the Retroactive Date and the policy expiration date.
┌─────────────────────────────────────────────────────────────────────────────┐
│ EXTENDED REPORTING PERIODS (ERPs) │
├─────────────────────────────────────────────────────────────────────────────┤
│ BASIC ERP (BERP) - Automatic, No Added Cost: │
│ ├── Mini-Tail: 60 days for ANY claim (known or unknown occurrence) │
│ └── Midi-Tail: 5 years for claims where occurrence was reported in 60 days │
│ │
│ SUPPLEMENTAL ERP (SERP / 'Maxi-Tail') - Optional Endorsement: │
│ ├── Request in writing within 60 days of expiration │
│ ├── Unlimited duration (lifetime reporting window) │
│ ├── Additional premium up to 200% of annual policy premium │
│ └── Reinstates General and Products-Completed Operations Aggregate limits │
└─────────────────────────────────────────────────────────────────────────────┘
1. Basic Extended Reporting Period (BERP)
The Basic Extended Reporting Period (BERP) is provided automatically under the CGL form without the need for an endorsement and at no additional premium. The BERP includes two distinct operational timeframes:
- The Mini-Tail (60-Day Window): Automatically provides a 60-day period immediately following policy cancellation or non-renewal during which the insured can report any claim first made against them, regardless of whether the underlying occurrence was previously known or reported to the insurer.
- The Midi-Tail (5-Year Window): Provides a 5-year reporting period for claims resulting from occurrences that the insured reported to the insurer in writing within 60 days after the policy ended. If an insured notifies the carrier of a potential accident during the initial 60-day window, a formal lawsuit arising from that accident filed up to 5 years later will be covered.
2. Supplemental Extended Reporting Period (SERP / "Maxi-Tail")
If an insured desires complete, permanent protection against future claims arising from past acts, they must purchase the Supplemental Extended Reporting Period (SERP) endorsement (often termed the Maxi-Tail). Key statutory and contractual features of the SERP include:
- Written Request Deadline: The first named insured must request the SERP in writing within 60 days following the end of the policy period.
- Unlimited Duration: The SERP takes effect after the BERP expires and provides an unlimited (lifetime) duration for reporting claims arising from covered occurrences between the retroactive date and policy termination.
- Premium Cap: The insurer may charge an additional premium for the SERP, but ISO rules cap this charge at a maximum of 200% of the annual policy premium.
- Non-Cancellable: Once the premium is paid, the SERP is fully earned and cannot be cancelled by either the insurer or the insured.
- Reinstatement of Aggregate Limits: A major exam-tested feature: under ISO rules, the purchase of a SERP reinstates the policy's aggregate limits (both the General Aggregate and Products-Completed Operations Aggregate) for claims reported during the supplemental reporting period.
Which of the following scenarios correctly demonstrates the application of the coverage trigger under an ISO Commercial General Liability Occurrence Form (CG 00 01)?
When an insurer issues a renewal Claims-Made CGL policy and advances the Retroactive Date from January 1, 2020, to January 1, 2024, what is the direct legal consequence for the insured?
Under the ISO Claims-Made CGL policy provisions, which statement accurately describes the characteristics and requirements of the Supplemental Extended Reporting Period (SERP)?