8.3 Occurrence vs. Claims-Made Triggers

The Two Coverage Triggers

A liability policy must decide which event 'turns on' coverage. There are two triggers, and confusing them is one of the most common exam errors.

The standard ISO Commercial General Liability (CGL) CG 00 01 is an occurrence form. The parallel CG 00 02 is the claims-made version. Most professional liability lines — errors and omissions (E&O), directors and officers (D&O), and medical malpractice — are written claims-made because of long-tail exposure.

How Occurrence Coverage Works

An occurrence policy responds if the bodily injury or property damage takes place during the policy period, no matter when the claim surfaces. A roofer who causes a leak in 2024 is covered by the 2024 occurrence policy even if the homeowner sues in 2029.

This is ideal for long-tail exposures where harm shows up years later, but it creates the 'long-tail' problem for insurers, who must hold reserves for decades. It also creates stacking potential: a continuing injury spanning several policy years may trigger multiple policies' limits.

Trap: On an occurrence form, the date the claim is REPORTED does not matter. Only the date the injury HAPPENED matters.

How Claims-Made Coverage Works

A claims-made policy responds only if the claim is first made against the insured during the policy period (or an extended reporting period) and the injury occurred on or after the retroactive date.

• Retroactive date — the floor for covered injury. Injury before the retro date is never covered, regardless of when reported. As a policy renews year after year, keeping the original retro date preserves coverage for past acts.
• Extended Reporting Period (ERP / 'tail') — allows reporting of qualifying claims after the policy ends:
  • Basic ERP — automatic, limited time (often 60 days for any claim, longer for claims arising from reported circumstances), no extra charge.
  • Supplemental ERP — purchased (the 'tail'), extends reporting indefinitely or for a long period.

Trap: Claims-made requires BOTH a claim during the period AND injury on/after the retro date. Failing either condition means no coverage.

Worked Example — Comparing Triggers

A physician's medical-malpractice claims-made policy has a retroactive date of 1/1/2022 and runs 1/1/2025–12/31/2025.

• Alleged malpractice occurred 6/1/2023, claim filed 3/1/2025 → COVERED: injury is after the retro date and the claim was made during the period.
• Alleged malpractice occurred 5/1/2021, claim filed 3/1/2025 → NOT COVERED: injury predates the 1/1/2022 retro date.
• Alleged malpractice occurred 6/1/2025, claim filed 2/1/2026 (no ERP purchased) → NOT COVERED under this policy: the claim was not made during the period and no tail was bought.

Now apply an occurrence policy to the same facts: malpractice on 6/1/2023 is covered by the policy in force on 6/1/2023, whenever the claim is later filed.

Why Claims-Made Forms Exist

Insurers developed claims-made coverage to control the long-tail problem that plagues occurrence policies in lines like medical malpractice, where injury may not surface for years. By tying coverage to the report date, the insurer can price each year using current loss data rather than guessing about claims that might emerge decades later. The tradeoff is administrative complexity and the need for tail coverage when an insured retires or switches carriers.

A claims-made program typically moves through maturity steps in its first few years. A first-year (immature) claims-made policy is cheap because the retro date equals the inception date — little prior exposure is covered. As the retro date stays fixed across renewals, the policy becomes mature (usually by year five), covering a wider window of prior acts, and the premium rises toward the occurrence-equivalent level.

Switching Carriers: Tail vs. Nose Coverage

When a claims-made insured changes insurers, a gap can open between the old policy's expiration and a claim's later report. Two solutions exist:

Buying nose coverage from the new insurer is often cheaper than buying a tail from the old one, but both achieve continuous protection.

Trap: An insured who lets a claims-made policy lapse with NO tail and NO prior-acts coverage on a new policy has a coverage gap — claims for past acts reported after the lapse fall through the cracks. Exam questions love this scenario.

Reporting Provisions and 'Awareness'

Many claims-made policies include a notice of circumstances or awareness provision: if the insured reports facts that might give rise to a claim during the policy period, a later claim arising from those facts is deemed made during the period — even after the policy ends. This protects insureds who spot trouble early.

The interplay of three dates governs every claims-made decision:

1. Retroactive date — earliest covered injury/act.
2. Policy period — the window in which a claim must be first made (or circumstances reported).
3. Extended Reporting Period — the tail that lengthens the reporting window after expiration.

Trap: A claim 'first made' includes a claim deemed made under an awareness provision. Reporting circumstances in time can pull an otherwise-late claim back into coverage.