Commercial General Liability: Occurrence vs. Claims-Made Policy Triggers & Tail Coverage

In commercial casualty underwriting, the coverage trigger defines the precise factual and legal circumstances that activate an insurance company’s contractual duty to defend and indemnify an enterprise against third-party lawsuits. Standard commercial casualty forms published by the Insurance Services Office (ISO) bifurcate liability into two fundamentally distinct legal mechanisms: Occurrence Coverage (ISO CG 00 01) and Claims-Made Coverage (ISO CG 00 02). Selecting the wrong policy trigger, failing to preserve a Retroactive Date during carrier transitions, or mismanaging Extended Reporting Periods (Tail Coverage) can leave corporate entities completely vulnerable to catastrophic uninsurable judgments.

1. The Mechanics of the Occurrence Policy Trigger (ISO CG 00 01)

Under the standard ISO CG 00 01 Occurrence form, the insurance carrier on the risk at the exact moment the bodily injury or property damage physically occurs is obligated to defend and indemnify the insured:

• The Date of Injury Controls: If a commercial plumbing contractor installs defective piping in 2024, and the pipe bursts causing $2,000,000 in water damage to an office building in 2026, the 2026 Occurrence policy is triggered—not the 2024 policy when the work was completed.
• Perpetual Runoff Security: The insured retains permanent defense and indemnification rights under that policy year’s limits forever. Even if the plumbing business dissolves or cancels its insurance in 2027, any lawsuit brought years later regarding the 2026 occurrence remains 100% covered.
• Continuous Injury & Exposure Theories: In latent toxic torts, asbestos litigation, or environmental chemical leaching, courts apply "continuous trigger" or "triple trigger" theories, activating every single occurrence policy in effect from initial exposure through manifestation.

2. Quantitative Trigger Comparison Matrix: Occurrence vs. Claims-Made

The table below compares legal responsibilities, pricing trajectories, tail liabilities, and risk exposures across both policy trigger frameworks.

Evaluation Dimension	Occurrence Form (ISO CG 00 01)	Claims-Made Form (ISO CG 00 02)	Risk Management Implication
Trigger Event	Physical injury or damage occurs	Claim is first made & reported in term	Occurrence protects against delayed lawsuits
Pricing Structure	Level mature premium from Year 1	Discounted Year 1; steps up over 5 yrs	Claims-made reaches "mature rate" at Year 5
Retroactive Date	None (Not Applicable)	Mandatory declaration line item	Advancing retro date creates uninsured gaps
Tail Coverage (ERP)	Never required upon cancellation	Mandatory if cancelled or non-renewed	SERP costs 150%–300% of expiring premium
Primary Lines of Use	CGL, Commercial Auto, Umbrella	E&O, D&O, Cyber, Environmental, Med-Mal	Specialty lines require claims-made mechanics

3. Deep-Dive: Extended Reporting Periods (Tail Coverage Architecture)

When an enterprise transitions away from a claims-made policy—whether through acquisition, corporate dissolution, or moving to an occurrence carrier—managing the reporting tail is critical:

• Basic Extended Reporting Period (BERP): ISO forms automatically provide a mini-tail granting 60 days post-cancellation to report claims arising from prior acts. Some forms include a 5-year window for incidents formally reported to the insurer prior to cancellation.
• Supplemental Extended Reporting Period (SERP): If the business closes or switches carriers without retroactive date continuity, it must exercise its contractual right to purchase a SERP within 30 to 60 days of cancellation. A SERP permanently extends the window to report future claims for pre-cancellation wrongful acts.
• Laser Endorsements & Prior Acts Carve-Outs: Watch out for insurer-drafted "laser endorsements" that carve out specific prior projects, high-risk product lines, or known claims history while leaving the rest of the retroactive date intact.

4. Notice Requirements & Potential Claim Reporting Pitfalls

Claims-made contracts enforce strictly construed notice provisions. Under modern case law, missing notice deadlines forfeits coverage automatically, even if the insurer suffered zero prejudice:

1. "Claims Made and Reported" Strictness: Under a pure claims-made-and-reported policy, a lawsuit served on the insured on the final day of the policy term must be reported to the carrier prior to policy expiration, or coverage is legally voided.
2. Notice of Circumstance: Most forms include a provision permitting the insured to give written notice of a specific wrongful act or occurrence that could reasonably give rise to a future claim. If properly filed, any lawsuit that manifests years later is deemed to have been made in the policy year notice was given.
3. Formal Lawsuit Definition: Claims are defined broadly as any written demand for monetary damages, civil lawsuit, arbitration proceeding, or formal regulatory investigation. Never treat an attorney demand letter as an informal dispute that can be addressed without insurer notification.

5. Five-Step Policy Trigger Governance Protocol

Corporate counsel and risk managers should execute this five-step checklist during every casualty renewal:

1. Audit Policy Trigger Designations on Every Declarations Page: Verify whether each casualty policy operates on an Occurrence or Claims-Made trigger.
2. Verify Retroactive Date Continuity: Ensure renewal binders display your firm’s original incorporation date or original retroactive date with zero advancement.
3. Review Merger & Acquisition Indemnity: In corporate acquisitions, ensure the seller purchases a dedicated 6-year multi-line D&O and E&O runoff tail policy.
4. Establish Centralized Claim Intake Procedures: Require that all cease-and-desist letters, customer demand notices, and legal summonses be routed to risk management within 24 hours.
5. Coordinate Occurrence Umbrella Attachment: When pairing a claims-made primary policy with an occurrence umbrella, ensure an appropriate concurrency endorsement is executed to prevent vertical coverage misalignment.